From: "Lee Dowling" <ledow@ledow.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: USB devices fail unnecessarily on unpowered hubs
Date: Mon, 05 Jun 2006 12:07:06 +0100 [thread overview]
Message-ID: <op.tan6h41hl78ldg@p1000> (raw)
This, of course, doesn't deal with outside cases.
It's common knowledge that a lot of equipment is running out of spec all
the time because of cheap components, bad BIOS's etc. As an example, my
Asus L4500R laptop (with the latest ASUS BIOS) ALWAYS shows "over-current"
under Linux on all *internal* USB ports the second ANYTHING is plugged in
(and I have nearly 50 different USB devices of different types,
manufacturers and quality).
The suggestion to simply stop over-current ports from working would
immediately disable all USB ports, including any powered hubs that I plug
into them, I assume. I can't update the BIOS any further to stop this and
if I could I doubt it would solve the problem (it looks like cheap
hardware to me). Therefore, you've just removed all my perfectly
functional USB capability because the best BIOS I can use reports an
incorrect error (hey, what's new?).
Windows XP, incidentally, runs flawlessly with all USB devices without
power warnings on this laptop. This may well be fixable somewhere else,
it may even be a bug in the internal USB code for my laptop which may be
help in hunting such bugs down. However, anything like this should be
optional and not with some convoluted command-line echo, but by as simple
binary switch accesible to userspace. I know what I'm doing, if I choose
to ignore the error, that's my problem. The fact is, if I don't ignore
this particular error, my laptop loses all USB functionality. Taint my
kernel if you want (that's what the new userspace taint is for, is it
not?) but I need to use the USB ports that I've paid a lot of money to
have and that DO work perfectly if given a nudge.
Spec's are lovely and all, but we all know that if real hardware confirmed
to the spec's all the time that the Linux kernel would be about half it's
current size.
Lee Dowling
ICT Technician
next reply other threads:[~2006-06-05 11:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 11:07 Lee Dowling [this message]
[not found] <6kl8h-1Uf-15@gated-at.bofh.it>
2006-06-07 0:51 ` USB devices fail unnecessarily on unpowered hubs Robert Hancock
-- strict thread matches above, loose matches on Subject: below --
2006-06-02 15:11 [linux-usb-devel] " Alan Stern
2006-06-02 19:49 ` David Liontooth
[not found] <6iYGP-5hv-3@gated-at.bofh.it>
[not found] ` <6iYQx-5Jc-7@gated-at.bofh.it>
2006-06-01 23:37 ` Robert Hancock
[not found] <6iWP5-2gj-71@gated-at.bofh.it>
[not found] ` <6iX82-2UJ-3@gated-at.bofh.it>
2006-06-01 23:35 ` Robert Hancock
2006-06-01 23:46 ` Randy.Dunlap
2006-06-01 9:18 David Liontooth
2006-05-30 20:01 ` Pavel Machek
2006-06-03 9:29 ` Oliver Neukum
2006-06-01 10:01 ` Andrew Morton
2006-06-01 11:42 ` Daniel Drake
2006-06-01 14:58 ` Alan Stern
2006-06-01 15:09 ` linux-os (Dick Johnson)
2006-06-01 15:23 ` Lennart Sorensen
2006-06-01 21:39 ` Dagfinn Ilmari Mannsåker
2006-06-01 15:53 ` Oliver Neukum
2006-06-01 17:24 ` linux-os (Dick Johnson)
2006-06-01 16:57 ` Alan Stern
2006-06-01 16:59 ` Andrew Morton
2006-06-01 17:08 ` Alan Stern
2006-06-01 17:34 ` Mark Lord
2006-06-01 17:47 ` Alan Stern
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=op.tan6h41hl78ldg@p1000 \
--to=ledow@ledow.org.uk \
--cc=linux-kernel@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