Hi William - On Wed, Jul 06, 2011 at 10:16:09PM -0400, William Hopkins wrote: > The drivers for a given device are responsible for initializing that > device, so rmmod && modprobe should do it. As originally mentioned, this unfortunately did not do it. I believe this reinitializes the portion of the modem that is responsible for the USB interface, but nothing more. In fact, when I first plug in the modem, the LED goes from blinking orange (no signal acquisition) to blinking blue (signal acquired). When removing and re-inserting the VL600-related modules, the LED remains blinking blue. If the whole unit was being reinitialized, I believe it would have to re-acquire the signal, and transition through the orange -> blue LED states. > If not, you could reset the USB stack by doing the same to ehci_hcd as > a last ditch measure. I removed all modules including usbcore, to the point where lsmod|grep usb returns nothing. Unfortunately the modem remained powered. > The reason for the kernel change IIRC is that modern hardware actually > *cannot* poweroff a USB port or bus. Over the years on various hardware I've encountered USB hubs being electrically powered off as a safety measure. Something like this (according to Google): hub 2-0:1.0: port 9 enable change, status 00000101 hub 2-0:1.0: port 9 disabled by hub (EMI?), re-enabling... hub 2-0:1.0: port 9, status 0101, change 0002, 12 Mb/s I suppose this is purely a hardware function? It seems odd that the software would have absolutely no control over this, but I've certainly heard of stranger things. Thanks for the reply! - Mark -- Mark Kamichoff prox@prolixium.com http://www.prolixium.com/
Attachment:
signature.asc
Description: Digital signature