When I try to connect to wireless, the first scan works fine, properly identifying the networks available. It will not connect, however. And after that, the scan no longer works.
I've tried NDISWRAPPER with a couple of drivers from the Dell support website, but they don't even recognized the card. The only module that will recognize the card is B43.
This is a selection of the messages file from the boot sequence:
Here's when the wireless dies:May 17 23:37:50 puppypc user.notice kernel: Linux version 2.6.33.2 (root@puppypc) (gcc version 4.3.4 (GCC) ) #1 SMP Mon Apr 5 12:55:04 Local time zone must be set--see zic m
May 17 23:37:50 puppypc user.info kernel: i801_smbus 0000:00:1f.3: PCI INT B -> GSI 19 (level, low) -> IRQ 19
May 17 23:37:50 puppypc user.err kernel: ACPI: I/O resource 0000:00:1f.3 [0x18a0-0x18bf] conflicts with ACPI region SMBI [0x18a0-0x18af]
May 17 23:37:50 puppypc user.info kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 17 23:37:50 puppypc user.info kernel: b43-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
May 17 23:37:50 puppypc user.debug kernel: b43-pci-bridge 0000:03:00.0: setting latency timer to 64
May 17 23:37:50 puppypc user.debug kernel: ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
May 17 23:37:50 puppypc user.debug kernel: ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
May 17 23:37:50 puppypc user.debug kernel: ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
May 17 23:37:50 puppypc user.debug kernel: ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
May 17 23:37:50 puppypc user.info kernel: ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
May 17 23:37:50 puppypc user.info kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
May 17 23:37:50 puppypc user.info kernel: r8169 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
May 17 23:37:50 puppypc user.debug kernel: r8169 0000:04:00.0: setting latency timer to 64
May 17 23:37:50 puppypc user.debug kernel: r8169 0000:04:00.0: irq 27 for MSI/MSI-X
May 17 23:37:50 puppypc user.info kernel: eth0: RTL8102e at 0xf825a000, 00:24:e8:b2:41:fd, XID 04a00000 IRQ 27
May 17 23:37:50 puppypc user.info kernel: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 17 23:37:50 puppypc user.info kernel: (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
May 17 23:37:50 puppypc user.info kernel: (2457000 KHz - 2482000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
May 17 23:37:50 puppypc user.info kernel: (2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
May 17 23:37:50 puppypc user.info kernel: (5170000 KHz - 5250000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
May 17 23:37:50 puppypc user.info kernel: (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
May 17 23:37:50 puppypc user.info kernel: b43-phy0: Broadcom 4312 WLAN found (core revision 15)
May 17 23:37:50 puppypc user.debug kernel: phy0: Selected rate control algorithm 'minstrel'
May 17 23:37:50 puppypc user.info kernel: Registered led device: b43-phy0::tx
May 17 23:37:50 puppypc user.info kernel: Registered led device: b43-phy0::rx
May 17 23:37:50 puppypc user.info kernel: Registered led device: b43-phy0::radio
May 17 23:37:50 puppypc user.info kernel: Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
(I can post the entire messages if it'd be useful.)May 17 23:48:17 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/ucode15.fw
May 17 23:48:17 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
May 17 23:48:17 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
May 17 23:48:17 puppypc user.info kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
May 17 23:48:27 puppypc user.err kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
May 17 23:48:27 puppypc user.err kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
May 17 23:48:27 puppypc user.err kernel: b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
May 17 23:49:48 puppypc user.debug kernel: wlan0: direct probe to AP 00:18:39:98:01:cc (try 1)
May 17 23:49:48 puppypc user.debug kernel: wlan0: direct probe to AP 00:18:39:98:01:cc (try 1)
May 17 23:49:48 puppypc user.debug kernel: wlan0: direct probe to AP 00:18:39:98:01:cc (try 1)
May 17 23:49:48 puppypc user.debug kernel: wlan0: direct probe to AP 00:18:39:98:01:cc (try 2)
May 17 23:49:49 puppypc user.debug kernel: wlan0: direct probe to AP 00:18:39:98:01:cc (try 3)
May 17 23:49:49 puppypc user.debug kernel: wlan0: direct probe to AP 00:18:39:98:01:cc timed out
May 17 23:50:17 puppypc user.info kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
May 17 23:50:23 puppypc user.err kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
May 17 23:50:23 puppypc user.err kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
May 17 23:50:23 puppypc user.err kernel: b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
I've skimmed through the thread "Extras for Puppy 4.3 with 2.6.30.5 kernel" by tempestuous, since there's a lot on the Broadcom drivers/modules in it. But I didn't want to start trying any of that on Puppy 5, since I have no idea if any of it is still relevant to the new release, or kernel 2.6.33.2.
Is there an easy fix I'm not seeing?
Should I post this in a different sub-forum/thread?
Do I really have to go back to the bloated, Dell-ified Ubuntu distro?