Puppy Linux Discussion Forum

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

Yeah, even with rerwin's modules-preference fix, I think that a preference setting for the wl module will fail to override ssb in kernel 2.6.30.5 Puppies because the ssb module is contained in the initrd.

If you're going to remaster Puppy with ssb removed from the initrd, you might as well go all the way and remove ssb/b43/b43legacy from the /lib/modules/2.6.30.5 directory as well.

mikeb · Joined: 23 Nov 2006 Posts: 4378

That poses the question ... is the ssb module only for broadcom then ?

If so then an either one or the other situation would make sense

regards

mike

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

I recall that Barry added the ssb module to the initrd to support a particular PCMCIA-USB adapter during initial boot, in order to boot to this USB interface. The only place I can find reference to it is here -
http://bkhome.org/blog/?viewDetailed=00160

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

I just had a thought - what about blacklisting the ssb module as a boot parameter?
That would avoid having to modify the initrd.

Try this - to the "kernel" line of your /boot/grub/menu.lst file, add a space, then this -

mikeb · Joined: 23 Nov 2006 Posts: 4378

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

Yes, the ssb module relates to an interface made by Broadcom, not just Broadcom wifi devices.

If you were unlucky enough to have a Broadcom wifi device which requires the proprietary wl driver,
plus another device which requires the ssb driver, then you would be in trouble ...

... but there's still hope if you're determined to find a solution!

I just checked the device ID's listed by ssb and wl.
The ssb module supports 15 device ID's, of which 6 overlap those claimed by the wl module.

It would be possible to hack the ssb module so that it no longer claims those 6 overlapping ID's.
Then the ssb module and wl module could be loaded at the same time without conflicting with each other.

Roy · Joined: 31 Dec 2008 Posts: 436

jrb,

Yes, pizzasgood's FSCK fix is the one I was thinking of.... you beat me to the search.

The only other change I might suggest is to overwrite Puppy 4.31's partition viewer with the Partview.pet found on this page: ttp://www.murga-linux.com/puppy/viewtopic.php?t=47563&start=45&sid=0b514e3db3291c4702fe1ea8f9523870

It seems a bit more intuitive than the original default (well, to me at least).

-Roy

jrb · Posted: Mon 21 Dec 2009, 16:32 Post subject:

mikeb · Joined: 23 Nov 2006 Posts: 4378

Roy · Joined: 31 Dec 2008 Posts: 436

I seem to remember past Puppy posts where a blacklisted ssb would not stay blacklisted....
Going through my notes, I see:

jrb · Posted: Tue 22 Dec 2009, 02:39 Post subject:

My pup-431-bcm4312v3.iso is uploaded at http://puppylinux.asia/members/choicepup/Puppy431-broadcom4312/. (Thanks Caneri)

Edit: I have changed the .iso with the addition of tempestuous' modified ssb.ko module which does not conflict with bcm4312 wifi card. 27dec09

It comes with the wl.ko driver for broadcom4312 wireless cards and has been stripped of ssb.ko, b43.ko and b43legacy.ko.

I have successfully booted and used it on a Lenovo s10-2 from cd, usb and frugal.

One very important note: When running frugal do not include "nosmp" on the kernel line in menu.1st. This crippled my system giving very poor performance.

Hope it works well for you, J

mikeb · Joined: 23 Nov 2006 Posts: 4378

Jrb ensures the 'nosmp' gets picked up by google Very Happy

.

Just wanted to add that I use wl even though b43 did work it disconnect when transffering files over a lan..it actually behaved ofor internet use.

As for ssb....perhaps a crude option for a wl pet would be to rename the module with a warning of what it may affect.

mike

Roy · Joined: 31 Dec 2008 Posts: 436

jrb,

Got it -- many thanks!

Attempted to use Puppy's BootFlash USB installer to put it onto a thumbdrive, but wound up with a non-bootable stick; tried G-Parted -- same thing. This must be a Puppy 4.31 thing, as the problem exists on all 4.31-based puppies.

Ended up using Quirky-002 to get it onto the thumbdrive -- and still had to copy the 431wl.sfs over manually, as it did not copy during the automated installation process.

Having said that, it works fine (providing further formatting is not required) -- and I am extremely grateful for your efforts!

-Roy

EDIT: If anybody is wondering, adjusting the PCM level with Menu > Multimedia > Zmixer audio mixer did not work for me until I loaded the 431wl.sfs via the bootmanager and rebooted with a save file.

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

jrb

It works in my neighbors s10e ideapad! He's very impressed.

Ran into a problem when I tried using the universal installer
to do a full, frugal or usb install. Got this message:

jrb · Posted: Tue 22 Dec 2009, 17:46 Post subject:

Oh my,

I thought I was being so clever when I changed the distro version to pup-431wl so that it wouldn't grab regular pup-431.sfs off the hard drive at boot. Looks like I opened the proverbial "can of worms". I notice the remaster script on mine is broken as well.

I'll change the distro version in initrd.gz back to pup-431 and re-upload. Version two coming up.