On Monday 29 June 2009, Johannes Berg wrote: > > [enable] > > usb 3-1: new full speed USB device using uhci_hcd and address 3 > > usb 3-1: configuration #1 chosen from 1 choice > > That is completely unrelated. You plugged in a USB device too :) No, it's my "bluetooth + wlan" device. Note that disabling wireless with the hardware switch also gives 'usb 3-1: USB disconnect, address 2'. >From lsusb: Bus 003 Device 002: ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface [Integrated Module] > > A lot uglier with those errors. And after that I have to run > > ifdown/ifup before networking is up again (ifup only does not work as > > it will complain "interface already configured"): > > And that's actually expected, and/or a bug in the debian networking > scripts. > (You can trigger the same problem by doing > ifup wlan0 > ip link set wlan0 down > ifup wlan0 -> error) OK, I can accept that. Wonder why it does work with 2.6.30 then. But it can certainly wait until the driver problem you mentioned is resolved. > To get your network connection back automatically we will require > changes to userland tools to listen to rfkill events. > > > BTW, would it make sense to bring back the first two lines shown with > > .30 (or at least the first one): > > iwlagn 0000:10:00.0: Radio Frequency Kill Switch is On: > > Kill switch must be turned off for wireless networking to work. > > IMHO it's good to register the reason for the disconnect. > > I guess something like that could be added to cfg80211: > phy0: taking interfaces down due to rfkill Yes, that would be nice. Thanks, FJP -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
