Hello Ehud,
I figured it out, and it was something very different: My laptop and the AP were too far away from each other. For testing purposes, I placed my box directly in front of my AP. Then, it wouldn't cease networking even if I shut the lid. On the contrary, when sitting on the couch, I must be at a critical distance. Still wondering, though, why it would work with ndiswrapper flawlessly. Could it be that the bcm43xx driver doesn't push the signal level as much as ndiswrapper possibly did? Ehud Gavron wrote: > What looks like is your power mode is set to suspend on lid close. If > you fix that you'll find your problem goes away. > > In gnome on F7 I go to system->preferences->system->power management and > change what lid-closed behavior is. For the sake of completeness: This laptop uses KDE. Kpowersave was running but configured not to do anything on lid closure. Thanks for helping! Cheers, --Timo > Timo Reimann wrote: >> Hi all, >> >> I'm having the following issue with a Broadcom 4306 802.11b/g mini-PCI >> card running under Ubuntu Feisty (7.04) kernel 2.6.20 and 2.6.22 with >> the bcm43xx driver on an IBM Thinkpad T40. >> >> Whenever I close my laptop's lid, the wifi interface seems to stop >> working as I can tell by trying to ping the machine remotely: It works >> right before I close the lid, stops when it's shut, and *mostly* works >> again if I re-open. Same thing with any other network service, e.g. ssh. >> >> The *mostly*-part is what is giving me headaches. Although iwconfig >> shows that the association to my AP is never dropped and the interface >> is still configured in terms of IP address, netmask and such, every now >> and then I cannot connect to either LAN or WAN machines, and all I can >> do in such a case is re-load the driver and restart the interface. Apart >> from that, I'd prefer my laptop to stay connected even when the lid is >> closed. >> >> I have two reasons why I suspect the Broadcom driver to be responsible: >> First, I have tried my best to make sure no other mechanism may be >> blamed for the observed behavior, including disabling ACPI/APM/APIC on >> bootup; disabling acpid; making sure no hiberating/suspending takes >> place; and checking the BIOS power management settings. >> >> Second, I used to use ndiswrapper for this machine but choose to switch >> to the bcm43xx driver since the first would not reliably connect my box >> during start-up. If it did connect, however, the link would never fail >> during lid closure (while not changing anything else, i.e. same network >> configuration tools were used during, before, and after the switch). >> >> Therefore, I'd be glad if anyone has a hint what else I could try to fix >> this problem. Especially, I'm curious if any of the bcm43xx module >> parameters deal with some power management/suspend control part I could >> tweak. (I wasn't able to figure what every `modinfo'-listed argument >> means.) >> >> Thanks for any help. If I forgot some vital piece of information, please >> don't hesitate to ask. >> >> >> Cheers, >> >> --Timo >> _______________________________________________ >> Bcm43xx-dev mailing list >> [email protected] >> https://lists.berlios.de/mailman/listinfo/bcm43xx-dev >> _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
