#81 closed defect (fixed)
USB attached Mouse & keyboard work randomly
Reported by: | Barry Landy | Owned by: | |
---|---|---|---|
Priority: | minor | Component: | basedrv |
Version: | 10.197 | Keywords: | |
Cc: | bl10@… |
Description
Running ECS21 with all the latest drivers from Arca Noae, especially USB11.08
system: Intel mobo: DQ67OW
mouse and keyboard are normally attached to a hub.
After boot, they sometimes both work; sometimes one works; sometimes neither works. If they dont work, sometimes replugging to a different port in the hub causes the mouse or kbd to be recognised. If that doesnt work, plugging mouse&kbd into usb slots on the box usually (but not always) gets them to work.
Attachments (9)
Change History (37)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Now switched back to 10.197 which was in use before I went to 11.08 precisely because of these effects.
I have attached config.sys
by , 10 years ago
Attachment: | Config.Sys added |
---|
comment:3 by , 10 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Please report issues with the 11.xx versions on the Arca Noae bug tracker.
If 10.197 works for you then you could mention that.
comment:4 by , 10 years ago
You misunderstood what I meant. "precisely because of these effects" meant that 10.197 was suffering this problem and I changed to 11.08 to see if it worked better (no, it works worse!).
SO this ticket is for the occasionally failure to start the USB attached mouse and/or keyboard (usually in an external hub) in version 10.197.
by , 10 years ago
Attachment: | blandy.zip added |
---|
comment:5 by , 10 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
comment:6 by , 10 years ago
blandy.zip made matters worse (sorry)!. Two attempts with the mouse/kbd in a hub and one attached to root, and they did not work any time. version 197 restored.
by , 10 years ago
remove delay after setting config and before calling client drivers
comment:7 by , 10 years ago
new version of USBD.SYS no improvement. Current state is that with all the modules from blandy.zip EXCEPT USBD.SYS which is from USB197 mouse & Keyboard work OK from hub and from root; with either new USBD.SYS M/K work from neither.
comment:8 by , 10 years ago
Cc: | added |
---|
by , 10 years ago
Attachment: | usbd.2.zip added |
---|
resetting status stalled bit on resuming operation after a pipe stall
comment:9 by , 10 years ago
Try usbd2.zip. If you hear a beep that means that your hubs has problems on its change notification pipe (detecting device attach or detach and such). Most likely this is what is happening on your external hub.
If you heard beeps already with older versions that would mean that your hub has an overcurrent condition (for whatever reason). If that is true, use as little devices as possible on that hub.
comment:10 by , 10 years ago
Sorry: no improvement.
The only beeps I hear when the hub is working are when a device is unplugged or replugged and I assume that comes from the USB system telling me that something is happening.
I hear no beeps with the usbd.sys from usbd.2.zip
by , 10 years ago
Attachment: | blandy.2.zip added |
---|
hid driver: change stalled pipe handling just like USBD.SYS
comment:11 by , 10 years ago
Try blandy.2.zip. Take at least USBHID and USBD from that package. The rest remains unchanged from 10.198.
By the way: it sometimes helps to completely shut down and power down the system and then to restart.
comment:12 by , 10 years ago
Also do this: REM out USBMSD.ADD from config.sys and see if that makes a difference
Also try the USBMSD.ADD from blandy.3.zip (in short: use all of blandy.3.zip, compared to blandy.2.zip it adds USBMSD.ADD).
comment:13 by , 10 years ago
None of the above seem to have improved things. I did a lot of tests which was quie complicated.
I seem to have left the USBMSD for blandy.3 in use and that seemed OK....
(I did power down occasionally which seemed to make no difference)
comment:14 by , 10 years ago
One question: are your USB mouse and Keyboard rather old or rather new ? Are these 2 physically separate devices or a "common" device like a USB attached IR Receiver that handles IR mouse and IR Keyboard ?
comment:15 by , 10 years ago
One more question: does the 11.08 USBD.SYS also completely fail,that is your USB mouse and Keyboard do also not work no matter if you plug them into an external hub or a root hub ?
comment:16 by , 10 years ago
USB mouse and Keyboard are not new but I do not recall exactly when I bought them; probably around 2011. They are two physically separate standard USB; no IR involved.
11.08 does not completely fail; my bug report says it works randomly (and certainly less well than 10.167).
I do not recall how well it works if both mouse & keyboard are initially plugged into root hub.
I could experiment again (later) and could try 1108 with the 10.167 USBD.
by , 10 years ago
Attachment: | blandy.4.zip added |
---|
changed USBD on device descriptor read: specify 64 bytes to read
comment:18 by , 10 years ago
try USBD.SYS from blandy.4.zip. I reverted some change I made from 10.197 to 10.198 but I did not do it correctly. But now I went back to what I had in 10.197.
comment:19 by , 10 years ago
I did some further tests (before reading above) and confirmed things not working!
I realised I had NOT tested the new USBMSD. Did so and it did not seem good. I got a strange message "mouse battery empty"; AFAIK the mouse does not have a battery; anyway the light was shining brightly....
comment:20 by , 10 years ago
Tested blandy.4. after a power off reboot worked OK (before the power off there were some oddities in that and other "working" versions).
I have NOT retested the new USBMSD.ADD
comment:21 by , 10 years ago
Ignore USBMSD.ADD for the time being and revert back to the USBMSD version 10.162. USBMSD.ADD is heavily under construction right now and I still need some time to get it into shape.
Use all other drivers I sent to you and observe if the system is sufficiently stable for the next couple of weeks or so. Report if you still have issues.
comment:22 by , 10 years ago
Test blandy.5.zip. The best would be to backup all your USB files and just unzip this zip over it. Have a look of what the zip contains.
I'd like to check an updated USBD.SYS but USBCOM.SYS and USBPRT.SYS have also been updated.
Let me know the results (traps, hangs, or to the better). If the system hangs, replace USBD.SYS by the backupped driver and let me know if that fixes the hang.
comment:23 by , 10 years ago
Trying this latest version of USB198 suite as requested (in both ECS21 and 22).
After needing one cold boot seems to be working well.
by , 10 years ago
Attachment: | blandy.6.zip added |
---|
comment:24 by , 10 years ago
Could you try blandy.6.zip ? I had to backout some stuff in USBD.SYS (I might be able to put it back in).
comment:25 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
fixed in 10.200 (to be released)
comment:27 by , 9 years ago
I have the same issue, I'm using 10.200 drivers (maybe a too old prerelease?). It seems to happen more frequently when rebooting from ubuntu or windows, or when a hub is used to connect keyboard and mouse. While the USB drivers are loading at boot time, using usbdock shows no devices connected to system.
comment:28 by , 9 years ago
Version: | → 10.197 |
---|
I appreciate you do not debug 11.xx versions. Quite happy to revert to 10.xxx versions.
11.05 (as supplied on the ECS22 beta DVD also fails in the same manner