since i deployed the latest update of Amiga OS4 (July) my A1 does not correctly recognize my USB devices (a Mac USB Keyboard and MigthyMouse) during booting.
But if i restart the USB Stack they get recognize and works without any problems, but to do so i always need to have my old PS/2 keyboard hooked up.
Anyone had similar problems and/or a solution for this problem.
My first try was to just restart the USB Stack in the User-Startup. But that does not solev the problem in two ways:
1.) A requetser pops up and asks about permission to restart, so my PS/2 Keyboard is still needed.
2.) If i confirm the requester they still does not get recognized correctly.
Thus to get my USB Keyboard working i need to restart the USB Stack after finished boot process.
One of the differences in the new version of the USB stack is that it handles correctly low power conditions. If the mobo doesn't deliver enough power, the USB Stack might disable devices to avoid a USB lockup.
It's unpredictable here. The message "Babble detected...", blew me away!
I posted all my USB.log at Yahoo for Detlef to look at. I noticed the VIA bug when bootup with a flash drive; it can't read the USB port. Or, is that the USB capacitor/transistor mixup?
I made more test. Especially with the back and ront ports and connected my USB Keyboard with the intergated non-powered hub and connection only my usb mouse.
Well if i only connect my mouse regardless in which port (back and front) it works right after booting.
If i connect my USB keybord without mouse connected to it, regrdaless in which port (back and front) it does not work after booting only after retsrating the usb stack.
Mmmh i forgett to test if i connect my usb keybord and my usb mouse drectly on the computer if the mouse works and the keyboard not. Have to reboot and check.
I got the same behavior from the July 2007 update. Reverting to the pre-July 2007 usbsys.device (and, if you want to use USBInspector, that too) fixed it for me - at least as a temporary solution. Dunno why, though.
After an update of my UBoot, my usb hub (unpowered) has stopped working if I have any devices connected on Cold Startup, when the usb stack then is loaded I can connect my devices and Fast reboot works fine after that.
I havent tested the old december version to se if that works with the new UBoot.
I read in the PTP docs that when a error condition rises it will STALL the endpoints.. but I'm not sure if it only means the Bulk endpoint or it include the Interrups Endpoints as well, so is there a way to se if an endpoint is stalled?
If not can I Destall and endpoint that is not stalled and get away with it?
You can see the EndPoint is stalled by the reception of USBERR_STALL (iiirc - don't have the include files here at work :)
You can also issue a GET_STATUS request to the Default Control Pipe (DCP) to get the status of a specific named EndPoint - check the USB spec on standard commands to the DCP for more info - I don't have that spec here at work either.
Btw. I don't know how a device will react to destalling a non-stalled EndPoint. Probably it will behave nicely and take it is a NOP, responding as if it destalled the EndPoint, but I'm not sure.
Reverting to the pre-July 2007 usbsys.device (and, if you want to use USBInspector, that too) fixed it for me - at least as a temporary solution. Dunno why, though.
I think the VIA USB has a bug. It can't keep count of ports it scans. I posted my usb.log at Yahoo AmigaOS4. I saw the same kind of redundancy in my old linux system.logs.
I just tried it out with a mighty mouse..it get recognized properly both after cold&warm reboot and even on powerup. It might be because the mouse is connected to a powered USB hub?
OS4.200707 on AmigaOne XE G4, not fixed and SII0680.