Belkin wifi dongle - iwd shows no devices,adapters,etc.

Zhme · 2024-07-28 19:34:49

So, I haven't used this PC before. I was given this computer by my family who no longer use it. It has Windows 7 and I intend to throw Arch onto it to use as a host OS for a larger project. I am stuck at the network phase of installation, obviously, and I haven't had much luck browsing for solutions in this case.

I am able to set the interface up with 'ip link' which is listed as wlan0.

Using 'iwctl' I am unable to get output from 'device list', and the rest of the list functions which were irrelevant but I thought I'd try them anyway.

After some hours of trying to verify the proper driver was being loaded and that the dongle was in working condition, I found this page from the Arch forums that gave me some hope.
https://bbs.archlinux.org/viewtopic.php?id=138337

I was able to run 'iwlist scan' and see my home AP name listed and this tells me that I have some path to connect, but that iwctl is giving me issues. The forum reply by ewaller suggests looking into wpa_supplicant. I have used wpa_supplicant effectively for years, so that seemed like an easy fix. I created a basic config file and ran my usual command 'wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/config' and was unsuccesful.

At this point I get a very robust output, but for some reason I can't find an answer when searching for these errors.

Output from 'wpa_supplicant ...' :

Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: Failed to initialize driver interface
wlan0: CTRL-EVENT-DSCP-POLICY clear_all

Pardon any typos - I am copying this onto a working laptop by hand because I don't know a reasonable way to export the output with no connection on an installation media OS.

I would imagine the issue lies somewhere in that POLICY error or the 'wlan0 disabled' line, but I have been having trouble finding a relevant solution for my particular situation - many people are having issues with successful packet transfers or getting dhcpcd to work - but I have yet to establish a connection with my own router.

Thanks in advance!

Edit: I forgot to mention that I have tried to 'systemctl stop' the iwd service to avoid conflictions with wpa_supplicant, but that still throws an error when I try to manually start wpa_supp.

Edit:...Edit: It is a Belkin 300N F7D2101 https://help.ubuntu.com/community/WifiD … %20F7D2101

Edit x3: I tried to specify the driver for this model located 4th from the bottom of https://help.ubuntu.com/community/Hardw … Belkin#USB(<- this) link.

root@archiso (tilde key doesnt work) # wpa_supplicant -i wlan0 -Dr8712u -c /etc/wpa_supplicant/config
Successfully initialized wpa_supplicant
wlan0: Unsupported driver 'r8712u'
wlan0: CTRL-EVENT-DSCP-POLICY clear_all

Last edited by Zhme (2024-07-28 19:56:59)

Zhme · 2024-07-28 20:18:12

So, I thought I'd add just another output that I had forgotten until now.

'dmesg -W'

Again, I am having issues with exporting output, so I have two images from a free hosting service for now for this dmesg output.

this is looping endlessly - reflector? for mirrors??
https://postimg.cc/WDnkqzx3

this is when I plug the Belkin dongle in
https://postimg.cc/LqRPsLCw

Zhme · 2024-07-28 21:18:19

This might not be relevant, but I have the output of 'iw --debug dev' because 'iw dev' shows no output, even though ip link shows it as a valid interface device.

https://postimg.cc/vx1hv5dX

Zhme · 2024-07-28 21:35:57

I have been noticing some of the deprecated wireless_tools have a relevant output (maybe?) whereas the iw commands are giving nothing useful or a wall of flying options that I can't make use of.

For instance, 'iw dev', 'iw dev wlan0', 'iw dev link', 'iw dev wlan0 link' provide either no output or a wall of options as if the command was typed incorrectly 0 or in my case the interface name is being interpreted as an extra option/command because it isn't being recognized as an interface.

'iwconfig wlan0' gives output with "rtl_wifi" as a nickname and a bunch of what look like default settings. I will provide that output if needed, but I don't think it is entirely relevant - just peculiar to have the interface being recognized by the deprecated tools.

'iwlist scan' (even omitting the wlan0 works but shows loopback etc.) shows my local ESSID which tells me that the dongle is working if this PC can find a name it should have no possible way of knowing.

I am curious if I can connect using the deprecated tools and write a startup script at least for initial downloading and setup?

Zhme · 2024-07-29 14:16:26

I tried USB tethering with my Android phone but was still unable to connect. The issue seems to be the device being unrecognized by the computer, not connectivity or a broken dongle. 'ip link' shows the Android device as enp....... and shows state as UNKNOWN, even after setting it up.

The AP does get recognized with deprecated 'iwlist scan' and this tells me there is a confliction somewhere in services. Perhaps?

I have tried stopping services and using wpa_supplicant directly, but I am searching in the dark with no flashlight at this point.

Last edited by Zhme (2024-07-29 16:09:40)

Zhme · 2024-07-29 20:28:59

I found these instructions to write a new_id directly into the driver directory at this post. https://bbs.archlinux.org/viewtopic.php?id=112120

There appears to be a 'usb:r8712u' already there that is referenced as the fix necessary in this post above. Can someone tell me how to use what is already there? Setting the option in wpa_supplicant doesn't work.

seth · 2024-07-29 20:58:42

Please don't DM me or any of the mods.
If you want the thread to be moved, report it and ask for the shift - that has a MUCH higher chance of some moderator actually seeing the request.

Also don't bump - edit your post to mend it if nobody has replied yet.

seth · 2024-07-29 22:52:20

[I'll bump so you get a mail]

https://postimg.cc/LqRPsLCw
The device is detected, modprobe alias applies, r8712u and firmware load.
But r8712u is a wext driver, which is what you want to pass to wpa_supplicant "-Dwext", not "-Dr8712u"

iw ill not allow you to connect to encrypted APs and iwd doesn't support wext.

Zhme · 2024-07-30 05:29:20

Thank you and my bad.

I tried to issue wpa_supplicant again with wext. I had tried before, but after your advice I noticed that the output is relatively more successful than the other attempts that I have made using improper driver options.

I issued 'wpa_supplicant -dd -i wlan0 -c /etc/wpa_supplicant/config -Dwext':

wpa_supplicant v2.10
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant/config' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/config' -> '/etc/wpa_supplicant/config'
Reading configuration file '/etc/wpa_supplicant/config'
ctrl_interface='/run/wpa_supplicant'
update_config=1
rfkill: Cannot get wiphy information
WEXT: RFKILL status not available
SIOCGIWRANGE: WE(compiled)=22 WE(source)=16 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0x1f flags 0x0
WEXT: Driver: r8712u
netlink: Operstate: ifindex=3 linkmode=1 (userspace-control), operstate=5 (IF_OPER_DORMANT)
Add interface wlan0 to a new radio N/A
wlan0: Own MAC address: c0:56:27:03:c6:4e
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=5 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wlan0: RSN: flushing PMKID list in the driver
wlan0: State: DISCONNECTED -> INACTIVE
TDLS: TDLS operation not supported by driver
TDLS: Driver uses internal link setup
TDLS: Driver does not support TDLS channel switching
wlan0: WPS: UUID based on MAC address: e8eea59b-a236-5818-8606-d83e820bd271
ENGINE: Loading builtin engines
ENGINE: Loading builtin engines
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
MBO: Update non-preferred channels, non_pref_chan=N/A
wlan0: Added interface wlan0
wlan0: State: INACTIVE -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
WEXT: if_removed already cleared - ignore event
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
WEXT: if_removed already cleared - ignore event
Wireless event: cmd=0x8b06 len=12
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
WEXT: if_removed already cleared - ignore event
EAPOL: disable timer tick
wlan0: Removing interface wlan0
wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=DISCONNECTED
TDLS: Tear down peers
wlan0: State: DISCONNECTED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
netlink: Operstate: ifindex=3 linkmode=-1 (no change), operstate=5 (IF_OPER_DORMANT)
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
QM: Clear all active DSCP policies
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
wpa_driver_wext_set_countermeasures
wlan0: WPA: Clear old PMK and PTK
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout
Off-channel: Clear pending Action frame TX (pending_action_tx=(nil)
HS20: Delete all stored icons
Off-channel: Action frame sequence done notification: pending_action_tx=(nil) drv_offchan_tx=0 action_tx_wait_time=0 off_channel_freq=0 roc_waiting_drv_freq=0
QM: Clear all active DSCP policies
wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Remove interface wlan0 from radio 
Remove radio 
netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
wlan0: CTRL-EVENT-TERMINATING

The command hangs where it says "disable timer tick" and the rest of the output that follows is after I ctrl-C.

Edit: I thought rfkill looked suspicious, but this behavior continues even after I issued 'rfkill unblock wlan0' and 'rfkill unblock all'.

Last edited by Zhme (2024-07-30 05:31:16)

seth · 2024-07-30 06:34:21

Did you previously bring the NIC up or is there another wpa_supplicant instance (service, called by NM( or iwd still running?
Don't either and try to simply scan & connect w/ wifi-menu from the netctl package.

Scimmia · 2024-07-30 16:43:27

wifi-menu? Really, seth? You want them to install some front-end that nobody uses (or even has installed anymore) instead of wpa_supplicant itself?

seth · 2024-07-30 20:42:56

Really.
With all respect to Zhme but there're no apparent driver issues and the thread started w/ iwd on a wext driver, attempting to define a kernel module as wifi driver and the wpa_supplicant output looks eerily like the NIC was already up for some reason.
So my immediate concern is to rule out this being down to any user errors, hence increase the abstraction layer and wifi-menu, regardless of who else still uses that, has a bunch of upsides:
1. it will complain and refuse any action if the NIC is already up
2. it first performs a scan, so we're not reaching for a stale SSID
3. Unlike NM the scan isn't prone to piss the AP off w/ MAC spoofing
4. it has a better chance of not fudging escaping (if necessary) special characters and generally to avoid typos and hail-mary efforts
5. Not the largest footprint in the world

Bottom line, wifi-menu will either "just work" (yay) or at worst produce additional data points (can't even find the SSID, yells this kind of error)

Zhme · 2024-07-30 20:56:39

seth wrote:

Really.
Bottom line, wifi-menu will either "just work" (yay) or at worst produce additional data points (can't even find the SSID, yells this kind of error)

I would like to narrow things down if possible. I was walking around my neighborhood and talked to some guy who gave me a free computer today, and am trying this Belkin dongle on this PC. It has similar errors, but it gets an output for adapter, device, and lets me almost connect to a station. Then the same problems arise.

I grabbed the netctl.zst and .zst.sig files and the same for resolvconf, and now both packages are on a usb and put them on my dead box, but I can't install it with -U because the repos aren't there.

How can I install wifi-menu offline? The wiki only talks about entire distro installation it seems, but I just want to get network connection and continue from there.

seth · 2024-07-30 21:25:55

but I can't install it with -U because the repos aren't there.

I assume to resovle further dependencies (mismatching versions or maybe you're missing dhcpcd)?
Can you use ethernet or https://wiki.archlinux.org/title/Tethering ?

Otherwise you'll have to pre-download all required packages an install them en block (or manually put them into the cache, I've never tried that but should™ theoretically work)

Can you comment on the NICs state during the previous wpa_supplicant attempt? Was it already up (and if so, for what reason)?

Arch Linux

#1 2024-07-28 19:34:49

Belkin wifi dongle - iwd shows no devices,adapters,etc.

#2 2024-07-28 20:18:12

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#3 2024-07-28 21:18:19

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#4 2024-07-28 21:35:57

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#5 2024-07-29 14:16:26

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#6 2024-07-29 20:28:59

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#7 2024-07-29 20:58:42

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#8 2024-07-29 22:52:20

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#9 2024-07-30 05:29:20

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#10 2024-07-30 06:34:21

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#11 2024-07-30 16:43:27

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#12 2024-07-30 20:42:56

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#13 2024-07-30 20:56:39

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

#14 2024-07-30 21:25:55

Re: Belkin wifi dongle - iwd shows no devices,adapters,etc.

Board footer