AmigaOS 4.1 Update 3 Borked My X5K 2.2 Enhanced Boot Drive

** for now I kept an older emergency Sata HDD handy in my computer just not connected with an older bootable system. Was for Radeon 7750 so I went back to that card for now and she boots so I know the X5K is OK at least. Means later one day I will start over making my X5K more what I want it to be again. The old drive was just that, a emergency bootable drive. **

Guessing this is where having a bootable USB emergency stick with newer Radeon RX580 drivers would have come in handy (nope I did not have one yet) but went ahead and tried to install the Amiga OS 4.1 Update 3 today and it hung at 100% done at the end, with it stuck on some backdrop.png and no Next button ever being clickable and the rest of workbench frozen.

I let it stay like this a bit in case it was slowly doing something but after a bit rebooted. Unfortunately I now hang at boot.

Appears I can't upload here and attach a picture here but what I get is the normal X5K boot screen and then after loading finishes this error and it hangs.

About to call loader entry at 0x7BD02020

never changes.

My X5K is a dual boot with 2 video cards. An RX580 for the Amiga OS and a Radeon 1950 for the MorphOS.

The good news is MorphOS still works. haha

Anyway, any tips other than swapping my old Radeon 7000 based video card back in and start the older bootable stick (I think I have one someplace). Would hate to have to go back to the old video card just to install the OS again.

Yes my Amiga OS X5K was a Hyperion Amiga OS 4.1u2 and Enhanced 2.2 as well so guessing the 2 are not happy now. haha

I did just email AmigaKit asking if they sell a bootable stick I can buy that will work for the newer video drivers but I emailed them the same last year and never heard back so trying again.

Bummer.

TJ

** Edit.. added this video link.

https://youtu.be/x8lrnPe_ZlM

@AmigaSociety

Salut, je n'ai pas d'idée concernant ton problem, mais j'ai toujours un disque de secours au cas où comme juste avant pour savoir pourquoi Candi est cassée!

Et oui Candi is cassée mais j'ai presque trouvé le coupable.

@AmigaSociety

try to load without WBStartup, IIRC is hile bootlader press left Amiga (or shift) and see if WB shows up.
If it loads fine the is something in your WBStartup that makes system crash/fail.

@jabirulo

As I don't have a keyboard with Amiga keys I tried holding down the left Shift (just that key) at boot.

No difference.

I get the same About to call loader entry at 0x7BD02020 during the boot process.

TJ

Folks, here is a boot video of what happens now.

Maybe this will help?

TJ

https://youtu.be/x8lrnPe_ZlM

@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.

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.

https://forum.amiga.org/index.php?topic=75005.30

TJ

@AmigaSociety

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!

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.

TJ

@graff

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.

tj

@AmigaSociety

You are not alone : I am also getting a black screen after updating from the archive downloaded from Hyperion website (and not through AmiUpdate).

I lost one week to get my backup back since it was on SFS2 partition (which is not recognized by the x5000 PreRelease CD, which is the only thing I had to boot from...)

Serial output is the following :


(Booting default)
Booting configuration AOS4.1FEupd2 SSD DH0/NGFS
Loading finished [########################################] 100 %
About to call loader entry at 0x7BD02020
Loader warning: Module kernel alignment 4060020736 > 32
Loader warning: Module kernel alignment 12288 > 32
Loader warning: Module dos.library.kmod alignment 1937012066 > 32
Loader warning: Module dos.library.kmod alignment 1702252129 > 32
Loader warning: Module dos.library.kmod alignment 1919508844 > 32
Loader warning: Module dos.library.kmod alignment 1346978816 > 32
Loader warning: Module elf.library.kmod alignment 1952407922 > 32
Loader warning: Module elf.library.kmod alignment 1869750309 > 32
Loader warning: Module elf.library.kmod alignment 628099584 > 32
Loader warning: Module elf.library.kmod alignment 1768842272 > 32
Loader warning: Module graphics.library.kmod alignment 17737462 > 32
Loader warning: Module graphics.library.kmod alignment 4069543672 > 32
Loader warning: Module graphics.library.kmod alignment 4059582200 > 32
Loader warning: Module graphics.library.kmod alignment 4046475000 > 32
Loader warning: Module graphics.library.kmod alignment 4037562104 > 32
Loader warning: Module graphics.library.kmod alignment 4026552056 > 32
Loader warning: Module graphics.library.kmod alignment 4016066296 > 32
Loader warning: Module graphics.library.kmod alignment 4005580536 > 32
Loader warning: Module graphics.library.kmod alignment 3996929784 > 32
Loader warning: Module graphics.library.kmod alignment 3987492600 > 32
Loader warning: Module graphics.library.kmod alignment 3977268984 > 32
Loader warning: Module graphics.library.kmod alignment 3966783224 > 32
Loader warning: Module usbsys.device alignment 627860521 > 32
Loader warning: Module usbsys.device alignment 544566889 > 32
Loader warning: Module usbsys.device alignment 1667329132 > 32
Loader warning: Module bootmouse.usbfd alignment 3043941 > 32

@Lio

So sorry to hear.

I think so far I count 3 that have had no boot after install.

No idea on how many have updated but never fun to have issues with no boot.

TJ

@AmigaSociety

Seems to be only X5000 issue?

Can we confirm this issue has only impacted people that have downloaded the update from Hyperion and tried to manually install (vs using the AmiUpdate tool)?

It would be good to narrow it down to 1) specifically X5000, and 2) upgrades that were done without using AmiUpdate

I downloaded the update direct from HYperion and installed it after unpacking on my X5040 enhanced and had no problems booting, I did encounter crrashing of Netsurf which Chris rectified very quickly, but all my disks were accessible without any issues. I have since noticed several programs no longer work however, i.e. ScummFM and Timberwolf. i get GR's from them now.

@AmigaSociety

Quote:

This is exactly the same behaviour we've experienced with my colleague when I was helping him out with Update 3 install on his X5000 (as described in this thread AmigaOS 4.1FE Update 3 - Bugs and Experience Report).


@cloverskull

Quote:

This is exactly the way we've proceed - downloaded the update package from Hyperion website, unpacked and run the install manually.

Just a guess based on the errors but could it be that the Update contains an updated bootloader (amigaboot or whatever is used on X5000) that needs to replace the one you boot with but it's not done if you have a boot partition or separate system partition or some other specific setup? The alignment values look completely wrong so looks if it gets an unexpected format for the data it is looking for and that data is supplied by the boot loader. Or because the boot loader uses the firmware to allocate memory and load files it could be an X5000 U-Boot issue too. Do you have the latest firmware?

@balaton

makes sense but I only have what my dealer sent me after I bought it

it is the latest publicly available (to my knowledge) and called cyrus_5020_uboot_08032018.img

like Djk83, the installation proceed to 100% but the GUI was stuck, all check boxes were greyed, so I waited a few minutes, nothing happened so I restarted and then black screen !