By the time I got home the cable was connected. As it turns out it is as I had originaly suspected, withouth the cable connection being connected the physical device must put itself into some kind of hibernation and thus making linux think that it has been removed. I guess when the module unregisters the device, it causes the device to wake up from it's hibernation and re-registers itself with the machine. thus causing the loop of what I saw (this is complete speculation however because I was too excited about having a decent connection to test the stuff below)
Matt Brad Hards wrote: > Whn you say that "the device keeps loading itself and unloading itself", I am > confused. The device can't do this, correct? Maybe the driver module could be > loaded and unloaded, or maybe the module could drop its connection to the > device, or some other problem. Can you please provide some detail on the > problem? Specifically, can you provide /proc/bus/usb/devices [with everything > OK, and when it "unloads itself"], and the kernel logs of the automatic load > and unload times? Also, can you show me what ifconfig -a looks like in any > interesting state [before you UP the interface, when it is running, and when > it drops]? > > Brad -- Matt Filizzi Michigan Poverty Law Program 611 Church Street, Suite 4A Ann Arbor, Michigan 48104 734.998.6100 x 23 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
