Opened 12 years ago
Closed 12 years ago
#45 closed defect (fixed)
USBEHCD.SYS 189 does not run USB mouse on Lenovo ThinkPad L530
Reported by: | Doug Bissett | Owned by: | somebody |
---|---|---|---|
Priority: | major | Component: | basedrv |
Version: | Keywords: | ||
Cc: | dougb007@… |
Description
I tried USB 189 version on my Lenovo ThinkPad L530. No USB mouse action is possible. I started with my wireless mouse (Logitech A220), and then tried my Logitech wired USB mouse. Still no action. I also tried a USB 1.0 device, which works okay, as do USB 2.0 devices.
NOTE: This machine has two EHCI adapters, and a USB 3.0 adapter (which is not relevant). It has no USB OHCI, or UHCI, adapters. The mouse works fine with the 186 version of the USB drivers. By going back to the 186 EHCI driver, and keeping the rest of the 189 package, the mouse will work. Also, USBRESMGR and USBDOCK, correctly identify the device as being attached.
USB189L530.zip contains: pci-D.txt, and USB189.ftf, as requested. The trace was done with the wireless USB mouse attached, and turned on.
Attachments (9)
Change History (29)
by , 12 years ago
Attachment: | USB189L530.zip added |
---|
comment:1 by , 12 years ago
by , 12 years ago
Attachment: | USB189T510.zip added |
---|
follow-up: 4 comment:2 by , 12 years ago
I looked at USB189T610.zip and I can see 2 USB 2.0 devices attached, 1 on each of the 2 controllers that you have. What 2 devices did you have attached ?
Will the Logictech mice work with the other systems that you have ? The mentioned Lenovo systems have a RMH (Rate matching hub) that will manage in HW the "bus conversion" from USB 2.0 to USB 1.x and I think those might make the difference. In that case I will need to look into USBEHCD.SYS of why
by , 12 years ago
USBEHCD: fix in FreeClaimed, additional recovery delay in USBD
follow-up: 5 comment:3 by , 12 years ago
Please try doug.zip: 1) first, replace only USBEHCD.SYS, tell me results 2) then, also replace USBD.SYS, tell me results 3) on your other machine with OHCI, please also replace USBOHCD.SYS, tell me results if it still works ok
comment:4 by , 12 years ago
Replying to erdmann:
I looked at USB189T610.zip and I can see 2 USB 2.0 devices attached, 1 on each of the 2 controllers that you have. What 2 devices did you have attached ?
I had forgotten that the L530 has a built in camera. Apparently, that is one of the devices. The other was the wireless mouse. I will upload the information from USBDock, if it is helpful. That information was gathered using version 186 of the USB drivers.
Interesting: I just looked at USBDock, using what is in Doug.zip. It shows the mouse twice.
Will the Logictech mice work with the other systems that you have ? The mentioned Lenovo systems have a RMH (Rate matching hub) that will manage in HW the "bus conversion" from USB 2.0 to USB 1.x and I think those might make the difference.
Yes, the mice work fine with other systems.
comment:5 by , 12 years ago
Replying to erdmann:
Please try doug.zip: 1) first, replace only USBEHCD.SYS, tell me results 2) then, also replace USBD.SYS, tell me results 3) on your other machine with OHCI, please also replace USBOHCD.SYS, tell me results if it still works ok
Okay, I put all of USB189 back in, then: 1) Replaced USBEHCD.SYS. Rebooted. No change. 2) Replaced USBD.SYS. Rebooted. No change. 3) Put USBOHCD.SYS on my main system (running with 189). Rebooted. The mice work fine.
I just noticed, that the previous entry mentioned "USB189T610" (I assume you meant T510). I will try that, and report back.
I just tried to plug in my old USB 1.0 thumb drive to the main machine, after removing the mouse dongle. It isn't recognized (appears to not get power). If I plug the mouse back in, it doesn't work. The other mouse (permanently attached to another USB OHCI adapter) is still working, but it is not moving smoothly. USBDock also does not show the wireless mouse. More after I do more testing...
comment:6 by , 12 years ago
I think you said you looked at "USB189T610", but meant "USB189L530". The T510 does not have a camera, and USBDock shows only the mouse attached. I suppose it might have showed the mouse twice (as I saw on the L530), but I don't see that this time. Otherwise, the T510 acts the same as the L530.
Looking at USBDock in the L530 again, I see the camera, and the mouse (once), and the mouse does not do anything.
Hmmm. I went back to USBOHCD.SYS from 189 on my main machine, and rebooted. After I connected my wireless mouse, the wireless mouse is working. However, the permanently attached mouse has quit working. USBDock shows the devices that are attached, and it shows when I attach/detach them.
Hopefully, all of this will give you a clue. I am going back to 186, which seems to work with no troubles.
NOTE: I am not being notified when TRAC is being updated (not sure why). I will try to remember to check regularly.
Thanks...
comment:7 by , 12 years ago
Cc: | added |
---|
follow-up: 9 comment:8 by , 12 years ago
I don't know why the heck you are using USBOHCD.SYS on your Lenovo thinkpad as it only has EHCI. Nonetheless, try updated doug2.zip. It contains a modified USBOHCD.SYS.
comment:9 by , 12 years ago
Replying to erdmann:
I don't know why the heck you are using USBOHCD.SYS on your Lenovo thinkpad as it only has EHCI. Nonetheless, try updated doug2.zip. It contains a modified USBOHCD.SYS.
I wasn't trying USBOHCD.SYS on the Thinkpads. You suggested trying it on my other machine (an Asus M3A78-EM), so I did (item 3, in a previous post). It had a problem. I will try the new one. Thanks...
comment:10 by , 12 years ago
For the following, I installed all of Doug.2.zip.
I hesitate to open a new incident for the USBOHCD.SYS problem mentioned here, because the original 189 USBOHCD.SYS works fine on the Asus M3A78-EM. It is only the one that was in DOUG.ZIP that was really broken. The one in DOUG,2.ZIP works better, but still has a problem. If I plug the wireless mouse dongle in, after the system is booted, the wireless mouse works fine, but the wired mouse quits working. If I pull the wireless mouse, the wired mouse still does not work, and when I plug the wireless mouse back in, it works, but it is "jumpy". If I leave both connected, and reboot, both seem to work okay. I am pretty sure that they are on different OHCI controllers.
Okay, back to the L530. USB 2.0 devices seem to work okay, but the wireless mouse does not work, even though USBDock says it is there, and it recognizes it. USB 2.0 devices seem to be okay, and my USB 1.0 thumb drive seems to be okay. Another wired USB mouse does not work. Attaching the mouse after booting makes no difference.
I did not try the T510.
I did not try to trace anything. If you would like traces, let me know.
follow-up: 12 comment:11 by , 12 years ago
Please take a trace only for USBOHCD.SYS which is trace code 225 (and from the doug2.zip package) on your Asus board. Boot with both devices attached, then unplug one after the other and then plug back in one after the other. After you have done so, save away the trace as unformatted trace (as described in readme.txt).
For your L530, T510 respectively: have older versions of USBEHCD.SYS worked for the mice ? Has original IBM version 10.162 for the mice ? You should also take a trace of this: trace only USBEHCD.SYS which is trace code 226, take USBEHCD.SYS from doug2.zip package and do the same: have the USB mouse plugged in on boot, then unplug after boot and plug back in. Save away trace.
Note: do not use the devices too much during these tests (for example, do not move the mouse too much and for too long) as otherwise too many data transfers will happen and the trace would wrap around (and I wouldn't be able to look at the relevant information).
comment:12 by , 12 years ago
Replying to erdmann:
Please take a trace only for USBOHCD.SYS which is trace code 225 (and from the doug2.zip package) on your Asus board. Boot with both devices attached, then unplug one after the other and then plug back in one after the other. After you have done so, save away the trace as unformatted trace (as described in readme.txt).
The trace will be uploaded, if I can get it created. I installed all of the contents of Doug.2.zip. Then set up the trace in CONFIG.SYS. The wired mouse was already connected, so I attached the wireless mouse, and rebooted. The boot succeeded, so I detached the wireless mouse. Then, I crawled under my desk to detach the wired mouse. When i pulled the cable, I heard the tune played when a Process dump is taken. I then plugged the wired mouse back in, and heard the tune again. By the time I got back to where I could see the screen, it showed a trap in USBMOUSE. I went to get my camera, and the system decided it needed to do a SysDump. After rebooting (I did not plug the wireless mouse back in), I followed instructions to extract the trace data. It took about 45 minutes to get to the point where the command line showed up. I typed in the command, and it spent another 45 minutes doing something, then the command disappeared from the command line, but no trace file, yet. It still seems to be doing something. I did extract a trace from the Process dump. It will be uploaded as FromPDUMP_TRACE.RAW. If TRACE.RAW ever shows up, from the SysDump, I will upload that too.
I should note, that there is also an APC UPS that connects by USB, and I have a Canon i960 printer that is also attached.
For your L530, T510 respectively: have older versions of USBEHCD.SYS worked for the mice ? Has original IBM version 10.162 for the mice ?
Yes. Both machines, and mice, work well, with the 186 version of USBEHCD.SYS. They also work with the original IBM version.
You should also take a trace of this: trace only USBEHCD.SYS which is trace code 226, take USBEHCD.SYS from doug2.zip package and do the same: have the USB mouse plugged in on boot, then unplug after boot and plug back in. Save away trace.
Hope I got it right. L530USBEHCD.ftf and T510USBEHCD.ftf, will be uploaded (possibly zipped since the upload limit is too small).
by , 12 years ago
Attachment: | L530USBEHCD.zip added |
---|
by , 12 years ago
Attachment: | T510USBEHCD.zip added |
---|
by , 12 years ago
Attachment: | FromPDUMP_TRACE.RAW added |
---|
comment:13 by , 12 years ago
Still trying to extract TRACE.RAW from the SysDump. The system hung hard (the mouse wouldn't even move) Starting over...
by , 12 years ago
ehci drivers built by Andy Willis (one change backed out, helps with ticket #35)
comment:15 by , 12 years ago
Look at ticket #35 to see the details but I backed out one ehci change and it started working on my system. If you want to try I uploaded just the ehci drivers, they are built from latest svn changes on Lars branch. This may not be a good thing to put back in but if it works for you then at least we may have a starting point if it is not good to have in there.
comment:16 by , 12 years ago
YES! That works.
To be clear, I put all of 189 back into my Lenovo ThinkPad T510, then replaced ehci with Andy's version. No problem with the mouse, my antique USB 1.0 USB key, or a modern USB 2.0 key. Of course, it was a quick check. I will try the L530 when it finishes doing a backup.
comment:17 by , 12 years ago
It also works fine, on my L530, as well as on another test machine, where I was having problems with the 189 version.
comment:18 by , 12 years ago
It also fixes the mouse problem with USBOHCD.SYS on the M3A78-EM system.
Performance is great.
comment:19 by , 12 years ago
The contents of usbhcd190.zip seem to work well, on all of my systems.
Thanks...
comment:20 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I will add this here, because it is the identical problem on my Lenovo ThinkPad T510.
USB189T510.zip contains: PCI-D.TXT, and T510USB189.ftf.