Hi,
As my Broadcom BCM43142 wasn’t recognized, I installed the broadcom-wl package from packman as I didn’t managed to run bcmw15.inf with ndiswrapper.
I can see the card now in the Network Manager, but when I intend to edit it to connect on a wi-fi network, there is a YasT2 error at the final step:
**Details: undefined method ‘empty’
for 0.fixnum
Caller /usr/share/YasT2/modules/CanItems.rb:2029:in ‘block in Commit’
**While i’m still looking a way to fix it, your help is welcome.Thanks
Actually, two packages are required (broadcom-wl, and the kernel-specific package eg broadcom-wl-kmp-default)
I can see the card now in the Network Manager, but when I intend to edit it to connect on a wi-fi network, there is a YasT2 error at the final step:
If you’re using NetworkManager, the YaST utility is not used (as you configure via NM itself). You probably need to back up a step and show us the hardware details with driver
/usr/sbin/hwinfo --wlan
or
/sbin/lspci -nnk |grep '\02' -A3
Confirm that the wl driver is loaded, then confirm that a network device node exists for it
/sbin/ifconfig
If that checks out, move on to configuring with NetworkManager. If you’re using wicked, then you can use YaST > System > Network Settings to configure.
Hey!
Here are the response to the following commands:
/usr/sbin/hwinfo – wlan
15: PCI 300.0: 0282 WLAN controller
[Created at pci.366]
Unique ID: hAO_.2DSEuO3QNiB
Parent ID: hoOk.uG2Sz4QzkbA
SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: "Broadcom BCM43142 802.11b/g/n"
Vendor: pci 0x14e4 "Broadcom"
Device: pci 0x4365 "BCM43142 802.11b/g/n"
SubVendor: pci 0x11ad "Lite-On Communications Inc"
SubDevice: pci 0x6605
Revision: 0x01
Driver: "wl"
Driver Modules: "wl"
Device File: wlp3s0
Features: WLAN
Memory Range: 0xf7900000-0xf7907fff (rw,non-prefetchable)
IRQ: 18 (no events)
HW Address: 30:10:b3:3f:ee:7f
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 36 38 40 42 44 46 48 52 56 60 64 100 104 108 112 116 120 124
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 5.18 5.19 5.2 5.21 5.22 5.23 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: "pci:v000014E4d00004365sv000011ADsd00006605bc02sc80i00"
Driver Info #0:
Driver Status: wl is active
Driver Activation Cmd: "modprobe wl"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)
/sbin/ifconfig
enp4s0f1 Link encap:Ethernet HWaddr 38:2C:4A:2B:38:93
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::3a2c:4aff:fe2b:3893/64 Scope:Link
inet6 addr: 2a00:6200:80:d03:3a2c:4aff:fe2b:3893/64 Scope:Global
inet6 addr: 2a00:6200:80:d03:484b:3efb:cd28:9d1b/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:596610 errors:0 dropped:1 overruns:0 frame:0
TX packets:330945 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:889189435 (847.9 Mb) TX bytes:22583490 (21.5 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2879 errors:0 dropped:0 overruns:0 frame:0
TX packets:2879 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:327814 (320.1 Kb) TX bytes:327814 (320.1 Kb)
Cheers
Thanks for the requested information. Perhaps your wireless device is blocked? Check with the ‘rfkill’ utility. (You may need to install the ‘rfkill’ package first.)
/usr/sbin/rfkill list
If the wireless is soft blocked, it can be unblocked with
sudo /usr/sbin/rfkill unblock wifi
Hey deano-ferrari,
Well, no, nothing is blocked. I tried to log on a GNOME session to see if YasT was working properly here to set up wifi, it ends that its using Wicked instead of Network Manager. Furthermore the problem persists as when i try to edit the broadcom card settings the same error message appears:
Caller /usr/share/YasT2/modules/CanItems.rb:2029:in 'block in Commit’
So, wicked is in use rather than NetworkManager? This will confirm…
sudo systemctl status network
Also, check that wlp3s0 is shown here
/sbin/ifconfig -a
Returning to your opening post where you mention
I can see the card now in the Network Manager, but when I intend to edit it to connect on a wi-fi network, there is a YasT2 error at the final step:
Details: undefined method ‘empty’
for 0.fixnum
Caller /usr/share/YasT2/modules/CanItems.rb:2029:in ‘block in Commit’
I’m not sure why that Ruby error occurs (not aware of it ever being reported before). However, you should be aware that when using NetworkManager, connections are configured and managed by NetworkManager itself, not via YaST. First, make sure that NetworkManager is selected via
YaST > System > Network Settings > Global Options, select ‘NetworkManager Service’, then ‘OK’. Once this has been done, you should be able to configure the wireless interface via the NM connection editor (part of the NM front-end).
It’s very strange because even with a sudo nm-connection-editor, or nm-applet;
it prompts back : Unable to init server: Could not connect: Connexion refused … Gtk Warning couldn’t open display
Why are you trying to edit the connection as root in a user session? NetworkManager is designed to run as regular user.
When I am on regular Network Manager Settings, I can’t add a wireless connexion: the only available options besides Wired are VPN Bond Team Bridge or Vlan.
That’s strange. What do the following report (as regular user)?
nmcli g
nmcli d
/sbin/ifconfig -a
Please enclose the output within code tags (refer to the # button in editor).
It’s strange because the WI-FI is supposed to be enabled according to NM, but there isn’t any way to put it on from the NM interface.
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (site only) limited enabled enabled enabled enabled
DEVICE TYPE STATE CONNECTION
enp4s0f1 ethernet connected Wired connection 1
lo loopback unmanaged --
enp4s0f1 Link encap:Ethernet HWaddr 38:2C:4A:2B:38:93
inet addr:192.168.1.108 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: 2a00:6200:80:d03:dd1c:20e0:91ea:4fcc/64 Scope:Global
inet6 addr: 2a00:6200:80:d03:3a2c:4aff:fe2b:3893/64 Scope:Global
inet6 addr: fe80::3a2c:4aff:fe2b:3893/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1686 errors:0 dropped:0 overruns:0 frame:0
TX packets:1684 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1000607 (977.1 Kb) TX bytes:285283 (278.5 Kb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1536 (1.5 Kb) TX bytes:1536 (1.5 Kb)
As the wireless network device node is not present, the wireless device does not exist as far as NM is concerned. Are you sure that you have the relevant driver packages installed (as already I hinted at in post #2)?
rpm -qa|grep broadcom
Well, I did install it from packman repository
broadcom-wl-6.30.223.271-29.2.x86_64
broadcom-wl-kmp-default-6.30.223.271_k4.6.3_176.gd4bcf2a-22.14.x86_64
The broadcom-wl package should take care of blacklisting the open source drivers, but worth checking anyway I guess…
lsmod | grep "brcmsmac\|b43\|ssb\|bcma
Check kernel messages relating to the wl driver
sudo journalctl -b |grep wl
or
dmesg|grep wl
Any errors? Other than that, I’m not sure what else might be the issue here.
Well I haven’t got a clue about those commands, but no, no error.
The first one opens a prompt
lsmod | grep "brcmsmac\|b43\|ssb\|bcma>
>
And nothing happens after both of the two following ones… I guess I ll have to remain close to my router for the moment
Sorry, that was due to missing quotes at the end. (I didn’t expect there to be any output from that command anyway as those modules shouldn’t be loaded.)
Any output from the journal log?
And nothing happens after both of the two following ones… I guess I ll have to remain close to my router for the moment
Ok, so no kernel output relating to wl? What happens when you manually try to load it (as root)?
modprobe wl
Is the wireless network device node then present?
/sbin/ifconfig
If not, you may need to check that the ‘broadcom-wl-kmp-default’ version matches your running kernel as with this thread.
Something interesting here
modprobe does a Fatal error : module wl not found in directory /lib/modules/…
I’m not surprised about this. The broadcom kernel package needs to match the kernel version. Have a read of the thread I linked to, and check that you have the correct Packman repo configured for TW.