On Apr 11, 2012, at 2:46 PM, Rich Shepard wrote: > My suspicion is that the wireless chip is still new enough that the driver > does not handle it under all circumstances, even with the 3.2.7 kernel.
Rich, Just throwing this out there... Wouldn't this assume it is the responsibility of the wireless driver to take down the wired driver? I would never assume that, as in some instances, both interfaces should be up. The only things that should be controlling wether the wired driver is up is A) the management software, or B) the driver for the device being brought up or down. There may be a C or later, but it wouldn't be the driver for a different interface. As I understand it, the network management software should, on transition from signal to no-signal (i.e. the cable is unplugged) should take the interface down, and it should remain down until another transition. My point is that looking for the wireless driver to do something with the wired driver is looking in the wrong location. Russell Johnson [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
