Trying to connect to WiFi network on Raspberry Pi 0 using Ralink 5370

ScheissSchiesser · 12-17-2016, 02:39 PM

Quote:

Originally Posted by stoat

The wpa service script expects your wpa_supplicant configuration file to have the .conf extension.

Another overlooked typo on my part. I do indeed have the .conf extension. Thank you.

Nothing is complaining in my system, which is what makes this a bit difficult. I don't get any obvious error messages. I just can't seem to find any WiFi connections when I scan, including my own router that I am connecting to.

ScheissSchiesser · 12-17-2016, 02:44 PM

Quote:

Originally Posted by spiky0011

These are the options I have for the same device

CONFIG_WLAN_VENDOR_RALINK=y
# CONFIG_RT2800PCI is not set
CONFIG_RT2800USB=m
CONFIG_RT2800USB_RT33XX=y
CONFIG_RT2800USB_RT35XX=y
# CONFIG_RT2800USB_RT3573 is not set
CONFIG_RT2800USB_RT53XX=y
# CONFIG_RT2800USB_RT55XX is not set
# CONFIG_RT2800USB_UNKNOWN is not set
CONFIG_RT2800_LIB=m

CONFIG_RT2800USB_RT53XX=y

I did not build the kernel myself. I am using the official Raspberry Pi 4.4 kernel. How can I check those configurations/options you have listed?

Quote:

lsmod
rt2800usb 14583 0
rt2x00usb 8338 1 rt2800usb
rt2800lib 68511 1 rt2800usb
rt2x00lib 34430 3 rt2800lib,rt2800usb,rt2x00usb
mac80211 477253 4 rt2800lib,b43,rt2x00lib,rt2x00usb
cfg80211 417021 3 b43,rt2x00lib,mac80211

Hope these help.

<NO-CARRIER,BROADCAST,MULTICAST,UP> means it,s up but not associated to a carrier access point

lsmod shows that I have those modules running, except yours seem to have the additional "b43" dependent module, which I do not have. Is that important? What does that do?

Should I go through and build the kernel myself? Do you think that is the problem?

ScheissSchiesser · 12-17-2016, 02:52 PM

Quote:

Originally Posted by spiky0011

as root

Code:

iwlist wlan0 scan

I suppose thats no output, struggerling here now

Code:

# iwlist wlan0 scan
wlan0     No scan results

#iwlist wifi0 scan
wifi0 Interface doesn't support scanning.

This is confusing. According to my wpa_supplicant files, I have named the interface "wifi0" (because the BLFS guide says to do so).

However, the interface is named wlan0 to everything else. Is this desired?

Still no scan results.

ScheissSchiesser · 12-17-2016, 03:54 PM

Here is some new information.

I have created a new wpa_supplicant config file for testing:

Code:

# cat /etc/sysconfig/wpa_supplicant_test.conf

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
update_config=1

Then, I brought up the interface with wpa_supplicant:

Code:

# wpa_supplicant -B -i interface -c /etc/sysconfig/wpa_supplicant_test.conf
Successfully initialized wpa_supplicant
[4097.871872] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

then I use wpa_cli

Code:

# wpa_cli
> scan
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND

> scan_results
bssid / frequency / signal level / flags / ssid

So, no results by scanning with wpa_cli. I cannot see any networks (which I should). So something is bonkers. I keep thinking it must be the drivers/firmware, but it appears I have set that up correctly. Any ideas what I should try next?

spiky0011 · 12-18-2016, 01:12 AM

I would redo wpa .conf name it wlan0.conf, redo /etc/sysconfig/ifconfig.wifi0 make it ifconfig.wlan0, for consistancy.

TheEzekielProject · 12-18-2016, 02:08 AM

Did you

Code:

dhclient -v wlan0

after you

Code:

ip link set wlan0 up

?

Luridis · 12-20-2016, 01:57 AM

Did you set your region? If you don't do that the kernel will repeatedly disconnect so you aren't broadcasting on illegal frequencies.

ScheissSchiesser · 12-20-2016, 06:25 PM

Quote:

Originally Posted by Luridis

Did you set your region? If you don't do that the kernel will repeatedly disconnect so you aren't broadcasting on illegal frequencies.

I will do that. But shouldn't there be some kind of error message stating that? Or a warning? Everything looks like it is working, except I can't see any WiFi ESSIDs when I scan. In fact, here's what I get when I scan with iwconfig:

Code:

# iwconfig wlan0 scan
iwconfig: unknown command "scan"

# iwlist wlan0 frequency
wlan0    14 channels in total; available frequencies :

Channel 01 : 2.412 GHz
...
...
[not typing all of the channels]
...
Channel 14 : 2.484 GHz

#iwlist wlan0 scanning
wlan0    No scan results

Can you be specific about what region I should be setting? Not sure how to do it. I am using iwconfig + wpa_supplicant and not iw.

Thanks for you help.

ScheissSchiesser · 12-20-2016, 06:27 PM

Quote:

Originally Posted by The EzekielProject

Did you

Code:

dhclient -v wlan0

after you

Code:

ip link set wlan0 up

?

I am using dhcpcd. Here is what I get when running it:

Code:

# dhcpcd wlan0
wlan0: waiting for carrier
timed out
dhcpcd exited

Makes sense, since I am not connected to an access point.

Luridis · 12-21-2016, 02:08 AM

Quote:

Originally Posted by ScheissSchiesser

Can you be specific about what region I should be setting? Not sure how to do it. I am using iwconfig + wpa_supplicant and not iw.

Thanks for you help.

Check your dmesg, you should see something like this:

Code:

cfg80211: Calling CRDA to update world regulatory domain
// If set correctly, it will continue like this:
cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:  DFS Master region: FCC

If it's not set correctly, it will continuously disconnect because the legal transmission frequencies are different depending on what country you're in. If you haven't configured it, then it cannot assume transmitting on any given frequency is legal where you are.

Try "man crda" for more info. That, or the 80211 docs in the kernel source. You can set it via certificate, kernel command line, config file for iw (I think) or udev rule.

https://wireless.wiki.kernel.org/en/...latory_domains

Luridis · 12-21-2016, 02:15 AM

Quote:

Originally Posted by ScheissSchiesser

This is confusing. According to my wpa_supplicant files, I have named the interface "wifi0" (because the BLFS guide says to do so).

However, the interface is named wlan0 to everything else. Is this desired?

Still no scan results.

The easiest way to fix that... IMO, even easier than udev rules is to add this to your kernel command line:

net.ifnames=0

ScheissSchiesser · 12-21-2016, 06:11 PM

Nothing in dmesg shows up regarding crda or regulatory domains. I don't have the crda program either! Did I miss a step somewhere in the build process? When would crda be installed?

Luridis · 12-21-2016, 06:34 PM

crda is a udev helper, it's not built in. You have to download the package, the links can be found on the websites I posted before. It's just one way to set the regulatory domain. If your kernel isn't complaining that it's not set, then you're likely missing something.

Some settings aren't in the drivers tree, they're off the root kernel menu under "Networking Support"

Networking Support --->
-*- Wireless---> (auto-selected by wireless drivers)
<M/*> cfg80211 - wireless configuration API[*] cfg80211 wireless extensions capability
<M/*> RF switch subsystem support

(Sorry I can't get them to line up correctly. Whatever idiot coded this site's software decided to assume automatic formatting was desired inside code tags, which is just brilliant. Of course, I'm not a web developer so it might be the browser overriding a correctly coded tag. In which case, my apologies to the developer.)

Without everything, your adapter will probably just run in some sort of failsafe mode.

ScheissSchiesser · 12-22-2016, 10:51 AM

Quote:

Code:

Networking Support --->
-*- Wireless---> (auto-selected by wireless drivers)
   <M/*> cfg80211 - wireless configuration API[*] cfg80211 wireless extensions capability
<M/*> RF switch subsystem support

I have all of those selected, but when I check dmesg for cfg80211, I don't see any messages from it.

Code:

# dmesg | grep regulatory
# dmesg | grep cfg
# dmesg | grep 80211
[   11.813392] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
[   11.880757] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
[   12.001265] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   17.616839] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[   17.636647] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.22

cfg80211 is running

Code:

# pgrep cfg80211
371

TheEzekielProject · 12-22-2016, 06:34 PM

....

Are you literally typing

Quote:

# wpa_supplicant -B -i interface -c /etc/sysconfig/wpa_supplicant_test.conf
Successfully initialized wpa_supplicant
[4097.871872] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Or are you replacing interface with wlan0?

Also did you change the instances of wifi0 to wlan0 as suggested by spiky0011?

Quote:

Originally Posted by ScheissSchiesser

I am using dhcpcd. Here is what I get when running it:

Code:

# dhcpcd wlan0
wlan0: waiting for carrier
timed out
dhcpcd exited

Makes sense, since I am not connected to an access point.

Yes, you are not connected to the access point and that is what dhcpcd is intended to do. It timing out waiting for the carrier seems to me that it's not being offered an ip address.

Try running

Code:

dhcpcd -d wlan0

:q

For a little more info on why it's timing out.

Also check here for other troubleshooting tips