Summary: | Insufficient USB Power on ML-350-G3, gentoo 2.6.16-r9 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Huttley <john> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output of lsusb -v with both devices plugged in.
updated lsusb -v |
Description
John Huttley
2006-06-18 14:47:51 UTC
Please attach "lsusb -v" output for both devices (doesn't matter that the kernel rejects one due to power budget, lsusb will still work) Created attachment 89512 [details]
output of lsusb -v with both devices plugged in.
As requested.
I initially thought both disks were identical.
Actually, they both just have blue lights...
Well, lsusb failed to get the info for the first device (the Prolific) - presumably this is the one that was rejected. The other device claims to require up to 2mA of power. It almost certainly requires a lot more. I'm still interested to see how much power the Prolific requires. When you see this message: usb 1-3: rejected 1 configuration due to insufficient available bus power Run this command: echo -n 1 >/sys/bus/usb/devices/1-3/bConfigurationValue Then run "lsusb -v" again and post the results here. By the way, the above command will bypass the power requirements, so you should be able to use your disk. Thanks, I'll do that this Sunday, when I have access to the machine. --John Created attachment 89947 [details]
updated lsusb -v
I see that it claims 510mA.
That's odd. Much more than it ought to, but I would think, not enough to kill the host port (2.5" external, USB powered disks take 1000mA on startup)
I believe the problem is that onboard ports have a maximum of 500mA power available. Previously, Linux just ignored the power budget. Now that it is computed and checked, anything which uses more than 500mA will always be rejected. This is basically a broken device.. you should report it to Prolific and at least for now, use the suggested workaround. Some more info can be found here: http://marc.theaimsgroup.com/?l=linux-usb-devel&m=115185194104984&w=1 I'll write a FAQ entry as suggested. |