[SOLVED] Broadcom BCM43142 driver and Porteus V5.01
Post here if you are a new Porteus member and you're looking for some help.
[SOLVED] Broadcom BCM43142 driver and Porteus V5.01
Post#1 by csc » 24 Feb 2024, 18:06
Hello, I am having difficulties getting the wifi driver running on my machine. I have followed a few of the guides on the website, but without success.
First I tried this advice from Slackbuilds https://slackbuilds.org/repository/15.0 ... oadcom-sta, as suggested by blaze. This failed, but I have concerns about blacklists, and whether that was done correctly.
Next I found this advice by blaze [Solved] No Wifi connection Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01), but I didn't have success. I am still concerned that possibly the drivers are not blacklisted properly. Any advice about proper blacklisting is appreciated.
Finally, I found this advice, Help with installation of Porteus from one usb(Live) to another usb (Post by Blaze #77732), but I am not totally sure how to swap the kernel. I am a newbie, and trying to figure this this out.
Thank you very much for any advice you can offer.
First I tried this advice from Slackbuilds https://slackbuilds.org/repository/15.0 ... oadcom-sta, as suggested by blaze. This failed, but I have concerns about blacklists, and whether that was done correctly.
Next I found this advice by blaze [Solved] No Wifi connection Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01), but I didn't have success. I am still concerned that possibly the drivers are not blacklisted properly. Any advice about proper blacklisting is appreciated.
Finally, I found this advice, Help with installation of Porteus from one usb(Live) to another usb (Post by Blaze #77732), but I am not totally sure how to swap the kernel. I am a newbie, and trying to figure this this out.
Thank you very much for any advice you can offer.
Last edited by csc on 25 Feb 2024, 20:19, edited 1 time in total.
csc
Ed_P
- Blaze
- DEV Team
- Posts: 3998
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
- Contact:
Broadcom BCM43142 driver and Porteus V5.01
Post#3 by Blaze » 24 Feb 2024, 18:46
Hi csc,.
Not bad to see:
Not bad to see:
Code: Select all
su
toor
lspci -knn | egrep 'eth|net|wir' -A6
dmesg | egrep -i 'rtl|broadcom|wlan|firmware|b43|phy|bcm|fw|wl|error|faile|warn|issue|resolve|found|bug|loaded'
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze
[SOLVED] Broadcom BCM43142 driver and Porteus V5.01
Post#4 by csc » 24 Feb 2024, 21:13
Oh, wow, thank you. That sounds easy enough.

One more question, in this same post, viewtopic.php?p=77732#p77732, Blaze starts out by suggesting we should download the broadcom-wl-dkms driver, and then there is a bash script. Do those two items interact? How are they related? Thanks again for your advice.
Last edited by csc on 26 Feb 2024, 02:38, edited 1 time in total.
csc
Broadcom BCM43142 driver and Porteus V5.01
Post#5 by csc » 24 Feb 2024, 21:17
Thanks Blaze. Here is the output:
Code: Select all
root@porteus:/etc/modprobe.d# lspci -knn | egrep 'eth|net|wir' -A6
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 07)
Subsystem: Toshiba America Info Systems Device [1179:f840]
Kernel driver in use: r8169
Kernel modules: r8169
09:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader [10ec:5229] (rev 01)
Subsystem: Toshiba America Info Systems Device [1179:f840]
Kernel driver in use: rtsx_pci
Code: Select all
root@porteus:/etc/modprobe.d# dmesg | egrep -i 'rtl|broadcom|wlan|firmware|b43|phy|bcm|fw|wl|error|faile|warn|issue|resolve|found|bug|loaded'
[ 0.000000] BIOS-provided physical RAM map:
[ 0.010612] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf]
[ 0.011698] No NUMA configuration found
[ 0.027629] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x25 (or later)
[ 0.215863] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[ 0.238191] ACPI: 5 ACPI AML tables successfully acquired and loaded
[ 0.244995] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.273935] libata version 3.00 loaded.
[ 0.279672] vgaarb: loaded
[ 0.282530] pnp: PnP ACPI: found 7 devices
[ 0.309693] zbud: loaded
[ 0.310101] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[ 0.330297] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 0.345279] loop: module loaded
[ 0.368653] ehci-pci 0000:00:1d.0: debug port 2
[ 0.379324] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05
[ 0.379478] hub 1-0:1.0: USB hub found
[ 0.381003] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.05
[ 0.381238] hub 2-0:1.0: USB hub found
[ 0.387432] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.05
[ 0.387638] hub 3-0:1.0: USB hub found
[ 0.429817] Loaded X.509 cert 'Build time autogenerated kernel key: 1895d7f18cef999c7a74af79081e0ec76183caa2'
[ 0.432052] Btrfs loaded, zoned=no, fsverity=no
[ 0.432350] No soundcards found.
[ 0.749654] usb 1-1: New USB device found, idVendor=8087, idProduct=8001, bcdDevice= 0.03
[ 0.750064] hub 1-1:1.0: USB hub found
[ 0.755923] usb 2-1: New USB device found, idVendor=18d1, idProduct=4ee3, bcdDevice= 4.40
[ 1.000591] usb 2-3: New USB device found, idVendor=090c, idProduct=1000, bcdDevice=11.00
[ 1.197518] psmouse serio2: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf00123/0x840300/0x2a800/0x0, board id: 3123, fw id: 1815284
[ 1.243451] usb 2-6: New USB device found, idVendor=0930, idProduct=0225, bcdDevice= 1.12
[ 1.243460] usb 2-6: Product: BCM43142A0
[ 1.243462] usb 2-6: Manufacturer: Broadcom Corp
[ 1.522801] usb 2-7: New USB device found, idVendor=04ca, idProduct=705b, bcdDevice= 0.01
[ 5.967838] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[ 6.212347] r8169 0000:08:00.0 eth0: RTL8106e, 2c:60:0c:e9:b1:de, XID 449, IRQ 50
[ 6.968439] intel_rapl_common: Found RAPL domain package
[ 6.968444] intel_rapl_common: Found RAPL domain core
[ 6.968446] intel_rapl_common: Found RAPL domain uncore
[ 6.968448] intel_rapl_common: Found RAPL domain dram
[ 7.218427] usb 2-7: Found UVC 1.00 device TOSHIBA Web Camera - HD (04ca:705b)
[ 7.421048] Bluetooth: hci0: BCM: chip id 70
[ 7.422053] Bluetooth: hci0: BCM: features 0x06
[ 7.438060] Bluetooth: hci0: BCM43142A0 (001.001.011) build 0000
[ 7.469348] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 7.469352] Bluetooth: hci0: BCM: 'brcm/BCM43142A0-0930-0225.hcd'
[ 7.469354] Bluetooth: hci0: BCM: 'brcm/BCM-0930-0225.hcd'
[ 8.518410] RTL8208 Fast Ethernet r8169-0-800:00: attached PHY driver (mii_bus:phy_addr=r8169-0-800:00, irq=MAC)
[ 14.074264] Bluetooth: hci0: Opcode 0x1003 failed: -110
[ 15.605493] xfwm4[1363]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[ 16.188900] Bluetooth: hci0: Opcode 0x1003 failed: -110
[ 22.095705] ACPI Warning: Time parameter 255 us > 100 us violating ACPI spec, please fix the firmware. (20230331/exsystem-141)
[ 24.122281] Bluetooth: hci0: Opcode 0x1003 failed: -110
[ 63.941138] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 63.941781] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 63.941786] cfg80211: failed to load regulatory.db
[ 64.043668] Broadcom 43xx driver loaded [ Features: PNLS ]
[ 185.304912] usb 2-2: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[ 5112.501087] usb 2-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40
[ 5120.839408] usb 2-1: New USB device found, idVendor=18d1, idProduct=4ee3, bcdDevice= 4.40
[15341.965489] usb 2-1: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40
[15356.936576] usb 2-1: New USB device found, idVendor=18d1, idProduct=4ee3, bcdDevice= 4.40
csc
Broadcom BCM43142 driver and Porteus V5.01
Post#6 by beny » 24 Feb 2024, 21:29
hi take a look if you have the crda package installled is on the /n directory on slackware15
take a look also at bluetooth maybe you have the dual option wifi and bluetooth and they are blocked, rfkill on terminal show you if it is so
take a look also at bluetooth maybe you have the dual option wifi and bluetooth and they are blocked, rfkill on terminal show you if it is so
beny
- ncmprhnsbl
- DEV Team
- Posts: 4290
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Broadcom BCM43142 driver and Porteus V5.01
Post#7 by ncmprhnsbl » 24 Feb 2024, 22:57
while not wrong, this is incomplete: you also must replace /boot/syslinux/vmlinuz with the new one.
fun fact: the vmlinuz is the kernel, and 000-kernel.xzm has the (kernel)modules and firmware that corresponds to that kernel.
they must match, otherwise while you can still boot, your hardware won't be much usable.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
ncmprhnsbl
- Ed_P
- Contributor
- Posts: 8956
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
Broadcom BCM43142 driver and Porteus V5.01
Post#8 by Ed_P » 24 Feb 2024, 23:36
ncmprhnsbl wrote: ↑24 Feb 2024, 22:57while not wrong, this is incomplete: you also must replace /boot/syslinux/vmlinuz with the new one.
fun fact: the vmlinuz is the kernel,


Ed_P
- Blaze
- DEV Team
- Posts: 3998
- Joined: 28 Dec 2010, 11:31
- Distribution: ⟰ Porteus current ☯ all DEs ☯
- Location: ☭ Russian Federation, Lipetsk region, Dankov
- Contact:
Broadcom BCM43142 driver and Porteus V5.01
Post#9 by Blaze » 25 Feb 2024, 11:50
Hi csc.
Note for me and for all =) broadcom-wl-dkms-2024-02-25
At this moment broadcom-wl-dkms and my broadcom-wl-dkms-2024-02-25 too are have:
Not sure if it work with my kernel 6.6.18 but I builded driver broadcom-wl-dkms-6.30.223.271-6.6.18-porteus-x86_64-1bl.xzm successfully.
1. Replace kernel to 6.6.18 from this tarboll 64bit-ALL-kernel6.6.18.tar
2. Copy to modules folder broadcom-wl-dkms-6.30.223.271-6.6.18-porteus-x86_64-1bl.xzm and dkms-3.0.12-x86_64-1_SBo.xzm
3. Reboot and test.
Note for me and for all =) broadcom-wl-dkms-2024-02-25
Code: Select all
#!/bin/bash
# Broadcom 802.11 Linux STA wireless driver
# Slackware build script for broadcom-wl-dkms
# base on https://www.archlinux.org/packages/community/x86_64/broadcom-wl-dkms/
# ported for Slackware by Blaze
# depends=(dkms)
PRGNAM=broadcom-wl-dkms
VERSION=${VERSION:-6.30.223.271}
SOURCE=https://docs.broadcom.com/docs-and-downloads/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz
DEST=/usr/src/$PRGNAM-$VERSION
KERNEL=${KERNEL:-`uname -r`}
BUILD=${BUILD:-1}
TAG=${TAG:-bl}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i586 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}
if [ "$ARCH" = "i586" ]; then
SLKCFLAGS="-O2 -march=i586 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
LIBDIRSUFFIX="64"
else
SLKCFLAGS="-O2"
LIBDIRSUFFIX=""
fi
set -e
rm -rf $PKG $TMP/$PRGNAM-$VERSION $DEST
mkdir -p $TMP $PKG $OUTPUT $TMP/$PRGNAM-$VERSION
cd /tmp/$PRGNAM
wget -q $SOURCE
cp -a *.patch *.conf *.conf.in *.install hybrid-*-nodebug-pcoem-*.tar.gz $TMP/$PRGNAM-$VERSION
cd $TMP/$PRGNAM-$VERSION
tar -xf hybrid-*-nodebug-pcoem-*.tar.gz && rm -f *.tar.gz
sed -i -e '/BRCM_WLAN_IFNAME/s/eth/wlan/' src/wl/sys/wl_linux.c
sed -i -e "/EXTRA_LDFLAGS/s|\$(src)/lib|/usr/lib${LIBDIRSUFFIX}/$PRGNAM|" Makefile
sed -e "s/@PACKAGE_VERSION@/$VERSION/" dkms.conf.in > dkms.conf
sed -n -e '/Copyright/,/SOFTWARE\./{s/^ \* //;p}' src/wl/sys/wl_linux.c
sed -i 's/get_ds()/KERNEL_DS/g' src/wl/sys/wl_iw.c
sed -i 's/get_ds()/KERNEL_DS/g' src/wl/sys/wl_cfg80211_hybrid.c
sed -i '/GE_49 :=/s|:= .*|:= 1|' Makefile
mkdir -p $DEST
install -Dm644 Makefile "$DEST/Makefile"
install -Dm644 dkms.conf "$DEST/dkms.conf"
install -Dm644 -t "$DEST/patches" *.patch
cp -a src "$DEST"
mv -f lib "$DEST/lib${LIBDIRSUFFIX}"
install -Dm644 $DEST/lib${LIBDIRSUFFIX}/wlc_hybrid.o_shipped \
"$PKG/usr/lib${LIBDIRSUFFIX}/broadcom-wl-dkms/wlc_hybrid.o_shipped"
install -Dm644 $DEST/lib${LIBDIRSUFFIX}/wlc_hybrid.o_shipped \
"/usr/lib${LIBDIRSUFFIX}/broadcom-wl-dkms/wlc_hybrid.o_shipped"
install -Dm644 broadcom-wl-dkms.conf \
"$PKG/etc/modprobe.d/broadcom-wl-dkms.conf"
dkms install --no-depmod -m broadcom-wl-dkms -v $VERSION -k `uname -r`
depmod `uname -r`
mkdir -p $PKG/lib/modules/`uname -r`/kernel/drivers/net/wireless $PKG/etc/modprobe.d $PKG/usr/lib${LIBDIRSUFFIX}/broadcom-wl-dkms
cp -a broadcom-wl-dkms.conf $PKG/etc/modprobe.d
cp -a /lib/modules/`uname -r`/kernel/drivers/net/wireless/wl.ko $PKG/lib/modules/`uname -r`/kernel/drivers/net/wireless
cp -a /usr/lib${LIBDIRSUFFIX}/broadcom-wl-dkms/wlc_hybrid.o_shipped $PKG/usr/lib${LIBDIRSUFFIX}/broadcom-wl-dkms
cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$KERNEL-$ARCH-$BUILD$TAG.${PKGTYPE:-txz}
Code: Select all
# https://archlinux.org/packages/extra/x86_64/broadcom-wl-dkms/
001-null-pointer-fix.patch
002-rdtscl.patch
003-linux47.patch
004-linux48.patch
005-debian-fix-kernel-warnings.patch
006-linux411.patch
007-linux412.patch
008-linux415.patch
009-fix_mac_profile_discrepancy.patch
010-linux56.patch
011-linux59.patch
012-linux517.patch
013-linux518.patch
014-linux414.patch
015-linux600.patch
016-linux601.patch
1. Replace kernel to 6.6.18 from this tarboll 64bit-ALL-kernel6.6.18.tar
Code: Select all
# All operations are must to do as root user!
# replace 000-kernel.xzm
# remove crippled_sources.xzm
# optionally add 06-crippled_sources-NNN-XXbit.xzm
/path-to/porteus/base
# replace vmlinuz
/path-to/boot/syslinux
# reboot Porteus
3. Reboot and test.
Linux 6.6.11-porteus #1 SMP PREEMPT_DYNAMIC Sun Jan 14 12:07:37 MSK 2024 x86_64 Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz GenuineIntel GNU/Linux
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
MS-7A12 » [AMD/ATI] Navi 23 [Radeon RX 6600] [1002:73ff] (rev c7) » Vengeance LPX 16GB DDR4 K2 3200MHz C16
Blaze
Broadcom BCM43142 driver and Porteus V5.01
Post#10 by csc » 25 Feb 2024, 18:30
Blaze, that worked. Thank you so much.
Also to everyone else, thank you for teaching me how to replace the kernel, I hadn't done that before either. Thank you very much.
Just to be clear, these are the steps I followed to correct my issue:

Also to everyone else, thank you for teaching me how to replace the kernel, I hadn't done that before either. Thank you very much.
Just to be clear, these are the steps I followed to correct my issue:
Blaze wrote: ↑25 Feb 2024, 11:50
1. Replace kernel to 6.6.18 from this tarboll 64bit-ALL-kernel6.6.18.tar2. Copy to modules folder broadcom-wl-dkms-6.30.223.271-6.6.18-porteus-x86_64-1bl.xzm and dkms-3.0.12-x86_64-1_SBo.xzmCode: Select all
# All operations are must to do as root user! # replace 000-kernel.xzm # remove crippled_sources.xzm # optionally add 06-crippled_sources-NNN-XXbit.xzm /path-to/porteus/base # replace vmlinuz /path-to/boot/syslinux # reboot Porteus
3. Reboot and test.
csc