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 Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

defacto7

(14,023 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.

Recommendations

0 members have recommended this reply (displayed in chronological order):

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
Latest Discussions»Culture Forums»Open Source and Free Software»Linux Mint 18.1 won't rec...»Reply #6