Thanks for the update. I used AmiUpdate to complete the update. Network seems to be much improved.
The only casualties I have found so far are AmiDVD, NetSurf 3.11 and Snoopy.
- AmiDVD ... no GUI, no crash, no messages. - NetSurf .. Couldn't resolve host name message. - Snoopy ... This Snoopy ceases working at dos.library V54.116
I do keep a "when the shit hits the fan" bootable hdd with an older Amiga OS 4.1 Update 1 for cases like this so have resorted to at least getting a booting Amiga OS X5K again.
Of course this means trying to either dissect what went wrong and nit pick to see what is needed for the corrupt drive or just bite the bullet and start over, and since this drive I have been using for the last 2 to 3 years was setup with that older NGFS that I understand can have issues, a good time to start fresh with a different file system and rebuild a nicer X5K again with RX580 and all that later.
For now I am back to Radeon 7750 and that is where I stop for today and thanks to my emergency SHTF HDD I keep at all times.
I just need to get me a newer all in one USB for this next time.
For now I went ahead and slapped my old Radeon 7750 back in and boot from an emergency sata hdd I had with an older Radeon driver and Amiga OS 4.1 Update 1. She boots at least.
Plan is to start fresh though and when I can install a new SSD and will do updates 1,2, and 3, and then minimum enhancer this time for main important drivers only and see how that goes.
Then will explore a MorphOS dual boot again later as that is now not working since switching to the older drive.
Anyway, that error seems to be "i can't find a good OS to boot from" and switching to an emergency backup at least I know my X5K runs.
This next time I will explore making a new USB stick with newer drivers or buy one from AmigaKit should they ever get back to me.
Don't mind buying a nice AMiga logo stick if they have one all set.
I noticed a strange thing after installing AmigaOS 4.1 FE Update3 on my X5000... If I do soft reboot (Ctrl-Amiga-Amiga) all the backlit leds of my Ducky One keyboard blink three times during the WB is reloaded! Very spooky...
Is there a way to get rid of this peculiarity? I have never seen this before I installed Update3. I have switched all the backlit leds off from the keybord's own settings. Is this blinking somehow related to the changes made in the USB software?
BTW, this does not happen if I reboot with ctrl-alt-alt, or when I start my machine from the power button.
Without knowing for sure it could look like some file did not get updated, or was corrupted, from the crash during install.
It seems your boot breaks when the 2nd-level bootloader is trying to enter the "Kickstart ROM" it has read in from disk. So it must be related to the modules in the kickstart folder on the boot partition, or the KickLayout file contained within.
Do you have another Amiga to attach the harddrive to? Then you could perhaps cross-reference the Kickstart folder contents with that from the Update3 archive (and also the X5000-specific drawer within it) and copy over anything missing. And maybe update the Kicklayout file to ensure your RadeonRX.chip (i believe it is called) driver also in it at the same time.
But I believe you'll need another working AmigaOS which can access your HD to do it (or perhaps the MorphOS you still have booting - never tried it).
And, when you got it working, an idea would be to make a safety AmigaOS4 boot partition for fallback in cases like this :)
I hope you'll have a swift recovery from the problem!
My buddy Mikey found me some older threads of the exact error I get although these are pre Update 3 of course.
But same error.
Has me baffled it just started working days later after all sorts of card swaps and this and that.
No idea if this new Update 3 has anything to do with boot up issues but anyway, if ya wanna see that others have had this error, this may be an eye opener.
@AmigaSociety Looking at your video i can say that all the modules load up fine to the memory, then, kernel calls fine, and then something at very begining borks : looks like when amigaboot tried to find bootable partition.
As usual in this kind of issues, you need to find a way to grab serial output, but before raise debug level to at least 3 or 5.
I got the update this morning through AmiUpdate. I got an error the first time I booted after install and a black screen afterwards. Turned off came back a few hours later and it seems to be running fine now.