Michael J McCafferty wrote: > Problem resolved... at least for now. > > I am not sure what exactly was wrong, but: > > 1) I commented out the entry > in /etc/udev/rules.d/70-persistent-net.rules for wlan0 > > 2) Then rebooted, and the system added wlan1. I didn't expect that. I > expected it to add a wlan0 back in there since there was no wlan0, or > rather it was commented out. > > 3) I removed that wlan1 entry and uncommented the wlan0 entry that was > the original and rebooted. > > It worked ! WTF !?!?!? > > > My suspicion is that you have come up against a phantom problem that I have had with other hardware like removable drives. There seems to be some entry, perhaps in /proc that persists when the hardware is improperly removed from the system (keep in mind that this could mean just a driver module crash ir IRQ conflict) . Then, when you reboot, the system thinks the hardware is already there and doesn't load the driver. By telling the kernel not to use that hardware (wlan0) it fixes the magic somehow and releases the unknown lock. This then tells the system that all is well and the reboot loads drivers as usual.
Now keep in mind that this is just my layman's guessing of what's going wrong and I may be way off base, but disabling the messed up hardware then re-enabling it has worked for me on a number of occasions. Congrats on getting it working. Tyrion -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
