From: florin@iucha.net (Florin Iucha)
To: linux-usb-users@lists.sourceforge.net,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Microsoft Wireless 6000 Mouse/Keyboard
Date: Sun, 18 Jun 2006 19:05:20 -0500 [thread overview]
Message-ID: <20060619000520.GR7905@iucha.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2778 bytes --]
Is the Microsoft Wireless Desktop 6000 supported under Linux? I am
plugging the dongle into the motherboard port and under Linux 2.6.17 I
cannot see it, but get the following error messages in the log:
[ 149.386325] usb 2-7: new low speed USB device using ohci_hcd and address 6
[ 149.469949] usb 2-7: device descriptor read/64, error -110
[ 149.600844] usb 2-7: device descriptor read/64, error -110
[ 149.728097] usb 2-7: new low speed USB device using ohci_hcd and address 7
[ 149.811719] usb 2-7: device descriptor read/64, error -110
[ 149.942610] usb 2-7: device descriptor read/64, error -110
[ 150.069866] usb 2-7: new low speed USB device using ohci_hcd and address 8
[ 150.258930] usb 2-7: device not accepting address 8, error -110
[ 150.338920] usb 2-7: new low speed USB device using ohci_hcd and address 9
[ 150.527982] usb 2-7: device not accepting address 9, error -110
[ 275.993109] usb 2-8: new low speed USB device using ohci_hcd and address 10
[ 276.076735] usb 2-8: device descriptor read/64, error -110
[ 276.207624] usb 2-8: device descriptor read/64, error -110
[ 276.334880] usb 2-8: new low speed USB device using ohci_hcd and address 11
[ 276.418503] usb 2-8: device descriptor read/64, error -110
[ 276.549394] usb 2-8: device descriptor read/64, error -110
[ 276.676650] usb 2-8: new low speed USB device using ohci_hcd and address 12
[ 276.862082] usb 2-8: device not accepting address 12, error -110
[ 276.942069] usb 2-8: new low speed USB device using ohci_hcd and address 13
[ 277.127496] usb 2-8: device not accepting address 13, error -110
[ 373.348645] usb 2-7: new low speed USB device using ohci_hcd and address 14
[ 373.534074] usb 2-7: device not accepting address 14, error -110
[ 373.614062] usb 2-7: new low speed USB device using ohci_hcd and address 15
[ 373.799490] usb 2-7: device not accepting address 15, error -110
[ 373.879484] usb 2-7: new low speed USB device using ohci_hcd and address 16
[ 373.961286] usb 2-7: device descriptor read/64, error -110
[ 374.090359] usb 2-7: device descriptor read/64, error -110
[ 374.217615] usb 2-7: new low speed USB device using ohci_hcd and address 17
[ 374.299421] usb 2-7: device descriptor read/64, error -110
[ 374.428495] usb 2-7: device descriptor read/64, error -110
This is on a Asus A8N-SLI motheboard using Nforce4 chipset. I have plugged it
into a Laptop using the Intel BX chipset, but I wasn't getting even these
errors. Nothing at all.
The OS is debian testing/unstable . Is there anything I can do to help debug
this problem?
Thank you,
florin
--
If we wish to count lines of code, we should not regard them as lines
produced but as lines spent. -- Edsger Dijkstra
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-06-19 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 0:05 Florin Iucha [this message]
2006-06-19 12:15 ` Microsoft Wireless 6000 Mouse/Keyboard Jan Engelhardt
2006-06-19 13:15 ` Florin Iucha
2006-06-20 15:47 ` Florin Iucha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060619000520.GR7905@iucha.net \
--to=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox