I have noticed my mouse wheel not working to scroll on my X5000 when booting from my System drive. When booting from the USB stick that was supplied with my motherboard mouse scrolling does work.
While troubleshooting this, I typed usbctrl restart in a shell and got this error:
USBCtrl only works with USB Stack v53.14.
By the way, usbctrl start is in the startup-sequence.
First of all, how do I determine the version number of my USB Stack? I've looked at version for various files associated with the usb system, but which one is the one? Hah.
Otherwise, anybody know what's going on here? Thanks!
First of all, how do I determine the version number of my USB Stack? I've looked at version for various files associated with the usb system, but which one is the one? Hah.
SYS:Kickstart/usbsys.device would be the core of the USB stack. It must be that one the error refers to.
As for why it's not working, not sure. Let's see when we know the version you've got.
Yes, it's the version of usbsys.device reflecting the USB stack version, as Niels mentions. The usbctrl version must match this - at least in earlier versions of the command.
Give me a PM if you fail to find the right version. I have many older versions still in storage :)
Thanks, guys, for helping me troubleshoot this. When I get back to my Amigas and other wonders this afternoon, I will check my versions of usbctrl. It sounds like I have mismatched pieces of the puzzle.
Niels and Thomas, thanks so much for your assistance. This was exactly the problem. I had somehow mixed usbctrl version 53.14 with usbsys.device 53.22. Now all is on 53.22 and everything is working as it should.
Besides the mouse wheel being nonfunctional, this mismatch seemed to also cause some of the keys on my keyboard to not work, such as the right "Amiga" key. I thought the keyboard thing was a different problem, but now that is solved as well.
Getting a bit technical here, the reason you keyboard (and mouse) started acting up is that usbctrl is required to tell the USB stack that the OS is booted far enough for file system access, UI etc. to be available. So when usbctrl does not run the USB stack stays "pre-booted" and only uses drivers already in memory as kickstart modules, and it won't read any environment variables holding configurations - only what may be set in UBoot variables.
That makes sense. I believe I may have also noticed an inability for the OS to notice I had inserted a new USB stick while I was stuck in this "pre-booted" state. But all is well now.
Would any of this usbctrl make or break early boot access on some keyboards? I have some keyboards that refuse to get into early boot while others work fine.
Personally, I would think your problem is most likely down to the fact that most manufacturers cannot stick to the USB standard...
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
@AmigaSociety The requirement for use in the Early Startup is that the keyboard in question supports the boot keyboard protocol. Maybe some gamer keyboards do not support that? But I don't know, just taking a wild guess.
At any rate this is too early in the boot sequence for usbctrl to have any say in it.