Cannot connect to wireless network via wifi dongle

waves

Sorry if I may have missed something upthread but like user utschu above I suspect there might be a power problem. I've myself in the past encountered wifi dongles that worked unreliably when plugged directly to pi devices. The list on http://elinux.org/RPi_USB_Wi-Fi_Adapters says for TL-WN722N: "needs powered USB Hub (B)". That list is user generated so may not be the last word. But if you have access to a powered USB hub, or if you're willing to buy one (they can be pretty inexpensive), then it might be worth to try using the wifi adapter through it and see if that helps.

daymz

Sorry for the lack of responses, I was away on vacation.

daymz wroteOK so, I can bring both eth0 and wlan0 up:

- netctl start eth0

for wifi, netctl start is not enough, I first need to have:

- my /etc/netctl/wlan0 file (typical, with reference to wpa_supplicant.conf which contains my wifi connection parameters)
- ip link set wlan0 up (as per a post above)
- netctl start wlan0

After starting wlan0 though, now eth0 is gone.

So based on HondaGX35's conversation, here are my next test steps:

hondagx35 wroteSo you tried it with a stock image (without your modifications)?

Will try again, I can't remember the results of this test (shouln't be long)

hondagx35 wroteTo find a solution / the reason i need more information about this.
- What is the exact problem?
- fixed IP or DHCP?
- debug data?

- Described in the post above. Wifi doesn't start at bootup. I can manully start it with netctl, but then I lose eth0 (see above quoted post and the one before it)
- I tried both DHCP originally, and then Static IP. Both exhibited the same issue. Now running Static IP
- I will provide debug data

hondagx35 wroteIt works without any updates, but updating doesn't hurt.
For some reason the git pull mechanism on the latest image is broken.
Please do:
- get access to the console (ssh or monitor and keyboard)
- execute this commands
cd /srv/http
git stash
git pull

I will also try that. I did update through git on the dev branch. Not sure what git stash does so I will try this again.

Thanks.

daymz

So, I've tried both the 0.3 img fresh install, and the last backup of my own image, and both work the same way.

It seems to work reliabily now, which is even more confusing. One thing that definitely threw me off here, I don't know if it's intentional or not, but it seems impossible to have both eth0 and wlan0 up and running, there is always one of the two not working.

Right now, for some unknown reason (or maybe by design), my wlan0 comes up and my eth0 doesn't, which is what I wanted for this specific board. A little tiny voice called experience tells me this is not the end of it (and, unjustified at this time in my head) so we will see how it fares in the future.

daymz

Well, Murphy's done it again. So now, I'm in a streak where eth0 comes up and wlan0 doesn't. Both eth0 and wlan0 are configured with static ip addresses.

I don't even have an Ethernet cable plugged in eth0, yet "ifconfig" (as well as "ip link") show that eth0 is UP.

Once booted, I can kill the unplugged eth0 and start wlan0 by issuing:

# netctl stop eth0
# ip link set eth0 down
# netctl start wlan0
# ip link set eth0 down

Somehow, I need to set the link down on eth0 (the first one), otherwise, wlan0 refuses to start with "Job for netctl@wlan0.service failed."
I also need to re-issue that same command after netctl staritng wlan0 because that brings up eth0 again.

Something is really weird with networking. I'm attaching a few logs..

dmesg after boot is completed: http://pastebin.com/N66Bcyup
ifconfig after boot is completed: http://pastebin.com/5cxB5kQ5
ifconfig after eth0 is taken down (see commands above) : http://pastebin.com/YDiddPNh
ifconfig after wlan0 is up (after all commands above): http://pastebin.com/0WqVRVMC
dmesg after wlan0 is up (after all commands above): http://pastebin.com/enD2Cqaf
RuneAudio Debug Data after all commands above: http://pastebin.com/Ax3eAjPr

If there is any other log or debug that can help, please let me know. I want to solve this.

hondagx35

Hi daymz,

first of all:

There are two different types of images out there.
a) RaspberryPi, Beaglebone Black, UDOO and CuBox
b) Raspberry Pi 2, Cubietruck and ODROID C1

a) uses its own mechanism to start network connections.

b) uses netctl-ifplugd (ethernet) and netctl-auto (wifi).
The next release will be based on this too.
I never had any problems with this images and networking.
netctl-ifplugd: your eth0 is automatically activated by plugging in the cable
netctl-auto: you can specify more than one profile and rune will select the right one (like Android)

So please do not mix things people tell you about networking.
Always ask for the used image (type a or b) first.

By updating to the nightly-builds it is possible to switch to version b.
The nightly builds are the base for the next release.

So if you experience problems with network please try to update first.
With the new version there is no need to do something manually.
All configuration can and should be done with the UI.

RP2, Cubietruck and ODROID user do not have to switch, because their images are based on the dev trunc (nightly builds).

Frank

daymz

hondagx35 wroteHi daymz,

first of all:
There are two different types of images out there.
a) RaspberryPi, Beaglebone Black, UDOO and CuBox
b) Raspberry Pi 2, Cubietruck and ODROID C1
a) uses its own mechanism to start network connections.

b) uses netctl-ifplugd (ethernet) and netctl-auto (wifi).
The next release will be based on this too.
I never had any problems with this images and networking.
netctl-ifplugd: your eth0 is automatically activated by plugging in the cable
netctl-auto: you can specify more than one profile and rune will select the right one (like Android)

So please do not mix things people tell you about networking.
Always ask for the used image (type a or b) first.

By updating to the nightly-builds it is possible to switch to version b.
The nightly builds are the base for the next release.

So if you experience problems with network please try to update first.
With the new version there is no need to do something manually.
All configuration can and should be done with the UI.

RP2, Cubietruck and ODROID user do not have to switch, because their images are based on the dev trunc (nightly builds).

Frank

Hi Frank,

I'm on the Raspberry Pi 1 image so I run the (A) image, as per the OP (the guy with a Raspberry Pi 2 who started posting past week may have made things confusing in this regard).

As I said in my last post, my eth0 is currently NOT plugged in, so it should NOT prevail over a valid and working wlan0 connection.

I'm trying to be helpful and investigate these problems, and I've already helped in several aspects of development on this forum before. I've ran Linux distros since the mid-90's and while I'm no expert, I'm no idiot either. I am not familiar with ArchLinux at all, and that is why I'm requesting help.

You mention the (A) image uses its own custom way for networking, and I suspect there is something fishy (or buggy) about it. With the number of threads from people who took the time to say there is a problem with Wifi connections, I'm guessing that there actually may be a problem worth looking at, and solving.

I`m willing to help. I've spent several dozens of hours on RA in the past months, and I want to see it work.

hondagx35

Hi ,

I'm trying to be helpful and investigate these problems, and I've already helped in several aspects of development on this forum before. I've ran Linux distros since the mid-90's and while I'm no expert, I'm no idiot either. I am not familiar with ArchLinux at all, and that is why I'm requesting help.

With my post i only wanted to clarify things. It was nothing against you.

You mention the (A) image uses its own custom way for networking, and I suspect there is something fishy (or buggy) about it. With the number of threads from people who took the time to say there is a problem with Wifi connections, I'm guessing that there actually may be a problem worth looking at, and solving.

Yes, and it is solved since months on the dev branch.
So either wait for the new image or switch to the dev branch (nightly-builds).
It would be best to make a fresh image and then switch the branch).
There are many things that have changed / fixed, so it's worth to try it.

Many thanks for your help and the time you investigate in RuneAudio.

Frank

daymz

hondagx35 wroteYes, and it is solved since months on the dev branch.
So either wait for the new image or switch to the dev branch (nightly-builds).
It would be best to make a fresh image and then switch the branch).
There are many things that have changed / fixed, so it's worth to try it.

Thanks for the information. So, are you saying that the (B) image is not only for Raspberry Pi 2 then? Because that is what I understood from your description earlier.

I'll try it out then according to the instructions posted.

hondagx35

Hi daymz,

So, are you saying that the (B) image is not only for Raspberry Pi 2 then?

The images are different (RuneOS) and can be used only for the specified device.
But the newer images (RP2, ODROID and Cubietruck) use the dev branch (RuneUI) from github.
Development work only happens on the dev branch (nightly builds).

Frank

XploD

@[deleted]: sorry for making a confusion. I saw that there's already a topic with Wi-Fi problems so I didn't want to open another same topic.

hondagx35 wroteHi

did you try to update:
- execute this commands
cd /srv/http
git stash
git pull
From now you can use the UI to update your image.
PROBLEM 2

Almost forgot, I have another problem with network. Once it connects, everything works fine (I can listen to online radio stations for hours, even in flac) but there are some problems with pac.....
Strange, but first let us try to fix your wifi problems.

- So please update like mentioned above.
- disable DHCPCD
systemctl disable dhcpcd
Let me know if something changes.

Frank

Sorry for not answering, I had some work and wasn't able to play with RuneAudio. Now it's working so far, I'm currently listening to music from it connected with Wi-Fi. In case of furtherproblems, I will try these commands and let you know how it works then. Thank you for your help!

XploD

Today I finally found a trace; seems that my problems with Wi-Fi are somehow related to LIRC. I moved to another city and I hoped that there won't be problems anymore since I have a better and newer router here and it's very close so signal strength is excellent but problems are here again, and this time sometimes even worse; sometimes the Wi-Fi dongle won't even start (the LED is off). Since I have a TV with HDMI here, I connected my Pi and here's what I discovered:

Sometimes I got this when I turn on or reboot my Pi, and in that case, the Wi-Fi doesn't work:

: DSC_0003.jpg (210 KiB) Viewed 2159 times

Otherwise I get this and then Wi-Fi works:

: DSC_0004.jpg (235.16 KiB) Viewed 2159 times

I tried to reboot it dozens of times and everytime it was the same situation: if there's this LIRC error, Wi-Fi is dead, if there's no error, Wi-Fi works. Sometimes I had to reboot it 5 or more times to get it working, without error. Also, I haven't noticed any regularity in appearing of this error.

Any idea what could cause this? I know that LIRC is not a part of RuneAudio but I just can't live without it

hondagx35

Hi XploD,

i do not think that your problem has something to do with lirc.
The message you get on the console is not an error it's only a notice that is printed to the console.
This message appears at the same time the login prompt is displayed.
Hit enter and you'll get the prompt back.

There is a timing issue with your wifi or with systemd on your system.
Please send me your debug info (dmseg) for the two situations (wifi OK / wifi NOK).

BTW: i have the same notice on my cubietruck and wifi works perfect all the time.

Frank

XploD

It makes sense what you say because, as far as I remember, I had the same problems even with clean install. But from the other side, why Wi-Fi dies exactly every time when message appears and why it works when there is no message? Also, why this message sometimes appear and sometimes not? LIRC works every time, regarding this message.

I will post here debug info as soon as I find a way to get wifi NOK since I don't have a keyboard nor a long enough cable to connect to router via Ethernet so once Wi-Fi dies, I'm not able to interact with Pi and I have to do power unplug/plug. That's why this problem bothers me so much because if the Wi-Fi is not working, I'm not able to do anything. The only solution is to bring the Pi closer to the router and connect it via cable but this is not easy because of the mess connected to it

(I'm trying to forward all the work for LCD and buttons to PIC microcontroller connected with Pi by serial connection) and my GPIO pins are a little bit bent so pulling out the cable is very hard.

XploD

I managed to share my Wi-Fi connection through Ethernet socket on my laptop and then connect my Pi there, so here you go:

Wi-Fi OK: http://pastebin.com/n1ys8KFn
Wi-Fi FAIL: http://pastebin.com/vEfj7mHQ

XploD

Have you found anything? Problems are back and now they're even worse than before. The whole thing is just unnusable. It takes 15-20 reboots for the Wi-Fi to get connected. I tried that other nano dongle, the same + it works even worse, the signal is almost full but I can't even play web radio, it stutters and breaks all the time.

And now, the whole thing is dead. It takes too long to boot and I get this message everytime:

: DSC_0045.JPG (151.7 KiB) Viewed 2056 times

And that bigger dongle with antenna is dead, it doesn't even light up (green led) It does at the beggining but then it dissapears before the system boots up.

The smaller one still works but it barely works. The connection keeps dropping all the time. I can get to load RuneUI (although it's slow) but when I try to play web radio, the connection drops.

It DEFINITELY has to do something with LIRC but I can't find what and why. I had these problems even with clean image.

What should I do? I don't see any other option than try some other system, but RuneAudio is far the best and this is not an option I want to take. But I have to fix this ASAP. I lost all my tempers with this Wi-Fi and ethernet cable is not an option at all. That's why I can't even fix it because I can't access it when Wi-Fi is not working.

hondagx35

Hi XploD,

It DEFINITELY has to do something with LIRC but I can't find what and why. I had these problems even with clean image.

This is a a contradiction in terms. If this also happens with a clean image it can't be an issue with lirc.

Please first update your installation:

cd /srv/http/
git stash
git pull/

Take a look at your debug info, there is a service "Test" running.
What is it good for? It stops the boot process for a few seconds.
If it only was a test, when disable it:

systemctl stop Test
systemctl disable Test

The country code on your system is set to china.

[ 7.111037] ath: EEPROM indicates we should expect a country code
[ 7.111048] ath: doing EEPROM country->regdmn map search
[ 7.111056] ath: country maps to regdmn code: 0x52
[ 7.111065] ath: Country alpha2 being used: CN

Please try to set it to croatia:

iw reg set HR

As i told you before, the message from lirc is normal and also appears on my system.

Frank

XploD

Thank you Frank for all your help.

This is a a contradiction in terms. If this also happens with a clean image it can't be an issue with lirc.

I know, but this thing with LIRC is to obvious to be accidentally. I tried maybe 100 times and everytime when Wi-Fi is not working, there's this message. But when Wi-Fi works, there's no messages at all. Now I'm thinking about trying again with clean image, but this is very hard to achieve since I can't remove my Pi to connect it via cable to router to do a initial Wi-Fi configuration. But I'm thinking about turning my other RasPi into Wi-Fi receiver and then to share this connection through ethernet port.

Take a look at your debug info, there is a service "Test" running.
What is it good for? It stops the boot process for a few seconds.
If it only was a test, when disable it:

This is an old debug info, as you can see, from 16 Oct 2015. I don't have this any more, but now I have a service for LCD and buttons which starts 20 seconds after network.

Please try to set it to croatia:

I'm getting the message that "iw" command doesn't exists. Do I have to install something?

Please first update your installation:

I've done this but no help.

« Previous Page