(old)Puppy Linux Discussion Forum

OK, fine, so I looked in the wrong place ... maybe in another decade with Puppy I will figure out the folder structure?

Here it is ...

Edoc. It looks like your broadcom is supported by wl driver. But ssb and b43 are loaded also. So...you need to try create savefile and reboot. Or....if that is not enough, blacklist ssb and b43, create savefile and reboot.

Just finished a new build of my purposefully-junky "Paper Tiger" system. Changed basically everything, of course.

Build log here --> http://hardforum.com/showthread.php?t=1772485

Runs Upup Raring 3991, here's the summary from HardInfo (taken with a camera) --



Check in the "My Puppy Is More Gorgeous..." thread shortly for a photo of the desktop

EDIT: boy, that was dumb! "Build log here" now has a link next to it...

pemasu wrote:Edoc. It looks like your broadcom is supported by wl driver. But ssb and b43 are loaded also. So...you need to try create savefile and reboot. Or....if that is not enough, blacklist ssb and b43, create savefile and reboot.

Every time I blacklist b43 and ssb and make sure wl is loaded ssb is reloaded - something somewhere keeps reloading it and over-riding my setting.

In Boot Manager - Module Preferences I see these modules appearing this way:

bcm43xx:ssb

ssb:wl

bcma:wl

ssb:bcma

Is this a meaningful variable?

Edoc. /etc/rc.d/MODULESCONFIG
Add in that file to SKIPLIST row those 2 modules more.
ssb and b43

SKIPLIST=" ssb b43 arcfb cirrusfb cyber2000fb ..........

And save. That might be enough. Reboot.

pemasu wrote:Edoc. /etc/rc.d/MODULESCONFIG
Add in that file to SKIPLIST row those 2 modules more.
ssb and b43

SKIPLIST=" ssb b43 arcfb cirrusfb cyber2000fb ..........

And save. That might be enough. Reboot.

b43 was already in that list once and ssb twice.

Edoc. Then it looks like that rerwin`s broadcom logistic file wants you to use b43.

Only solution is to remove it:
/lib/modules/all-firmware/b43/etc/modprobe.d/b43.conf

Reboot.

OK, deleted b43.conf at that location and rebooted.

No joy.

ssb and wl show in Pup Kview but no more b43.

Still, wifi that works in MS win7 doesn't work in Puppy.

Edoc. Well....ssb cant be loaded before wl. I hope that I am right with idea that wl is right module for your wireless. It would help if you would know that wl has worked with that laptop in other Puppy, but you havent at least posted so, I suppose it hasnt.

Last resort. Remove also the wl logistic file:
/lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf

And install this pet and reboot. This pet has logistic file for recognizing your chip and it should unload ssb and then load wl. It has the older logistic mechanism but it should work with your chip id.

@pemasu,edoc -- sorry to quite likely add confusion to confusion (I never like doing that), but WikiDevi (a great info source for matching drivers to wifi cards) says that the b43 driver *should* work for that chipset...

I looked at these two cards:
Dell Wireless 1397 WLAN Half Mini-Card
Dell Wireless 1395 WLAN Mini-Card

Both say to use b43.

Dunno if that helps or just adds to the mess, but I thought I'd throw it out there...

pemasu wrote:Edoc. Well....ssb cant be loaded before wl. I hope that I am right with idea that wl is right module for your wireless. It would help if you would know that wl has worked with that laptop in other Puppy, but you havent at least posted so, I suppose it hasnt.

I just stopped the process and booted from a Lucid Puppy DVD - the wifi works fine.

Edoc and Starhawk. Well. Yeah. I play with chip id`s solely.

http://wireless.kernel.org/en/users/Drivers/b43

ID: 14e4:4315

14e4:4315 b43 yes (2.6.33+), alternative wl

Both should work, at these situations, I would go for wl. But my reasoning can be faulty.

Edoc. It would help if you could post what driver worked. I suppose it was b43, but reading it from you is better than assuming.
In that case, disabling wl module loading would be the way to go. Which means opposite as we have done, and as Starhawk suggested.
Blacklisting wl, removing its logistic file, etc...

And yes. My wifi works also fine. Lol.

Sorry, was called away from my desk.

Lucid is using b43

So, since I deleted the b43.conf file ... where do I get a replacement, please?

You have backup of all your distro included files:
/initrd/pup_ro2.
Everything you remove, with frugal installation and savefile usage, are essentially only flagged as deleted. The original files are always there.
But after messing that much, I would recommend fresh start.

OK ...

Opened iso and replaced the three Frugal files, also replaced devx, just in case.

Deleted the savefile and rebooted.

I blacklisted wl and added b43 then rebooted again.

Internet Connection Wizard sees the b43 module but will not 'find' the router, neither will Frisbee.

Something in Raring is interfering that is not in Lucid.

Where should I look, please?

Edoc. To be sure...I would remove wl logistic file and also wl kernel module. Then reboot. If that does not help....then there isnt much more I can do.

in console.
rm /lib/modules/3.9.9-upup/kernel/drivers/net/wireless/wl.ko
rm /lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf

And then there isnt anymore possibility that wl.ko module interferes.

If this does not help, post pdiag tarball again after unsuccesful trial.

Your b43 chip should be supported without any problems. So...I really dont know what is wrong with this build. I think we will need spiritual session soon....

Hi Pemasu!
FInally i can try raring (only version working is 3.9.9.1). Now it works on my Fujitsu laptop laptop

But.. I have found a bug in resizepfile script (this is 0.14 version). It returns an error whatever size of personal resize file increase.

I have patched this with the script of Don570 or older script from Precise.

Can you correct next release of raring with this?
Thanks

Fabio T. Thanks of the feedback. I will check the resizepfile script. I think that I updated it but I admit that I didnt test the update.
Thanks. Will fix....

pemasu wrote:Edoc. To be sure...I would remove wl logistic file and also wl kernel module. Then reboot. If that does not help....then there isnt much more I can do.

in console.
rm /lib/modules/3.9.9-upup/kernel/drivers/net/wireless/wl.ko
rm /lib/modules/all-firmware/wl/etc/modprobe.d/wl.conf

And then there isnt anymore possibility that wl.ko module interferes.

If this does not help, post pdiag tarball again after unsuccesful trial.

Your b43 chip should be supported without any problems. So...I really dont know what is wrong with this build. I think we will need spiritual session soon....

Did it all, rebooted multiple times, no joy. Very odd.

Here's the pdiag output: