The wireless access point (AP), also sometimes called a router, is not relevant to my problem. It was not the cause and it did not need to be rebooted. My problem was not one of connectivity, per se. My wireless card was unable to see any SSID's (networks), including ones that are always present but to which I have never connected. Upon taking the steps I described, this situation was remedied.
2010/3/24 ikorot <iko...@earthlink.net>: > Hi, Chris, > > > -----Original Message----- >>From: Chris Lopes <clo...@gmail.com> >>Sent: Mar 23, 2010 4:31 PM >>To: Larry Finger <larry.fin...@lwfinger.net> >>Cc: bcm43xx-dev@lists.berlios.de >>Subject: Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of >> b43 driver >> >>Ok. I got my wireless card to detect networks again. I also had a >>theory and tried to reproduce the problem, and was successful in doing >>so. Here are my steps to reproduce: >>1) Have Vista running and connected to a wireless network >>2) Hibernate Vista >>3) Boot Parted Magic from a USB drive >>4) Start the network in Parted Magic, ask it to use wireless, and then >>attempt to connect to my normal SSID, which at this point sees the >>SSID, but cannot connect due to an apparent DHCP lease error >>5) Start the network in Parted Magic again, which this time fails with >>a generic error and does not show any SSID's (starting it a second >>time is necessary to reproduce the problem) >>6) Reboot >>7) Resume Vista >>8) At this point, Vista loses connectivity to the wireless network >>9) Reboot Vista >>10) Vista still cannot see any wireless networks >>11) Shutdown >>12) Remove power cord and battery and wait a bit >>13) Boot Vista, and it now works and sees the network >> >>As you just eluded to, it seems that the power-down and battery >>removal is necessary >>What do you think is the culprit here? > > Unfortunately, that's how it works. I had the same problem myself. > WHen you either hibernate or shutdown Windows you need to reset the > power on you AP in order to successfully connect in Linux. > The same goes to Linux -> Windows scheme. > > My guess is that this is how the AP/DHCP/router or whatever protocol > is used in the router works. It connects the MAC address of the hardware > to the leased IP address, and until you reboot the router this connection > stays. > > Unfortunately this is far beyond the control of any wireless driver in > WiFi network card... ;-) > > Thank you. > > P.S.: Please someone correct me if I'm wrong. > >> >>This laptop is a Dell Latitude E6400 >> >>On Wed, Mar 24, 2010 at 3:24 AM, Larry Finger <larry.fin...@lwfinger.net> >>wrote: >>> On 03/23/2010 02:53 PM, Chris Lopes wrote: >>>> Thanks for the quick reply. So are you saying that it is impossible >>>> that the b43 driver could have somehow made my wireless card unable to >>>> detect any networks after a reboot (in either Windows or Linux)? >>> >>> I don't know of any way that b43 could have done that. A power-down >>> including >>> removal of the battery should completely put the device in the original >>> condition. >>> >>> Larry >>> >>_______________________________________________ >>Bcm43xx-dev mailing list >>Bcm43xx-dev@lists.berlios.de >>https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > > _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
