Unable to connect wifi ap

Please, if you wanna post terminal output use spoiler and format it like a code
Also, what OS you use? How are you trying to connect to AP?

I’m experiencing the same issue… New board with fresh Ubuntu Server downloaded from this site, trying to connect to my AP. nmcli commands all seem to respond as expected, but the connect command fails with “no reason given”.

If you figure it out, please post back :slight_smile:

Can you use nmtui to be sure that you properly configure the interface?

I’m also experiencing this but only for the Ubuntu Server. When using Debian Desktop it seems to work. I tried some debugging and compare both os version and even with my laptop which is running Ubuntu Desktop 18.04.

Wifi that I have is a WPA2-PSK version.

I used nmtui to setup the wifi on both my laptop and the rock pi (same setup steps on both os). My laptop started working and the rock pi didn’t. I also manually compared serveral files which nmtui setups but found no differences.
When using the graphical interface from Debian to setup the wifi is also starts working.

Another test I did on the Ubuntu Server is manually disabling the networkmanager and setting up wpasupplicant which causes my wifi to start working. This however seems to disable the0.

I still haven’t found the underlying cause. I can’t seem to find any logs of the networkmanager, let alone run it in debug and see what the issue is. I think that the networkmanager can see the network but the negotiation about the PSK is just failing. So currently my suspicion is that its just a missing package.

I did some more debugging and I found some logs about what is happening.

See picture:

For some reason it can’t initialize the driver.

Hi guys

I was experiencing the same issue with Ubuntu. My workaround is to turn the wifi radio off and then on again (The IT Crowd solution):

nmcli radio wifi off
nmcli radio wifi on

An then try to connect. I don’t know what is the real problem, but for now I’m using that solution.

Hope it helps. Regards!

2 Likes

Hi ajcalderont:
I tried your workround and it works! Thank you.

Perfect, I’m glad it worked!

Hi @ajcalderont,

This does seem to work, at least for one time. After each reboot you have to do this again.

Its at least a quick fix, but now a sustainable solution. Normally I don’t have a screen attached and I access it over ssh which requires an network connection. Something with a chicken and egg comes to my mind :slight_smile:

Thnx for the tip.

Regards, Jork

Yes @jork, with every reboot you need to do that again. What I did was to add those instructions to /etc/rc.local to be executed automatically after booting, because as you, I work over SSH without a screen attached to the board. Let’s hope we find a better solution soon.

Regards

I am experiencing this as well, is this a known bug/any updates?
Image:

rockpi4b-ubuntu-bionic-minimal-20190104_2101-gpt.img

We are looking at it now.

Hi
I’m having the same issue with wifi not working on ubuntu server. I’ve tried the work around to stop and start wifi but it still I cant connect to wifi and the answer is only “Connection activation failed: (0) No reason given”
Anybody who has any further info how to solve this issue?

Hi, @pethun

Try this way to see if it helps.

Add the following lines in file, /etc/NetworkManager/NetworkManager.conf

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false

[device]
wifi.scan-rand-mac-address=no
1 Like

Hi @Stephen

Many thanks for the advice. After modifying the file /etc/NetworkManager/NetworkManager.conf according to your instructions wifi is working for ubuntu server.
The working NetworkManager.conf are now as follows:
[main]

plugins=ifupdown,keyfile

[ifupdown]

managed=false

[device]

wifi.scan-rand-mac-address=no

[keyfile]

unmanaged-devices=*,except:type:wifi,except:type:wwan,except:type:ethernet

2 Likes

Hi, found the solutions provided by Stephen and pethun work! Thank you all!

1 Like

Hello,
I am still experiencing the same problem, radio off/on seems to be a work around but I noticed
a delay in pinging the Rockpi4 from a wired ethernet machine but did not notice a delay pinging the same wired ethernet machine from the Rockpi.

kernel logs are also filled with:
bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=01, Err: -5

I am on a rockpi 4 1.3 using a Rockpi eMMC on Armbian with kernel:
Linux rockpi4 4.4.182-rockchip64 #1 SMP Fri Jun 28 17:34:00 CEST 2019 aarch64 GNU/Linux

I am using a QC power supply

Any suggestions what this might be / fix?

Hi All,

After applied workaround from pethun and Stephen (thanks both), seems it works.

But further testing found, wlan0 is able to IP address from Router but not able to connect via SSH or other. Until eth0 is connected, then WiFi connection becomes working properly.

From dmesg, found below message flooding,
[Mon Oct 21 09:05:15 2019] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=01, Err: -5

Any idea?

I’m using rockpi4b-ubuntu-bionic-minimal-20190104_2101-gpt.img, Rock Pi 4b v1.4.

Regards,
Barry

Which kernel version? uname -r ?

Hi Jack,

uname -r output is:
4.4.154-59-rockchip-g5e70f14

Barry