PuppyThis forum is for the discussion of Puppy Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 386
Rep:
Wifi Networking Dies on Restart
Installed latest Lucid Puppy Linux (full install). Working great and I love it, that is until I reboot the machine and then suddenly wireless is broken. I have tried this now 4 or 5 times on three different PCs and all returned the same results. Everything works great from the LiveCD and it works great after installing and booting for the first time.
However, after that, wifi dies hard and won't come back.
Sometimes you can run
Code:
# rmmod b43
# modprobe b43
And wireless comes back but other times that it does nothing. I really have no idea why wireless would work and then not work randomly? I would think that it would work or it wouldn't work but not intermittently work at random.
Here is the contents of /tmp/sns_wireless.log when wireless goes out:
Code:
Information about this interface:
Interface: wlan0 Driver: b43 Bus: pcmcia MacAddress: 00:16:CE:37:9D:E6
Description: Broadcom B43 wireless driver
STEP1a: ifconfig wlan0 up
ifconfig: SIOCSIFFLAGS: No such file or directory
*********************************************************
LAST 10 LINES of /var/log/messages:
Jan 15 12:38:01 puppypc user.info kernel: usbhid: USB HID core driver
Jan 15 12:38:27 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
Jan 15 12:38:27 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
Jan 15 12:38:27 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
Jan 15 12:38:27 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
Jan 15 12:38:27 puppypc user.err kernel: firmware ssb0:0: firmware_loading_store: unexpected value (0)
Jan 15 12:38:27 puppypc user.info kernel: b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: Firmware file "b43/b0g0bsinitvals5.fw" not found
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
Have you followed the error information you posted from the wireless log?
Quote:
Firmware file "b43/b0g0bsinitvals5.fw" not found
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
Yes, the files all exist and wireless works fine every 10th boot or so on its own. It also works if I run:
Code:
# rmmod b43
# modprobe b43
After every reboot. The wireless definitely works, it doesn't work until root manually intervenes and unloads and reloads the driver.
I'm trying to figure out what I need to do to allow the OS to properly load the wireless driver without having to load it manually all the time. Maybe if its loaded earlier in the boot sequence or I use a different driver or something. I don't know, that's why I'm asking.
Last edited by thund3rstruck; 01-16-2012 at 07:47 AM.
Distribution: Debian, Arch Linux, Linux Mint, Ubuntu, Fedora, Suse, Mepis, Redhat, Sayabon, mandrake and android (
Posts: 192
Rep:
better luck
Quote:
camorri Have you followed the error information you posted from the wireless log?
Quote:
Firmware file "b43/b0g0bsinitvals5.fw" not found
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
Jan 15 12:38:27 puppypc user.err kernel: b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
Run the command 'lspci' as root, and look for the info on your wireless card. You need the rev number to follow the instructions at http://wireless.kernel.org/en/users/Drivers/b43
Hope this helps.
Look Camorri gave you wealth of information and when trying to fix a wifi card this becomes a scientific nightmare.
With common sense we can elimanate the problems.
General rules for linux support of hardware on wifi cards.
1. New Wifi cards take usually till the next release update. (Without a internet link with land line unable to update drivers.)
2. Revesions is were the problems exsist with software and chipset updates. (the link that camorri provided stated in the chart below not all chipsets are supported.)
Conclusion:
There are only 1 or 2 ideas here that can fix problem
1. connect to a landline and download kernel update this usually contians latest wifi card revesions.
2. Which far goes beyond but simply put would waste lots of time is to download a fresh copy of Licud Puppy Linux and install it.
Personnel experience have in the past owned a broadcom wifi card and only Debian based distros seemed to support it within first several weeks with a driver update. With other distros had to wait till there next release for update. Not all distro's have the support of the larger distro's to update as often as Ubuntu, Fedora or Suse.
Last, but not least I would post to puppy linux board that your having trouble with wifi card revesion included and chipset.
Note last time I had a broadcom card it was in a laptop and support I was concerned , but Ubuntu seemed to have an update for the chipset.
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 386
Original Poster
Rep:
I really don't want to sound ungrateful because I do sincerely appreciate quality comments and feedback so I'll just re-iterate again that the wireless card works fine. I'm using it right now, in fact.
The trouble is that it ONLY works if I manually unload the kernel module and then reload it after I log into the machine.
*for the 3rd time
Code:
# rmmod b43
# modprobe b43
Obviously, I've already placed the rmmod b43 && modprobe b43 commands into ~/.bash_profile but I'd prefer to not have to do this.
Make it executable and put it in ~/Startup. Reboot and see if it works. I am in Racy 5.2.2 right now and my chip and gear are different than yours. So I don't experience the same problems. This might help also http://wellminded.com/puppy/pupsearch.html
Edit: Just further instruction. In ~/Startup folder in Rox File Manager. Just right click on empty space and from menu pick New>Script to make the text file. Like I said. Make sure it is executable in permissions or properties also.
Distribution: Fedora 18, Slackware64 13.37, Windows 7/8
Posts: 386
Original Poster
Rep:
Quote:
Originally Posted by rokytnji
Make a simple bash script text file like
Code:
#!/bin/bash
rmmod b43
modprobe b43
Make it executable and put it in ~/Startup. Reboot and see if it works.
*facepalm*
Per my earlier post, yea I did that already before posting my question:
Quote:
Obviously, I've already placed the rmmod b43 && modprobe b43 commands into ~/.bash_profile but I'd prefer to not have to do this.
NOTE: That should have said ~/Startup and not ~/.bash_profile.
And yea, per my earlier post that gets the driver loaded. Of course that wasn't my question; my question was how to configure the Operating system to function correctly so that I don't have to do that manually (or through a hack script).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.