No joy: Dell Mini 910, Broadcom 4312, Puppy 5

Post Reply
Message
Author
pi3832
Posts: 8
Joined: Mon 07 Dec 2009, 03:01
Location: Reserve, LA

No joy: Dell Mini 910, Broadcom 4312, Puppy 5

#1 Post by pi3832 »

I am trying to install Puppy 5 on my niece's Dell Mini 910. I have installed it to the hard drive, and it boots fine.

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:
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 ]
Here's when the wireless dies:
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 can post the entire messages if it'd be useful.)

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? :cry:

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#2 Post by rjbrewer »


Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

pi3832
Posts: 8
Joined: Mon 07 Dec 2009, 03:01
Location: Reserve, LA

#3 Post by pi3832 »

deleted

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#4 Post by rjbrewer »

username.....puppy

psswd.....linux

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#5 Post by Roy »

pi3832,

As an owner of a Puppy-ized Dell 910 myself, perhaps I can expand on what rjbrewer already (correctly) said. You will want to use version 3 instead of the version 2 rjbrewer's link refers to (same server directory). While earlier Puppies do function on the I910, I would certainly start with one of the Puppy 4.31-based versions. Earlier than that, and you start running into problems with booting while the SD card is installed in the I910 and problems with the Xorg video (must use XVesa driver). Versions 3.xx (and prior) will not do your required 1024x600 screen resolution. That resolution started at version 4.xx.

Right now, I am running Boxpup 4.31 on my own machine.

There are two other Puppies that will work with the I910, although I do not use them. One is Big Bass' Slaxer-pup (you will find the wl.ko Broadcom driver for that Puppy in the Slaxer-pup thread). The other, believe it or not, is Barry's very own Quirky 1.00. The amazing thing about Barry's Quirky 1.00 is that your Broadcom wireless will work with Quirky's B43 driver out-of-the-box (a first, to my limited knowledge).

These netbooks certainly have their place, and I think Puppy is a perfect distro to run on them.

-Roy

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#6 Post by rjbrewer »

Roy wrote:pi3832,

As an owner of a Puppy-ized Dell 910 myself, perhaps I can expand on what rjbrewer already (correctly) said. You will want to use version 3 instead of the version 2 rjbrewer's link refers to (same server directory). While earlier Puppies do function on the I910, I would certainly start with one of the Puppy 4.31-based versions. Earlier than that, and you start running into problems with booting while the SD card is installed in the I910 and problems with the Xorg video (must use XVesa driver). Versions 3.xx (and prior) will not do your required 1024x600 screen resolution. That resolution started at version 4.xx.

Right now, I am running Boxpup 4.31 on my own machine.

There are two other Puppies that will work with the I910, although I do not use them. One is Big Bass' Slaxer-pup (you will find the wl.ko Broadcom driver for that Puppy in the Slaxer-pup thread). The other, believe it or not, is Barry's very own Quirky 1.00. The amazing thing about Barry's Quirky 1.00 is that your Broadcom wireless will work with Quirky's B43 driver out-of-the-box (a first, to my limited knowledge).

These netbooks certainly have their place, and I think Puppy is a perfect distro to run on them.

-Roy
Thanks Roy; I'd forgotten the v2-v3 distinction.

I wonder if Wary 020 also works with that Broadcom card.
Did you use sns or regular wireless wizard with Quirky?

Most of the Quirkys and Lupu 500 caused black screen on
my 700m.
Wary 020 is the only o.s. (old or new) that lets me choose
xorg or vesa at different resolutions that fit my screen.
With 4.xx series I had to use xvesa, both for preferred resolution
and to have media players play with correct color rendering.
Gnome-mplayer dvd playback is the only problem I have with
Wary.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

Roy
Posts: 451
Joined: Wed 31 Dec 2008, 18:31

#7 Post by Roy »

Did you use sns or regular wireless wizard with Quirky?
I **think** I used the regular wireless wizard with Quirky... was surprised to see BCM43 loaded for my wireless and thought, 'What the heck. I'll just try it', and it worked!

Tried the same on Lupo -- but no go. Or at least the BCM43 wasn't loading by default. Wonder what the difference is (what did Barry do differently)?

-Roy

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#8 Post by rjbrewer »

Roy wrote:
Did you use sns or regular wireless wizard with Quirky?
I **think** I used the regular wireless wizard with Quirky... was surprised to see BCM43 loaded for my wireless and thought, 'What the heck. I'll just try it', and it worked!

Tried the same on Lupo -- but no go. Or at least the BCM43 wasn't loading by default. Wonder what the difference is (what did Barry do differently)?

-Roy
No way i could possibly keep up with all the changes going on in
Quirky-Loopy Lucie.....(':lol:')

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

pi3832
Posts: 8
Joined: Mon 07 Dec 2009, 03:01
Location: Reserve, LA

#9 Post by pi3832 »

Roy wrote:Right now, I am running Boxpup 4.31 on my own machine.
I booted Boxpup 431 on the Mini and I really like the window manager.

But the network wizard doesn't recognize the wireless, and none of the default available modules appear to be for Broadcom chipsets. What module are you using to get the wireless to work?

pi3832
Posts: 8
Joined: Mon 07 Dec 2009, 03:01
Location: Reserve, LA

#10 Post by pi3832 »

I tried pup-431-bcm4312v3.iso and the wireless works for open networks. Thanks.

No sound, however. :(

EDIT:
Ran the ALSA set-up, then switched from XVesa to Xorg, and sound works! :D

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#11 Post by rjbrewer »

pi3832 wrote:I tried pup-431-bcm4312v3.iso and the wireless works for open networks. Thanks.

No sound, however. :(

EDIT:
Ran the ALSA set-up, then switched from XVesa to Xorg, and sound works! :D
Glad it's working!

I looked at a Boxpup thread and Roy mentioned using cd to load
Boxpup; so I think he was referring to a different machine that he
runs Boxpup on.

When I installed 4312v3 on my neighbors Lenovo s10 we used WPA
withoutproblem.

edit;
Think I'll load up Boxpup just to get that desktop background.

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

pi3832
Posts: 8
Joined: Mon 07 Dec 2009, 03:01
Location: Reserve, LA

#12 Post by pi3832 »

rjbrewer wrote: When I installed 4312v3 on my neighbors Lenovo s10 we used WPA
withoutproblem.

edit;
Think I'll load up Boxpup just to get that desktop background.
I was trying WPA2, so that may be why it wouldn't connect. But it's not a big deal--I was trying to connect to my home network just to test things like YouTube. (My niece is 12.) At her house, there's an unsecured wireless network for the kids' various electronic toys to connect to, so WPA/WPA2 is a non-issue for this netbook.

I would still like to try Boxpup. Puppy has always been impressive in a lot of ways, but I've never liked the desktop/window manager much. Hopefully there's an easy fix for the wireless.

If not, oh well, I appear to have a working OS that doesn't fill the entire SSD. I'll test it a little more, then give it back to my niece to find out what she thinks.

Thanks, again, in advance, etcetcetc. :D

User avatar
rjbrewer
Posts: 4405
Joined: Tue 22 Jan 2008, 21:41
Location: merriam, kansas

#13 Post by rjbrewer »

Doesn't look like there will be an easy fix for earlier kernel versions.

http://www.murga-linux.com/puppy/viewto ... 821#419821

Inspiron 700m, Pent.M 1.6Ghz, 1Gb ram.
Msi Wind U100, N270 1.6>2.0Ghz, 1.5Gb ram.
Eeepc 8g 701, 900Mhz, 1Gb ram.
Full installs

pi3832
Posts: 8
Joined: Mon 07 Dec 2009, 03:01
Location: Reserve, LA

#14 Post by pi3832 »

rjbrewer wrote:Doesn't look like there will be an easy fix for earlier kernel versions.

http://www.murga-linux.com/puppy/viewto ... 821#419821
Thanks for the info/link. I appreciate it.

I should probably consider a better long-term solution: replace the wifi card. Everything else seems to be working out of the box with every flavor of Puppy I've tried.

The really sad thing is that I went through this same sort of frustration/complexity with a ThinkPad years ago. I eventually just bought an Intel something or other card, and never had to fiddle with the wireless ever again. (I'm currently running ZenWalk on that ThinkPad--but I keep an old 256 Mb USB flash drive with Puppy on it as a back-up.)

Anyway, thanks again. Puppy continues to move up in my list of preferred distros--in no small part because of y'all's help.

Post Reply