Re: BCM4312: interface does not show up
Γαλανομάτης Ιωάννης wrote: > Hi! > > My problem is that upon b43 module load, no interface shows up. > I would expect an eth1 or something from iwconfig but there are only > lo and eth0 (wired). > > I followed the instructions from the page > http://linuxwireless.org/en/users/Drivers/b43 > I "cut" the firmware and install it to the proposed directory, > exported the env var and then compiled the kernel. > > I do not know how to tell kernel to look for the extracted firmware, > there ware no instructions for such a thing. > > When I "modprobe b43" the following modules are pulled automatically: > b43 134832 0 > ssb31364 1 b43 > rng_core4744 1 b43 > mac80211 135692 1 b43 > cfg80211 25488 1 mac80211 If you have to modprobe b43 to get it to load, your device is not supported. You can verify that with an '/sbin/lspci -nnv' command, and compare the codes in the first line of the wireless device with the list of supported interfaces. For example, my unit reports "[14e4:4311]". If the device were supported, the driver would load the firmware from /lib/modules/b43 with no further input by you. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
On Sunday 16 November 2008, Yuval Hager wrote: > On Saturday 15 November 2008, Larry Finger wrote: > > > You can test this by starting only the X server and nothing else, > > > simply run the command X (one capital X) instead of startx or an init > > > script for kdm or anything else. You will get only the X server > > > running (black/white dots background) and you have to kill it with > > > Ctrl-Alt-Backspace. It would be interesting to know the results. > > > > That is a good idea. > > When I just run 'X' - nothing happens, all works fine. > When I start xdm/kdm - it dies in the same way as before. > Don't know how much helpful this is, but I also tried to run 'startx' directly, bypassing xdm/kdm. In this case, I got: Nov 16 03:07:19 happy b43-phy0: Controller RESET (DMA error) ... Nov 16 03:07:20 happy b43-phy0 ERROR: DMA RX reset timed out Nov 16 03:07:20 happy b43-phy0 ERROR: DMA TX reset timed out Nov 16 03:07:20 happy b43-phy0 ERROR: DMA TX reset timed out Nov 16 03:07:21 happy b43-phy0 ERROR: DMA TX reset timed out Nov 16 03:07:21 happy b43-phy0 ERROR: DMA TX reset timed out Nov 16 03:07:22 happy b43-phy0 ERROR: DMA TX reset timed out Nov 16 03:07:22 happy ssb: Backplane Revision 0xF000 Nov 16 03:07:22 happy [ cut here ] Nov 16 03:07:22 happy WARNING: at drivers/ssb/main.c:1042 ssb_tmslow_reject_bitmask+0x5e/0x68 [ssb]() Nov 16 03:07:22 happy Modules linked in: rfkill_input arc4 ecb b43 rfkill mac80211 cfg80211 led_class input_polldev snd_hda_intel rtc snd_pcm snd_timer snd_page_alloc snd_hwdep snd soundcore hci_usb bluetooth ssb pcmcia pcmcia_core video backlight output battery thermal ac processor button thermal_sys tg3 libphy e1000 jfs raid10 raid456 async_memcpy async_xor xor async_tx raid1 raid0 dm_bbr dm_snapshot dm_mirror dm_log dm_mod sbp2 ohci1394 ieee1394 sl811_hcd usbhid ohci_hcd uhci_hcd usb_storage ehci_hcd usbcore lpfc qla2xxx firmware_class megaraid_sas megaraid_mbox megaraid_mm megaraid aacraid sx8 DAC960 cciss cpqarray 3w_9xxx 3w_ mptsas scsi_transport_sas mptfc scsi_transport_fc scsi_tgt mptspi mptscsih mptbase atp870u dc395x sim710 53c700 qla1280 dmx3191d sym53c8xx qlogicfas408 gdth aha1740 advansys initio BusLogic arcmsr aic7xxx aic79xx scsi_transport_spi sg pdc_adma sata_inic162x sata_mv ata_piix ahci sata_qstor sata_vsc sata_uli sata_sis sata_sx4 sata_nv sata_via sata_svw sata_sil24 sata_sil sata_promise scsi_wait_scan pata_sis libata dock Nov 16 03:07:22 happy Pid: 10704, comm: b43 Not tainted 2.6.27-gentoo-r2 #3 Nov 16 03:07:22 happy [] warn_on_slowpath+0x40/0x63 Nov 16 03:07:22 happy [] __wake_up_common+0x2e/0x58 Nov 16 03:07:22 happy [] __wake_up+0x29/0x39 Nov 16 03:07:22 happy [] wake_up_klogd+0x2b/0x2d Nov 16 03:07:22 happy [] pci_write+0x1c/0x21 Nov 16 03:07:22 happy [] pci_bus_write_config_word+0x50/0x5b Nov 16 03:07:22 happy [] printk+0x14/0x18 Nov 16 03:07:22 happy [] ssb_tmslow_reject_bitmask+0x5e/0x68 [ssb] Nov 16 03:07:22 happy [] ssb_device_is_enabled+0x9/0x2d [ssb] Nov 16 03:07:22 happy [] b43_wireless_core_init+0x37/0x64e [b43] Nov 16 03:07:22 happy [] b43_chip_reset+0x38/0x84 [b43] Nov 16 03:07:22 happy [] b43_chip_reset+0x0/0x84 [b43] Nov 16 03:07:22 happy [] run_workqueue+0x6d/0xe0 Nov 16 03:07:22 happy [] worker_thread+0x0/0xbd Nov 16 03:07:22 happy [] worker_thread+0xb3/0xbd Nov 16 03:07:22 happy [] autoremove_wake_function+0x0/0x2d Nov 16 03:07:22 happy [] kthread+0x38/0x5d Nov 16 03:07:22 happy [] kthread+0x0/0x5d Nov 16 03:07:22 happy [] kernel_thread_helper+0x7/0x10 Nov 16 03:07:22 happy === Nov 16 03:07:22 happy ---[ end trace 9156cfca767d0e87 ]--- Nov 16 03:07:23 happy b43-phy0 ERROR: Microcode not responding Nov 16 03:07:23 happy b43-phy0 ERROR: You must go to http://linuxwireless.org/en/users/Drivers/b43#devicefirmware and download the latest firmware (version 4). Nov 16 03:07:23 happy b43-phy0 ERROR: Controller restart FAILED Nov 16 03:07:25 happy wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range Nov 16 03:07:25 happy dhcpcd[12900]: wlan0: carrier lost --y signature.asc Description: This is a digitally signed message part. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
On Saturday 15 November 2008, you wrote: > Yuval Hager wrote: > > Yes, It's a brand new HP Mini 2133 (HP product number FU346EA). > > the power supply is ok, and this problem is recreated exactly the same > > every time. wireless works correctly as long as I don't start X (or maybe > > it's KDE trying to reset something when it loads?) > > I booted Vista once (that came with the machine) and everything was > > working fine, so I assume the hardware is ok (but I don't have vista > > anymore). > > Yuval, what happens if you > # modprobe -r b43 && sleep 1 && modprobe b43 > > ? I can run the above command fine before I start xdm/kdm, and after that, it simply doesn't work (b43 gets loaded, but wlan0 is not identified). --y signature.asc Description: This is a digitally signed message part. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
On Saturday 15 November 2008, Larry Finger wrote: > > You can test this by starting only the X server and nothing else, > > simply run the command X (one capital X) instead of startx or an init > > script for kdm or anything else. You will get only the X server > > running (black/white dots background) and you have to kill it with > > Ctrl-Alt-Backspace. It would be interesting to know the results. > > That is a good idea. > When I just run 'X' - nothing happens, all works fine. When I start xdm/kdm - it dies in the same way as before. > > Yes. I expect it's the ABG causing problems because it isn't so well > > known. > > No, I have one of these and it works perfectly in B/G mode - even with X. > Of course, the A part doesn't work, but no problem. Any idea how do I go about debugging this? --y signature.asc Description: This is a digitally signed message part. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
BCM4312: interface does not show up
Hi! My problem is that upon b43 module load, no interface shows up. I would expect an eth1 or something from iwconfig but there are only lo and eth0 (wired). I followed the instructions from the page http://linuxwireless.org/en/users/Drivers/b43 I "cut" the firmware and install it to the proposed directory, exported the env var and then compiled the kernel. I do not know how to tell kernel to look for the extracted firmware, there ware no instructions for such a thing. When I "modprobe b43" the following modules are pulled automatically: b43 134832 0 ssb31364 1 b43 rng_core4744 1 b43 mac80211 135692 1 b43 cfg80211 25488 1 mac80211 The following *single* line is added to dmesg: Broadcom 43xx driver loaded [ Features: P, Firmware-ID: FW13 ] File versions: b43-fwcutter-011 broadcom-wl-4.150.10.5.tar.bz2 I have disabled "Select only drivers that don't need compile time external firmware" and "Prevent firmware from being built" (did not have effect) I have a HP 550 (64bit celeron) laptop with the gentoo distribution. My kernel: 2.6.27-gentoo-r2 Drivers I tried: b43, b43legacy I compile everything as a module, so if something is not listed with lsmod, it probably is not compiled at all. Output from lspci: 10:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01) Subsystem: Hewlett-Packard Company BCM4312 802.11b/g Wireless LAN Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable- Address: Data: Capabilities: [d0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <4us, L1 <64us ClockPM- Suprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSVoil- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSVoil- CESta: RxErr+ BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 21-00-5a-ff-ff-00-c2-fa Capabilities: [16c] Power Budgeting lsmod: b43 134832 0 ssb31364 1 b43 rng_core4744 1 b43 mac80211 135692 1 b43 cfg80211 25488 1 mac80211 snd_seq46848 0 snd_seq_device 6932 1 snd_seq ipv6 238952 16 i915 33536 0 drm85704 1 i915 usb_storage46976 0 fan 4096 0 snd_hda_intel 451788 1 sr_mod 14372 0 snd_pcm63628 1 snd_hda_intel ehci_hcd 33292 0 cdrom 35752 1 sr_mod uhci_hcd 22168 0 snd_timer 19848 2 snd_seq,snd_pcm snd_page_alloc 8336 2 snd_hda_intel,snd_pcm usbcore 135632 4 usb_storage,ehci_hcd,uhci_hcd snd_hwdep 7560 1 snd_hda_intel thermal18464 0 psmouse39196 0 Thank you very much for your attention. Have a nice day! ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
unsuscribe
___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
Yuval Hager wrote: > Yes, It's a brand new HP Mini 2133 (HP product number FU346EA). > the power supply is ok, and this problem is recreated exactly the same every > time. wireless works correctly as long as I don't start X (or maybe it's KDE > trying to reset something when it loads?) > I booted Vista once (that came with the machine) and everything was working > fine, so I assume the hardware is ok (but I don't have vista anymore). > > Yuval, what happens if you # modprobe -r b43 && sleep 1 && modprobe b43 ? Ehud -- Legal Disclaimer that you are now contractually bound to under all laws with no recourse: http://attrition.org/security/rants/z/disclaimers.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
Peter Stuge wrote: > Yuval Hager wrote: >> HP Mini 2133 > > I posted about the wifi in this guy a while back. It has ABG b43 > which isn't really properly supported, at least not the A part but > the reaction I got from mentioning the chipset made me not expect too > much. I don't know if the ABG can be expected to behave exactly like > the BG when not using .11a. I doubt it. Wrong - if does. The B/G part of this BCM4312 is the same as the BCM4311. I think the card you asked about (also called the BCM4312) has an LP PHY, which is not supported. >> (HP product number FU346EA). > > I just now noticed that the wifi seems to be a miniPCI card. If I > was you I would just replace it. :) One problemn is the HP BIOS whitelists PCI cards. If you plug the wrong one in, the BIOS refuses to boot. > You can test this by starting only the X server and nothing else, > simply run the command X (one capital X) instead of startx or an init > script for kdm or anything else. You will get only the X server > running (black/white dots background) and you have to kill it with > Ctrl-Alt-Backspace. It would be interesting to know the results. That is a good idea. > > Yes. I expect it's the ABG causing problems because it isn't so well > known. No, I have one of these and it works perfectly in B/G mode - even with X. Of course, the A part doesn't work, but no problem. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
Yuval Hager wrote: > HP Mini 2133 I posted about the wifi in this guy a while back. It has ABG b43 which isn't really properly supported, at least not the A part but the reaction I got from mentioning the chipset made me not expect too much. I don't know if the ABG can be expected to behave exactly like the BG when not using .11a. I doubt it. > (HP product number FU346EA). I just now noticed that the wifi seems to be a miniPCI card. If I was you I would just replace it. :) > this problem is recreated exactly the same every time. wireless > works correctly as long as I don't start X (or maybe it's KDE > trying to reset something when it loads?) You can test this by starting only the X server and nothing else, simply run the command X (one capital X) instead of startx or an init script for kdm or anything else. You will get only the X server running (black/white dots background) and you have to kill it with Ctrl-Alt-Backspace. It would be interesting to know the results. > I booted Vista once (that came with the machine) and everything was > working fine, so I assume the hardware is ok (but I don't have > vista anymore). Yes. I expect it's the ABG causing problems because it isn't so well known. I'm looking to get one of those machines too. RSN.. :) //Peter pgpgwthlfigzv.pgp Description: PGP signature ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
Wow! thanks for the prompt response. On Saturday 15 November 2008, you wrote: > Is this a new machine, or has this problem just started? Can you rule out a > hardware problem? Perhaps the power supply is flaky. Yes, It's a brand new HP Mini 2133 (HP product number FU346EA). the power supply is ok, and this problem is recreated exactly the same every time. wireless works correctly as long as I don't start X (or maybe it's KDE trying to reset something when it loads?) I booted Vista once (that came with the machine) and everything was working fine, so I assume the hardware is ok (but I don't have vista anymore). -- Yuval Hager [T] +972-77-341-4155 [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [BCM4312][kernel 2.6.27] - wireless fails after X starts
Yuval Hager wrote: > Hi, > > I am having the following situation: > System starts fine, b43 module loaded (firmware installed instructions), and > wireless works fine. After I start X, I get: > b43-phy0: Radio hardware status changed to DISABLED > wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range > > and wireless just stops. All future attempts to start it (rmmod/modprobe) > fails. > > See below the workflow, let me know if there is any info missing, or > something > you think I should try to debug this issue. > I'll be yhager on #bcm-users as well. --snip-- > After running X: > --- > > b43-phy0: Radio hardware status changed to DISABLED > wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range Normally, this message means that your radio-enable switch has been turned off. The driver cannot control this switch - it can only read the state. In your case, it looks to me as if something has taken your ssb device off-line. We are no longer getting useful info from the registers, but it is as if the reads are returning all ones. --snip-- > b43-pci-bridge :02:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24 > b43-pci-bridge :02:00.0: setting latency timer to 64 > Bluetooth: Core ver 2.13 > NET: Registered protocol family 31 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > Bluetooth: HCI USB driver ver 2.10 > usbcore: registered new interface driver hci_usb > ssb: Sonics Silicon Backplane found on PCI device :02:00.0 > Real Time Clock Driver v1.12ac > HDA Intel :80:01.0: power state changed by ACPI to D0 > HDA Intel :80:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > HDA Intel :80:01.0: setting latency timer to 64 > HDA Intel :80:01.0: PCI: Disallowing DAC for device > Marking TSC unstable due to TSC halts in idle > b43-phy0: Broadcom 4311 WLAN found > Clocksource tsc unstable (delta = -172616486 ns) > phy0: Selected rate control algorithm 'pid' > Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ] > EXT3 FS on sda3, internal journal > Unable to find swap-space signature > tg3: eth0: Link is up at 100 Mbps, full duplex. > tg3: eth0: Flow control is on for TX and on for RX. > input: b43-phy0 as /class/input/input8 > firmware: requesting b43/ucode13.fw > firmware: requesting b43/b0g0initvals13.fw > b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) > b43-pci-bridge :02:00.0: PCI: Disallowing DAC for device > b43-phy0: DMA mask fallback from 64-bit to 32-bit > Registered led device: b43-phy0::tx > Registered led device: b43-phy0::rx > Registered led device: b43-phy0::radio > wlan0: authenticate with AP 00:22:3f:18:89:5e > wlan0: authenticate with AP 00:22:3f:18:89:5e > wlan0: authenticated > wlan0: associate with AP 00:22:3f:18:89:5e > wlan0: RX AssocResp from 00:22:3f:18:89:5e (capab=0x401 status=0 aid=2) > wlan0: associated > wlan0: authenticate with AP 00:22:3f:18:89:5e > wlan0: authenticated > wlan0: associate with AP 00:22:3f:18:89:5e > wlan0: RX ReassocResp from 00:22:3f:18:89:5e (capab=0x401 status=0 aid=2) > wlan0: associated At this point, all is normal and you are connected. Below here, the entire ssb/b43 subsystem has been compromised. In particular, the code that issues the warning on an unknown backplane revision has been executed previously without a problem. Suddenly the returned value of the appropriate register has 0xF in the most significant position instead of 0x6 or 0x7 that was previously found. That is why I think that the read is returning all ones. > evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. > See http://userweb.kernel.org/~dtor/eviocgbit-bug.html > b43-phy0: Radio hardware status changed to DISABLED > wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range > b43-phy0 ERROR: DMA RX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > b43-phy0 ERROR: DMA TX reset timed out > input: b43-phy0 as /class/input/input9 > ssb: Backplane Revision 0xF000 > [ cut here ] > WARNING: at drivers/ssb/main.c:1042 ssb_tmslow_reject_bitmask+0x5e/0x68 [ssb] > () Unfortunately, I have no idea what part of X might be causing this. Perhaps Michael might have a suggestion. Is this a new machine, or has this problem just started? Can you rule out a hardware problem? Perhaps the power supply is flaky. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[BCM4312][kernel 2.6.27] - wireless fails after X starts
Hi, I am having the following situation: System starts fine, b43 module loaded (firmware installed instructions), and wireless works fine. After I start X, I get: b43-phy0: Radio hardware status changed to DISABLED wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range and wireless just stops. All future attempts to start it (rmmod/modprobe) fails. See below the workflow, let me know if there is any info missing, or something you think I should try to debug this issue. I'll be yhager on #bcm-users as well. Thanks! Versions info: - # uname -a Linux happy 2.6.27-gentoo-r2 #3 SMP Sat Nov 15 15:00:40 IST 2008 i686 VIA C7-M Processor 1600MHz CentaurHauls GNU/Linux # lspci -vvn|grep 43 -A7 00:00.4 0600: 1106:4364 Subsystem: 103c:3030 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- GSI 24 (level, low) -> IRQ 24 b43-pci-bridge :02:00.0: setting latency timer to 64 b43-phy0: Broadcom 4311 WLAN found input: b43-phy0 as /class/input/input8 firmware: requesting b43/ucode13.fw firmware: requesting b43/b0g0initvals13.fw b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-pci-bridge :02:00.0: PCI: Disallowing DAC for device b43-phy0: DMA mask fallback from 64-bit to 32-bit Registered led device: b43-phy0::tx Registered led device: b43-phy0::rx Registered led device: b43-phy0::radio wlan0: authenticate with AP 00:22:3f:18:89:5e wlan0: authenticate with AP 00:22:3f:18:89:5e wlan0: authenticated wlan0: associate with AP 00:22:3f:18:89:5e wlan0: RX AssocResp from 00:22:3f:18:89:5e (capab=0x401 status=0 aid=2) wlan0: associated wlan0: authenticate with AP 00:22:3f:18:89:5e wlan0: authenticated wlan0: associate with AP 00:22:3f:18:89:5e wlan0: RX ReassocResp from 00:22:3f:18:89:5e (capab=0x401 status=0 aid=2) wlan0: associated After running X: --- b43-phy0: Radio hardware status changed to DISABLED wlan0: No ProbeResp from current AP 00:22:3f:18:89:5e - assume out of range and: # iwconfig wlan0 wlan0 IEEE 802.11bg ESSID:"NETGEAR" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 so I try: # /etc/init.d/net.wlan0 restart * Caching service dependencies ... [ ok ] * Stopping wlan0 * Bringing down wlan0 * Stopping dhcpcd on wlan0 ... [ ok ] * Shutting down wlan0 ... [ ok ] * Starting wlan0 SIOCSIFFLAGS: No such device SIOCSIFFLAGS: No such device SIOCSIFFLAGS: No such device * Configuring wireless network for wlan0 * Failed to configure wireless for wlan0 [ !! ] something is different in /proc/interrupts: # cat /proc/interrupts CPU0 0: 370543 IO-APIC-edge timer 1: 70 IO-APIC-edge i8042 8: 2 IO-APIC-edge rtc 9: 3720 IO-APIC-fasteoi acpi 12:132 IO-APIC-edge i8042 14: 0 IO-APIC-edge ide0 15: 0 IO-APIC-edge ide1 16: 42430 IO-APIC-fasteoi eth0 17:503 IO-APIC-fasteoi HDA Intel 20: 0 IO-APIC-fasteoi uhci_hcd:usb2 21: 11736 IO-APIC-fasteoi sata_via, ehci_hcd:usb1, uhci_hcd:usb3 23: 0 IO-APIC-fasteoi uhci_hcd:usb4 24: 34154 IO-APIC-fasteoi NMI: 0 Non-maskable interrupts LOC: 2098 Local timer interrupts RES: 0 Rescheduling interrupts CAL: 0 function call interrupts TLB: 0 TLB shootdowns TRM: 0 Thermal event interrupts SPU: 0 Spurious interrupts ERR: 0 MIS: 0 full dmesg output below: # dmesg gsi_base[0]) IOAPIC[0]: apic_id 1, version 3, address 0xfec0, GSI 0-23 ACPI: IOAPIC (id[0x02] address[0xfecc] gsi_base[24]) IOAPIC[1]: apic_id 2, version 3, address 0xfecc, GSI 24-47 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 2 I/O APICs Using ACPI (MADT) for SMP configuration information SMP: Allowing 1 CPUs, 0 hotplug CPUs mapped APIC to b000 (fee0) mapped IOAPIC to a000 (fec0) mapped IOAPIC to
