AmigaOS 4.1FE Update 3 - Bugs and Experience Report

@Boabster

Thanks for det update

Update...

I had to update NetSurf and Snoopy ...

NetSurf 3.12 Dev CI #6994 working fine.

Snoopy 54.127 working fine.


Otherwise, my only casualities are AmiDVD, Imagine and Real3D.

Imagine would launch ok for Update 2 but window was too big for the screen.
Imagine does not launch after Update 3.

Real3D has crashed during launch ever since I installed AmigaOS 4.1 FE, so I think it is a lost cause.

So, I think Imagine and Real3D are toast.

AmiDVD 1.53 (06/03/2022) from A-EON Enhancer Software 2.2 was working just fine on Update 2 and quit working after Update 3.

I hope we can get a working version of AmiDVD soon, because it has been my main backup tool for many years (and many versions of AmiDVD).

Cheers,
redfox

Update:

The problem with me not being able to access Update 3 is now resolved. I have now been able to access it via the website and I have now downloaded it. Will test it out tonight

Not deep testing but it feels fast and steady. Pegasos2, no random Grims
/bugging any more.

Using it is as Amiga should be, everything flows well, finally. Remarkable better.

Thanks for all involved :)


Missing AmiDVD as many, but most likely it will come back. No other victims atm here.

@Mr_byte

Great to hear that you got it sorted! Enjoy the update!

I had the worst experience with the Update 3: downloaded with Amiupdate for my X5000, installed and everything seemed to be alright, but after installation machine did not reboot automatically.

I performed hard reset, but after splash screen of X5000, when turning to AmigaOS 4.1 splash screen, I have grey screen and anything else happens, also after many other reboot.

I'm stucked and I fear I have to reinstall all the OS from the beginning

@AmigaOldskooler

Quote:

Thanks Looking good so far

@Kyle

Quote:

Thats strange.
I did not understand where exactly in the boot process it ends up with a gray screen, is it before or after the Aos4.1 splash screen?
I'm just asking because if it's right after amigaboot have loaded the kickstart it's generally a kickstart problem, if it's after the splash screen it's something else.


I think this might be a case when a serial cable is needed to see where it fails without guessing like crazy.

There's "never" a need to reinstall Aos unless the harddrive is broken so i'm sure we could get you going again if we figure out where it fails.

A separate thread might be needed here :)

It does seem to pause on boot for a little while, which it never used to do (Sam440EP here).

The only real issue I've come across so far is that ssh2-handler is significantly slower than it was under update 2.

Update...

One very pleasant surprise for me since Update 3 ...

Odyssey Web Browser v 1.23 r5 (Jan 01 2022) is performing very well on my ancient MicroA1 system.

With Update 2, I would often see "Failed to allocate" memory messages from Odyssey. Changing active connections from 16 to 8 helped but did not entirely eliminate the problem.

Since updating to AmigaOS 4.1 Final Edition Update 3 this issue seems to be resolved.

No dancing bananas yet, but I am very happy to be able to use Odyssey again.

The new alpha version of Odyssey freezes up on my system, probably because I do not have enough RAM available.

Cheers,
redfox

@Kyle

Quote:
Together with my colleague we've been unfortunate to share your experience when trying to apply Update3 on his AmigaOne X5000. The update seemed to be progressing well up to 100%. Then it stopped on 100% and several minutes passed, but nothing seemed to be happening. Eventually we've chosen to restart the machine, after which the grey screen welcomed us.

@smf

Quote:
It happens before AOS4.1 splash screen so it looks like a Kickstart problem, according to what you've mentioned. Do you possibly have any ideas on how we could narrow down the issue to find the problem?

Personally, I had more luck as on my Sam460LE the update (through AmiUpdate) went smooth. The only inconvenience was that after the first reboot I had AmigaDOS window opened instead of Workbench and I had to restart the OS again.

I got the X5000 back on track by restoring a 3-year-old backup, but the RX570 doesn't work anymore. I'm probably missing something with the drivers; perhaps another driver that had priority should have been deleted? I don't remember...

Anyway, I'm using a 4670 now, and after restoring everything tomorrow, I'll try to do update 3 (I'll make a more recent backup first) with this graphics card. Let's see how it goes this time.

Update 3 installed on X5000, so far everything has been fine, except after the first reboot, when the system froze right at the workbench screen.
After a hard reset, everything was fine, and now I'm testing the system's stability.

The only thing I'm still missing is the Radeon RX570 installation. For that, I'll have to search for old threads, to try to figure out how to fix it.
I seem to recall that an older radeon driver needs to be deleted to allow the southern RXs to initialize properly

Quote:

same here, except that I updated from the file downloaded from Hyperion website...

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

After spending 1 week getting my backup back, I am posting this from my Update 2 partition, still fearing the install the next update...