Puppy Linux Discussion Forum

A list of Broadcom Drivers & requirements is here (thanks to rcrsn51 for finding this)
Need to run in a terminal: lspci -nn | grep etwork (note: command starts with lowercase L & has pipe symbol in middle)
Then find code at end (format [9x9x:9x9x]) & scroll down to table in link below to search for it:
https://wireless.docs.kernel.org/en/lat ... s/b43.html

Commonly sought older updated wl drivers:

Bionicpup64 (k4.19.23) - https://archive.org/download/Puppy_Linu ... k41923.pet

Fossapup64 9.5 (k5.4.53) - https://archive.org/download/Puppy_Linu ... -k5453.pet

Fossapup64 9.6 (k6.0.12-FP): https://www.mediafire.com/file/axjuoixz ... p.pet/file

Seems some folk need an old-style driver for Fossapup64-9.6CE (k6.0.12-FP).
Is here: https://www.mediafire.com/file/axjuoixz ... p.pet/file

Many drivers can be found here: https://archive.org/download/Puppy_Linu ... iver_Repo/

My newer 32bit Drivers:

k5.10.218: https://www.mediafire.com/file/ngwwuwm0 ... e.pet/file

.

My newer 64bit Drivers (unless specified, are aufs/overlayfs/non-usrmerge):

k6.6.58 (hi-freq; overlayfs): https://www.mediafire.com/file/ecxymry3 ... p.pet/file

k6.10.14 (hi-freq; usrmerge; overlayfs): https://www.mediafire.com/file/0kn0klme ... p.pet/file

k6.1.115: https://www.mediafire.com/file/c3j3rs0d ... p.pet/file

k6.6.59 (hi-freq): https://www.mediafire.com/file/n7y5wker ... p.pet/file

k6.8.12 (upup64n; usrmerge; overlayfs): https://archive.org/download/Puppy_Linu ... n-skip.pet

k5.4.285: https://www.mediafire.com/file/n493rhbk ... x.pet/file

k5.10.208 here: https://archive.org/download/Puppy_Linu ... .208ao.pet

Note:
Drivers are Linux kernel specific. Use at own risk.
The driver pet, is only good to use, in a Puppy version, using the identified kernel, in the name of the pet.
Example:
bcm4211-43142-wl-64-k5453.pet is for Puppy version using the 5.4.53 Linux kernel.

There was an OLD MANUAL METHOD - superseded in 2021. .pets after that have automatic blacklisting, depmod & modprobe.

superseded.

thank you for posting. I have installed your pet file.
my lspci output is ----06:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev01)
I have done all the steps as described but wifi not started. So I searched further and got following command line to execute in terminal
sudo modprobe -rv bcma wl
sudo modprobe -v wl
then some how my wifi got connected
Now my problem is -for everytime I boot my laptop with fossapup I have to execute these two commands in terminal. then only I can connect to my mobile phones tethering(wifi).
Is there any way to avoid this???

out put of these commands is
root# sudo modprobe -rv bcma wl
rmmod wl
rmmod cfg80211

root# sudo modprobe -v wl
insmod /lib/modules/5.4.53/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/5.4.53/kernel/drivers/net/wireless/wl.ko

Do not add anything to the boot loader entry or enter anything in terminal to load drivers.

Install the pet package.
Do not black list bcma

Reboot and save.

Do you fully understand how to use the network connection wizards?

Also run this in terminal to make sure it is not being hard or soft blocked.

rfkill list all

If it says wlan is hard blocked.
Turn on the WIFI with the switch or F key that turns wifi on/off
check it again with rfkill list all to see if it is now not blocked.

If still blocked.

Use

 rfkill unblock all

in a terminal.

After you get a completed setup, using one of the network connection wizards.
Shutdown and saved changes.
It should auto connect at next boot.

POST OUTDATED.

@chimnya123 - sudo is unnecessary in Puppy, but if your 2 commands work for you, you can run this in a script at startup. Open a text editor & copy the commands below to it.

#!/bin/sh
modprobe -r bcma wl
sleep 0.5
modprobe wl

Then save as file named wlstarter, into folder /root/Startup.
Then from a terminal, run: chmod 755 /root/Startup/wlstarter

Upon each reboot (assuming you use a savefile or savefolder), wireless should work.

hi ozsouth
when I run: chmod 755/root/Startup/wlstarter
I got this error
chmod: missing operand after ‘755/root/Startup/wlstarter’
Try 'chmod --help' for more information.

Did you try what I posted?

@chimnya123 - you are missing a space after 755. Try it again -
chmod 755 /root/Startup/wlstarter

@ozsouth that worked for me
thanx

see first post

superseded

superseded

superseded

.

Is there any driver for Intel WiFiLink3945ABG/4965AGN series network card?

@linuxunix - Intel wifi is a different topic, so I've started a new one here: viewtopic.php?p=35020#p35020

Several wl drivers a few posts back.

See first page

Hi all,

I have a "Dell Wireless WLAN 1397 Half MiniCard" and am running S15Pup64 Puppy Linux.

I am unable to get S15Pup64 to detect the wifi card.

The card runs a Broadcom BCM4312 chipset.

If I run PupSysInfo/Sys-Specs/Kernel it says I have version 5.15.148 (x86_64).

So I went to https://archive.org/download/Puppy_Linu ... iver_Repo/ and downloaded the file broadcom-sta-wl-20201202-k5.15.148-20240203-kirkstone64.pet

I then opened the file manager and double clicked it and it installed successfully.

I then rebooted.

I then ran "Setup Networking/Connect to Internet by Wired or Wireless LAN".

The "Simple Network Setup" doesn't detect the card.

The "Frisbee" also doesn't detect the card.

With the "Network Wizard" it also doesn't detect the card but If I click "Load Module" I now have a WL module in the list.

I select the "WL" module and click "Load Module" and I get the error "Loading wl failed with the following message: modprobe: ERROR: could not insert 'wl': Exec format error. Maybe try a different driver"

What am I doing wrong?

Is the downloaded file broadcom-sta-wl-20201202-k5.15.148-20240203-kirkstone64.pet not the right one?

Regards,

fbagnato

Update......

I did a fresh install of S15Pup64 and this time installed the PET file wl-64-updt-k5.15.148aoum-skip.pet (the last link in the first post in this thread).

The PET was reported as installed correctly.

I then ran "Setup Networking/Connect to Internet by Wired or Wireless LAN".

The "Simple Network Setup", "Frisbee" and "Network Wizard" do not detect the card.

This time in "Network Wizard" If I click "Load Module" I do not have a WL module in the list.

If I run "lspci" I can see an entry for my Wifi card (Broadcom BCM4312).

Again, is the PET file wl-64-updt-k5.15.148aoum-skip.pet the wrong file to install?

Why is the wl drivers not showing in "Network Wizard/Load Module"?

Regards,

fbagnato

Hi

You'd better read this:

viewtopic.php?p=72899#p72899

Regards

Piku

fbagnato wrote: ↑Wed May 08, 2024 9:35 am

Update......

I did a fresh install of S15Pup64 and this time installed the PET file wl-64-updt-k5.15.148aoum-skip.pet (the last link in the first post in this thread).

The PET was reported as installed correctly.

I then ran "Setup Networking/Connect to Internet by Wired or Wireless LAN".

The "Simple Network Setup", "Frisbee" and "Network Wizard" do not detect the card.

This time in "Network Wizard" If I click "Load Module" I do not have a WL module in the list.

If I run "lspci" I can see an entry for my Wifi card (Broadcom BCM4312).

Again, is the PET file wl-64-updt-k5.15.148aoum-skip.pet the wrong file to install?

Why is the wl drivers not showing in "Network Wizard/Load Module"?

Regards,

fbagnato

Hello Piku,

Thanks for your reply.

I read the entire thread that you linked but did not learn anything new about my situation.

From what I read, the stock B43 drivers don't support Dell and HP variants of wifi cards with Broadcom BCM4312 chipsets.

I believe I need to install the wl drivers for the card to work.

I tried both the kernel 5.15.148 (x86_64) PETs found in this thread and its links.

Neither work......

I think the PET file wl-64-updt-k5.15.148aoum-skip.pet is not working is because it is "usrmerge" (which I don't understand) but I don't think S15Pup64 22.12 is a "usrmerge" system??????

The PET file broadcom-sta-wl-20201202-k5.15.148-20240203-kirkstone64.pet, which at least appears in the "Network Wizard/Load Module" list, as mentioned returns the error "Loading wl failed with the following message: modprobe: ERROR: could not insert 'wl': Exec format error. Maybe try a different driver"

If I search the internet for this error it mentions that it can be due to the module being compiled for a different version of the kernel.

My kernel is 5.15.148, the PETs I tried are 5.15.148, so I don't know how this could be.

If I open PupSysInfo and select "Devices/PCI Devices/Complete" I see an entry for the Wifi card and it says that the "Kernel modules" is ssb.

If I install the PET file broadcom-sta-wl-20201202-k5.15.148-20240203-kirkstone64.pet then open PupSysInfo and select "Devices/PCI Devices/Complete" I see an entry for the Wifi card and it says that the "Kernel modules" is ssb,wl.

Regards,

fbagnato

I thought I would try and compile the wl drivers.

I am not experienced with Linux compiling so excuse my ignorance.

I installed devx, to give me make capabilities, which went into the folder mnt/home

It did not go into the S15Pup64 subfolder (where I have installed S15Pup64 files) which I would have preferred but I don't know if it should be in mnt/home root directory.

Anyway,

I copied the wl source files to a newly created /usr/local/src folder called broadcom-wl-path-linux4.7 (the name of the download archive file).

I then opened a terminal at /usr/local/src folder called broadcom-wl-path-linux4.7 and ran the make command.

I get the error "/lib/modules/5.15.148/build: No such file or directory"

So, I create the folder /lib/modules/5.15.148/build and rerun make

I get the error "*** No targets specified and no makefile found"

But in the " /usr/local/src/broadcom-wl-path-linux4" folder that I have the terminal at has the makefile file.

Anyone know what is wrong?

Regards,

fbagnato

@fbagnato You will need to load the kernel sources SFS for the kernel 5.15.148 you are running in S15Pup64!

This SFS supplies the kernel source that the driver will be compiled against.

@fbagnato

Before you dig into kernel module compilation, let me suggest to try swapping kernel version that includes wl module, like:

viewtopic.php?p=62063#p62063
(you could search forum by: "ozsouth wl kernel" to find more options)

FYI, Kernel swap is not dificult to do:

viewtopic.php?t=7832

Hope this helps

Pika

fbagnato wrote: ↑Wed May 08, 2024 4:14 pm

Hello Piku,

Thanks for your reply.

I read the entire thread that you linked but did not learn anything new about my situation.

From what I read, the stock B43 drivers don't support Dell and HP variants of wifi cards with Broadcom BCM4312 chipsets.

I believe I need to install the wl drivers for the card to work.

I tried both the kernel 5.15.148 (x86_64) PETs found in this thread and its links.

Neither work......

I think the PET file wl-64-updt-k5.15.148aoum-skip.pet is not working is because it is "usrmerge" (which I don't understand) but I don't think S15Pup64 22.12 is a "usrmerge" system??????

The PET file broadcom-sta-wl-20201202-k5.15.148-20240203-kirkstone64.pet, which at least appears in the "Network Wizard/Load Module" list, as mentioned returns the error "Loading wl failed with the following message: modprobe: ERROR: could not insert 'wl': Exec format error. Maybe try a different driver"

If I search the internet for this error it mentions that it can be due to the module being compiled for a different version of the kernel.

My kernel is 5.15.148, the PETs I tried are 5.15.148, so I don't know how this could be.

If I open PupSysInfo and select "Devices/PCI Devices/Complete" I see an entry for the Wifi card and it says that the "Kernel modules" is ssb.

If I install the PET file broadcom-sta-wl-20201202-k5.15.148-20240203-kirkstone64.pet then open PupSysInfo and select "Devices/PCI Devices/Complete" I see an entry for the Wifi card and it says that the "Kernel modules" is ssb,wl.

Regards,

fbagnato

@fbagnato - my kernel 5.15.148 is a usrmerge-only kernel. It is not for s15pup64 - need to use my 5.15.147 for that (see: viewtopic.php?p=113087#p113087). Kernels must match exactly - you can't use one with the same number from a different source. The wl module for my 5.15.147 is in first post. If you are using someone else's 5.15.148, will need its kernel sources & devx for particular version of s15pup64 you are using. Will save yourself much time & trouble by using my 5.15.147 kernel & driver.

Hello @rockedge , @ozsouth and hello again to @Pikaxhu,

Thanks for your replies.

It seems the consensus is to change kernel, so I am going to try ozsouth's 5.15.147 kernel.

@ozsouth

A few questions:

1) You say in viewtopic.php?p=113087#p113087

(if your puppy is recent, like S15Pup64-22.12) have punionfs=overlay in the grub/syslinux kernel line.

I reran Grub4DosConfig to look at the grub parameters for S15Pup64 and it has the options "pmedia=atahd pfix=fsck", it does not have "punionfs=overlay" as an option.

I also did a "find syslinux.cfg" command from the / folder but nothing was found.

From some reading it seems that "punionfs=overlay" is better than "punionfs=aufs" which I think it must default to.

Am I looking in the right place for the punionfs=overlay parameter and should I add the line "punionfs=overlay" to the Grub4DosConfig Frugal Installed Puppy options?

2) You say

Has no firmware - needs recent fdrv

.

I see that in my mnt/home/S15Pup64 folder (which is where I installed S15Pup64) I have a "fdrv_s15pup64_22.12.sfs" file.

Do I just rename your "fdrv_26feb24oz.sfs" to "fdrv_s15pup64_22.12.sfs" file and replace the file in my mnt/home/S15Pup64 folder?

3) You say

Is mostly Spectre/Meltdown mitigated (needs microcode too - see viewtopic.php?p=9658#p9658).

.

I read that thread but am not sure how to load it as the computer with S15Pup64 installed on it is a Legacy BIOS not a UEFI BIOS.

It has an Intel Core 2 Duo CPU T6400 processor.

You say

/micd .cpio file goes in folder micd, on same level as folders with initrd.gz

Do I just create a micd folder in my mnt/home/S15Pup64 folder (which is where I installed S15Pup64) and copy the extracted "microcode-update-64.cpio" file into my mnt/home/S15Pup64 folder?

Then you say

if grub bootloader, initrd line:
initrd /EFI/BOOT/micd/microcode-update-(x)-64.cpio /EFI/BOOT/(folder)/initrd.gz

My mnt/home/S15Pup64 folder (which is where I installed S15Pup64) has an initrd.gz file so I am guessing that my initrd line would be:

initrd /mnt/home/S15Pup64/micd/microcode-update-64.cpio /mnt/home/S15Pup64/initrd.gz

Do I edit initrd.gz as per the instructions at https://oldforum.puppylinux.com/viewtopic.php?t=53019?

4) You say

Important Note: when switching kernels, if you have an ...initmodules.txt file (i.e. fossapup64initmodules.txt or similar)
must delete it before first boot into new kernel. Otherwise it may try to load modules that don't exist, causing failure.

I did a "find *initmodules*.txt" command from the / folder but nothing was found.

From some reading the initmodules.txt file would be in my mnt/home/S15Pup64 folder (which is where I installed S15Pup64) if it existed in my installation.

Does that sound right to you????

Regards,

fbagnato

@fbagnato - I state many options for users of my kernels. User have different setups. I make different types - non-usrmerge slacko derivative is what you want for s15pup64. You would rename kernel-modules.sfs... to zdrv_s15pup64_22.12.sfs .
The punionfs=overlay is only used if you want to run overlayfs. This is obviously not what you want, so ignore it.
It appears you have been running s15pup64 without microcode - it is safer to use it, but not essential for operation. Perhaps try running without it initially.
There are several bootloaders. Most are a grub type (grub, grub4dos, grub2 are a few variants) but I use syslinux. I wanted to explain that any bootloader needs changes to use microcode. Again, initially, just use what came with your system. No need to change initially.
As for firmware, there are different systems - yours is based on slackware, so yes rename my fdrv to fdrv_s15pup64_22.12.sfs .
Hope that helps.

Hello @ozsouth

Well mainly good news and that is I have successfully installed your 5.15.147 kernel and Wifi is now working.

I tried to install your microcode but am now getting a "Wrong EFI loader signature" error upon startup after the initrd messages (right at the start of the bootup sequence).

What I did:

I created a "micd" directory in the directory that I have S15Pup64 installed (mnt/home/S15Pup64/micd)

I copied the file "microcode-update-64.cpio" to the mnt/home/S15Pup64/micd directory.

I then ran the "Setup/Grub4Dos bootloader config" program and proceeded with the install until I could click the "Edit '/menu.lst'" button.

I clicked that button and added the line "initrd /S15Pup64/micd/microcode-update-64.cpio /S15Pup64/initrd.gz" under the other initrd line in the S15Pup64 section of grub.

Saved the file and rebooted.

Do you know why I am getting that error?????

I also did some digging around and found a "Boot manager" utility which when opened (Then titled "Startup Manager") had a tab called "Microcode fixes".

Clicking that tab there is a button called "Run Microcode Installer".

Clicking that button prompts that there is no microcode installed and offers a "Remote Intel Microcode Version: 20240312"

Is this the same thing as your Microcode and am I better just installing that or is your Microcode better?

Regards,

fbgnato

@fbagnato - you should have only 1 active initrd line - so place # to the left of the old one. Not sure what the auto-install microcode will do. Nice to see you're progressing well.

Hello @ozsouth

OK, what I have done is looked at the "Boot manager/Run Microcode Installer" and it seems to do what your Microcode does (protect against certain vulnerabilities).

I then deleted my micd directory, reran Grub2Dos config and did not add the initrd line to reference the now deleted micd/microcode-update-64.cpio file.

Then I ran the "Boot manager/Run Microcode Installer" and downloaded and installed the "Early Loading" microcode option.

You may want to have a look at the "Boot manager/Run Microcode Installer" as it may save you ongoing work updating the Microcode thread with new versions and provide an out-of-the-box solution instead?

All is well except......

I am still getting the "Wrong EFI loader signature" error upon startup after the initrd messages (right at the start of the bootup sequence).

I removed the punionfs=overlay and now the Microcode code was already removed and the error still occurs.

It seems to be related to your kernel/fdrv/zdrv files (don't know which one).

S15Pup64 boots up fine except for that error message being spat out.

Any ideas?

Regards,

fbagnato