AmigaOS 4.1FE Update 3 - Bugs and Experience Report

So thought I would have post my results about Update 3. I was hopeful for Update 3 after Update 2 introduced an interrupt issue on my X1000 hardware setup. However, it's almost made my machine worse now, which was unexpected. I disabled vertical blanking interrupts to work around the screen opening freeze issue I have. But now I have USB issues.

First there is a longer delay in the USB boot drivers picking up keyboard and mouse. I had just figured out what wait ticks I need so the early startup detector picks up my mouse. Only to find after installing Update 3 the new drivers take longer to pickup my mouse and I can no longer get into the early startup menu! I thought scroll lock was assigned to Help but I cannot get it detected from keyboard either. Though using a generic Esc key would make sense for a lot of these quick key menus. I have to pull my mouse out of it's home spot and plug it into the front USB port of my X1000. For whatever reason, only the right USB port works, so with mouse plugged in and cable hanging out I cannot plug in USB sticks to my front port.

Then, once OS4 is booted, all is fine until I plug a USB stick in. Or I leave one in the USB port. The USB drivers then cause the Workbench to freeze for about 20 seconds and then give up and cannot mount the stick. To be exact it is only USB2 EHCI. Sticks can work with OHCI or UHCI through a hub. Unlike on my XE years away when EHCI was introduced, there is no freeze or crash in the driver thankfully, so at least that is stable. But somehow I have an unusable system with USB devices. I'm used to plugging in a USB stick and transferring data. But now I have to avoid it or plug it through an older hub and use slower transfer speeds. This is an annoying step backward. For the most part, Update 3 brings AmigaOS4 forward, but unfortunately for me, it crippled my system. I'm avoiding the typical work around of copying over older USB drivers and other modules, since it isn't the right to pollute the system with crossed components, and the right solution is for compatible fixed modules. In the meantime I'm hoping the issues will be resolved and a hot fix will be on it's way.

@Hypex

Debugging never worked on the X5000... there was a bug in the X5000's kernel since day one.

Update 3 claimed that the X5000's kernel was finally fixed.