You are not logged in.
Hey guys,
I've got a problem with the brcmsmac module for my BCM4313: Wifi doesn't work when I load it at boot time, only removing it and inserting it manually helps. I know there was a bug report about a similar problem at https://bugs.archlinux.org/task/27938 but that didn't help me much...
Journalctl reads the following:
Jun 03 19:18:45 archbook kernel: cfg80211: Calling CRDA to update world regulatory domain
Jun 03 19:18:45 archbook kernel: bcma: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x24, class 0x0)
Jun 03 19:18:45 archbook kernel: bcma: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x18, class 0x0)
Jun 03 19:18:45 archbook kernel: bcma: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x11, class 0x0)
Jun 03 19:18:45 archbook kernel: bcma: Bus registered
Jun 03 19:18:45 archbook kernel: brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
Jun 03 19:18:45 archbook udevd[1046]: starting version 184
Jun 03 19:18:45 archbook systemd-journal[1047]: Journal started
Jun 03 19:18:46 archbook systemd-fsck[1048]: [66B blob data]
Jun 03 19:18:46 archbook kernel: firmware 0000:02:00.0: firmware_loading_store: unexpected value (0)
Jun 03 19:18:46 archbook kernel: ieee80211 phy0: brcmsmac: fail to load firmware brcm/bcm43xx-0.fw
Jun 03 19:18:46 archbook kernel: ieee80211 phy0: brcmsmac: Failed to find firmware usually in /lib/firmware/brcm
Jun 03 19:18:46 archbook kernel: brcmsmac: brcms_bcma_probe: brcms_attach failed!
Jun 03 19:18:46 archbook systemd-modules-load[1049]: Inserted module 'brcmsmac'
Jun 03 19:18:46 archbook kernel: brcms_module_init: register returned 0
What can I do about this?
As I already pointed out, adding it manually afterwards works without the slightest problem
Offline
One thing i notice is:
Jun 03 19:18:46 archbook kernel: ieee80211 phy0: brcmsmac: Failed to find firmware usually in /lib/firmware/brcm
While the actual firmware is in /usr/lib/:
% locate brcm
[...]
/usr/lib/firmware/brcm
ᶘ ᵒᴥᵒᶅ
Offline
Hi litemotiv, thanks for your advice! I placed symlinks for bcm43xx-0.fw and bcm43xx_hdr-0.fw and now loading at bootup works.
Hmm, strange though... why does modprobing manually look in /lib/usr/firmware/ while systemd-modules-load while uses /lib/firmware/?
Offline
A lot of system paths have changed recently, i think this is fixed in the current packages in [testing] and will come to [core] in the near future.
ᶘ ᵒᴥᵒᶅ
Offline
Ah, perfect, thanks again!
Offline