Re: USB devices fail unnecessarily on unpowered hubs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux