Welcome, Guest. Please login or register.
Amiga Kit Amiga Store Hollywood MAL AMIStore App Store A600 Memory

AuthorTopic: Kickstart 3.1.4 crashing issue A4000D  (Read 1074 times)

0 Members and 2 Guests are viewing this topic.

Offline arttu80

Kickstart 3.1.4 crashing issue A4000D
« on: February 09, 2019, 11:42:39 AM »
If somebody can help me with this one..

I have installed new Kickstart ROM upgrade in my A4000D / A3640 setup, which work otherwise fine, but throws me random "software failure program failed" windows. I noticed that this happens only after SetPatch command is loaded (the one which came with 3.1.4 disks). I have used clean install, so there is no "clutter" in my SYS: partition. Could this be from wrong mmu or 68040 library? I tried mmu version 43 and 46 with no luck. Also tried 68040.library version 37 and 46. My old 3.1 setup had worked without this problem.
 

Offline kolla

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #1 on: February 09, 2019, 12:01:56 PM »
3.1.4 should work with the included 68040.library, your system is the primary 040 system by Commodore, and the reason why 68040.library was made in the first place.
B5D6A1D019D5D45BCC56F4782AC220D8B3E2A6CC
 

Offline NinjaCyborg

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #2 on: February 09, 2019, 01:46:29 PM »
is it intermittent? maybe something is loose connection inside.
 

Offline Thomas Richter

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #3 on: February 09, 2019, 03:12:47 PM »
I have installed new Kickstart ROM upgrade in my A4000D / A3640 setup, which work otherwise fine, but throws me random "software failure program failed" windows. I noticed that this happens only after SetPatch command is loaded (the one which came with 3.1.4 disks). I have used clean install, so there is no "clutter" in my SYS: partition.
If you made a clean install, then the CPU command in the startup-sequence should give you an error that no CPU library was installed. Note that 3.1.4 does not come with a CPU library. Did you install one? If so, which one? If this is from the MuLib package, please post the output of ShowConfig here, along with the output of MuScan (part of the same package) and your MMU-Configuration file (if you have one), you find this in ENVARC:

If you see a "random" failure, please - which failure is it?

Offline arttu80

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #4 on: February 09, 2019, 07:14:16 PM »
Libraries I've tried are mentioned in first post. So if I leave Setpatch command in startup-sequence, machine will throw me software failure window before it goes to workbench screen, in other words I cannot get in WB without disabling setpatch command. To be exact, I get "software failure program failed (error #8000000B) C:AddDataTypes". Sometimes I got in WB and got error message while starting some other application, for example error #80000004.. Very confusing. Can this be related to bad RAM or CF card somehow? But to think of it, it worked fine with 3.1..
 

Offline goldfish

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #5 on: February 09, 2019, 08:48:03 PM »
HI

Have you tried this lib

http://aminet.net/util/libs/MMULib.lha

I crash issue with my Mediator and ACA1233n before I tried this.
 

Offline Thomas Richter

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #6 on: February 09, 2019, 08:48:57 PM »
Libraries I've tried are mentioned in first post.
Please provide the version numbers. I am sorry to be so persistent, but I cannot read your mind. You need to provide more information. In particular the information I requested above.

So if I leave Setpatch command in startup-sequence, machine will throw me software failure window before it goes to workbench screen, in other words I cannot get in WB without disabling setpatch command. To be exact, I get "software failure program failed (error #8000000B) C:AddDataTypes".
Which datatypes do you have installed? In particular, do you have the SVX datatype installed? If so, please remove it. It does not work correctly and will cause such types of problems. 0x80...B is a "line F" exception, which could mean that the 68040.library *is not* loaded. Please use a tool like Xoper to determine whether it is actually running. What does "CPU Checkinstall" tell if you run it from the command line?
 

Offline arttu80

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #7 on: February 13, 2019, 07:07:20 PM »
Sorry for taking so long answering, but job and familylife kept busy.
The 68040.library versions I tried was 46.3 and 37.10. Also mmu.library 46.14 and 43.13 were tried. And I don't have this SVX datatype installed. I mean it's stock 3.1.4 install without any other modifications except those libraries I mentioned.

I see some other guy is struggling with same kind of problem..

http://forum.hyperion-entertainment.com/viewtopic.php?f=15&t=4243

I would be more than glad to know if there is workaround.
 

Offline Thomas Richter

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #8 on: February 13, 2019, 08:12:24 PM »
Please boot with disabled caches, and install the 46.3 release of the 68040.library. Then please run "ShowConfig" and post the output here. Then also run "MuScan" from the MMULib archive, and also post the output here.

It seems that some part of the host memory of your system does not support bursting (probably?). If so, one can, in principle, disable the caches for the affected memory selectively, but for that, we first have to find out what is in this system.

For me, this looks like a hardware issue at this point.
 
 

Offline arttu80

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #9 on: February 13, 2019, 09:30:04 PM »
MuScan report after running SetPatch NoCache command;



ShowConfig;



Is it of any help? Do I have some ChipRam issue (I see this Cache Inhibit Imprecise NonSerial message)?
« Last Edit: February 13, 2019, 09:42:54 PM by arttu80 »
 

Offline Thomas Richter

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #10 on: February 14, 2019, 06:26:16 AM »
Everything is configured correctly here, including the chip ram - cacheinhibit imprecise is the right cache mode for it. But if you see issues with caching enabled, I suggest replacing the ZorRAM board (this is the board with the 256MB, right?). You can of course disable caching there to prevent the issue, but this will be a speed-brake.

Hence: Remove the ZorROM, see whether the system runs then stable, and check for another RAM expansion if you can.
 

Offline arttu80

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #11 on: February 14, 2019, 11:47:01 AM »
Thank you for reply, but the thing is, I already tried to run Amiga without ZorRam and even removed fast ram simms after that. No improvement. Even tried switching simm for chipram.. As a side note my RTC isn't keeping up time, can it somehow mess with cpu hardware? Amiga had some battery leakage when I got it. Just guessing.
 

Offline Thomas Richter

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #12 on: February 14, 2019, 03:11:43 PM »
Thank you for reply, but the thing is, I already tried to run Amiga without ZorRam and even removed fast ram simms after that. No improvement. Even tried switching simm for chipram.. As a side note my RTC isn't keeping up time, can it somehow mess with cpu hardware? Amiga had some battery leakage when I got it. Just guessing.
If the issue continues even with only ChipRam present, then there is a defect in the chip ram. That's really all I can say. Try to get the board repaired - the battery might have made some damage.
 

Offline arttu80

Re: Kickstart 3.1.4 crashing issue A4000D
« Reply #13 on: February 14, 2019, 08:28:08 PM »
Okay, I will take motherboard out someday and go trace by trace probing, as I made some jumper wire repairs previously, maybe I missed something. I thank you for logical explanations and mental support on this! Will post when some progress is made, but for now it seems problem is outside of 3.1.4 upgrade, which is obviosly good considering the work that went into it.



edit:

moved this to HW Issues;

https://forum.amiga.org/index.php?topic=73970.msg842658#new
« Last Edit: February 27, 2019, 07:27:06 PM by arttu80 »