svkatielee

Thanks zador. When I asked the question the kernel was in the repo, but none of the images were updated on the download page so I jumped to the wrong conclusion. Just being impatient. haha

Do I understand this correct? The 5.20 reflects the patch level of the kernel, not necessarily anything about the "Armbian distribution". Such as when download images will have NM instead of wicd. Or maybe you meant: the kernel that will be in "Armbian distribution release 5.20" is now available. I just did the upgrade: The following packages will be upgraded: linux-firmware-image-sun8i linux-headers-sun8i linux-image-sun8i linux-jessie-root-orangepiplus2e linux-u-boot-orangepiplus2e-default and the apt-get dist-upgrade says nothing to do. This is: cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=orangepiplus2e BOARD_NAME="Orange Pi+ 2E" VERSION=5.20 LINUXFAMILY=sun8i BRANCH=default ARCH=arm Boot and login seem faster, but was already nice on the 2E installed to th eeMMC. Thank you. Larry

I set static IPs for several Opi's with nn-applet seems to work ok. However, I had to do it al as root. My user can not edit connections still. Armbian Jessie 5.18 from above link. No desktop, only nodm. if I su - root then nmtui I can edit oK. any other, the edit button is grayed out or the OK button is.

Thank you. It seems to work fine. I still have not had time to figure out hostapd with NM yet. My other life gets in the way. Where is the additional discussion where you have decided to go ahead with switching these out instead of wicd? I have been having trouble finding the discussions since the big documentation change.

See this post for probable problem: http://forum.armbian.com/index.php/topic/1775-wicd-gets-erroneous-bad-password/?p=14708 Since the problem seems to be a wicd to wpa_supplicant timeout problem, any change in information (password, driver, SSID,etc.) can change the amount of time it takes wpa_supplicant to reply. So lots of these differing solutions work some of the time.

I've just spent 2 complete days trying to reproduce the above steps for switching from wicd to NM and failing. (with 5.16 Opi 2E eMMC) If I run vncserver as root, nm-applet works just fine: connects to wifi, edit connections. But not as a user. Finally, the difference, I was trying to do it with tightvncserver (VNC) instead of a direct monitor. In frustration this morning I plugged the monitor in and there was the dialog pop-up to unlock the keyring! So these are not the complete instructions for using VNC exclusively.

Where is the final destination for the HOWTOs? Since this re-organization of the github vs forum, I can't find the discussion streams about the claimed tasks.

@Igor I wonder if you had as much trouble getting NM installed as I did? I tried for a combination that did not need gnome-keyring and network-manager-gnome because of all the extra support packages. And I did not want to enter a password at every boot. To avoid the password I had to use the null passphrase in the default keyring which I thought might not be acceptable. I also tried to find a different alternative. I didn't find any that seemed to work headless and in a desktop. Most choices were various subsets of wicd or NM (wpa_supplicant, netctl, etc.). I even tried to compile wicd.1.7.4 but it needs things in newer kernels I think.

It has taken a while but finally I now have Network Manager running instead of wicd. Here is what I did on my Opi PC 2E installed and booting from nand: Armbian Jessie desktop 5.14 apt-get upgraded to 5.16 and updated Aug 10, 165. Connected to cheap CDR-King Wireless-N AP Router (Chinese) apt-get install network-manager network-manager-gnome xfce4-notifyd xfce4-indicator-plugin gnome-keyring gcr libgck-1-0 libgcr-3-common libgcr-base-3-1 libgcr-ui-3-1 p11-kit p11-kit-modules apt-get remove --purge wicd python-wicd wicd-daemon wicd-gtk gpasswd -a USERNAME netdev Comment out eth0 from /etc/network/interfaces, (also wlan0 if you have it) Change managed= to true in /etc/NetworkManager/NetworkManager.conf Create new file with this content: /etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla [nm-applet] Identity=unix-group:netdev Action=org.freedesktop.NetworkManager.* ResultAny=yes ResultInactive=no ResultActive=yes with eht0 connected and on-board WiFi, reboot came up with eth0 and WiFi available click nm-applet in menu bar select ifupdown (eth0) Ethernet comes up selected my wifi ssid Prompt for password entered password, prompted for default keyring password, left blank and click Continue and Continue again for clear text storage of password rebooted, still have both connected, but icon in nm-applet only shows WiFi but right-click->Connection Info shows both. Now for some testing ....

I am willing to try some. I have only Orange Pis: One, PC, PC +, and PC 2E. I have a few cheap wifi dongles and a couple really cheap Chinese routers. What I don't have is a good understanding of hostapd/network manager and all the wpa_supplicant pieces. And I don't' have much network access. I can't run your build tools because the network is too slow and unreliable. So with a little guidance I'll give it a shot.

I found an old bug report on the same version of wicd that is delivered with the legacy builds. Try to authenticate WPA for wifi, get bad password error. Repeated attempts to authenticate as many as 10 times before it is successful. It will finally succeed, therefore; the password is not bad. https://bugs.launchpad.net/wicd/+bug/1084380 A short summary includes, there seems to be a problem in the wpa_supplicant that causes it to occasionally take too long to return from an authentication request. wicd rev 1.7.2 is set to wait 35 seconds then times out and reports BAD PASSWORD, when it should have reported a timeout. The suggested fix was to allow user config for the timeout, but the test of 250 system startups showed an averaged between 35 and 55 seconds. Their request was to set the default timeout for wpa_supplicant to 120 seconds. The fix was promised for 1.7.3. Jessie/Trusty have wicd 1.7.2.4-4.1 Xenial has 1.7.4.xx I believe this is why so many complaints are posted about wifi on the various armbian SBCs. And why there are so many different "solutions" that only work in special cases. But this is a work-around for wpa_supplicant taking too long in some instances. Can we get a newer release of wicd in the build? I tried just downloading and installing wicd 1.7.4 but without anything else, it no longer connects at all ....

I am a sailor and use OpenCPN for the navigation chart plotter. The charts load and zoom much faster with hardware openGL/ or ES. It has a way to display rendering technique and frames/sec and is barely useful without acceleration. It is very nice with it, even on the Orange Pi One. But I will use the Opi PC Plus for my final installation. I compiled opencpn(4.2 and 4.4) on the default Jessie desktop of both 5.05 and 5.10. I will be recompiling on 5.17 soon. So it is not only games and display managers that use openGL and hardware acceleration. Thank you all for armbian and the rest.

I have just discovered the u-boot help file. On console during power-up, when it says Hit any key to stop autoboot: I hit a key, got a prompt and typed help. Are all the capabilities listed real? pxe, tftpboot, nfs, usbboot, dhcp, bootefi Are many implemented? I did just discover the nfs how-to. -- Larry

Sorry I was not complete and accurate. Debian Jessie desktop 5.14 apt-get upgraded to 5.16 as of 36 hours ago. The gui in the upper right of the default X interface autologed in as the user defined during install The Wicd Network Manager GUI, properties of the wireless AP, selected "WPA 1/2 (Passphrase) preshared key" The first key was "bbbbbbbb" which could be interpreted as HEX or as ascii. The second key was "katielee" unmistakably ascii. The bbbbbbbb was changed to bbbbbbbbz and then it worked.(did not get "Bad Password" and succeeded in connecting to network.) As for code I meant the probable C code that the gui is using to evaluate the key. The log of my install is here: https://www.facebook.com/groups/1483270805309190/permalink/1573610346275235/

Same problem, but this did not help. Tried two Opi PC pluses on two different networks, two different sd cards. It seems to be related to the password. Both networks are set to WEP (Passphrase), but have different passwords, each only 8 characters. One password is too simple, all characters could be either hex or text. the other network's password is also 8 characters but random alpha. We altered the simple password network password by adding a 'z' to the end of its password and now it works fine. It seems as if the wireless code is having difficulty between HEX ans Passphrase.