Bionic not recognizing broadcom b43 module

[xenial]

I have installed bionicpup64 on to another partition and it is not recognising the broadcom b43 module.I tried the method bigpup kindly showed me in regard to fossapup but bionic is not having it.

any ideas please?
thank you.

[mikewalsh]

@xenial :-

Mm. Well, there's ONE possibility.

Given that wireless driver modules have to be compiled for the kernel in-use, if Xenialpup64 connects on the same hardware without issues, then step back a little way to the slightly older kernel. Your hardware's not brand spanking new, and I'm betting that Xenial's k4.9.58 will support all your hardware just as well as Bionic's k4.19.23 does.

A kernel swap is a simple, easy way of finding out.....and it's NOT 'rocket-science'. Not these days, with Puppy's modular build-system. It's worth a shot.

Mike.

[xenial]

Hello mike and thank you.
My xenial kernel is v.4.4.95

Are older kernels built into bionic or do i download myself.?

thanks

[rcrsn51]

any ideas please?
thank you.

In the fossapup thread, you were asked to provide some diagnostics, which you never did.

They would be useful here before doing anything else.

[xenial]

@rcrsn51
Hello.
yes indeed i was asked to provide diagnostic data but however another forum member helped me on my way and i was subsequently able to connect to my wlan.

i do not believe diagnostic data is warranted here as it is pretty obvious that the broadcom module is the issue or rather the fact bionic is not seeing it.

I shall take previous advice and try an earlier kernel.
process of elimination.

[rerwin]

@xenial

Before you try swapping kernels, be sure that the problem isn't the absence of some firmware for the b43. Not all of the b43 firmware is included in bionicpup64. Check /var/log/messages for anything about "firmware". I had to add it to my bionicpup.

[xenial]

@rerwin
Thank you kindly for that info. What exactly was it you eventually had to add to get bionic connected? It may shed some light on my current situation.

[mikeslr]

Hi Xenial,

As is my usual method, I explain what's going on and provide instructions. If you are in a hurry, you can skip the explanation and just scroll down to the instructions.
Explanation:
I missed or don't recall reading bigpup's advice regarding Fossapup. But I take it that you were able to get Fossapup to recognize your broadcom wifi adapter. If that Fossapup is 64 bit, there's no reason to downgrade to Xenialpup64's kernel. You can just use the same kernel you use with Fossapup and do the same things you did with Fossapup in order to get Bionicpup64 to recognize your wifi.
This is a screenshot of both my Fossapup64 and Bionicpup64 folders, Fossapup64 being on top:

Puppy's Kernels.png (156.73 KiB) Viewed 1661 times

Ignore everything else except these three files found in both Fossapup64 and Bionicpup64: vmlinuz, fdrv_Version_Number.sfs and zdrv_Version_Number.sfs.
Technically, only vmlinuz is the kernel. But, to communicate with hardware --such as wifi adapters-- a kernel uses drivers which have to compiled against that specific kernel. So Puppy Devs publish what they refer to as "hugh-kernels" which include both the vmlinuz and an SFS named "kernel-modules" which contains the drivers. To communicate with hardware, the kernels also need firmware. Firmware can be used by any kernel. So, while some Devs include firmware within the kernel-modules.sfs, others package it separately: once downloaded it can be used with any kernel. When separately packaged, firmware is published as an fdrv.sfs.
Now note a file named initrd.gz in both sections of the Screenshot. This is the file which is first loaded when you boot up a Puppy. It contains the instructions of what other files to use. Fossapup's initrd.gz tells it to use a file named vmlinuz, one named zdrv_fossapup64_9.5.sfs and (if it is present) a file named fdrv_fossapup64_9.5.sfs. Bionicpup64's initrd.gz says to use a zdrv_bionicpup64_8.0.sfs and (if present) fdrv_bionicpup64_8.0.sfs.
If you downloaded a 'hugh kernel' to use it with Bionicpup64 you would rename the vmlinuz (by removing its identifying ending) and rename kernel-modules.sfs to zdrv_bionicpup64_8.0.sfs. But you already have a kernel whose zdrv.sfs provides the drivers you need. So all you have to do is:
Instructions:
1) move Bionicpup64's current vmlinuz and zdrv_bionicpup64_8.0.sfs somewhere --for example, the "protect" folder shown in the bottom half of the Screenshot >just in case you have to revert.
2) Copy Fossapup64's vmlinuz and zdrv_fossapup64_9.5.sfs into Bionicpup64's folder and rename the latter zdrv_bionicpup64_8.0.sfs.
3) I don't recall if my Bionicpup64's ISO had an fdrv.sfs. If your Fossapup64 didn't need one, forget about it. If it has one, copy it into the Bionicpup64 folder and rename it fdrv_bionicpup64_8.0.sfs.

You can do all that from any Puppy, including Bionicpup64 if you are then running it. But, before Bionicpup64 can make use of the new vmlinuz and f-and-z drv.SFSes, you have to reboot.

[ozsouth]

@xenial - there are broadcom wl modules available. All are kernel-specific. I found that 4 modules had to be blacklisted for that to work, as b43 bcma brcmsmac and ssb modules clashed with wl.

Since you have had some success with the standard module, you may just require firmware to make b43 work. To find out if any firmware missing, in a terminal run: dmesg | grep irmware

The wl modules are linked below:

- the broadcom wl driver for fossapup64 (with blacklisting instructions at 1st post ) is here (driver at 2nd post):
viewtopic.php?f=97&t=1474

- the broadcom wl driver for bionicpup64 is here: https://archive.org/download/Puppy_Linu ... 23_amd.pet

[xenial]

hello,
Thank you for those incredible replies,very knowledgeable people on here.

Just an update and please bear in mind i am quite the noob here,i tried mikesir's suggestion and was subsequently met upon reboot with some form of kernel panic message and untangible red writing.My error no doubt.

I downloaded the broadcom wlan driver as suggested by ozsouth and installed the pet into bionic but nothing shows in the network wizard modules list so i am at a loss from this point forward.I should add and all due respect to ozsouth i did not blacklist the broadcom modules as suggested as further down the forum post it was suggested not to add anything to the bionic grub.cfg.

My situation is at the moment is that bionic64 is installed on flashdrive and boots perfectly but in a sort of stalemate in regard to my wlan being noticed..no doubt with me being a novice to this is incremental in this.

regards and thanks to all.

[rcrsn51]

To find out if any firmware missing, in a terminal run: dmesg | grep irmware

Once again, solving this problem requires some diagnostics.

[mikewalsh]

@xenial :-

Don't panic. We'll get you sorted, one way or another.

Broadcom have historically always been a complete PITA under Linux; they're about the only network hardware firm that don't pay even lip-service to the fact that Linux even exists. As far as they're concerned, it doesn't; just Windows & MacOS.

There's usually workarounds of one sort or another.....mostly involving 3rd-party-compiled drivers. Bear with us!

Mike.

[ozsouth]

@xenial - another simpler approach (if this doesn't work we'll need to do diagnostics).
Copy the ydrv linked below into the same folder as puppy_bionicpup64_8.0.sfs etc.
Reboot. Hopefully, you should then be able setup wireless (by right-clicking the taskbar wireless icon).

EDIT: didn't work - withdrawn

[rcrsn51]

Broadcom have historically always been a complete PITA under Linux; they're about the only network hardware firm that don't pay even lip-service to the fact that Linux even exists. As far as they're concerned, it doesn't; just Windows & MacOS.

??????

In August 2008, Broadcom released the 802.11 Linux STA driver officially supporting Broadcom wireless devices on GNU/Linux. This is a restrictively licensed driver and it does not work with hidden ESSIDs, but Broadcom promised to work towards a more open approach in the future.

In September 2010, Broadcom released a fully open source driver. The brcm80211 driver was introduced in the 2.6.37 kernel and in the 2.6.39 kernel it was sub-divided into the brcmsmac and brcmfmac drivers.

[mikewalsh]

@rcrsn51 :-

I hold my hand up to that; I DO apologize for giving false info. Must have got hold of the wrong end of the stick....

I'd always assumed, from what I've read, that much of the "awkward" reputation Broadcom wireless stuff seems to enjoy under Linux was due to the need to 'reverse-engineer' Windows driver code, or something along those lines.

Like many, I know a little about most things, but not enough to be dangerous. Drivers, and source-code for same, I know next to nothing about, so I'm more than happy to defer to those with greater knowledge than I. Best I leave such discussions to those who DO know, else I shall end up making a bigger prat of myself than I already do.....

Mike.

[xenial]

@xenial - another simpler approach (if this doesn't work we'll need to do diagnostics).
Copy the ydrv linked below into the same folder as puppy_bionicpup64_8.0.sfs etc.
Reboot. Hopefully, you should then be able setup wireless (by right-clicking the taskbar wireless icon).

ydrv (bionicpup64 & its standard kernel 4.19.23 only):
https://www.mediafire.com/file/ibxe4ikq ... 0.sfs/file

Hello ozsouth.
Ok i have now downloaded your suggested package..just to be clear do i just move it into the folder or replace the ydrv folder already present?.
sorry for the dumb question but yea dummies like me do ask them.

[xenial]

Just an update.
i tried ozsouth's suggested fix and it did not work,nothing,nada so im in despair lol.

To save everyone's time i may have to give up trying and just stick with my xenial32 which has worked flawlessly for the past couple of years.

I am trying so hard to get a 64bit puppy on my flashdrive and it is obstacle after obstacle.

[rcrsn51]

I set up a Bionicpup64 machine with Broadcom wifi. I ran the diagnostic and identified that firmware was missing. I installed a b43 firmware package. I rebooted. I identified that the wlan0 interface was now recognized. I ran SNS and got a WiFi connection.

[xenial]

Ok which broadcom package did you download and install.?

[xenial]

ok just an update.
i performed dmesg grep irmware within the terminal and i have uploaded an image which maybe of interest.
I have no idea how to save the terminal output.

Screenshot.png (193.79 KiB) Viewed 1602 times

[mikewalsh]

@xenial :-

i performed dmesg grep irmware within the terminal and i have uploaded an image which maybe of interest.
I have no idea how to save the terminal output.

Now that's one thing I can help with. That is really, REALLY easy.

Whatever your terminal command is to be, enter it, followed by (space)>>(space)/root/xxxxxxx.txt.......where "xxxxxxx" is whatever name you decide to use for the file, and ".txt" saves it as a text document. In this case it could be:-

Code: Select all

dmesg | grep irmware >> /root/firmware.txt

You won't get a readout, but if you then open Rox at the usual /root window, you'll find a text file there with the name you gave it, and the contents of your terminal readout inside. This can then be attached to your next post in the normal way (you may have to re-name "firmware.txt" to, say, "firmware.txt.gz".....add a ".gz" on the end to keep the forum software happy..!)

Useful info for future use.

Mike.

[xenial]

Thanks mike.
Do you have any idea where the best place would be to download older kernels..4.4..95 preferably.

[ozsouth]

Found firmware for b43 here: https://github.com/OpenELEC/wlan-firmwa ... rmware/b43

@xenial - .pet for your firmware 2 posts down.

[mikewalsh]

Thanks mike.
Do you have any idea where the best place would be to download older kernels..4.4..95 preferably.

Shouldn't be any need, TBH. If you've still got the copy of Xenial64 that connects OK for you, you can "borrow" the vmlinuz & zdrv_xenialpup_7.5.sfs files from it.

Delete the existing ones from Fossapup64 (or Bionicpup64, whichever one you want to use), Then, copy those two files over to replace them. Make sure to do the following:-

- For Bionicpup64, rename the zdrv_xenialpup64_7.5.sfs to zdrv_bionicpup64_8.0.sfs

_ For Fossapup64, rename the zdrv_xenialpup64_7.5.sfs to zdrv_fossapup64_9.5.sfs

This is so that each Puppy will find the files it expects to see, as detailed in its initrd.gz. Do a re-boot, then perform a check, like this:-

• Open a terminal.

• Enter

  Code: Select all

  uname -ra

  .....and hit the "Enter" key. It should confirm you're running the default Xenial64 k4.4.95 kernel.

------------------------------------

If you still want to try this, and don't have the ISO anymore, re-download it from here:-

http://distro.ibiblio.org/puppylinux/pu ... 5-uefi.iso

Now; see what happens when you try to connect.

Mike.

[ozsouth]

@xenial - from your screenprint I see 3 missing firmware files. I have made a .pet containing them.
If you just boot standard bionicpup64 (without my earlier ydrv) then install the .pet you should have wireless.

[xenial]

fantastic replies and thanks,
@ozsouth,
sorry mate that was a non starter.I downloaded your pet and installed into bionic64 and then saved and rebooted and still no wlan interface found.If it isn't meant to be then i will have to console myself that this great distro is not going to connect for me.

I found and downloaded kernel 4.4.95 which is what my xenialpup32 uses and tried changing the kernel on bionic and that caused a kernel panic on reboot.

Running out of ideas.
my xenialpup32 has run fantastic for the past few years.
Maybe this laptop is rejecting 64bit versions for some odd reason.

[xenial]

Just out of curiousity i installed 32bit focalpup on to a partition and there were no issues what so ever.
Common denominator with my connection problems seem to be 64bit pup specific.

Maybe this old laptop just doesn't want 64bit pups installed.

[ozsouth]

@xenial

Have attached the firmware from xenial32 bit as a .pet - please try in bionicpup64.

Should this .pet not work, please run in a terminal (last resort):
lspci -nn | grep etwork

(starts with lowercase L - it is the output code in [x9x9:x9x9] format I'm after).

[xenial]

hello ozsouth.
Rather than booting up bionic etc and transferring files i have performed your terminal command here on my xenial32 and the output was just 32.

[one]

Maybe this laptop is rejecting 64bit versions for some odd reason.

...............................................................................

I think that by now you have lost track. In the fossapup thread you wrote:

viewtopic.php?p=34008#p34008

by xenial » Fri Aug 13, 2021 11:20 pm

okay xenialpup64 is now installed on the flashdrive and it connects perfectly with no issues.I must have a xenial only laptop lol.

...............................................................................

viewtopic.php?p=34033#p34033

by xenial » Sat Aug 14, 2021 9:01 am

I followed your instructions to the letter and upon reboot of fossa i was able to connect but i have to do it manually which is not such an issue but at least the saved profile was found and i could connect.

...............................................................................

So your laptop is definitely 64bit capable, both xenialpup64 and fossapup64 boot and work with your wlan module. Correct?

...............................................................................

PS: # getconf LONG_BIT gives you output from current running OS (xenial32 in your case) - run PupSysInfo to see if your CPU is 64bit capable.

peace