From: David Cannings <lists@edeca.net>
To: linux-hotplug@vger.kernel.org
Subject: USB printing support problems
Date: Wed, 22 Sep 2004 11:06:21 +0000 [thread overview]
Message-ID: <200409221206.21695.lists@edeca.net> (raw)
I have an Intel L440GX+ SMP motherboard which has two onboard USB ports. I am
trying to get a Samsung ML-1210 printer, which works fine in Windows, to work
with a 2.6.8 kernel (patched with the Gentoo patches).
After compiling EHCI, OHCI and UHCI as modules and running hotplug, I get
errors in syslog when a device is plugged in. There are no options in my
BIOS concerning the onboard USB.
Is there anything I can do to get USB working? I'm guessing it's a problem
with the USB subsystem but am not sure where to turn for more information.
Thanks,
David
-- Output from syslog upon plugging in a device --
kernel: usb 1-1: new full speed USB device using address 2
kernel: uhci_hcd 0000:00:12.2: uhci_result_control: failed with status 440000
kernel: [f73d9240] link (373d91e2) element (3730d040)
kernel: 0: [f730d040] link (3730d080) e0 Stalled CRC/Timeo Length=7 MaxLen=7
DT0 EndPt=0 Dev=0, PID-(SETUP) (buf716f3a0)
kernel: 1: [f730d080] link (00000001) e3 IOC Active Length=0 MaxLen\x7ff DT1
EndPt=0 Dev=0, PIDi(IN) (buf\0000000)
kernel:
kernel: uhci_hcd 0000:00:12.2: uhci_result_control: failed with status 440000
kernel: [f73d9240] link (373d91e2) element (3730d040)
kernel: 0: [f730d040] link (3730d080) e0 Stalled CRC/Timeo Length=7 MaxLen=7
DT0 EndPt=0 Dev=0, PID-(SETUP) (buf716f3a0)
kernel: 1: [f730d080] link (00000001) e3 IOC Active Length=0 MaxLen\x7ff DT1
EndPt=0 Dev=0, PIDi(IN) (buf\0000000)
kernel:
kernel: usb 1-1: device not accepting address 2, error -71
kernel: usb 1-1: new full speed USB device using address 3
kernel: uhci_hcd 0000:00:12.2: uhci_result_control: failed with status 440000
kernel: [f73d9240] link (373d91e2) element (3730d040)
kernel: 0: [f730d040] link (3730d080) e0 Stalled CRC/Timeo Length=7 MaxLen=7
DT0 EndPt=0 Dev=0, PID-(SETUP) (buf716f3a0)
kernel: 1: [f730d080] link (00000001) e3 IOC Active Length=0 MaxLen\x7ff DT1
EndPt=0 Dev=0, PIDi(IN) (buf\0000000)
kernel:
kernel: uhci_hcd 0000:00:12.2: uhci_result_control: failed with status 440000
kernel: [f73d9240] link (373d91e2) element (3730d040)
kernel: 0: [f730d040] link (3730d080) e0 Stalled CRC/Timeo Length=7 MaxLen=7
DT0 EndPt=0 Dev=0, PID-(SETUP) (buf716f3a0)
kernel: 1: [f730d080] link (00000001) e3 IOC Active Length=0 MaxLen\x7ff DT1
EndPt=0 Dev=0, PIDi(IN) (buf\0000000)
kernel:
kernel: usb 1-1: device not accepting address 3, error -71
-- Output for USB from 'lspci -v' --
0000:00:12.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
(prog-if 00 [UHCI])
Flags: bus master, medium devsel, latency 64, IRQ 21
I/O ports at 2060 [size2]
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2004-09-22 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200409221206.21695.lists@edeca.net \
--to=lists@edeca.net \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).