BCM4312 and Puppy431 on Lenovo s10-2 [SOLVED]

Message
Author
User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#41 Post by mikeb »

Ah ha...well I'm not the compile king (did make a working wl.ko though :D )

So basically one to be incorporated into newer puppy releases as from what I understood this approach keeps everything compatible.

Nice work all...lots of puppy users with broadcom devices :)

Hope holidays went well

mike

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

#42 Post by rjbrewer »

Did an upgrade of the v2 full install with v3. Works fine and
long count of usb modules is gone. Very nice.

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

jojonouvo
Posts: 53
Joined: Mon 10 Mar 2008, 14:57

#43 Post by jojonouvo »

Hi all, after too many hours with no results I'm asking your help. I have a broadcom pcmcia WPCB-104GB and puppy 431.
My kernel is 2.6.30.5
I can see ssb when I do lsmod but there's no wl.
The card seems to be recognised:
# pccardctl ident
Socket 0:
product info: "Broadcom", "802.11g PCMCIA", "8.0", ""
manfid: 0x02d0, 0x0425
function: 6 (network)
# pccardctl status
Socket 0:
3.3V 16-bit PC Card
Subdevice 0 (function 0) [unbound]
I don't know if that helps but I have this as well:
# lspci
00:00.0 Class 0600: 1002:cab0 (rev 13)
00:01.0 Class 0604: 1002:700f (rev 01)
00:02.0 Class 0c03: 10b9:5237 (rev 03)
00:06.0 Class 0401: 10b9:5451 (rev 02)
00:07.0 Class 0601: 10b9:1533
00:08.0 Class 0703: 10b9:5457
00:0a.0 Class 0607: 1217:6972
00:10.0 Class 0101: 10b9:5229 (rev c4)
00:11.0 Class 0680: 10b9:7101
00:12.0 Class 0200: 100b:0020
01:05.0 Class 0300: 1002:4336
# iwconfig
lo no wireless extensions.

eth0 no wireless extensions.
I tried everything I could read in the forums but never got to see anything but the eth0 in the connection manager.
The problem seems to be solved with jrb's iso but I don't want to reinstall my puppy again, what's left?
Thanx for your help.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#44 Post by tempestuous »

jojonouvo wrote:The problem seems to be solved with jrb's iso
No, not necessarily.
jojonouvo wrote:# pccardctl ident
Socket 0:
product info: "Broadcom", "802.11g PCMCIA", "8.0", ""
manfid: 0x02d0, 0x0425
Wow. That device ID is hard to identify. Googling indicates it's a Freebox WPCB-152G, which is possibly a rebranded Belkin F5D7010. The device ID 02d0:0425 is not generally recognised, which might explain the problem. But it should be supported by the standard b43 driver already in Puppy.

1. First check check if the b43 module has automatically loaded

Code: Select all

lsmod
2a. if you don't see b43 listed, try loading it manually

Code: Select all

modprobe b43
2b. or if you see b43 listed, unload/reload it -

Code: Select all

rmmod b43
modprobe b43
3. now check if a second (wifi) interface has been created with -

Code: Select all

ifconfig -a

jojonouvo
Posts: 53
Joined: Mon 10 Mar 2008, 14:57

#45 Post by jojonouvo »

Thank you tempestuous, it is a freebox card.
b43 module doesn't automatically load, but I can load it:
# modprobe b43
# lsmod
Module Size Used by
b43 127240 0
rfkill 10672 1 b43
mac80211 166056 1 b43
cfg80211 64972 2 b43,mac80211
led_class 4112 1 b43
input_polldev 3764 1 b43
usbhid 26112 0
wl 1275072 0
lib80211 6416 1 wl
...
Then I can see lo:
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:C0:9F:13:2A:A5
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:388 errors:0 dropped:0 overruns:0 frame:0
TX packets:381 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:237637 (232.0 KiB) TX bytes:64148 (62.6 KiB)
Interrupt:11 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
And still nothing else than eth0 in the connection manager. I tried to load b43 from the manager but it didn't find the card. I also rmmod wl which brought no change and tried to rmod ssb but was told that:
# rmmod ssb
ERROR: Module ssb is in use by b43,ohci_hcd
Now here's a tough puppy challenge for me, what's missing?

jojonouvo
Posts: 53
Joined: Mon 10 Mar 2008, 14:57

#46 Post by jojonouvo »

Any new hint in 2010?

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#47 Post by mikeb »

Erm..I think this discussion drifted onto another thread or the email notification never got sent

mike

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#48 Post by tempestuous »

jojonouvo wrote:# lsmod
Module Size Used by
b43 127240 0
...
wl 1275072 0
Both the b43 and wl modules are loaded, and this will obviously create a conflict. It might (?) be possible to unload the wl module, but then it's likely that the b43 needs to be unloaded/reloaded.

You could possibly set PREFLIST in BootManager to use the b43 in preference to wl, but the PREFLIST function only works properly after applying a certain hotfix ... and I'm not sure if jrb's version of Puppy includes this hotfix
... it's getting too confusing.

The best thing to do would be to go back to Puppy 4.3.1 and try to load the b43 module in an environment where the wl module is not installed.

jojonouvo
Posts: 53
Joined: Mon 10 Mar 2008, 14:57

#49 Post by jojonouvo »

Thanx tempestuous, I'm using the original Puppy 4.3.1, not jrb's version.
I'm able to unload wl and then load b43 but what should I do next?
The wizard still doesn't see eth1..

By the way, tell me if you think I should buy a card that's known to work, it's cheap and maybe we wouldn't need to bother that much on broacom.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#50 Post by tempestuous »

jojonouvo wrote:I'm able to unload wl and then load b43 but what should I do next?
Well let's double-check this: the b43 module can only load successfully once the wl module has been unloaded.
So if they're both loaded, then you must unload both, then reload the b43 module.

Then check if a new (wifi) interface has been created with

Code: Select all

ifconfig -a
If no new interface, then run this diagnostic command

Code: Select all

dmesg
and look for clues about how the b43 module loaded.

jojonouvo wrote:if you think I should buy a card that's known to work, it's cheap and maybe we wouldn't need to bother that much on broacom.
Yes, this would be the ideal solution. Broadcom wifi devices have an unhappy history with Linux, and Broadcom has still not fully released its source code (the proprietary driver includes a closed-source binary file).
The situation becomes worse when vendors like Dell and HP mess with the hardware specs.
And in your situation, we're dealing with an "oddball" model.

I'm not up to date with current wifi adaptors, but generally the Ralink-based miniPCI and Cardbus devices are well regarded.

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#51 Post by mikeb »

If its the original puppy and you have added wl which is what I'm seeing then ssb will still be in there conflicting with wl.ko and the b43 is not happy with your card as otherwise why have the wl module in the first place. so
rmmod b43
and
rmmod ssl
modproble wl

as per the way with the original setup.

mike

jojonouvo
Posts: 53
Joined: Mon 10 Mar 2008, 14:57

#52 Post by jojonouvo »

mikeb wrote:If its the original puppy and you have added wl which is what I'm seeing then ssb will still be in there conflicting with wl.ko and the b43 is not happy with your card as otherwise why have the wl module in the first place. so
rmmod b43
and
rmmod ssl
modproble wl

as per the way with the original setup.

mike
Yes I managed to disable ssb when I tried the commands.

Well let's double-check this: the b43 module can only load successfully once the wl module has been unloaded.
So if they're both loaded, then you must unload both, then reload the b43 module.

Then check if a new (wifi) interface has been created with
Code:
ifconfig -a


If no new interface, then run this diagnostic command
Code:
dmesg

and look for clues about how the b43 module loaded.
ifconfig -a gave:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
and dmesg:
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x200-0x207 0x220-0x22f 0x330-0x337 0x388-0x38f
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff: clean.
pcmcia 0.0: pcmcia: registering new device pcmcia0.0
eth0: remaining active for wake-on-lan
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See http://userweb.kernel.org/~dtor/eviocgbit-bug.html
cfg80211: Using static regulatory domain info
cfg80211: Regulatory domain: US
(start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
(2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
(5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
cfg80211: Calling CRDA for country: US
Broadcom 43xx driver loaded [ Features: PMLR, Firmware-ID: FW13 ]

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#53 Post by mikeb »

Well that shows the b43 loaded but you say it does not work so why not try the wl since you have it there but b43 and ssb need removing first.

mike

lowcam
Posts: 3
Joined: Sat 20 Jun 2009, 13:44

#54 Post by lowcam »

JRB, thanks for the iso!!! I have an s10e that I have had problems with connecting to my WPA2 router. The iso worked great! Thank you!!!

Wognath
Posts: 423
Joined: Sun 19 Apr 2009, 17:23

Thanks

#55 Post by Wognath »

Thanks for making the iso file available, jrb. Wireless now works perfectly on my Lenovo S12, with WPA2.

User avatar
daftdog
Posts: 120
Joined: Thu 22 Jun 2006, 00:47
Location: Western Australia

Thanx, jrb

#56 Post by daftdog »

Thanks for the bcm4312 iso, jrb. Bought an old laptop (Acer Extensa) on ebay for parts only to find it had the BCM94312MCG wireless chip. Tried several flavours of Puppy and a few workarounds before loading your iso. Now working flawlessly.
Even lets me turn off wireless with the button on the front of the laptop (something I've never had work before using Puppy)!
"We are monkeys with money and guns." Tom Waits

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#57 Post by mikeb »

You must have done something right jrb...you will not be popular :lol:

mike

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

Wireless almost solved but not quite there

#58 Post by eponyn »

I've been following this thread and a few others to get the wireless working on my Aspire One D150 and jbr's ISO is the closest to a solution that I've found. I went through the network wizard and it detected my wireless card as eth0. I was able to scan and see the networks around me. I selected my home network, entered the WEP key and DHCP has got the IP address successfully.
For some reason though, all software that requires internet says that it can not find a connection (browser, irc, puppy package manager).
Blinky says that is connected and that is receiving and sending.

ifconfig shows eth0 with inet addr:169.254.63.182
when connected with wired eth1 inet addr:192.168.1.3

I can ping my router with wired but not with wireless connection it returns nothing.

Any ideas? please?

User avatar
eponyn
Posts: 31
Joined: Mon 24 Jul 2006, 08:36

#59 Post by eponyn »

Nevermind. Found the problem. My Netgear router seemed to be having problems with identifying the card. I updated it's firmware and now it works like a charm. Thanks for making this ISO!

DaDrivel
Posts: 8
Joined: Sat 02 Oct 2010, 13:32

#60 Post by DaDrivel »

Hi there,

as you might guess, i had issues with my Dell Wireless 1395 Card.
After reading through this thread, i got it fixed with blocking the ssb-Module in the Boot-Parameters and using the pup_event_backend_modprobe_fix_to_p43x-1.pet script.
I just didn't really get, why the script is necessary and what exactly it is doing. And if there might be another way to block the ssb-module (maybe even uninstall it)
The reason why I ask this questions is, that since i used to be Windowsuser, I know that every time i changed something in Windows it became slower.

I hope you can take your time so that I learn more about this =)

Thanks,
DaDrivel

Post Reply