AmigaOS 4.1FE Update 3 - Bugs and Experience Report

@daveyw
For the test of it, could you try removing the bootkeyboard.usbfd from a new test section in kicklayout and boot with that?
Note you won't have keyboard support before the OS fully boots with that kicklayout, at which time the HID driver picks up your keyboard. I imagine the problem is between bootkeyboard.usbfd driver and your USB keyboard, and this will (to some extend) test that by disabling the driver.

Why clib4 should interfere with emotion? I don't think it is compiled with clib4..

@afxgroup

Yep, but just for having "clean" emotion and odyssey3 installations, better don't mix AV#? and SW#? they both have/use.

And (maybe I'm mistaken) if you use CLIB4 you can't mix with CLIB2 or NEWLIB libraries.

Odyssesy3 comes with "new" AV#? and SW#? libs inside its package and they don't seem to work with emotion that has its "own" AV#? and SW#? libs too.

On SAM460CR I lost my network configuration after Update3 - it seems the Wizard can't anymore find my network adapter.

I am about to ask info to Acube.

@MazinKaesar

You can try Internet Prefs and then in Interfaces see what interfaces you have and there change/reconfigure to suit your home network.

On my SAM460ex:

DEVS:Networks/ppc460ex_eth.device
Type: Ethernet
Unit: 0

[ x ] use static IP
IP: <your_IP>
Mask: 255.255.255.0

...

MTU: 2048 [ x ] Automatic

The network device in no more present in the list of the wizard, you can use the "folder" button to get the correct file and it is recognized and the connection is refreshed. But it does not work anyway.

Maybe it could be a bug of Update3 you can find only in SAM460CR/LE.

@MazinKaesar

I just checked on my Sam460LE, I don't have the problem.

I set my PubTest partition (the one I used to test the various beta versions of Update 3 up to the release) back to its initial state, i.e. with Update 2 and the other later small updates. Then I installed the publically released Update 3 (fetched from my account at Hyperion's page) and let it reboot, and the network came up with no problems.

Best regards,

Niels

It seems the issue is in AmiSSL version provided but I can't find any log to check.

@MazinKaesar

Update 3 installs AmiSSL 5.25 - I believe it is still the latest.

An installation log is not saved by the OS4 Installation Utility (unlike what you can choose to do with the Installer).

Edit: BTW, I would be very surprised if AmiSSL had anything to do with the network driver working or not.

Best regards,

Niels

* I restored a backup with the pre-update3 installation -> Internet connection is fine
* I applied update3 again -> Internet connection is KO

At least, the issue is reproducible at will.

@daveyw

Looks like Update 3 can mess up with USB.

Feel free to look at my post in the other thread (which also is a follow up on this post). I described issue with USB after applying Update 3 on X5000 and how it was resolved.

@smf

Quote:

As @smf mentioned in the quoted fragment, grey screen occurring between the U-Boot and AmigaOS splash screen indicates a problem with Kickstart. Obviously, grey screen is not very informative, and connecting through a serial cable may be a bit of a hassle for somebody who didn't do it before. Being a Sam owner, I have little experience with X5000, but still I have a small observation that I somehow hope could be helpful.

When supporting my colleague in restoring his X5000 back to life after Update 3, accidentally I've made a typo in the Kicklayout file in the bootable pendrive I've created. This resulted in a strange behaviour and also a grey screen - even after we've reinstalled AmigaOS from scratch. Of course the problem here was that because of that typo, one of the files from the Kickstart wouldn't load and at the same time it tried to load the mistyped file that did not exist at all.

How did I learn about it? I have entered the boot menu, selected Boot from Hard Disk option, and then triggered boot procedure by typing "boota" in the command line. This way I could see some useful information during Kickstart loading, in particular the message about the missing file. Much more helpful than simply a grey screen. Now I wish I knew that before we decided to format the SYS partition.

My point is, maybe someone who still hasn't resolved this issue, could try this approach and see if it brings anything to the table.

@Djk83

Create and restore a backup of AmigaOS4 is easy.

I simply created a drawer on another disk different then SYS: and copied all the SYS: contents here.

As I applied Update3 and I found some issues, I rebooted with OS4 install CD, run directory opus, deleted all files and drawers in SYS: and copied there the backup.

@MazinKaesar

Thank you for the hint! It will certainly be very helpful at some point in future!

@AlfredOneQuote:

1.277

@graffQuote:

I'll give it a try.

@Djk83Quote:

Yes, I had seen your message, that was my clue that USB might be the problem. But I don't think I saw a resolution? Was it removing Candi? I don't use it.

But what's really unusual is that this didn't happen right after I installed update 3. It happened weeks later.

@daveyw

I was referring this part:

Quote:

So in our case, the solution to the USB problem was to go into U-Boot command line and run "usb reset" command.

I tried again to update, using AmiUpdate this time instead of the archive from Hyperion website -> still no go and here is the screenshot after installation, which never reach the end...

@daveyw
Quote:WTF!? Pirate copies of SFS, or of any other of my AmigaOS software, distributed by Hyperion without permission, aren't supposed to work at all.
According to https://www.amisphere.com/updater/ the current public version of SFS is version 1.293.
Even the last public versions of my AmigaOS 4.x port of SFS on AmiNet, OS4Depot.net (and my own SFS homepage at that time, but deleted since several years), before A-EOn got an exclusive licence for it for their Enhancer Software, were version 1.279.