On Monday 16 May 2005 1:14 pm, Martin Loschwitz wrote: > Hi folks, > > attached you find the mail I sent to the Linux Kernel Mailinglist about my > problems with my nVIDIA nFORCE-board and my Logitech MX900 Bluetooth dongle.
There's is a general enumeration issue that seems to crop up most often with various Bluetooth dongles ... they don't react well to Linux lately. However this particular failure mode doesn't loook like that one. It looks like you may just have forgotten to "modprobe ohci_hcd". > Kind regards > > ----- Forwarded message from Martin Loschwitz <[EMAIL PROTECTED]> ----- > > From: Martin Loschwitz <[EMAIL PROTECTED]> > Subject: USB broken for certain devices on nVIDIA nFORCE-ehci-chipsets > To: Linux Kernel mailing list <[email protected]> > Date: Sun, 15 May 2005 22:41:38 +0200 > User-Agent: Mutt/1.5.9i > Message-ID: <[EMAIL PROTECTED]> > > Hi folks, > > I just got my new nVIDIA nFORCE-board this morning, I put it into my computer > and got it working up all nicely. Apart from one exception: The USB-chip does > work nicely with my USB scanner, but not with the USB-dongle of my Logitech > MX900 bluetooth mouse. Whenever I put the plug of the dongle in, I just see > the following in dmesg: > > hub 1-0:1.0: state 5 ports 10 chg 0000 evt 0200 > ehci_hcd 0000:00:02.1: GetStatus port 9 status 001002 POWER sig=se0 CSC > hub 1-0:1.0: port 9, status 0100, change 0001, 12 Mb/s > hub 1-0:1.0: debounce: port 9: total 100ms stable 100ms status 0x100 > hub 1-0:1.0: state 5 ports 10 chg 0000 evt 0200 > ehci_hcd 0000:00:02.1: GetStatus port 9 status 001803 POWER sig=j CSC CONNECT > hub 1-0:1.0: port 9, status 0501, change 0001, 480 Mb/s > hub 1-0:1.0: debounce: port 9: total 100ms stable 100ms status 0x501 > ehci_hcd 0000:00:02.1: port 9 full speed --> companion > ehci_hcd 0000:00:02.1: GetStatus port 9 status 003001 POWER OWNER sig=se0 > CONNECT > hub 1-0:1.0: port_wait_reset: err = -107 That's the failure I'm not used to seeing: "port_wait_reset", with err 107 being ENOTCONN, probably indicating that the device disconnected itself during the reset. But hmm, that's actually NOT an error for a full speed device; it's just usbcore (the hub driver) calling a normal ocurrence an error. (Though maybe there was something odd about it? You DO have "ohci_hcd" loaded, don't you? EHCI doesn't handle full speed devices except through a high speed (transaction translating) hub. > lsusb does not list the device afterwards, and even the blue light in front > of the dongle, that is usually switched on once the thing works, is off. The > lspci-tool shows the following for the chipset: > > 0000:00:02.0 USB Controller: nVidia Corporation: Unknown device 005a (rev a2) > 0000:00:02.1 USB Controller: nVidia Corporation: Unknown device 005b (rev a3) I suspect you have a pretty ancient /usr/share/pci.ids ... mine's from late last year and it knows those device numbers. > Board is Asus A8N SLI Deluxe. It seems that with Linux 2.6.10, the mouse or > rather the dongle works just fine, so I assume this has been introduced in > the 2.6.11-series. Is this a known problem and is a fix available for it? > ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
