You are not logged in.
Hi! So every time I boot I have to run
# rfkill unblock all
or otherwise I can't use WiFi. After running that everything works perfectly.
Network controller: Broadcom Limited BCM4312 802.11b/g LP-PHY (rev 01)
Subsystem: Hewlett-Packard Company BCM4312 802.11b/g Wireless LAN Controller
Kernel driver in use: wl
Kernel modules: ssb, wl
I am using broadcom-wl. The same issue occurs with broadcom-wl-dkms. I installed using pacman, so I didn't blacklist any other modules.
I am using Wicd. Disabled every other network management services.
dmesg:
https://pastebin.com/raw/9HA3cLky
Last edited by CarterCox (2018-05-09 20:02:20)
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline
Humpty bumpty.
https://askubuntu.com/questions/55868/i … ss-drivers
I followed that but rfkill changes are not persistent.
IMPORTANT NOTE - After September 2014, if you follow this answer and still you have problems installing the correct driver, please try the firmware-b43-installer package and notify us via comments. There were some changes and some drivers will only work with this package. Remember to have a clean system before installing it:
sudo apt install firmware-b43-installer
In some particular cases, after installing the firmware-b43-installer you need to remove the b43 module, enable it again and even proceed to unblock with rfkill:sudo modprobe -r b43
sudo modprobe b43
sudo rfkill unblock all
If you have a Broadcom card that has a different pci.id, please ask a new question. Once solved, the solution will be added to this howto.
Last edited by CarterCox (2018-05-07 00:57:16)
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline
Have a look at adding
rfkill.default_state=1
to your boot options. This should set rfkill to default to unblocked. Theres some other options in the kernel parameters too which may help.
You may also want to look at the wmi module(s) being loaded and possible configuration options for these. Could be wrong module being loaded, or wrong configuration being applied. There's also a possibilty that this may be overiding the rfkill option.
Offline
Hmm. Yeah I'll try that. I'll also try blacklisting possibly conflicting modules.
Thanks for the answer!
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline
Ok I added this
/etc/modprobe.d/blacklist.conf
blacklist b43
blacklist b43legacy
blacklist bcm43xx
blacklist bcma
blacklist brcm80211
blacklist brcmfmac
blacklist brcmsmac
blacklist ssb
because when I install "broadcom-wl-dkms" I get this message:
To load the new module, run the following commands as root:
rmmod b43 b43legacy bcm43xx bcma brcm80211 brcmfmac brcmsmac ssb wl
modprobe wl
Or just reboot the system.
which makes me think this are conflicting modules.
Also
/etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet rfkill.default_state=1"
...
Sadly the problem is still there.
Maybe some modules I don't know about?
Output of mkinitcpio -M:
==> Modules autodetected
ac
acpi_cpufreq
ahci
amd64_edac_mod
ata_generic
atkbd
battery
ehci_pci
evdev
ext4
firewire_ohci
fjes
forcedeth
hid_generic
hp_wmi
i2c_nforce2
i8042
input_leds
joydev
k8temp
kvm_amd
mac_hid
mousedev
nouveau
ohci_pci
pata_acpi
pata_amd
pcc_cpufreq
pcspkr
powernow_k8
psmouse
r592
r852
rtc_cmos
sdhci_pci
sd_mod
serio_raw
shpchp
snd_hda_codec_conexant
snd_hda_intel
sr_mod
ssb
usbcore
usbhid
uvcvideo
wdat_wdt
wl
wmi
wmi_bmof
I don't know what else I could try.
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline
Maybe one of the suggestions in [SOLVED] Wireless hard blocked could help...
Offline
If running `rfkill unblock all` works, then why not just enable the rfkill-unblock service? (Of course also check that you haven't actually enabled the rfkill-block service which would itself explain your symptoms).
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
@artesano: I have tried removing /dev/rfkill, nothing. However, the topic is about a hard block, this is a soft block. I'll try removing the battery later though, althoug my hopes are not up.
@Trilby: Good thinking. However, the service fails:
$systemctl --type=service
...
rfkill-unblock@multi-user.service loaded failed failed ...
Is this strange? Should I have other services availebla other than "rfkill-unblock@.service"?
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline
systemctl cat rfkill-unblock@.service
# /usr/lib/systemd/system/rfkill-unblock@.service
[Unit]
Description=RFKill-Unblock %I
After=rfkill-block@all.service
[Service]
Type=oneshot
ExecStart=/usr/bin/rfkill unblock %I
[Install]
WantedBy=multi-user.target
rfkill-unblock@multi-user.service
is executing
/usr/bin/rfkill unblock multi-user
Offline
So I should create a new service or do I have to enable rfkill-unblock@all.service?
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline
You can either enable rfkill-unblock@all, ...@wlan or ...@YOUR_DEVICE.
If you run rfkill without any arguments, you get a list of all switches with their device names and types.
Edit: grammar...
Last edited by progandy (2018-05-09 20:17:54)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
It lives! Thanks everyone!
And neither the angels in Heaven above
Nor the demons down under the sea
Can ever dissever my soul from the soul
Of the beautiful Annabel Lee;
Offline