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.

@FlynnTheAvatar

I wasn't aware GDB debugging failed because of a kernel issue. What I know about it is it hadn't been updated to work on newer CPUs. I don't recall if it worked on the Sam series but it never worked on my X1000 and I only know of it working on my G3/G4 XE.

So if Update 3 was meant to fix GDB so step debugging worked, on any other platform, that would be welcome. There may be a reason it didn't if it's kernel related, as the kernel is now handled by a different team since Trevor bought it out, so will not always contain the latest kernel release in the Hyperion produced updates.

Update 3 installed here on X1000 using the ESP beta components.

CANDI is broken - GR at test command from prefs.
USB seems to work fine from within Workbench.

Hi Everyone!

Okay, some more to report. First, my machine still hangs on boot sometimes like Hypex describes. It definitely is the USB and this needs to be fixed. I tried putting the old keyboard bootkeyboard.usbfd from Update 2, but that did not fix the problem. I still had to replace the bootmouse.usbfd back to Update 2 or my A-Eon Logitech Boing mouse does not work.

On the update from programs running side, AmigaAmp plugin BlueShift 1.1 and Widespectrum 1.3.2 freeze up after a while of music playing. What is funny is that the 68k version of Widespectrum runs fine indefinitely and so do the other 68k plugins. I like to let Christmas music play on my AmigaOne 500/Sam 460 24 hours a day so I was able to test those plugins for extended times.

On a side note, I have bought the A1222+ and another Sam 460 board, neither of them are assembled since I am waiting for this original AmigaOne500/Sam 460 to die. I have had it on 24 hours a day for almost 13 years. I only replace power supply from time to time and the hard drives once. Even the original cards are working fine. I am afraid to update the original Uboot that I might brick it so I haven't done that. Maybe it will never die! LOL.

I will be back if I discover any other programs not working under Update 3.

Yogi

@yogi32

Quote:

Good to know I'm not the only one with a machine that goes cranky and I wasn't going crazy.

I can't leave any USB sticks in my drive as it will stall boot. Or stall Workbench on boot. Once when my mouse was plugged in to the front case port that stalled it but somehow it's been fine since.

From reports I've read in places it might be related to Radeon model and drivers. I have an R7 250 and am using the RadeonHD.chip 3.7 driver. There is some unresolved interrupt issue I've had since Update 2. Some how vertical blanking interrupts are going missing. Since EHCI uses interrupts I wonder if a related issue is causing it to miss USB interrupts as well.

@MazinKaesar

I solved my network issue with help from guys from Hyperion forums.

I run the command c:CheckRoadshowConfig VERBOSE and this was the output:



I removed all the duplicate entris in DEVS:Internet/service file and after a restart all seems working fine.

@Hypex

I am using this driver to Hypex. Radeon HD 3.7 since I have an old Radeon card in this AmigaOne 500. That must be the problem. Like I said earlier, I am waiting for this thing to die to upgrade and I really don't want to change the video card. I bought a new Radeon card for the A1222+ I have and haven't assembled the computer yet. Well, it is manageable, actually, I put back the new update to the bootkeyboard kickstart module and it has been behaving better, less hanging on reboot.

Yogi

@MazinKaesar

Hi MazinKaesar,

I'm very happy for you that everything is back to normal!

@skynet

thank you, some guys from Hyperion forum would like to understand something more, we will continue our investigatio, anyway

@yogi32
you have a problem with the new bootmouse driver and your aeon mouse works not correctly?
it is possible that your are using a special driver in devs/usb from mousedriver pack out of the aminet/os4depot.
if this is the case, not the bootmouse driver is the problem, the special driver from the driverpack is the source of trouble.
please use the new 1.4 driver from the mousedriver pack from aminet, which is apppear the next days. this includes also a new special mouse driver for the aeon mouse and you can put the new bootmouse driver pack in kickstart.