Ancient laptop seeks Broadcom drivers solution

I ran a 1545 on Linux from 2012 [when it was given to me broken], up to when it died as a laptop a few months back and never had a problem with the BCM43 Wi-Fi,
BCM43 chip didn't work on OpenBSD. So I swapped it with cheap Intel card, for increased compatibility (with Linux also). BCM43 require proprietary driver even in Linux, while Intel one is open-source I think (or, at least is much easier to install and manage).
 


Hello Brickwizard and others; thanks for your helpful suggestions. I apologise for the delay in getting back to this forum. It's that four letter word: work.

>Open the Antix software repository, search for Broadcom FW cutter and install , it will select and build the correct drivers for your chipset [provided they are still on file] oh you will need alternative means to connecting to the net

Yeah, I am connecting to the net via a CAT5 cable. I installed the FW cutter as you suggested. Rebooted. No change. I shall try to go through the other suggestions that you made. Kind regards.
 
Hello Brickwizard and others. Thanks once more for your helpful suggestions. I invested twelve quid in a TP Link 300Mbps Mini Wireless N USB adapter. I had to download the Linux drivers for it to work, I understood. I was in the ICE WP desktop. I fumbled around and found a wifi connector in a window. I pressed and pressed... as you do... and as if by magic the Broadcom drivers appeared to lift off (ie start working) as the blue light on the wifi hardware switch on the computer lit up. Then I moved onto the Cinnamon desktop... and the internal wifi stopped working. Back to bleep-bleep square one. I think the issue is within Connman. Any suggestions? For the avoidance of doubt, I have not installed the TP link drivers yet.
 
Well, I have a solution. I think the start of it was Mr Wizard's suggestion of installing the BCM4312 Broadcom driver set. But I hit some snags along the way. Painful ones. So much so I purchased a TP link wifi dongle, as suggested by another user here. It did not work. After to-ing and fro-ing with the TP Link's customer service link in the Philippines, they told me the product would not work with my version of Linux - Anti X. I returned for an efficient refund. Then I turned to a well-known AI service and did loads of stuff (I forget exactly which). The good news was that now the wifi card light on the computer was now on all the time. More investigations with Mr AI. Terminal told me: hp-wifi: Wireless LAN soft blocked no/ hard blocked yes. Followed the instructions from AI and eventually got the bally thing to work. NB: Mr AI told me that certain TP link dongles work with AntiX; including ones available from a well-known online retailer. Meantime, I plumped for the Cinnamon front end and really like it. Clearly, part of the AntiX attraction is the slim resources needed. I am happy with it. I will probably use it to bring back other old laptops from the dead. Thanks to everyone for your support. Kind regards, Jingleman1
 
hp-wifi: Wireless LAN soft blocked no/ hard blocked yes.
Slap me round the head with a wet grouper. I should have thought of that...
 
Never mind, Mr Wizard. FYI here is the print out from the AI supporter. I only needed to get to step 2. Also, remember that your support with BCM4312 was the start of the road to victory. Kindest regards and thanks. JM1

Step-by-Step Guide to Fixing Wi-Fi on HP Mini 1100 (Linux)

Problem: Wi-Fi shows NO-CARRIER, Hard Blocked, or fails to connect with errors like "Not authorized to control networking".

1. Check Wi-Fi Interface Status

bash
ip a
  • Look for wlan0 or similar. If missing, the driver isn’t loaded.

2. Unblock Wi-Fi (If Hard/Soft Blocked)

bash
rfkill list # Check blocks
sudo rfkill unblock all # Unblock all

3. Verify Driver and Firmware

bash
lspci -k | grep -A 3 -i network # Identify Wi-Fi chipset
sudo dmesg | grep -i firmware # Check for errors
  • Reinstall drivers/firmware (e.g., for Intel Wi-Fi):
    bash
  • sudo apt install --reinstall iwlwifi firmware-iwlwifi # Debian/Ubuntu
    sudo modprobe -r iwlwifi && sudo modprobe iwlwifi # Reload driver

4. Fix Permission Issues

Temporary Fix (Use sudo)

bash
sudo nmcli device wifi connect "SSID" password "PASSWORD"

Permanent Fix:

  1. Add user to netdev group:
    bash
  • sudo usermod -aG netdev $USER
  • Update Polkit rules:
    bash
sudo nano /etc/polkit-1/localauthority/50-local.d/50-network-manager.pkla
Paste:
ini
  • [NetworkManager Permissions]
    Identity=unix-group:netdev
    Action=org.freedesktop.NetworkManager.*
    ResultAny=yes
    ResultInactive=yes
    ResultActive=yes
  • Restart services:
    bash
  1. sudo systemctl restart polkit NetworkManager

5. Connect to Wi-Fi

bash
nmcli device wifi list # List networks
nmcli device wifi connect "SSID" password "PASSWORD"
  • Still failing? Use --ask for password input:
    bash
  • nmcli --ask device wifi connect "SSID"

6. Disable Power Saving

bash
sudo sed -i 's/wifi.powersave = 3/wifi.powersave = 2/' /etc/NetworkManager/conf.d/*
sudo systemctl restart NetworkManager

7. Blacklist Conflicting Modules (HP Laptops)

bash
echo "blacklist hp-wmi" | sudo tee /etc/modprobe.d/hp-wmi.conf
sudo reboot

8. Test Hardware (Last Resort)

  • Boot a Live USB (e.g., Ubuntu). If Wi-Fi works:
    • Reinstall your OS or drivers.
  • If not, try a USB Wi-Fi adapter.

Summary of Key Commands

PurposeCommand
Unblock Wi-Fisudo rfkill unblock all
Reinstall Intel Wi-Fisudo apt install --reinstall iwlwifi firmware-iwlwifi
Fix Permissionssudo usermod -aG netdev $USER + Polkit rule
Connect to Wi-Finmcli device wifi connect "SSID" password "PASSWORD"
 
Try before you buy.

To avoid the headache as described above, I always try to connect to wifi, play a youtube video, to be sure it works before hitting the Install button.

I am not a brand fidelity so as long as can save an old clunker I am happy.

Between MX, Antix and Puppy I never failed - never had to go to a fourth try. The machines (all more than a decade old) include brands from HP, Acer, Asus, Samsung … one Acer Chromebook and a few Mac) . Puppy is a strange beast , but its ways to connect and to test sound cards are superb.
 
Puppy is a strange beast...

Ooh, don't let her hear you say that! She'll go into a sulk, and refuse to come out & "play ball..."

LOLOL!! :P :P


Mike. :D
 
Try before you buy.

Between MX, Antix and Puppy I never failed -
So you are saying that I should have installed a different distro immediately, rather than faff around with making Antix work with my hardware?
 
Taken from my what is the best Linux thread.

"What is best for me or any other member, Is not necessarily the best for you,
ONLY YOU CAN CHOOSE"
 
Taken from my what is the best Linux thread.

"What is best for me or any other member, Is not necessarily the best for you,
ONLY YOU CAN CHOOSE"
I took ML's remarks the way they were intended; as a learning point. I am feeling really chuffed with the outcome overall. Thank you all for the interest that you have shown in my case.
 
I have investigated the alternative of using different 32 bit distros. The following is from Dr AI. However, there is no way on God's cyber-space that I am going to undo what I have done already. I merely repost here as a way for subsequent users to learn from my three weeks of hell (surely intensive learning process? Ed).

1. MX Linux (32-bit) – Top Recommendation

  • Why?
    • Same lightweight efficiency as AntiX, but with non-free firmware included (fewer driver headaches).
    • Uses Xfce (more polished than IceWM/Fluxbox).
    • MX Tools make system tweaks easier.
  • Best for: Old 32-bit PCs with 512MB–2GB RAM.

2. Debian 12 (32-bit) – The "DIY" Option

  • Why?
    • The base for AntiX/MX Linux—install Xfce/LXDE and manually add non-free firmware.
    • More control, but requires setup.
  • Best for: Tinkerers who want a clean slate.

3. Q4OS (32-bit) – Windows-Like & Lightweight

  • Why?
    • Uses Trinity Desktop (like old Windows XP) or KDE Plasma.
    • Runs on very old PCs (even 256MB RAM).
  • Best for: Nostalgic users or extremely low-spec hardware.

4. Bodhi Linux (32-bit) – Ultra-Light Moksha Desktop

  • Why?
    • Ubuntu-based (but still supports 32-bit!).
    • Moksha Desktop (Enlightenment fork) sips RAM (~150MB idle).
  • Best for: Machines too weak for Xfce.
 
Since antix is debian based, this page: https://wiki.debian.org/wl, covers how to support broadcom in detail.
This thread explains a lot about why ive had issues on debian. You can also write the un-free version of debian to iso ironically for free, as i don't like these partial solutions. I wish debian wasn't so fragmented in terms of driver support.

I saved that page though in case i need help with this again.
 
But in retrospect would it have been easier to install a different distro?

How long is a piece of string?

Computers and their users can be as individual as two sets of fingerprints.

I have all the distros you mentioned at #32 in my stable, but the 64-bit versions.

I had no issues in installing them, and would find it hard to pick one as being easier to install.

Wizard
 
This thread explains a lot about why ive had issues on debian. You can also write the un-free version of debian to iso ironically for free, as i don't like these partial solutions. I wish debian wasn't so fragmented in terms of driver support.

I saved that page though in case i need help with this again.
 
"I saved that page though in case i need help with this again." Thank you for the thought. That workaround was far too complex for this newbie.
 


Follow Linux.org

Members online

No members online now.

Top