|
A rabbit chewed through a USB cable, overloading USB port. How to reset?
'USB 1-0:1.0 Over-current change on Port 1'
'USB 1-0:1.0 Over-current change on Port 2' Yes, I realize there are a few similar threads around here, however many are rather old, and most of them reach one of two conclusions: "blacklist the usb/uhci module" or "your hardware/power supply is defective". While (1) might get get if the 'over-current' messages in dmesg, they aren't exactly my problem. Since the rabbit DID eat through the cable, likely shorting the port, I KNOW there *was* an over-current condition at one point. And (2) *may* be the case now with the USB port (defective) but I doubt it; and the power supply is good. The machine is my (older) QDI Intel 440-LX 333MHz firewall machine, with only one USB port. The controller has always reported 2 ports, and maybe there is a pin header in the box for a second port, but the box only has one obvious USB port. The port had been in use for my GE wireless keyboard & mouse when the rabbit ate through the wire for the base-station. I have since repaired the base-station USB wire, and the device works fine when connected to another computer, but nothing works now in the single USB port on the firewall machine, and I get those 'over-current' messages, once per port, in dmesg when I boot it up. I have also since bought a new PS/2 mouse for the machine. Google took me to the LQ threads on the subject, as well as to various similar/related threads from the Linux USB mailing list(s), but I have yet to see directly addressed anywhere, how exactly (if possible) to reset the over-current status of the port or hub in question. The way I figure it, if the Linux USB driver is able to determine that there *has been* a change in the over-current bit set by the hub or port, then by extension, it ought to have a mechanism for *resetting* that status, or otherwise shutting off/on or resetting the entire hub or port. Until I have exhausted all ideas of how to reset the port, I am assuming that it is not DEAD, but needs to be reset. Up above, when I wrote 'I doubt that the port is defective', I wrote that because I remember a few years ago when I still used "that other OS" before switching to Linux, I had had occasion to need to reset an over-current status on a USB port. "That other OS" would pop up a little balloon which read "Overload on USB port. Click here to reset" and after clicking, the port would work again. So, is there a way of doing this from Penguin-Land? :) (P.S. - for those wondering: my workstation is a corner unit, all open areas of which are protected by 1/2" hardware cloth attached from the workstation to the wall & from the floor to the tabletop, but despite all that, the &&$(@^# rabbit in question managed to climb some furniture on the other side of the room, in the middle of the night, then traverse a wall by way of a window ledge, and literally 'fall' its way into behind my workstation where it constantly endeavors to get, and where I found it in the morning having a hearty breakfast of Ethernet cables, USB wires, two NULL-modem cables, and the adapter for a wireless router :/ so needless to say I was *very* displeased, but please, no more discussion of the rabbit..) Sasha |
Don't know how to solve your problem, Sasha, but I had a good laugh at it. Sorry. :)
Get a muzzle for the pesky wabbit. |
I once had a rabbit that would chew thru electric cords---how he survived that I will never know.
My hunch is that--if a reboot doesn't fix it, that port is probably history. My hunch is that a PCI USB card is cheaper than a new MB. If you were looking for an excuse to buy a new MB (I am) then don't read the previous sentence....;) |
Hmm, some say to turn on 'CONFIG_USB_SUSPEND'.
Possibly offtopic, I did find a java API and class that can reset the USB port: http://jusb.sourceforge.net/apidoc/usb/core/Hub.html If you know enough C, take a look at usb.h, you may be able to write a program to reset it. Somehow I think it's fried. |
Quote:
Since that last episode which cooked my USB port (the rabbit is VERY LUCKY it was my old machine and not my nice machine, or I'd have been hunting it with a stew pot in hand) we confine the rabbit to the hallway at night. A new MB for that machine is not practical, especially as I did get a shiny new MB for my 'nice machine' a year or so ago; if anything, my roomie may one day get a new machine or new laptop, in which case I will get her old machine and make something of that if necessary. @ H-Tex-MeX -- thank you very much for those two suggestions; I will be looking into both of them (the CONFIG_USB_SUSPEND and the Java class) and will post updates either way once I try them. As for the usb.h and writing a C tool to do this, I'm afraid my C is not up to the task, but I will ask the roomie about it; she is the C person here. Thanks you two :) Sasha |
I was once told by a woman I purchased a pet rabbit from (so it must be true...)that rabbits couldn't eat apples, because the seeds were toxic to them.
So, if you were to venture to the iDark Side (shudder), would that be the end of the rabbit? Yet another reason that Linux is just so much better (as the choir rejoices in yet another resounding crescendo.) cheers, |
I do not know about rabbits but you can prevent squirrels from chewing on stuff by hitting it with pepper spray. 1Tbls Dave's insanity sauce to 3 Tbls olive oil sprayed on with a mister usually works. A very light coat goes a long ways and do NOT get this stuff in your eyes or lungs.
|
Well.. CONFIG_USB_SUSPEND did not help. With it enabled, I get some occasional dmesg lines about like:
"USB 1: Remote Wakeup is needed for autosuspend" and "usb 1-0:1.0: uevent:" but no change in the initial 'over-current change..' message, and `lsusb -v` shows full info from the hub, but also still shows the over-current status. I tried plugging a USB stick into it, but nothing happened. I am still considering about the Java class mentioned above-- I am prolly further ahead trying something in C vs. Java though. Here's a thought: what I need is something like 'setpci' but for USB, though the USB hub *is* on the PCI bus.. Thing is, one of the methods thay setpci uses is via the /proc filesystem, and since reading in a USb mailing-list thread of the idea to do like "echo '1' > power/state" to (re)enable/suspend the USB port or hub, I went looking for some of the indicated /proc files.. None were there. I'm not a stranger to echoing stuff into /proc or using sysfs, but in this case, there's simply no meaningful files in the USB areas of these filesystems, and the ones that *are* there, aren't getting me anywhere. Still thinking on it.. PS-- RE: pet store employees.. much of the time, they don't know their butts from a hole in the ground, let alone the needs of many of the animals they sell. No offense to those few who actually do, but most don't, and it isn't entirely their fault either-- it's generally a low paying job for high school and college kids, and they can't be expected to be experts. FWIW, our rabbit likes apples very much, and has been known to eat some of the seeds with no ill effects. She LOVES oatmeal-peanut-butter 'Pirate Cookies' too.. Weird bunny.. And oddly enough, we have other rabbits here who don't like carrots! Finally: here at out place, the 'iDarkside' would involve the rabbit meeting the boa constrictor :O :D Sasha |
The short probably fried your USB controller for those ports, if its built into the MB you might try turning them off in the BIOS, otherwise you are hosed, if you can turn them off and your OS quits giving you fits, get an add on card, and install it.
Good Luck :-D |
Settling for no USB for now..
Quote:
Nothing has changed with the USB ports. Maybe they ARE fried, or maybe I just have no means of resetting them. The OS isn't giving me fits, merely a single line in dmesg for each port being 'over-current status', so that isn't a big deal. I'll be darned if I'm going to temporarily install that 'other' OS just to try to reset the USB port-- I'd rather have no USB ;) so meanwhile, I have focused on other things, and am happily using my PS/2 mouse. The only drag may be if in the future I decide to purchase a USB dongle modem I have been eyeing; I would have to take up that suggestion of a PCI->USB card, but I don't know if it would be worth the $$ just for a new modem. I WOULD like to get the new modem one day, because with my current PCI Intel 536EP, I am stuck at kernel 2.6.24.4 because the (un-maintained) Intel 536 modem driver will not build on any newer kernel, and I have already jury-rigged the driver as it is to get it to build on 2.6.24.4. I'd like to upgrade the kernel on that machine. And by the looks of things, hell will freeze before we ever get high-speed out here. Thanks to those who commented and provided suggestions here; if the USB ports ever come back to life, I'll let you'se know how/why they did! Sasha |
One other thing you could try, if you have a voltage tester, test the port to see if it's getting power, see here for the layout of the pins:
http://en.wikipedia.org/wiki/USB http://pinouts.ru/Slots/USB_pinout.shtml You could also try to install Window$ to see if you can actually reset anything, but somehow I think if there is no voltage going to the USB port, it's dead. |
Here's an odd thing; I recently have gotten a USB overcharge warning in dmesg as well, but all ports seem to be functioning normally. No warnings in Win XP, though, and no animal involvement.... It is a circa 2002 MB, so perhaps just showing its age.
So, I haven't worried, much, about it. Should I? (I'll try the above voltage test when I get a chance, thanks) |
Some have suggested cleaning out the port with compressed air in case something is shorting the pins.
|
Next time, instead of a rabbit, get yourself a Tasmanian Devil.
Obviously they are not able to chew cables. At least that's true for Tuz, included in kernel 2.6.29 Image by Andrew McGown and Josh Bush. Image is licensed CC BY-SA. |
Quote:
I did a double-take when I first booted up 2.6.29 (in fact I rebooted to get a second look!) and I like the Tuz character. Because of the name I guessed he was a tasmanian devil, but had to check out the /documentation to be sure. Unfortunately, 2.6.29 is giving me a problem with my NIC, so I am awaiting a few patches to see if they fix the issue, before switching from 2.6.28.7 |
| All times are GMT -5. The time now is 02:20 AM. |