Date: Wed, 12 Jun 2002 13:45:26 -0600 From: Colin Harford <colin.harford@mail.su.ualberta.ca> To: James Earl <kim-james@telusplanet.net> Cc: <freebsd-questions@freebsd.org> Subject: Re: uhub0: device problem, disabling port 2 Message-ID: <B92D00F6.199B8%colin.harford@mail.su.ualberta.ca> In-Reply-To: <20020612143519.435f5e02.kim-james@telusplanet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/12/02 2:35 PM, "James Earl" <kim-james@telusplanet.net> wrote: > I recompiled my kernel with some of the usb debug options. Here's some of the > new info it gave me. I'm not sure if it helps though: > > uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xe000-0xe01f irq 11 at > de > vice 7.2 on pci0 > uhci0: LegSup = 0x00000010 > uhci_run: setting run=0 > uhci_run: done cmd=0x80 sts=0x20 > uhci_run: setting run=1 > uhci_run: done cmd=0x81 sts=0x0 > usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.00, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > uhci_waitintr: timeout > usbd_transfer_cb: short transfer 0<18 > usbd_new_device: addr=3, getting full desc failed > uhub_explore: usb_new_device failed, error=SHORT_XFER > uhub0: device problem, disabling port 2 > > On Tue, 11 Jun 2002 11:31:30 -0600 > Colin Harford <colin.harford@mail.su.ualberta.ca> wrote: > >> On 6/11/02 3:52 PM, "James Earl" <kim-james@telusplanet.net> wrote: >> >>> Hi, >>> >>> I have an HP ScanJet 4100C USB scanner. FreeBSD (4.5, 4.6) gives for >>> following message when the device is connected to either usb port on my >>> computer: >>> >>> uhub0: device problem, disabling port 2 >>> >>> My USB controller is stated as an: Intel 82371AB/EB (PIIX4) on uhci0 >>> >>> I have searched through the mailing list archives, and have seen a couple >>> other posts from people with a similar problem, but they haven't received >>> any >>> follow-up posts. >>> >>> Can anyone here give me any direction regarding this problem? Should I post >>> this message on freebsd-hardware? >>> >>> To Unsubscribe: send mail to majordomo@FreeBSD.org >>> with "unsubscribe freebsd-questions" in the body of the message >> >> >> 1) try disabling pcibios >> 2) check IRQ conflicts... >> >> >> Colin Harford >> >> >> Systems and Network Administrator Apple Product Professional >> ================================= >> Computer and Network Support >> University of Alberta Students' Union >> Phone: (780) 492-4241 Fax: (780) 492-4643 >> http://www.su.ualberta.ca >> >> >> "I sense much NT in you, NT leads to Blue Screen. >> Blue Screen leads to downtime, downtime leads to suffering. >> NT is the path to the darkside." >> - Unknown Unix Jedi >> >> >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message Try unplugging your mouse and see if you still get the uhub errors. As for the pcibios, it doesn't matter if you have a device that uses it or not. In my experience a lot of hardware problems in BSD based systems stem from it. Colin Harford Systems and Network Administrator Apple Product Professional ================================= Computer and Network Support University of Alberta Students' Union Phone: (780) 492-4241 Fax: (780) 492-4643 http://www.su.ualberta.ca "I sense much NT in you, NT leads to Blue Screen. Blue Screen leads to downtime, downtime leads to suffering. NT is the path to the darkside." - Unknown Unix Jedi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B92D00F6.199B8%colin.harford>