LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-18-2020, 01:36 PM   #1
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,773

Rep: Reputation: 138Reputation: 138
RTNETLINK answers: Operation not possible due to RF-kill


I've installed Slackware-current on a Dell Latitude E5420 laptop with Intel i3-2350M and 4G of memory. I'm trying to get the WiFi working. I have the following in /etc/rc.d/rc.inet1.conf
Code:
IFNAME[4]="wlan0"
IPADDR[4]=""
NETMASK[4]=""
USE_DHCP[4]="yes"
The WiFi toggle switch on the laptop is enabled. I have the correct configuration in /etc/wpa_supplicant.conf (I've used this same config elsewhere).

When I try to start the WiFi I get:
Code:
# /etc/rc.d/rc.inet1 wlan0_restart

RTNETLINK answers: Operation not possible due to RF-kill
RTNETLINK answers: Operation not possible due to RF-kill
/etc/rc.d/rc.inet1:  wlan0 information: 'Any ESSID'
Error for wireless request "Set Nickname" (8B1C) :
    SET failed on device wlan0 ; Operation not supported.
Polling for DHCP server on interface wlan0:
dhcpcd_prestartinterface: wlan0: Operation not possible due to RF-kill
wlan0: waiting for carrier
timed out
dhcpcd exited
rfkill gives:
Code:
rfkill list all
0: dell-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
I've tried 'rm /dev/rfkill' and 'rfkill unblock all'. Those do nothing. lspci gives:
Code:
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
0a:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme BCM5761 Gigabit Ethernet PCIe (rev 10)
I did have Slackware 14.2 on this computer before installing current, but I really don't know if I've ever tried using the WiFi before.

Any suggestions on what I can do or try?
 
Old 06-18-2020, 01:50 PM   #2
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,517

Rep: Reputation: Disabled
looking around on google I found this: I'm not sure it applies but it's worth a try...

https://bbs.archlinux.org/viewtopic....24810#p1324810
 
Old 06-18-2020, 08:55 PM   #3
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,773

Original Poster
Rep: Reputation: 138Reputation: 138
Thanks for the reply. I saw that one too, but that poster had an HP Elitebook, whereas I have a Dell Latitude E5420. I therefore though that blacklisting hp_wmi in /etc/modprobe.d/hp.conf probably wouldn't apply. But I went ahead and tried it and no, it didn't work. Still have the same problem.

The full lspci on this device is:
Code:
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01)
        Subsystem: Dell Inspiron M5010 / XPS 8300
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at e3c00000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [d0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel
        Capabilities: [160] Device Serial Number 00-00-57-ff-ff-9c-44-6d
        Capabilities: [16c] Power Budgeting <?>
        Kernel driver in use: bcma-pci-bridge
        Kernel modules: bcma
Module bcma is loaded.

Other ideas?
 
Old 06-19-2020, 12:22 AM   #4
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,773

Original Poster
Rep: Reputation: 138Reputation: 138
OK, taking another approach. I've turned off the WiFi switch on the laptop and installed a USB WiFi: Ralink Tech, MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter). I've modified /etc/rc.d/rc.inet1.conf to have:
Code:
IFNAME[5]="wlan1"
IPADDR[5]=""
NETMASK[5]=""
USE_DHCP[5]="yes"
/etc/udev/rules.d/70-persistent-net.rules:
Code:
# USB device 0x148f:0x761a (usb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="50:3e:aa:d3:7d:fe", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan1"
ifconfig:
Code:
wlan1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 50:3e:aa:d3:7d:fe  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
iwconfig:
Code:
# iwconfig wlan1
wlan1     IEEE 802.11  ESSID:"secret"  
          Mode:Managed  Frequency:5.745 GHz  Access Point: Not-Associated   
          Tx-Power=14 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
start:
Code:
# /etc/rc.d/rc.inet1 wlan1_start
/etc/rc.d/rc.inet1:  wlan1 information: 'Any ESSID'
Error for wireless request "Set Nickname" (8B1C) :
    SET failed on device wlan1 ; Operation not supported.
Polling for DHCP server on interface wlan1:
wlan1: waiting for carrier
timed out
dhcpcd exited
I've even tried setting WLAN_ESSID[5] in rc.inet1.conf

/var/log/messages:
Code:
Jun 19 01:07:51 labrat mfoley: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan1 nick labrat.hprs.local
Jun 19 01:07:51 labrat mfoley: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan1 essid "secret"
Jun 19 01:07:51 labrat mfoley: /etc/rc.d/rc.inet1:  /sbin/iwconfig wlan1 essid "secret"
Jun 19 01:07:51 labrat mfoley: /etc/rc.d/rc.inet1:  /sbin/dhcpcd -L -t 15  wlan1
Jun 19 01:07:51 labrat dhcpcd[1488]: wlan1: waiting for carrier
Jun 19 01:08:06 labrat dhcpcd[1488]: dhcpcd exited
Normally, setting up WiFi is a snap and "just works". In this case I can find no further information as to why dhcpd is failing. Nothing I've found on the Internet helps. Is it a driver issue? How do I know what driver wlan1 uses?

Last edited by mfoley; 06-19-2020 at 11:03 AM.
 
Old 06-21-2020, 04:31 PM   #5
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,575

Rep: Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876
Your extra Ralink WiFi adapter could be also subjected to the general RF Kill policy (disabled), have you checked that ?
(run again rfkill list all)
To see what driver is used for your wlan1 adapter, you could list the links in:
Code:
ls -al /sys/class/net/wlan1/device/driver/module/drivers/
A similar issue you have with your Dell laptop is discussed here:
https://askubuntu.com/questions/1279...-inspiron-1750
& here:
https://ubuntuforums.org/showthread.php?t=1957419
and the solutions range from pressing some FN key combination, unloading & blacklisting the dell_laptop driver, to loading Windows and enabling the WiFi there
 
Old 06-22-2020, 11:56 PM   #6
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,773

Original Poster
Rep: Reputation: 138Reputation: 138
abga, thanks for your post. Below is my rfkill. The only difference between this and my post #1 is the addition of 2: Phy0, and the current 1: phy1 was 1hy0 before. I'm assuming that 2: is the 2nd WiFi adapter since that was not there before. It shows neither soft nor hard block.
Code:
# rfkill list all
0: dell-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: phy1: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
Your suggested 'ls -al /sys/class/net/wlan1/device/driver/module/drivers/' was a link to the directory shown:
Code:
# ls -al /sys/class/net/wlan1/device/driver/module/drivers/usb\:mt76x0u/*
lrwxrwxrwx 1 root root    0 2020-06-23 00:36 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/2-1.2:1.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/
--w------- 1 root root 4096 2020-06-23 00:36 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/bind
lrwxrwxrwx 1 root root    0 2020-06-23 00:35 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/module -> ../../../../module/mt76x0u/
-rw-r--r-- 1 root root 4096 2020-06-23 00:36 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/new_id
-rw-r--r-- 1 root root 4096 2020-06-23 00:36 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/remove_id
--w------- 1 root root 4096 2020-06-22 20:24 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/uevent
--w------- 1 root root 4096 2020-06-23 00:36 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/unbind
I'll confess that I don't know what here would refer to the driver of wlan1.

ifconfig gives the same results as in my post #4 showing wlan1 UP, it shows the MAC address, but DHCP fails, as per my post #4.

Your first suggested link discusses making sure the non-keyboard WiFi switch was turned on, which I've made sure of. Furthermore, this WiFi is a USB dongle which I don't think would be subject to the same hardware switch.

Your 2nd suggested link is exactly my problem. That poster found that an earlier version of Linux was able to see the WiFi w/o problem. This version is Slackware-current. I will try installing the dongle on a Slackware 14.2 system. I cannot test that immediately, but I'll do so at my earliest convenience and post back.
 
Old 06-23-2020, 03:45 AM   #7
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,427

Rep: Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018Reputation: 2018
That the 'rfkill' output shows a hard block suggests that the wireless switch is not working. Do you see a visual indication of the WiFi turning on?
I did find this, which, while not specific for your Dell Latitude E5420, may be worth investigating.
 
Old 06-23-2020, 11:49 AM   #8
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,575

Rep: Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876
Quote:
Originally Posted by mfoley View Post
abga, thanks for your post. Below is my rfkill. The only difference between this and my post #1 is the addition of 2: Phy0, and the current 1: phy1 was 1hy0 before. I'm assuming that 2: is the 2nd WiFi adapter since that was not there before. It shows neither soft nor hard block.
Well, this could be a (funny) development. If phy1 is the device for the wlan1, which is your recently added USB Mediatek (mt76x0u) adapter, then it got blocked according to the output of rfkill. And, the phy0, which should be the device for wlan0, is the former Broadcom onboard WiFi adapter, that got unblocked now ....
You can only verify this with the help of:
Code:
iw dev
You could also rename them if you wish/if it helps (kernel won't let you use phyX - X = 1 digit only):
Code:
iw phy phy0 set name phy01
iw phy phy1 set name phy00
Quote:
Originally Posted by mfoley View Post
I'll confess that I don't know what here would refer to the driver of wlan1.
Code:
lrwxrwxrwx 1 root root    0 2020-06-23 00:35 /sys/class/net/wlan1/device/driver/module/drivers/usb:mt76x0u/module -> ../../../../module/mt76x0u/
It's the module highlighted in bold at the end of the line.
https://cateee.net/lkddb/web-lkddb/MT76x0U.html
Quote:
Originally Posted by mfoley View Post
This version is Slackware-current. I will try installing the dongle on a Slackware 14.2 system. I cannot test that immediately, but I'll do so at my earliest convenience and post back.
It's not Slackware as a distribution (-current or 14.2) but the kernel version and its drivers, -current has a new and actual kernel, 14.2 has an old and maintained (patched) kernel.
Have you checked if the dell_laptop driver is loaded? - use lsmod and rmmod to unload it and issue again a rfkill to unblock all, also maybe blacklist it (could help you with that too).
 
1 members found this post helpful.
Old 06-23-2020, 01:16 PM   #9
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,773

Original Poster
Rep: Reputation: 138Reputation: 138
Problem Solved! I had to add the line: 'WLAN_WPA[5]="wpa_supplicant"' to rc.inet1.conf making the overall config:
Code:
IFNAME[5]="wlan1"
IPADDR[5]="" 
NETMASK[5]="" 
USE_DHCP[5]="yes" 
WLAN_WPA[5]="wpa_supplicant"
You Slacksters must have missed that in my O.P! wlan0 still gives the "Operation not possible due to RF-kill" error, regardless of how I have the actual WiFi switch set on the laptop case. I'll just have to assume the WiFi switch on this laptop is broken. No matter, in the end I have a usable WiFi.

The Slackware 14.2 distro didn't see the Ralink MT7610U at all (and abga, that model corresponds with the driver name you pointed out, thanks).

Thanks all for your feedback and help!
 
Old 06-23-2020, 04:54 PM   #10
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,575

Rep: Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876Reputation: 876
I don't know about other "Slacksters", but I expect Slackware users (Slackers) to carefully read & follow the documentation
I must admit I focused only on your "Operation not possible due to RF-kill" error and didn't bother with other details.

The kernel provided with Slackware 14.2 doesn't look to contain the driver for your Mediatek MT7610U WiFi adapter (don't know where Ralink comes from) and you could build it on your own as an out-of-tree module or use the kernel from -current.
I couldn't find an actual/stable driver, other than what is discussed here in this old thread:
https://superuser.com/questions/7380...-rt2860-driver

If you want to use the kernel from -current, you could follow this older post of mine (use the actual kernel versions):
https://www.linuxquestions.org/quest...ml#post6053120

Gald to hear you have a working solution now. I'd still suggest to investigate further on the RFKill issue, check your BIOS settings, presence of dell_laptop module (if loaded) and why not, try to load a windows on it and SW-enable the Radio.

Last edited by abga; 06-23-2020 at 05:03 PM. Reason: wrong (second) URL
 
  


Reply

Tags
wifi problem


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ip xfrm policy count: error: RTNETLINK answers: Operation not supported Li Zhao Linux - Networking 0 01-19-2020 03:48 AM
[SOLVED] OpenVPN Installed but "RTNETLINK answers: Operation not permitted" when Starting Server WhiteTitan Linux - Server 2 07-10-2018 05:24 PM
RTNETLINK answers: Operation not permitted sparkling Linux - Newbie 1 02-13-2018 03:35 PM
SIOCSIFFLAGS: Operation not possible due to RF-kill signsanssignified Linux - Wireless Networking 3 03-31-2017 06:30 PM
"Operation not possible to due rf-kill" with command: ifconfig wlan0 up Quon Linux - Networking 5 04-03-2012 01:58 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:02 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration