You are not logged in.

#1 2014-08-10 08:27:21

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

[SOLVED] Automatically loading module

Hi everyone,

Since I succeeded (with the help of some of you) to get my wi-fi back, I am unable to configure my system in order to automatically load the wi-fi module at boot. I actually read this post and this page of the wiki and so I created a new file : /etc/modules.load.d/brcmsmac.conf.

This file only contains a line : brcmsmac.

Despite this, brcmsmac isn't loaded.  Is there something I am missing?

Last edited by nugetchar (2014-08-10 12:32:33)

Offline

#2 2014-08-10 08:52:12

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED] Automatically loading module

/etc/modules-load.d/brcmsmac.conf


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2014-08-10 09:17:02

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

My bad, it's a typo in my message. Anyway, the path is good :

[nugetchar@arch ~]$ more /etc/modules-load.d/brcmsmac.conf 
brcmsmac

But it is still not working.

Last edited by nugetchar (2014-08-10 09:17:17)

Offline

#4 2014-08-10 09:35:28

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,240

Re: [SOLVED] Automatically loading module

A couple of thoughts - do you need to blacklist a different wireless module that the kernel is trying to load automatically at boot that might interefere with the brcmsmac module that is working?  Also do  you need to add the brcmsmac module to the mkiinitcpio.conf modules array and then remake the initial ramdisk using mkinitcpio -p linux so that the module is loaded during boot?  (See https://wiki.archlinux.org/index.php/mkinitcpio). I don't have the same wireless card as you but it may be worth exploring these ideas?


Mike C

Offline

#5 2014-08-10 09:56:04

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

I don't have to blacklist any other wireless module. Actually I had to unblacklist bcma to have brcmsmac to work. I also tried to add the brcmsmac module to the mkiinitcpio.conf file but mkinitcpio -p linux gives me the following output :

[nugetchar@arch ~]$ mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img

I tried to reboot anyway but then, nothing happened. I still have to manually load the brcmsmac module with

 modprobe brcmsmac 

.

Offline

#6 2014-08-10 10:27:20

rebootl
Member
Registered: 2012-01-10
Posts: 431
Website

Re: [SOLVED] Automatically loading module

What is the output of 'systemctl status systemd-modules-load' ?

As for the mkinitcpio, you need to execute it as root, respectively using sudo.


Personal website: reboot.li
GitHub: github.com/rebootl

Offline

#7 2014-08-10 10:40:37

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

I'll try to execute mkinitcpio as root and tell you.

Here's the output for sudo systemctl status systemd-modules-load :

[nugetchar@arch ~]$ sudo !!
sudo systemctl status systemd-modules-load
[sudo] password for nugetchar: 
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: active (exited) since Sun 2014-08-10 11:50:26 EDT; 48min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 174 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
 Main PID: 174 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-modules-load.service

Aug 10 11:50:26 arch systemd[1]: Started Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Last edited by nugetchar (2014-08-10 10:41:10)

Offline

#8 2014-08-10 10:43:25

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,240

Re: [SOLVED] Automatically loading module

nugetchar wrote:

I don't have to blacklist any other wireless module. Actually I had to unblacklist bcma to have brcmsmac to work. I also tried to add the brcmsmac module to the mkiinitcpio.conf file but mkinitcpio -p linux gives me the following output :

[nugetchar@arch ~]$ mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> ERROR: Unable to write to /boot/initramfs-linux.img
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> ERROR: Unable to write to /boot/initramfs-linux-fallback.img

I tried to reboot anyway but then, nothing happened. I still have to manually load the brcmsmac module with

 modprobe brcmsmac 

.

It looks like you did the mkinitcpio command as normal user - I think you will need to do it as root.  I guess you changed the line (as root) in the file /etc/mkinitcpio.conf to include:

MODULES="brcmsmac"

Mike C

Offline

#9 2014-08-10 10:47:06

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

Well, I did both of your suggestions and this is the result for executing mkinitcpio as root :

[nugetchar@arch ~]$ sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.15.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.15.8-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: smsmdtv
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

And here is the output of the /etc/mkinitcpio.conf file :

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="brcmsmac"

# BINARIES
# This setting includes any additional binaries a given user may

....

After a reboot, it is still not working hmm

Offline

#10 2014-08-10 10:57:54

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,240

Re: [SOLVED] Automatically loading module

OK maybe have a look at the systemd journal for clues about the modules straight after the boot - you can see this for the log since the last boot by doing as root

# journalctl -b

Or to put the output into a file called journal-debug.log you can do

# journalctl -b > journal-debug.log

The # is the prompt showing you are root (or you can prefix the command with sudo as normal user if you have sudo set up).

There may be some lines in the log showing what is happening with module loading or failure to load.

Also just to check the file permissions on your module conf file what is the output of

ls -l /etc/modules-load.d/

Last edited by mcloaked (2014-08-10 11:08:09)


Mike C

Offline

#11 2014-08-10 11:34:19

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

Okay, so here are the permissions :

[nugetchar@arch ~]$ ls -l /etc/modules-load.d/
total 4
-rw-r--r-- 1 root root 8 Aug 10 00:21 brcmsmac.conf

And here is the part of the journal which might be interesting :

Aug 10 13:22:28 arch org.a11y.Bus[424]: Activating service name='org.a11y.atspi.Registry'
Aug 10 13:22:28 arch org.a11y.Bus[424]: Successfully activated service 'org.a11y.atspi.Registry'
Aug 10 13:22:28 arch org.a11y.atspi.Registry[449]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Aug 10 13:22:28 arch org.a11y.atspi.Registry[449]: ** (at-spi2-registryd:452): WARNING **: Failed to register client: GDBus.Error:org.freedeskto
Aug 10 13:22:28 arch org.a11y.atspi.Registry[449]: ** (at-spi2-registryd:452): WARNING **: Unable to register client with session manager
Aug 10 13:22:30 arch dbus[353]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
Aug 10 13:22:30 arch systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Aug 10 13:22:30 arch systemd[1]: Started RealtimeKit Scheduling Policy Service.
Aug 10 13:22:30 arch dbus[353]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully called chroot.
Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully dropped privileges.
Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully limited resources.
Aug 10 13:22:30 arch rtkit-daemon[485]: Running.
Aug 10 13:22:30 arch rtkit-daemon[485]: Watchdog thread running.
Aug 10 13:22:30 arch rtkit-daemon[485]: Canary thread running.
Aug 10 13:22:30 arch rtkit-daemon[485]: Successfully made thread 484 of process 484 (/usr/bin/pulseaudio) owned by '1000' high priority at nice 
Aug 10 13:22:30 arch rtkit-daemon[485]: Supervising 1 threads of 1 processes of 1 users.
Aug 10 13:22:31 arch org.freedesktop.Notifications[424]: ** (notify-osd:496): WARNING **: dnd_is_screensaver_active(): Got error "The name org.g
Aug 10 13:22:32 arch pulseaudio[484]: Availability of port 'analog-input-headset-mic' is inconsistent!
Aug 10 13:22:32 arch pulseaudio[484]: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez was not provided
Aug 10 13:22:42 arch org.freedesktop.Notifications[424]: ** (notify-osd:496): WARNING **: dnd_is_screensaver_active(): Got error "The name org.g
Aug 10 13:22:42 arch org.freedesktop.Notifications[424]: (notify-osd:496): Wnck-WARNING **: Unhandled action type _OB_WM_ACTION_UNDECORATE
Aug 10 13:22:54 arch slim[357]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 10 13:22:54 arch slim[357]: > Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
Aug 10 13:22:54 arch slim[357]: >                   Ignoring extra symbols
Aug 10 13:22:54 arch slim[357]: Errors from xkbcomp are not fatal to the X server
Aug 10 13:23:24 arch sudo[545]: nugetchar : TTY=pts/0 ; PWD=/home/nugetchar ; USER=root ; COMMAND=/usr/bin/modprobe brcmsmac
Aug 10 13:23:24 arch sudo[545]: pam_unix(sudo:session): session opened for user root by nugetchar(uid=0)
Aug 10 13:23:24 arch kernel: bcma: bus0: Found chip with id 0x4313, rev 0x01 and package 0x08
Aug 10 13:23:24 arch kernel: bcma: bus0: Core 0 found: ChipCommon (manuf 0x4BF, id 0x800, rev 0x24, class 0x0)
Aug 10 13:23:24 arch kernel: bcma: bus0: Core 1 found: IEEE 802.11 (manuf 0x4BF, id 0x812, rev 0x18, class 0x0)
Aug 10 13:23:24 arch kernel: bcma: bus0: Core 2 found: PCIe (manuf 0x4BF, id 0x820, rev 0x11, class 0x0)
Aug 10 13:23:24 arch kernel: bcma: bus0: Bus registered
Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
Aug 10 13:23:24 arch sudo[545]: pam_unix(sudo:session): session closed for user root
Aug 10 13:23:24 arch NetworkManager[351]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/bcma
Aug 10 13:23:24 arch systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill1...
Aug 10 13:23:24 arch kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Aug 10 13:23:24 arch kernel: ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243
Aug 10 13:23:24 arch systemd[1]: Started Load/Save RF Kill Switch Status of rfkill1.
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): using nl80211 for WiFi device control
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): driver supports Access Point (AP) mode
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'brcmsmac' ifindex: 3)
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/2
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Aug 10 13:23:24 arch systemd-udevd[547]: renamed network interface wlan0 to wlp3s0
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): preparing device
Aug 10 13:23:24 arch dbus[353]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement)
Aug 10 13:23:24 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Aug 10 13:23:24 arch systemd[1]: Starting WPA supplicant...
Aug 10 13:23:25 arch dbus[353]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Aug 10 13:23:25 arch NetworkManager[351]: <info> wpa_supplicant started
Aug 10 13:23:25 arch systemd[1]: Started WPA supplicant.
Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0) supports 4 scan SSIDs
Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: starting -> ready
Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 
Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
Aug 10 13:23:25 arch NetworkManager[351]: <info> (wlp3s0) supports 4 scan SSIDs
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
Aug 10 13:23:26 arch NetworkManager[351]: <info> Auto-activating connection 'Livebox-B34A'.
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) starting connection 'Livebox-B34A'
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 10 13:23:26 arch NetworkManager[351]: <info> NetworkManager state is now CONNECTING
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0/wireless): connection 'Livebox-B34A' has security, and secrets exist.  No ne
Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'ssid' value 'Livebox-B34A'
Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'scan_ssid' value '1'
Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'auth_alg' value 'OPEN'
Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: added 'psk' value '<omitted>'
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
Aug 10 13:23:26 arch NetworkManager[351]: <info> Config: set interface ap_scan to 1
Aug 10 13:23:26 arch kernel: wlp3s0: authenticate with b0:75:d5:87:b3:4a
Aug 10 13:23:26 arch kernel: wlp3s0: send auth to b0:75:d5:87:b3:4a (try 1/3)
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: inactive -> authenticating
Aug 10 13:23:26 arch kernel: wlp3s0: authenticated
Aug 10 13:23:26 arch kernel: wlp3s0: associate with b0:75:d5:87:b3:4a (try 1/3)
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
Aug 10 13:23:26 arch kernel: wlp3s0: RX AssocResp from b0:75:d5:87:b3:4a (capab=0x431 status=0 aid=1)
Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: associated
Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: true (implement)
Aug 10 13:23:26 arch kernel: wlp3s0: associated
Aug 10 13:23:26 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: associating -> associated
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: associated -> 4-way handshake
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): supplicant interface state: 4-way handshake -> completed
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Aug 10 13:23:26 arch NetworkManager[351]: <info> dhcpcd started with pid 585
Aug 10 13:23:26 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
Aug 10 13:23:26 arch dhcpcd[585]: version 6.4.3 starting
Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: version 6.4.3 starting
Aug 10 13:23:26 arch NetworkManager[351]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: DUID 00:01:00:01:1b:77:fa:2f:0c:84:dc:63:61:ef
Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: IAID dc:63:61:ef
Aug 10 13:23:26 arch dhcpcd[585]: DUID 00:01:00:01:1b:77:fa:2f:0c:84:dc:63:61:ef
Aug 10 13:23:26 arch dhcpcd[585]: wlp3s0: IAID dc:63:61:ef
Aug 10 13:23:26 arch dhcpcd[585]: wlp3s0: soliciting an IPv6 router
Aug 10 13:23:26 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: soliciting an IPv6 router
Aug 10 13:23:27 arch dhcpcd[585]: wlp3s0: rebinding lease of 192.168.1.23
Aug 10 13:23:27 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: rebinding lease of 192.168.1.23
Aug 10 13:23:32 arch dhcpcd[585]: wlp3s0: leased 192.168.1.23 for 86400 seconds
Aug 10 13:23:32 arch dhcpcd[585]: wlp3s0: adding route to 192.168.1.0/24
Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
Aug 10 13:23:32 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: leased 192.168.1.23 for 86400 seconds
Aug 10 13:23:32 arch NetworkManager[351]: dhcpcd[585]: wlp3s0: adding route to 192.168.1.0/24
Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): DHCPv4 state changed preinit -> reboot
Aug 10 13:23:32 arch NetworkManager[351]: <info>   address 192.168.1.23
Aug 10 13:23:32 arch NetworkManager[351]: <info>   plen 24 (255.255.255.0)
Aug 10 13:23:32 arch NetworkManager[351]: <info>   gateway 192.168.1.1
Aug 10 13:23:32 arch NetworkManager[351]: <info>   server identifier 192.168.1.1
Aug 10 13:23:32 arch NetworkManager[351]: <info>   lease time 86400
Aug 10 13:23:32 arch NetworkManager[351]: <info>   nameserver '192.168.1.1'
Aug 10 13:23:32 arch NetworkManager[351]: <info>   nameserver '192.168.1.1'
Aug 10 13:23:32 arch NetworkManager[351]: <info>   domain name 'home'
Aug 10 13:23:32 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Aug 10 13:23:32 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Aug 10 13:23:32 arch NetworkManager[351]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Aug 10 13:23:32 arch NetworkManager[351]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Aug 10 13:23:32 arch NetworkManager[351]: <info> NetworkManager state is now CONNECTED_LOCAL
Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
Aug 10 13:23:32 arch NetworkManager[351]: <info> NetworkManager state is now CONNECTED_GLOBAL
Aug 10 13:23:32 arch NetworkManager[351]: <info> Policy set 'Livebox-B34A' (wlp3s0) as default for IPv4 routing and DNS.
Aug 10 13:23:32 arch NetworkManager[351]: <info> Writing DNS information to /usr/bin/resolvconf
Aug 10 13:23:34 arch NetworkManager[351]: <info> Activation (wlp3s0) successful, device activated.

It kind of unreadable so here is the result with a grep :

Aug 10 13:22:09 arch systemd-modules-load[175]: Module 'brcmsmac' is blacklisted
Aug 10 13:23:24 arch sudo[545]: nugetchar : TTY=pts/0 ; PWD=/home/nugetchar ; USER=root ; COMMAND=/usr/bin/modprobe brcmsmac
Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: mfg 4bf core 812 rev 24 class 0 irq 17
Aug 10 13:23:24 arch NetworkManager[351]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/bcma0:0/ieee80211/phy0/rfkill1) (driver brcmsmac)
Aug 10 13:23:24 arch kernel: ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 243
Aug 10 13:23:24 arch NetworkManager[351]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'brcmsmac' ifindex: 3)
Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Aug 10 13:23:24 arch kernel: brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement)
Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcmsmac: brcms_ops_bss_info_changed: associated
Aug 10 13:23:26 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: true (implement)
Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
Aug 10 13:23:32 arch kernel: brcmsmac bcma0:0: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)

It appear that brcmsmac is blacklisted, but this is weird because in the /etc/mordprobe.d/modprobe.conf file, it is not :

[nugetchar@arch etc]$ more modprobe.d/modprobe.conf 
alias floppy off
blacklist fd0
blacklist floppy
blacklist ipv6
blacklist pcspkr
blacklist snd_pcsp

Offline

#12 2014-08-10 11:42:24

lucke
Member
From: Poland
Registered: 2004-11-30
Posts: 4,018

Re: [SOLVED] Automatically loading module

Don't you have other files in /etc/modprobe.d/?

Offline

#13 2014-08-10 11:48:46

oliver
Member
Registered: 2007-12-12
Posts: 448

Re: [SOLVED] Automatically loading module

take a look at /lib/modules-load.d and see if it's blacklisted there.

Offline

#14 2014-08-10 12:05:26

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,240

Re: [SOLVED] Automatically loading module

The lines in the journal log either side of the line saying that the module was blacklisted would be possibly useful, but those lines are earlier than the start of the log segment that was quoted.  But certainly it would be useful to find in which conf file the module is being blacklisted - if that can be fixed then it is likely that the problem will be resolved.


Mike C

Offline

#15 2014-08-10 12:27:55

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

Aaaaand there it is!

[nugetchar@arch lib]$ ls ./mod
modprobe.d/     modules/        modules-load.d/ 
[nugetchar@arch lib]$ ls ./modprobe.d/
broadcom-wl.conf  usb-load-ehci-first.conf
[nugetchar@arch lib]$ more ./modprobe.d/broadcom-wl.conf 
blacklist b43
blacklist ssb
blacklist bcma
blacklist brcmsmac
blacklist brcmfmac

So, I believe I should unblacklist bcma and brcmsmac. But what about brcmfmac ?

Offline

#16 2014-08-10 12:30:22

mcloaked
Member
From: Yorkshire, UK
Registered: 2012-02-02
Posts: 1,240

Re: [SOLVED] Automatically loading module

Perhaps just try the two you suggest and see if it works - and if not then unblacklist the third if that doesn't work?


Mike C

Offline

#17 2014-08-10 12:32:19

nugetchar
Member
Registered: 2014-08-09
Posts: 39
Website

Re: [SOLVED] Automatically loading module

I tried, it worked, so I'm not going to touch the third smile

Well, thank you for you help and your suggestions everyone wink

Offline

Board footer

Powered by FluxBB