Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

bucolic_frolic

(42,676 posts)
Sun Nov 5, 2017, 07:16 PM Nov 2017

Linux Mint 18.1 won't recognize wireless connections

Been on this most of the afternoon. Waded through lots of forums, videos. I think it's a software tweak, maybe a network connection problem. It recognizes the Broadcom 802.11b/g

Maybe I have to setup a network first? seems that's what I did under Windows. But these setup videos all looking for Wifi connections.

The "Network" icon recognizes the network name, security type, and network key.

The router firewall is enabled, as is the Linux firewall.

I've tried to locate networks with terminal, and with the Linux software. Nada.

14 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
Linux Mint 18.1 won't recognize wireless connections (Original Post) bucolic_frolic Nov 2017 OP
did you just install it d_r Nov 2017 #1
It sometimes depends on your hardware... defacto7 Nov 2017 #2
HERE might be some useful info ---- bucolic_frolic Nov 2017 #5
It means.. defacto7 Nov 2017 #6
wow, thanks ... no rfkill didn't work bucolic_frolic Nov 2017 #10
Good luck. defacto7 Nov 2017 #11
One other stupid question... defacto7 Nov 2017 #3
Well thanks for the suggestions so far bucolic_frolic Nov 2017 #4
Did you find any other conflicting drivers? defacto7 Nov 2017 #7
do I have to unblock the router firewall or unblock outgoing traffic? bucolic_frolic Nov 2017 #8
These have nothing to do with a firewall. defacto7 Nov 2017 #9
Yes, connection established bucolic_frolic Nov 2017 #12
Post removed Post removed Aug 2018 #13
Message auto-removed Name removed May 2019 #14

defacto7

(13,485 posts)
2. It sometimes depends on your hardware...
Sun Nov 5, 2017, 10:13 PM
Nov 2017

I remember on a couple upgrades that Broadcom had issues with a hardware vs. software block in a config file that even if your external wifi switch is turned on (laptop) the file has wifi harware set to block. In that file you just unblock both hardware and software. You have the choice of either. There is also a terminal command to do the same. These are all root commands/text not local user.
I'm on my phone now but I'll look it up when I'm on my main machine. In the mean time maybe that gives you something to search.

Try...
sudo rfkill list all

See if your network hardware is listed and if it's blocked.

If anything is blocked then..

sudo rfkill unblock all

or

sudo rfkill unblock (whatever the name of the hardware is)

Broadcom also has issues with other loaded drivers. An installed driver may need to be blacklisted in /etc/modprobe.d/blacklist.conf

bucolic_frolic

(42,676 posts)
5. HERE might be some useful info ----
Sun Nov 5, 2017, 10:46 PM
Nov 2017

sudo rfkill list all

0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: brcmwl-0: Wireless LAN
Soft blocked: no
Hard blocked: yes
2: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
__________________________

So this is telling me there is a hard block on brcm and hp-wifi I think?

Hard block might be the modem/router firewall?

Is that what it's saying to you?

defacto7

(13,485 posts)
6. It means..
Sun Nov 5, 2017, 11:20 PM
Nov 2017

The drivers that run the hardware are blocked. You can unblock them using the rfkill unblock command. If it works you found your issue. Sometimes it's just a Broadcom glitch and it won't return, but sometimes it means there's a driver conflict and Broadcom won't continue after reboot. You have to find the hardware driver that is in conflict then add it to modprobe.d blacklist.conf so it won't try to initialize on restart.

bucolic_frolic

(42,676 posts)
4. Well thanks for the suggestions so far
Sun Nov 5, 2017, 10:42 PM
Nov 2017

I did use
sudo rfkill unblock all earlier today, and just now, no that didn't change things

I didn't know there was a wifi key on my keyboard

should I be looking at the BIOS?

It was a clean install, not an upgrade

defacto7

(13,485 posts)
7. Did you find any other conflicting drivers?
Sun Nov 5, 2017, 11:23 PM
Nov 2017

If there are other wifi drivers or even incorrect Broadcom drivers it will re-block your wifi.

And yes, look in your bios...

It also looks like you have 2 hardware drivers. Do you actually have 2 wifi network cards or harware? If you know you are using Broadcom, blacklist the hp one exactly as it's presented there or find the actual driver name. If you rfkill unblock both, they may turn off again if they're not happy together.

bucolic_frolic

(42,676 posts)
8. do I have to unblock the router firewall or unblock outgoing traffic?
Sun Nov 5, 2017, 11:29 PM
Nov 2017

these were 2 router settings made today

defacto7

(13,485 posts)
9. These have nothing to do with a firewall.
Sun Nov 5, 2017, 11:34 PM
Nov 2017

They are hardware driver conflicts most likely.

If traffic is blocked it won't keep the wifi hardware from activating and wont block the driver in your machine.

bucolic_frolic

(42,676 posts)
12. Yes, connection established
Mon Nov 6, 2017, 08:57 AM
Nov 2017

Wifi button? No.
Wifi heat-sensitive switch? yes. Hasn't worked in years. Suddenly it's alive

But now it asks for password, and the router password doesn't work?

It probably a setup problem from here

Is this a Client, HotSpot, or AdHoc mode?

IPv4 mode automatic, link-local, manual, or shared?

IPv6? similar choices as IPv4

Should the network adapter in BIOS be disabled again?

______________

I think I need to install legacy Broadcom drivers in Linux. Most of the instructions I've found are in Ubuntu or Debian, which are close. Do you think they are close enough to work in Linux Mint?

Response to bucolic_frolic (Original post)

Response to bucolic_frolic (Original post)

Latest Discussions»Culture Forums»Open Source and Free Software»Linux Mint 18.1 won't rec...