Jump to content

Orange Pi Zero Armbian Nightly Build


scargill
 Share

Recommended Posts

Current nightly build of Armbian on the Orange Pi Zero.

 

As root - add a WIFI connection and fill in details. Save.

 

It is there - but does not appear in the ACTIVATE option (which weirdly you have to exit from NMTUI and go back in to find).... hence - can't start WIFI.

 

Link to comment
Share on other sites

Open source development is fun. Join Armbian Linux development team today!

Hmm... it seems xradio_wlan is missing in /etc/modules. Does it help if you manually do a 'sudo modprobe xradio_wlan' and then try again using 'sudo nmtui'?

 

Is this double loading already fixed? In case not, module must be loaded twice.

Link to comment
Share on other sites

sudo modprobe xradio_wlan   returns nothing... just back to the prompt

 

sudo nmtui still shows the connection when you go to edit - but does not show anything in the ACTIVATE area - seems more like a bug in nmtui surely... after reboot the entry is still there under edit - but no sign of it in activate.

Link to comment
Share on other sites

First, it is loaded automatically due to DT "compatible" property (currently only dev kernel based nightlies are available).

Second, I didn't observe any problems with the module loading last time I tested it on dev kernel.

 

And third, providing this kind of feedback for the nightly images (especially with the dev kernel) without providing any necessary details (at least armbianmonitor logs) won't change anything.

Link to comment
Share on other sites

providing this kind of feedback for the nightly images (especially with the dev kernel) without providing any necessary details (at least armbianmonitor logs) won't change anything.

 

True. Pete, please provide output from 'sudo armbianmonitor -u' when connected via Ethernet (or at least dmesg output if you access the board through serial console).

 

JFTR: WiFi on my OPi Zero stopped working some weeks ago after I did some hardware stuff so my assumption was that I managed to damage the board glueing a heatsink to the SoC or exchanging antennas. But maybe this was unrelated and WiFi is broken on some boards. At least logs would help to diagnose the problem (or let's better say they're necessary). Please see posts #155 and #158 here: https://forum.armbian.com/index.php/topic/2808-orange-pi-zero-went-to-the-market/?p=21561

Link to comment
Share on other sites

Just tested the wireless again with Xenial FEL booted system. Worked fine for me: nmtui - Activate a connection - (selected wireless network) - (input password) - connected.

One time before my wireless network was not displaying in "Activate a connection" window, so I had to run "iwlist wlan0 scan" since there is no rescan option in nmtui network list.

Link to comment
Share on other sites

Just tested the wireless again with Xenial FEL booted system. Worked fine for me: nmtui - Activate a connection - (selected wireless network) - (input password) - connected.

One time before my wireless network was not displaying in "Activate a connection" window, so I had to run "iwlist wlan0 scan" since there is no rescan option in nmtui network list.

Hi there

 

iwlist wlan0 scan

 

wlan0     Interface doesn't support scanning

 

What version operating system and release did you use? I used the latest nightly build as an earlier version was unreliable (but actually worked)

Link to comment
Share on other sites

True. Pete, please provide output from 'sudo armbianmonitor -u' when connected via Ethernet (or at least dmesg output if you access the board through serial console).

 

JFTR: WiFi on my OPi Zero stopped working some weeks ago after I did some hardware stuff so my assumption was that I managed to damage the board glueing a heatsink to the SoC or exchanging antennas. But maybe this was unrelated and WiFi is broken on some boards. At least logs would help to diagnose the problem (or let's better say they're necessary). Please see posts #155 and #158 here: https://forum.armbian.com/index.php/topic/2808-orange-pi-zero-went-to-the-market/?p=21561

 

I've been experimenting and getting no-where - so to be safe I'll reload the operating system then send the logs. .(zador.blood.stained - I had no idea about this logging -not everyone has the same level of knowledge of Armbian)

Link to comment
Share on other sites

True. Pete, please provide output from 'sudo armbianmonitor -u' when connected via Ethernet (or at least dmesg output if you access the board through serial console).

 

JFTR: WiFi on my OPi Zero stopped working some weeks ago after I did some hardware stuff so my assumption was that I managed to damage the board glueing a heatsink to the SoC or exchanging antennas. But maybe this was unrelated and WiFi is broken on some boards. At least logs would help to diagnose the problem (or let's better say they're necessary). Please see posts #155 and #158 here: https://forum.armbian.com/index.php/topic/2808-orange-pi-zero-went-to-the-market/?p=21561

 

As per request - the log is here...  

 

http://sprunge.us/VWZB

 

This line stood out from the crowd...

 

xradio_wlan mmc1:0001:1: Direct firmware load for xr819/sdd_xr819.bin failed with error -2

 

As did these later on

 

[ 12.031511] xradio_wlan mmc1:0001:1: Direct firmware load for xr819/sdd_xr819.bin failed with error -2

[ 12.031532] xradio_wlan mmc1:0001:1: Falling back to user helper

 

Standing out is one thing of course - I've no idea what to do about it.

Link to comment
Share on other sites

@scargill

Looks like you are missing the firmware... If a directory /lib/firmware/xr819 doesn't exist, then please create it and put files from here inside it.

Hi there

 

The "firmware" subfolder did not exist at all - so I created it and put those files in.

 

I then rebooted the board. I deleted the WIFI connection and recreated it. Still nothing - no Activate.

 

I tried sudo modprobe and then nmtui again - no difference. I tried iwlist wlan0 scan - still - wlan0 interface doesn't support scanning.

 

Here is the latest log output - http://sprunge.us/YFJF

 
Somewhat different message now
 
xradio_wlan: unknown parameter 'macaddr' ignored
 
Anything I've missed?
Link to comment
Share on other sites

Somewhat different message now

 
xradio_wlan: unknown parameter 'macaddr' ignored

This is normal

 

I then rebooted the board. I deleted the WIFI connection and recreated it. Still nothing - no Activate.

Please provide output of "iwconfig" and please check if any wireless networks are displayed in nmtui - Activate a connection

Link to comment
Share on other sites

In my case, after several issue, crappy cable, crappy sdcard, I got it working several times.

But unfortunately, I got back into troubles again, I presume my PiZero has hardware issue.

It is flooding the dmesg with the following lines :

[   28.399502] xradio_wlan mmc1:0001:1: Failed to read control register.
[   28.443148] sunxi-mmc 1c10000.mmc: smc 1 err, cmd 53, RD RTO !!
[   28.449194] sunxi-mmc 1c10000.mmc: data error, sending stop command
[   28.455622] sunxi-mmc 1c10000.mmc: send stop command failed
[   28.461347] sunxi-mmc 1c10000.mmc: smc 1 err, cmd 53, RD RTO !!
[   28.467458] sunxi-mmc 1c10000.mmc: data error, sending stop command
[   28.473820] sunxi-mmc 1c10000.mmc: send stop command failed

Trying to SSH thru ETH, sometime take minutes to get to the prompt, probably due to flooding taking to much CPU.

So, I will forget about WiFi for now until I get another PiZero.

 

EDIT: In fact, even if xradio is commented in DT, the flooding still present, to get rid of it, I need to comment the whole mmc@01c10000.

Link to comment
Share on other sites

This is normal

 

Please provide output of "iwconfig" and please check if any wireless networks are displayed in nmtui - Activate a connection

 

IWCONFIG says:

eth0  no wireless extensions

lo      nowireless  extensions..

 

Thewireless network I put into nmtui is there - but nothing when you go to activate - just nothing there at all in the menu to activate.

Link to comment
Share on other sites

@zador.blood.stained, in my case it was a self made build of Mainline.

 

With perseverance, I've just made another new build, use another sdcard, and it is now working again, but I'm crossing my fingers :

3 sdcard failed within the same week for this PiZero ? I can't believe it, especially that Kingston/Lexar should be so crappy !

Maybe this board still has something wrong ...

 

EDIT : %*!@%#^%^%&!! the fourth sdcard start doing the same again after a reboot !!!

Link to comment
Share on other sites

For clarity - I have just created a new SD - this time using the legacy JESSIE.

 

sudo ifconfig shows this...

 

wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
After nmtui creation and seamless activation..
 
 
wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
          inet addr:192.168.0.158  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::9aa6:91ff:fe6c:5e80/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:87 errors:0 dropped:0 overruns:0 frame:0
          TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:10047 (9.8 KiB)  TX bytes:4057 (3.9 KiB)
 
 
Disconnect power - disconnect ETHERNET - reconnect power - wait...and wait.....

 

Nothing. A quick system scan shows nothing...  disconnect  - back to ETHERNET...

 

 
wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 
 
sudo nmtui
 
The WIFI is there - but needs activating - this time it wants a password!!?? Connection takes several seconds this time.
 
 
wlan0     Link encap:Ethernet  HWaddr 98:a6:91:6c:5e:80
          inet addr:192.168.0.158  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::9aa6:91ff:fe6c:5e80/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:83 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9099 (8.8 KiB)  TX bytes:2956 (2.8 KiB)
 
 
Clearly something there.  I figured I'd try a reboot and leave the ETHERNET connected (last time was actual power off)
Sudo reboot.
 
No Ethernet (correct as WIFI should take precidence).
 
Sure enough  - WIFI working. Working but slow and stuttering - the very reason I went for the latest build in the first place (I'm 3ft from the access point in a small non-metal office).
 
Power off - disconnect Ethernet - power on.
 
 
This time it works - but slowly.
At this point, from earlier advice from TKaiser - sudo h3consumption -w off
 
Please be patient, external requirements are to be installed.
 
Aborted
fex2bin/bin2fex not found and unable to install. Exiting
Aborted
Writing script.bin went wrong. Nothing changed.
 
Tried again - same thing.
 
So - I tried the sudo armbianmonitor -u command..
 
 
ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
ICMP Host Unreachable from 192.168.0.130 for ICMP Echo sent to sprunge.us (216.2                                               39.36.21)
Network/firewall problem detected. Please fix this or upload /var/log/armhwinfo.                                               log manually.
/var/log/armhwinfo.log has been uploaded to curl: (7) Failed to connect to sprun                                               ge.us port 80: Network is unreachable
gzip: /var/log/armhwinfo.log.1.gz: No such file or directory
Please post the URL in the Armbian forum where you've been asked for.
pi@orangepizero:~$
 
Before anyone says that sounds like a connection issue - that has been my constant complaint about earlier WIFI on the Pi Zero.
 
pi@orangepizero:~$ ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.246.54) 56(84) bytes of data.
From orangepizero (192.168.0.130) icmp_seq=1 Destination Host Unreachable
From orangepizero (192.168.0.130) icmp_seq=2 Destination Host Unreachable
From orangepizero (192.168.0.130) icmp_seq=3 Destination Host Unreachable
 
 
Note that the first ping went through.
 
 
I think it is fair to say that the hardware WORKS?
 
 
 
 
 
 
Link to comment
Share on other sites

I made some tests with latest nightly Xenial with kernel 4.9

 

Firmware for the board is missing, since it's missing in our repository too (compiled without externals - my mistake - will be fixed in tomorrows build). After downloading it, things works as expected. 

[  4]   0.00-1.00   sec  1.98 MBytes  16.6 Mbits/sec    0   97.6 KBytes       
[  4]   1.00-2.00   sec  2.02 MBytes  17.0 Mbits/sec    0    150 KBytes       
[  4]   2.00-3.00   sec  2.04 MBytes  17.1 Mbits/sec    0    184 KBytes       
[  4]   3.00-4.00   sec  2.21 MBytes  18.5 Mbits/sec    0    205 KBytes       
[  4]   4.00-5.00   sec  2.27 MBytes  19.0 Mbits/sec    0    228 KBytes       
[  4]   5.00-6.00   sec  2.03 MBytes  17.0 Mbits/sec    0    252 KBytes       
[  4]   6.00-7.00   sec  2.04 MBytes  17.2 Mbits/sec    0    253 KBytes       
[  4]   7.00-8.00   sec  2.15 MBytes  18.1 Mbits/sec    0    284 KBytes       
[  4]   8.00-9.00   sec  1.97 MBytes  16.5 Mbits/sec    0    284 KBytes       
[  4]   9.00-10.00  sec  2.25 MBytes  18.9 Mbits/sec    0    284 KBytes 

Relevant log entries:

[   11.567849] input: r_gpio_keys as /devices/platform/r_gpio_keys/input/input0
[   11.698492] systemd-journald[288]: Received request to flush runtime journal from PID 1
[   11.922987] xradio_wlan: unknown parameter 'macaddr' ignored
[   11.991440] thermal thermal_zone0: failed to read out thermal zone (-16)
[   12.311111] xradio_wlan mmc1:0001:1: missed interrupt
[   12.358444] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   12.946516] libphy: 1c30000.ethernet: probed
[   13.061659] Generic PHY 1c30000.ethernet:01: attached PHY driver [Generic PHY] (mii_bus:phy_addr=1c30000.ethernet:01, irq=-1)
[   13.061699] sun8i-emac 1c30000.ethernet: device MAC address slot 0 02:20:48:b5:7f:05
[   13.063208] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.660577] random: crng init done
[   16.063662] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.172021] sun8i-emac 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   16.172085] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   16.235921] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   16.237278] ieee80211 phy0: Interface ID:0 of type:2 added
[   16.238013] ieee80211 phy0: configuring tx for vif 0
[   16.238480] ieee80211 phy0: configuring tx for vif 0
[   16.238933] ieee80211 phy0: configuring tx for vif 0
[   16.239370] ieee80211 phy0: configuring tx for vif 0
[   16.239816] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (1)IEEE80211_CONF_CHANGE_IDLE (1)
[   16.240053] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   16.616302] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  120.078243] wlan0: authenticate with e8:de:27:fd:6d:25
[  120.078347] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (0)IEEE80211_CONF_CHANGE_IDLE (1)
[  120.078364] ieee80211 phy0: Freq 2427 (wsm ch: 4).
[  120.078769] wlan0: send auth to e8:de:27:fd:6d:25 (try 1/3)
[  120.236605] wlan0: authenticated
[  120.240999] wlan0: associate with e8:de:27:fd:6d:25 (try 1/3)
[  120.244902] wlan0: RX AssocResp from e8:de:27:fd:6d:25 (capab=0x411 status=0 aid=1)
[  120.244995] ieee80211 phy0: configuring tx for vif 0
[  120.245671] ieee80211 phy0: configuring tx for vif 0
[  120.246359] ieee80211 phy0: configuring tx for vif 0
[  120.246997] ieee80211 phy0: configuring tx for vif 0
[  120.250970] wlan0: associated
[  120.251286] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  120.305960] ieee80211 phy0: vif 0: set_key cmd 0
[  120.305985] ieee80211 phy0: CCMP_PAIRWISE keylen=16!
[  120.307309] ieee80211 phy0: vif 0: set_key cmd 0
[  120.307329] ieee80211 phy0: CCMP_GROUP keylen=16!
[  251.211499] sun8i-emac 1c30000.ethernet eth0: Link is Down

I have to note that reconnecting to previously associated AP (after reboot as example) is slow so you need to wait some more time to get an IP. This is somehow strange ... Speed? It's a low cost chip ... from Allwinner.

 

One more thing to note: sometimes it doesn't see my AP even it's 1m away.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...