(old)Puppy Linux Discussion Forum

Anyone has wl module for slacko64-6.3.0. (k 4.1.11) or Tahr64-6.0.5 (k 3.14.54)?
If not, can someone point to the sources, patches and any special module making instructions? (long thread to search )

mavrothal wrote:Anyone has wl module for slacko64-6.3.0. (k 4.1.11) or Tahr64-6.0.5 (k 3.14.54)?
If not, can someone point to the sources, patches and any special module making instructions? (long thread to search )

Hi Mav

Check current version (currently 6.30.223.271) from:
http://www.broadcom.com/support/802.11

Get the most recent patched source from ubuntu or debian - e.g. from:
https://launchpad.net/ubuntu/+source/br ... .223.271-7
(try upping the last number to get latest) get
https://launchpad.net/ubuntu/+archive/p ... rig.tar.xz

Extract the sources for the required arch - i386 or amd64 and have a look in broadcom-sta-6.30.223.271/amd64/src/wl/sys and check the latest kernel mentioned LINUX_VERSION in:
wl_cfg80211_hybrid.c
wl_linux.c

(Currently = 4.2.0 so 4.1.11 and 3.14.54 should be ok)

patch wl_linux.c at about line #220 - change eth% to wlan%

In a system with devx and kernel sources installed, open a terminal in the extracted sources folder and type:
make

Result if compilation finishes without errors is wl.ko in the folder

If the compilation fails and your kernel is later than the one above, search the web for suitable patches!!

Package as a .pet for the particular kernel (i.e. correct name for /lib/modules/xxxx/kernel/drivers/net/wireless) with a pinstall.sh that just calls depmod -a

Test - install the .pet, then:
modprobe wl
lsmod
dmesg

to check that the new module loads without errors

then in a running system, blacklist whatever drivers were claiming the wifi device

upload to a repository and share....

Cheers
peebee

Thanks for the info.

peebee wrote: Get the most recent patched source from ubuntu or debian - e.g. from:
https://launchpad.net/ubuntu/+source/br ... .223.271-2
<snip>
patch wl_linux.c at about line #220 - change eth% to wlan%

So from all the 8 Debian patches you only apply "03-rename-to-wlan0.patch" or others too?
Do you use any of the Debian control files?

mavrothal wrote:Thanks for the info.

peebee wrote: Get the most recent patched source from ubuntu or debian - e.g. from:
https://launchpad.net/ubuntu/+source/br ... .223.271-2
<snip>
patch wl_linux.c at about line #220 - change eth% to wlan%

So from all the 8 Debian patches you only apply "03-rename-to-wlan0.patch" or others too?
Do you use any of the Debian control files?

I think? the other patches should already have been applied in the ubuntu sources.....

don't use any control files.....

OK thanks.
Was actually pretty smooth and fast (should be easy to just make script to automate this ) .
Only the "03-rename-to-wlan0.patch" debian patch was used.

The modules works fine in my hardware with Slacko64-3.6.0.1 (k4.1.11) and Tahr64-6.0.5 (k3.14.54).

So here are the pets for the Broadcom wl WiFi module for the 3.14.54 64bit kernel and for the 4.1.11 64bit kernel
(Note: datafilehost is both sneaky and annoying. The "Download" button is the small one... and even then you should unckeck the "Download with Secured Download manager" option just under it)

UPDATE I experienced freezes with the 4.1.11 module. So I recompiled using the 03-rename-to-wlan0, 04-user_ioctl, 05-remove-time-and-date-macros, and 13-broadcom-sta-6.30.223.248-linux-3.18-null-pointer-crash debian patches and is more stable.
Also updated the install scripts and added also an unisntall script in the pets. Both pets uploaded in the above links and are now in version 5.

Just a notion to early adopters that the files above have been updated.

see next post - best to use peebee's driver.

Updated 17-feb

Thanks @ozsouth

The complete set of drivers in .pet format for all flavours of tahrpup-6.0.5 with "standard" kernels are now in 666philb's tahrpup repositories:

http://distro.ibiblio.org/puppylinux/pet_packages-tahr/
http://distro.ibiblio.org/puppylinux/pe ... es-tahr64/

Thanks PeeBee. Would definitely be good to have these in the general repository, as I couldn't find one, so made another somewhat untidy module.

peebee wrote:Thanks @ozsouth

The complete set of drivers in .pet format for all flavours of tahrpup-6.0.5 with "standard" kernels is at:
http://smokey01.com/peebee/broadcom/tahr-6.0.5/

I've sent a pm to 666philb suggesting he might like to add them to his repository.

Hello. I am running TahrPup 6.0.5 64 bit with a Broadcom BCm4313 driver. Can you help me withe specific directions to get it working? I understand some of the basics, but just can't quite get it correct.
Thank you.

Welcome. I don't have the 64 bit Tahrpup, but peebee's .pet (the amd64 version) should be able to be downloaded (from the smokey01 site) & installed via file manager (just click on the .pet - takes under a minute).
That should automatically do the necessary blacklisting of conflicting modules. A reboot is then required (save session if frugal install). Then the connect tool (choosing simple network setup) should offer you wlan0 to connect to. Hope that helps.

ozsouth wrote:Welcome. I don't have the 64 bit Tahrpup, but peebee's .pet (the amd64 version) should be able to be downloaded (from the smokey01 site) & installed via file manager (just click on the .pet - takes under a minute).
That should automatically do the necessary blacklisting of conflicting modules. A reboot is then required (save session if frugal install). Then the connect tool (choosing simple network setup) should offer you wlan0 to connect to. Hope that helps.

Wow, works great! Thanks so much. This is really awesome.

bdkemp1952 wrote:

ozsouth wrote:Hope that helps.

Wow, works great! Thanks so much. This is really awesome.

Thanks @ozsouth for the clear instructions.

Glad it works for you @bdkemp1952

666philb has now uploaded the pets to the tahrpup repositories so they should be available via his excellent download and update mechanisms so I'll remove the link to smokey01

Cheers
peebee

p.s. @mavrothal made the 64 bit pet so thanks are also due to him

PPM made me uninstall the multi-kernel pet on page 1 due to kernel incompatibility. Are there any made for:

#Note: Ubuntu 14.10 is named Utopic Unicorn.
DISTRO_NAME='Quirky Unicorn'
#version number of this distribution:
DISTRO_VERSION=6.2.1
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='ubuntu'
DISTRO_COMPAT_VERSION='utopic'
#the kernel pet package used:
DISTRO_KERNEL_PET='linux_kernel-3.16.6-nopae-builtin_aufs_f2fs_squashfs_zram-i586-unicorn.pet'

Just bought a new HP Stream and really need that wifi working...

slavvo67 wrote:Are there any made for:
DISTRO_KERNEL_PET='linux_kernel-3.16.6-nopae

Best I can suggest is follow the HowTo at:
http://www.murga-linux.com/puppy/viewto ... 946#884946

Being Quirky rather than Puppy, it is not possible to get the correct compiling environment other than by downloading and installing Quirky....

PeeBee:
the source files at ubuntu for ubuntu and debian cannot be decompressed by my system-their .xz is not recognised, neither is all_Debian.

whot to do? thx

PeeBee
<Here is the 32-bit wl driver for Slacko-6.3.0 k3.14.55-nopae as a .pet:

broadcom_wl_v6.30.223.271_x86_32-k3.14.55_nopae_s630.pet>

== Error 404

Makes life hard.

I have WL.ko installed, but cannot load it. It appears to be in wrong place. Have deleted all broadcom drivers but this one from /lib/modules/3.14.55/kernel/drivers/net/wireless/ wl.ko is here.

boof wrote:PeeBee
<Here is the 32-bit wl driver for Slacko-6.3.0 k3.14.55-nopae as a .pet:

broadcom_wl_v6.30.223.271_x86_32-k3.14.55_nopae_s630.pet>

== Error 404

Makes life hard.

Sorry...

link should be:
http://www.smokey01.com/peebee/broadcom ... e_s630.pet

Amended in original post.

Slack0-6.3.0 definitely has .xz compression - what system were you using???

Many thanks to PeeBee and all who helped with the 64 bit driver. My Dell inspiron running slacko 6.3 now has wifi. I had a difficult time because I only blacklisted one module. After days of pulling my hair out searching the internet for answers i finally returned here and noticed that PeeBee suggested to blacklist two modules. After I blacklisted the second module it worked perfect. Thanks Again