New Install. WiFi working but no networks show up.
Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
New Install. WiFi working but no networks show up.
I've installed 18.2 as the only OS on a first generation MacBook Air using a USB stick. The wireless card is on, but no networks are showing up in the list. From another computer, I downloaded the Broadcom b43-cutter-installer wireless card installer and the B43 driver for my wireless card (PCI.ID [14e4:4328]).
$ lspci -knn | grep Net -A3; rfkill list
02:00.0 Network controller [0280]: Broadcom Corporation BCM4321 802.11a/b/g/n [14e4:4328] (rev 05)
Subsystem: Apple Inc. AirPort Extreme [106b:008b]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
****
$iwconfig
wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
lo no wireless extensions.
I tried disabling BlueTooth, but it didn't help.
I can successfully select and login into my WiFi network when I start the install, but it doesn't retain that info after it finishes and I have to install the Broadcom drivers.
It has worked once and I was able to update the default packages. I was able to reboot immediately after that and get an Internet connection. The next day, I don't have a connection anymore and can't see the WiFi networks. I tried disabling and re-enabling the Broadcom driver.
Can anyone see what's wrong or tell me what else to try?
Ok, I just rebooted the machine to run those commands in Terminal and when I did, the machine connected to my network with the preferred connection and now shows the wifi access points in the list when I click on the wifi icon in the task bar. I have rebooted this somewhere around 10 times before this on different days hoping for a connection, but didn't get one. It waited until after I posted on this forum to start working. [Arrrg!!!]
But maybe something else is going on. I've seen others mentioning dropped connections or a loss of wifi connections in their list after updating. Is this Broadcom driver less reliable than others? Is there a better one that I should use?
Please tell me how to gracefully uninstall this and install the better one (if there is one).
Thank you.
Here is the output of the ifconfig statement now that I DO have a connection:
if the first is working, but the second doesn't, that means your issue is not driver related, but name resolution is not working.
a working ping looks like this:
Code:
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=55.3 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=26.5 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=54.8 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=92.4 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=33.2 ms
...etc etc...
But maybe something else is going on. I've seen others mentioning dropped connections or a loss of wifi connections in their list after updating. Is this Broadcom driver less reliable than others?
I've had several computers with Broadcom wireless and used them with Ubuntu, Slackware, and Mint. In my experience, once I've gotten a Broadcom wireless connection working, it remains stable.
For what it's worth, I think something more is going on.
As Frankbell has suggested it does look like 'something more is going on'. It may well be a USB power management issue. Some users have found TLP useful for taming power management in laptops...
@ferrari: there was definitely something else going on, but we'll never know what it was. I bought a USB Ethernet dongle on Amazon and reinstalled (The lesson learned is to try to get a wired connection to make life easier.)
I'm still having dropoff issues with my connection and am installing TLP, but I have a question.
Here's is the output of lsusb:
Code:
$ lsusb
Bus 002 Device 003: ID 05ac:8505 Apple, Inc. Built-in iSight
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 003: ID 05ac:0223 Apple, Inc. Internal Keyboard/Trackpad (ANSI)
Bus 007 Device 002: ID 05ac:8242 Apple, Inc. Built-in IR Receiver
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 05ac:8210 Apple, Inc.
Bus 005 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 005 Device 006: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Should I BLACKLIST the range "0a5c:4500" for the Broadcom hub instead of the range you gave (i.e. "106b:008b").
How did you get that range and what is it for?
I didn't give a range - I gave a specific chipset (106b:008b), which was the one listed in the output in your opening post pertaining to the wireless device. If you read the reference I provided a link to, it explains how to exclude particular devices (by chipset) from USB autosuspending. YMMV.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.