Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
On Tue, 23 Mar 2010 23:37:45 +0100 Gábor Stefanik wrote: >(On 2.6.33, b43 works around this by falling back to PIO.) I think it requires 2.6.34 for this (currently 2.6.34-rc2). Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
On Tue, Mar 23, 2010 at 11:23 PM, Chris Lopes wrote: > I didn't try a "cold reboot" that did not involve the removal of > battery and power supply, so maybe it would work. > > Honestly I am still perplexed (given modern hardware and software), as > to why/how: > 1) Hibernate and un-hibernate, regardless of what happens in between > with the wireless card, could somehow result in it stopping working > 2) Rebooting (warm), regardless of how the wireless card is messed up > in my situation does not fix the problem > 3) Cold rebooting and warm rebooting are different in any way whatsoever > > (all of the above involve zero changes on the hard disk during the > time when the OS is not running) > > Is this behavior some sort of "feature" with unintuitive results, or > is it a bug? And what is the buggy component, exactly? > It seems like something that would happen with early 1990's technology. > > Also, are you saying that there is some sort of known problem that > results in you having to "recover the wireless" via a cold-reboot? > What is this problem and is it similar to my situation? Well, the following sequence can easily happen: 1. You boot Vista. The Broadcom official driver initializes the card (writing a complete register setup) with the embedded firmware. 2. You hibernate Vista. The card is un-initialized and prepared for restore upon return from hibernation. Some registers are left in the state they were originally, to aid in quicker restore. 3. You boot Linux. b43 finds the Broadcom card, and, seeing that it is un-initialized, quickly initializes it (again, overwriting all registers, including the ones left intact by hibernation) with your installed firmware. Due to a known bug, the driver misses some part of the initialization routine; we are working on fixing this,. 4. With the card only partially initialized, DMA TX is broken. (On 2.6.33, b43 works around this by falling back to PIO.) 5. You leave Linux. b43 either doesn't uninitialize the card at all, or does a full uninit, in preparation for a shutdown (as opposed to hibernate) 6. You restore Vista. The Broadcom driver expects the card to be in the state it left it during hibernation; but it is really either in the (broken) init state produced by Linux, or completely uninitialized. The driver does a resume routine, assuming the card is prepared for it. The result of this operation is completely undefined; as my college programming professor once said: "even if it becomes self-aware and nukes the world, it is still operating correctly". 7. You scan for wireless networks. The card is in an undefined state, so this obviously doesn't work! -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
I didn't try a "cold reboot" that did not involve the removal of battery and power supply, so maybe it would work. Honestly I am still perplexed (given modern hardware and software), as to why/how: 1) Hibernate and un-hibernate, regardless of what happens in between with the wireless card, could somehow result in it stopping working 2) Rebooting (warm), regardless of how the wireless card is messed up in my situation does not fix the problem 3) Cold rebooting and warm rebooting are different in any way whatsoever (all of the above involve zero changes on the hard disk during the time when the OS is not running) Is this behavior some sort of "feature" with unintuitive results, or is it a bug? And what is the buggy component, exactly? It seems like something that would happen with early 1990's technology. Also, are you saying that there is some sort of known problem that results in you having to "recover the wireless" via a cold-reboot? What is this problem and is it similar to my situation? On Wed, Mar 24, 2010 at 5:03 AM, Chris Vine wrote: > On Wed, 24 Mar 2010 03:31:42 +0700 > Chris Lopes wrote: >> 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? > > I have never had to do anything with my netbook to recover the > wireless with the 2.6.32 kernel other than to shutdown the netbook down > and then switch the netbook on again. It has never been necessary to > disconnect the battery. A warm reboot however has never been > sufficient to recover the wireless. > > I am not saying that your laptop might not be different, but if you do a > proper shutdown which actually switches the laptop off followed by a > switch on (cold boot), rather than a restart (warm boot), then if it > follows my experience then it should be OK. > > Chris > > > ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
On Wed, 24 Mar 2010 03:31:42 +0700 Chris Lopes wrote: > 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? I have never had to do anything with my netbook to recover the wireless with the 2.6.32 kernel other than to shutdown the netbook down and then switch the netbook on again. It has never been necessary to disconnect the battery. A warm reboot however has never been sufficient to recover the wireless. I am not saying that your laptop might not be different, but if you do a proper shutdown which actually switches the laptop off followed by a switch on (cold boot), rather than a restart (warm boot), then if it follows my experience then it should be OK. Chris ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
Hi, Chris, -Original Message- >From: Chris Lopes >Sent: Mar 23, 2010 4:31 PM >To: Larry Finger >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 >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
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
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 : > Hi, Chris, > > > -Original Message- >>From: Chris Lopes >>Sent: Mar 23, 2010 4:31 PM >>To: Larry Finger >>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 >>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
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
What does (or might) "Wake On LAN" have to do with this problem, exactly? 2010/3/24 Larry Finger : > On 03/23/2010 03:31 PM, Chris Lopes wrote: >> 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? > > You should never hibernate one OS and run a different one. That is a > prescription for disaster. Although there is nothing in the BCM4312 that can > be > changed, Vista could set a given state in the BIOS that is destroyed by > booting > Linux. Fortunately, this info seems to be in volatile memory, thus the power > off > and battery removal fixes it. > > You might look at the BIOS settings to see if there is a "Wake On LAN" option > for the wireless. It should be off. > > Larry > ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
On 03/23/2010 03:31 PM, Chris Lopes wrote: > 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? You should never hibernate one OS and run a different one. That is a prescription for disaster. Although there is nothing in the BCM4312 that can be changed, Vista could set a given state in the BIOS that is destroyed by booting Linux. Fortunately, this info seems to be in volatile memory, thus the power off and battery removal fixes it. You might look at the BIOS settings to see if there is a "Wake On LAN" option for the wireless. It should be off. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
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? This laptop is a Dell Latitude E6400 On Wed, Mar 24, 2010 at 3:24 AM, Larry Finger 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
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
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
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
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)? On Wed, Mar 24, 2010 at 2:46 AM, Larry Finger wrote: > On 03/23/2010 02:30 PM, Chris Lopes wrote: >> Hi, >> >> I had a perfectly working Dell system running Windows Vista and using >> version 5.60.188.1 of the Broadcom windows driver (distributed by >> Dell) for what Windows calls the "Dell Wireless 1397 WLAN Mini-Card", >> which is actually 14e4:4315. >> >> I booted Parted Magic 4.9 from a USB flash drive, which uses the >> 2.6.32 linux kernel. >> I started up networking in Parted Magic and asked it to configure the >> wireless driver. >> >> At first it found my normal SSID and I asked it to try to connect, but >> it failed. I thought this was just a transient issue specific to >> Parted Magic and/or linux. >> >> So I booted bank into Vista, only to see that although Vista reports >> everything as being fine with the card, no wireless networks are ever >> detected. I have verified that the wireless networks that I expect >> indeed exist and are in range (the machine has not moved). >> >> Is it possible that the b43 driver somehow corrupted the firmware/ROM >> of my card such that it does not function correctly? Can I fix this? >> There is a DMA error (also shown below in context): b43-phy0 ERROR: >> Fatal DMA error: 0x0400, 0x, 0x, 0x, >> 0x, 0x > > No, b43 did not corrupt your firmware. The firmware is not contained in > non-volatile memory. With a power-down, it goes away. There is an EEPROM > containing some initial values, but changing that requires specific actions > through the sysfs, and does not happen accidentally. The wl and Windows > drivers > have the firmware embedded in the driver. For copyright reasons, we cannot do > that, which is why there is external firmware. > > Your DMA error is a known problem with 14e4:4315 devices with Netbooks and > some > other systems with Intel processors and a Phoenix BIOS. Again, we have no fix. > With a 2.6.33 kernel, the system will seamlessly switch to PIO mode when the > fatal DMA error occurs. > > Larry > > ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
On 03/23/2010 02:30 PM, Chris Lopes wrote: > Hi, > > I had a perfectly working Dell system running Windows Vista and using > version 5.60.188.1 of the Broadcom windows driver (distributed by > Dell) for what Windows calls the "Dell Wireless 1397 WLAN Mini-Card", > which is actually 14e4:4315. > > I booted Parted Magic 4.9 from a USB flash drive, which uses the > 2.6.32 linux kernel. > I started up networking in Parted Magic and asked it to configure the > wireless driver. > > At first it found my normal SSID and I asked it to try to connect, but > it failed. I thought this was just a transient issue specific to > Parted Magic and/or linux. > > So I booted bank into Vista, only to see that although Vista reports > everything as being fine with the card, no wireless networks are ever > detected. I have verified that the wireless networks that I expect > indeed exist and are in range (the machine has not moved). > > Is it possible that the b43 driver somehow corrupted the firmware/ROM > of my card such that it does not function correctly? Can I fix this? > There is a DMA error (also shown below in context): b43-phy0 ERROR: > Fatal DMA error: 0x0400, 0x, 0x, 0x, > 0x, 0x No, b43 did not corrupt your firmware. The firmware is not contained in non-volatile memory. With a power-down, it goes away. There is an EEPROM containing some initial values, but changing that requires specific actions through the sysfs, and does not happen accidentally. The wl and Windows drivers have the firmware embedded in the driver. For copyright reasons, we cannot do that, which is why there is external firmware. Your DMA error is a known problem with 14e4:4315 devices with Netbooks and some other systems with Intel processors and a Phoenix BIOS. Again, we have no fix. With a 2.6.33 kernel, the system will seamlessly switch to PIO mode when the fatal DMA error occurs. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
14e4:4315 (Dell Wireless 1397) cannot find networks after use of b43 driver
Hi, I had a perfectly working Dell system running Windows Vista and using version 5.60.188.1 of the Broadcom windows driver (distributed by Dell) for what Windows calls the "Dell Wireless 1397 WLAN Mini-Card", which is actually 14e4:4315. I booted Parted Magic 4.9 from a USB flash drive, which uses the 2.6.32 linux kernel. I started up networking in Parted Magic and asked it to configure the wireless driver. At first it found my normal SSID and I asked it to try to connect, but it failed. I thought this was just a transient issue specific to Parted Magic and/or linux. So I booted bank into Vista, only to see that although Vista reports everything as being fine with the card, no wireless networks are ever detected. I have verified that the wireless networks that I expect indeed exist and are in range (the machine has not moved). Is it possible that the b43 driver somehow corrupted the firmware/ROM of my card such that it does not function correctly? Can I fix this? There is a DMA error (also shown below in context): b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x, 0x, 0x, 0x Please help I booted back into Parted Magic and got this info from uname, dmesg, and lspci: uname: Linux PartedMagic 2.6.32.9-pmagic #3 SMP Fri Mar 12 15:53:22 CST 2010 i686 GNU/Linux lspci: 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4 :4315] (rev 01) Subsystem: Dell Wireless 1397 WLAN Mini-Card [1028:000c] Flags: bus master, fast devsel, latency 0, IRQ 7 Memory at f1ffc000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 83-42-5f-ff-ff-53-00-22 Capabilities: [16c] Power Budgeting Kernel driver in use: b43-pci-bridge Kernel modules: ssb dmesg: b43-pci-bridge :0c:00.0: PCI INT A -> Link[LNKB] -> GSI 7 (level, low) -> IRQ 7 b43-pci-bridge :0c:00.0: setting latency timer to 64 b43-phy0: Broadcom 4312 WLAN found (core revision 15) Registered led device: b43-phy0::tx Registered led device: b43-phy0::rx Registered led device: b43-phy0::radio b43 ssb0:0: firmware: requesting b43/ucode15.fw b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-phy0 ERROR: Fatal DMA error: 0x0400, 0x, 0x, 0x, 0x, 0x b43-phy0: Controller RESET (DMA error) ... b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-phy0: Controller restarted (followed by repeated errors with the same messages) Thanks ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
