On Tue, 14 Dec 2004, Robert Hoffler wrote: > I am a newbie to Linux, but wanted to ask everyone > about what seems to be a VIA USB hardware controller > bug in initial hardware detection...optical mice and a > printer in particular. I've been using Kernel > 2.6.8/9. Paul (from Rocklyte Systems) and I have been > trying to fix a problem with my USB optical mice under > the Athene Linux distro. Here’s the situation in a > nutshell: > > *Computer being used is a laptop-Gateway 7405GX AMD > Athlon64, 512MB RAM, and a 60GB hard drive…4 USB ports > with VIA controller > > *USB optical mice not detected on startup of Athene > Linux in 3 out of 4 ports…same with my Samsung ML-1710 > > > *Mouse would not respond to movement; Paul at Rocklyte > had me try several “tests” at the command line > > *Mouse and printer are both detected when using 1 of > the 4 ports > > *’lspci’ command seems to show 1 USB port and 3 > “hubs”; shouldn't they all be alike???
Shouldn't what all be alike? -- all the ports or all the hubs? Are all 3 of those hubs external units connected to the one port listed by lspci? > *Hubs don’t appear to be initialized properly on > startup; however, the USB mouse does function when > it’s unplugged and replugged into any of the USB ports > (hotplug OK) What makes you say the hubs aren't initialized properly on startup? > *I can send info from 'lspci'...just tell me where to > send/post it Post it to this mailing list. Also post the contents of /proc/bus/usb/devices after booting with your mouse plugged into one of the non-working ports. And it would help a lot if you can turn on the USB verbose debugging switch in your kernel configuration and post the system log (or dmesg output) showing the debug messages during the boot procedure. > I think this is a VIA USB controller problem; both > Windoze and Linux users have reported this problem. > What a pain to replug devices for them to be detected! VIA controllers have several problems. This one is new to me, though other people may know about it. > Can a workaround for this issue be put into the > kernel? I know that it shouldn't have to be this way. It's impossible to say whether the problem can be worked around in the kernel without knowing what the actual problem is! Alan Stern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
