Puppy Linux Discussion Forum

paintenzero · Joined: 20 Nov 2009 Posts: 1

First of all, I'm really sorry for creating yet another thread about this wireless chipset. I found at least 5 of them and they marked as solved. Still none of them helped me.
I have Dell Inspiron 1720 and Dell 1395 Wireless Mini-card. This card has "BCM4312 802.11b/g (rev01)" chipset. And here is output of lspci: "0c:00.0 Class 0280: 14e4:4315 (rev 01)". I'm using Puppy 4.31.
I have openSuSE installed on this laptop and b43 module doesn't work with this wireless card, so I have to install package named "broadcom-wl" to make it work. I get both b43 and wl modules loaded after installation of broadcom-5.10.91.9.3-k2.6.30.5.pet package Smile

So I blacklisted b43 and have only wl loaded on start-up, but interface still doesn't show up Sad

Am I missing something? I really don't want to stop using Puppy because of this!
Thanks in advance.

P.S. Sorry for my english.

jrb · Posted: Thu 17 Dec 2009, 23:07 Post subject:

Hi paintenzero,
I had the same problem setting up a Lenovo s10-2. I got it to work using ndiswrapper as explained at http://www.murga-linux.com/puppy/viewtopic.php?p=373026#373026.

Hope it works for you as well, J

scottbg1 · Joined: 26 Dec 2009 Posts: 7

Hi jrb,

I am having the same problem too, and I have half the problem solved.

If you are like me, I prefer the STA driver over ndiswrapper.

The problem with wl working is due to module 'ssb'.

'ssb' is used by b43, b44, and another one I cant recall right now.

remove all the modules I just listed including wl, and then reload wl. You should have wireless.

rjbrewer · Joined: 22 Jan 2008 Posts: 4352 Location: merriam, kansas

jrb solved that problem much more elegantly days ago.

http://www.murga-linux.com/puppy/viewtopic.php?p=374374#374374

jrb · Posted: Sat 26 Dec 2009, 17:11 Post subject:

scottbg1,
Thanks for the reply. I ended up making a modified Puppy431 in which I removed ssb, b43 and b43legacy. It finds wl, lists it as eth1 and connects to it at boot.

Edit: .iso modified with tempestuous' new ssb.ko module 27dec09

The new iso is at http://puppylinux.ca/members/choicepup/Puppy431-broadcom4312/pup-431-bcm4312v3.iso.

Give it a try, I hope it works equally well for you.

Cheers, J

scottbg1 · Joined: 26 Dec 2009 Posts: 7

Great news jrb.

Sorry to have responded to this. It was right under my new post today and it said nothing about it being resolved so I added my 2 cents.

I actually need ssb for my ethernet card, I just need to change the order that they are loaded. So removing it isn't a solution.

Maybe Mr. Brewer can help me find a more elegant solution to my problem as well.

Happy New Year to you both.

scottbg1 · Joined: 26 Dec 2009 Posts: 7

J,

Reading back through the threads on the subject, I just now noticed that it was you who had been posting. Smile

I never much pay attention to "who" as I am to "what" when I am reading.

Again, thanks and HNY...

jrb · Posted: Sat 26 Dec 2009, 18:10 Post subject:

scottbg1,
ssb couldn't be blacklisted because it was in initrd.gz and was loaded before puppy read the skiplist.

If you take my iso and copy the ssb.ko module into the filesystem after boot then you should be able to come up with a workable solution.

I am attaching a .pet which will place it in your filesystem. I am also attaching the module info files from initrd.gz which mention ssb. They're not the same as the files in the puppy-431.sfs but may contain lines which you will need to add to those.

Good Luck, J

Edit: Attachments removed in favour of new .iso with tempestuous' modified ssb.ko module. See below

scottbg1 · Joined: 26 Dec 2009 Posts: 7

Thanks a million!!

I will try this straight away.

Scott

tempestuous · Joined: 10 Jun 2005 Posts: 4944 Location: Australia

jrb,
I suspect that loading the ssb module, regardless of whether it's contained in the initrd, will create a conflict with the Broadcom wl wifi driver.
As I mentioned in an earlier post, the only comprehensive way of dealing with this problem is to disable support for device ID's in the ssb module which overlap those of the wl module.
This is relatively straightforward, and I just did so now.

The modified ssb module has support for these Broadcom (wifi) device ID's removed:
14e4:432b
14e4:4329
14e4:4328
14e4:4315
14e4:4312
14e4:4311

In theory, this module can now be loaded without any chance of conflicting with the wl module

EDIT: dotpet attachment removed. jrb's remaster contains the modified driver. See later in this thread.

Looking at the kernel source code for this module was interesting. There's quite a range of other devices and modules which rely on this module, so removing it entirely is not a particularly good idea ...

tempestuous · Joined: 10 Jun 2005 Posts: 4944 Location: Australia

jrb, removing the ssb module from the initrd means that some users may have problems at bootup with USB interfaces, Cardbus interfaces, and PCI interfaces which depend upon it.

I suggest you could go one step further, and incorporate my modified ssb module into your initrd, and then into your ISO. If you do so, you must also replace the modules.alias file which has been accordingly modified to remove the defunct device ID's. It's located at /lib/modules/2.6.30.5/

EDIT: attachments removed.

jrb · Posted: Mon 28 Dec 2009, 02:56 Post subject:

tempestuous · Joined: 10 Jun 2005 Posts: 4944 Location: Australia

Well done.
I suggest that your remastered Puppy ISO is significant enough to deserve a separate forum thread to announce its availability, and so the information can be easily found in the future.
The thread title should make sense - something like "Puppy 4.31 modified for Broadcom wifi"
and located in "Puppy Projects" or "Cutting edge"??

EditionLocus · Joined: 21 Sep 2008 Posts: 21

rcrsn51 · Posted: Mon 05 Jul 2010, 11:05 Post subject:

The login to puppylinux.ca is "puppy" and "linux". However that ISO appears to be missing.

Maybe this will be useful to you.