Christos

Thanks for pointing this out, I'll give it a try as soon as my new image gets 'baked', I'm waiting by the oven lol !! BTW, was looking at this -> http://docs.armbian.com/boards/orangeopipcplus/ which supposedly is relevant but it does not say anything and missed what you indicated.

For OPiPCplus there are only two Orange-images and the only that easy to login is Lubuntu, though I didnt try it yet. OPiPCplus comes pre-installed on eMMC with android. So, in Armbian is still pending to get a OrangePi eMMC flashing image method?

Thanks for pointing this. Yet, did not quite understood what you were doing there to be honest. How did you write to eMMC? with what command? In any case, it looks quite accidental and not clear. I'm interested if Armbian has a formal or a real tested way of writing firmware image to eMMC.

Hi, Just received a OPiPCplus and first things first ..loading it with Armbian. Is there a guide on how to flash Armbian image to OPiPCplus internal eMMC? Searched the forum but couldnt pinpoint anything.. Christos

Reporting, After 'apt-get install armbian-firmware-full' wifi is istalled, the 8192cu-based wifi works ok. The additional driver that installed ok previously, the 8192eu now was not working. Re-installed it via 'make install', but again was not working.. needed a build again and install and then it works this ok too. Christos

Ok, Seen that a couple of times on other threads and now happened to me too. Did the latest upgrade and after that no more WiFi dmesg complain about 8192cu bin firmware missing.. Any easy solution? (tried apt-get install firmware-realtek but did not complete, broken)

Managed so far to have hostapd with 8192cu and client with 8192eu. But still hostapd with 8192eu is elusive for me.. (keep trying and using hostapd-realtek).

Solved, now its ok.

Got this when I do an apt-get update root@nanopineo:~# apt-get update Hit http://security.debian.org jessie/updates InRelease Ign http://httpredir.debian.org jessie InRelease Hit http://httpredir.debian.org jessie-updates InRelease Hit http://httpredir.debian.org jessie-backports InRelease Hit http://security.debian.org jessie/updates/non-free armhf Packages Hit http://httpredir.debian.org jessie Release.gpg Hit http://security.debian.org jessie/updates/non-free Translation-en Hit http://security.debian.org jessie/updates/main armhf Packages Hit http://security.debian.org jessie/updates/contrib armhf Packages Hit http://httpredir.debian.org jessie Release Hit http://security.debian.org jessie/updates/contrib Translation-en Hit http://security.debian.org jessie/updates/main Translation-en Get:1 http://httpredir.debian.org jessie-updates/main armhf Packages/DiffIndex [5,440 B] Get:2 http://httpredir.debian.org jessie-updates/contrib armhf Packages [32 B] Get:3 http://httpredir.debian.org jessie-updates/non-free Translation-en/DiffIndex [736 B] Get:4 http://httpredir.debian.org jessie-updates/non-free armhf Packages/DiffIndex [736 B] Get:5 http://httpredir.debian.org jessie-updates/contrib Translation-en [14 B] Get:6 http://httpredir.debian.org jessie-updates/main Translation-en/DiffIndex [2,704 B] Get:7 http://httpredir.debian.org jessie-backports/main armhf Packages/DiffIndex [27.8 kB] Get:8 http://httpredir.debian.org jessie-backports/contrib armhf Packages/DiffIndex [18.7 kB] Ign http://apt.armbian.com jessie InRelease Err http://apt.armbian.com jessie Release.gpg Unable to connect to apt.armbian.com:http: Ign http://apt.armbian.com jessie Release Ign http://apt.armbian.com jessie/main armhf Packages/DiffIndex Ign http://apt.armbian.com jessie/utils armhf Packages/DiffIndex Ign http://apt.armbian.com jessie/jessie-desktop armhf Packages/DiffIndex Err http://apt.armbian.com jessie/jessie-desktop Translation-en_US Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/jessie-desktop Translation-en Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/jessie-desktop Translation-en_US.UTF-8 Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/main Translation-en_US Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/main Translation-en Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/main Translation-en_US.UTF-8 Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/utils Translation-en_US Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/utils Translation-en Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/utils Translation-en_US.UTF-8 Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/main armhf Packages Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/utils armhf Packages Unable to connect to apt.armbian.com:http: Err http://apt.armbian.com jessie/jessie-desktop armhf Packages Unable to connect to apt.armbian.com:http: Get:9 http://httpredir.debian.org jessie-backports/non-free armhf Packages/DiffIndex [4,594 B] Get:10 http://httpredir.debian.org jessie-backports/contrib Translation-en/DiffIndex [5,500 B] Hit http://httpredir.debian.org jessie/contrib Translation-en Get:11 http://httpredir.debian.org jessie-backports/main Translation-en/DiffIndex [27.8 kB] Get:12 http://httpredir.debian.org jessie-backports/non-free Translation-en/DiffIndex [9,790 B] Hit http://httpredir.debian.org jessie/main armhf Packages Hit http://httpredir.debian.org jessie/contrib armhf Packages Hit http://httpredir.debian.org jessie/non-free armhf Packages Hit http://httpredir.debian.org jessie/main Translation-en Hit http://httpredir.debian.org jessie/non-free Translation-en Fetched 104 kB in 18s (5,614 B/s) W: Failed to fetch http://apt.armbian.com/dists/jessie/Release.gpg Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/i18n/Translation-en_US Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/i18n/Translation-en Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/i18n/Translation-en_US.UTF-8 Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/main/i18n/Translation-en_US Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/main/i18n/Translation-en Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/main/i18n/Translation-en_US.UTF-8 Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/utils/i18n/Translation-en_US Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/utils/i18n/Translation-en Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/utils/i18n/Translation-en_US.UTF-8 Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/main/binary-armhf/Packages Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/utils/binary-armhf/Packages Unable to connect to apt.armbian.com:http: W: Failed to fetch http://apt.armbian.com/dists/jessie/jessie-desktop/binary-armhf/Packages Unable to connect to apt.armbian.com:http: E: Some index files failed to download. They have been ignored, or old ones used instead. root@nanopineo:~# apt-get update But when I go with my browser to lets say http://apt.armbian.com/dists/jessie/jessie-desktop/binary-armhf/Packages I do get the file.. what is going on here? did I do something wrong?

And the funny part is that Armbian's repository is down, cannot do an apt-get whatever.. (a few hours later, apt-get started working again)

lol

Ok, After succesfully using the 8192eu as client, its time to set ip up with hostapd use. I got two of those dongles, each is plugged to a NanoPi NEO v1.1 running Armbian 5.21 jessie 3.4.112. Both got the 8192eu .ko driver installed and are able to operate as clients succesfully. Now one of them I like to make it as AP with hostapd. Followed the tutorial here for AP -> http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/ but did report errors root@nanopineo:~# hostapd /etc/hostapd.conf Configuration file: /etc/hostapd.conf nl80211: deinit ifname=wlan1 disabled_11b_rates=0 nl80211 driver initialization failed. wlan1: interface state UNINITIALIZED->DISABLED wlan1: AP-DISABLED hostapd_free_hapd_data: Interface wlan1 wasn't started root@nanopineo:~# the /etc/hostapd.conf contents root@nanopineo:~# cat /etc/hostapd.conf ssid=NanoPiNEO interface=wlan1 hw_mode=g channel=5 driver=nl80211 logger_syslog=0 logger_syslog_level=0 wmm_enabled=1 ieee80211n=1 wpa=3 preamble=1 #wpa_psk=66eb31d2b48d19ba216f2e50c6831ee11be98e2fa3a8075e30b866f4a5ccda27 wpa_passphrase='123456789' wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP auth_algs=1 macaddr_acl=0 noscan=1 #ht_capab=[HT40-][SHORT-GI-40][SHORT-GI-40][DSSS_CCK-40] country_code=GR #ieee80211d=1 root@nanopineo:~# thats the ifconfig -a report root@nanopineo:~# ifconfig -a eth0 Link encap:Ethernet HWaddr ee:1e:a4:bb:94:e9 inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: 2a02:582:d2e:1100:ec1e:a4ff:febb:94e9/64 Scope:Global inet6 addr: fe80::ec1e:a4ff:febb:94e9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:818 errors:0 dropped:0 overruns:0 frame:0 TX packets:702 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:74303 (72.5 KiB) TX bytes:87621 (85.5 KiB) Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:43 errors:0 dropped:0 overruns:0 frame:0 TX packets:43 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4436 (4.3 KiB) TX bytes:4436 (4.3 KiB) tunl0 Link encap:IPIP Tunnel HWaddr NOARP MTU:1480 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:0 RX bytes:0 (0.0 TX bytes:0 (0.0 wlan1 Link encap:Ethernet HWaddr 24:05:0f:00:00:75 inet addr:192.168.10.1 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: 2a02:582:d2e:1100:2605:fff:fe00:75/64 Scope:Global inet6 addr: fe80::2605:fff:fe00:75/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:31 errors:0 dropped:2 overruns:0 frame:0 TX packets:124 errors:0 dropped:1 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5427 (5.2 KiB) TX bytes:9680 (9.4 KiB) root@nanopineo:~# Any hints? Christos

@shaidali55 Thanks!! Tested and t works just fine. Thank you Christos

Just to report, NanoPi-NEO v1.1, with FA heatsink, under cpuburn-a7 stressed for more than 6 hours, with Armbian 5.21, kernel 3.4.112 was ok at circa 70degrees, running alternate at 600-800 MHz with FA image, it was also ok but they probably have pushed cpu/ram and temp thresholds parms a bit higher and went to circa 80degrees, in both with FA heatsink no problems were observed even after really long stress periods, alternating again at about 600-800 MHz.

Ok, The 8192cu based on specs go up to 150Mbps and 8192eu to 300Mbps, the protocol itself and its theoretical limit is another story. What you forgot to mention is the actual current medium congestion where in rural areas and appartment buildings with lots of devices in the vicinity, achieving high speeds is dificult. I kinda know all these things.. yet I do want to give a try and have a higher (capable) bandwidth wifi hardware. So if anyone can propose such a device would be great. Or just to give me a pointer on how to integrate in Armbian a new driver. Christos

Ok, The dongle came with a CD containing linux driver sources, a SDK for it, so if you have any pointer on how to add this myself, then I could give it a shot. Also, which 300Mbps dongles do work with Armbian? do you happen to know? is the other you bought a 300Mbps one? P.S. I do have 8192cu 150Mbps dongles that are configured and work just fine, but do need now the extra bandwidth of the 300.. P.S. 2 Forgot to mention that I'm interested only in kernel 3.4.112

Hi, I got one of those cheap 300Mbps wifi dongles with 8192EU chip with USB Vid/Pid 0bda:818b. How can we enable this in Armbian? lsmod does not show any detected h/w driver and wan0 is not showing up in ifconfig. Only lsusb has the following root@nanopineo:~# lsusb Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 0bda:818b Realtek Semiconductor Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@nanopineo:~# Any hint or pointer welcome. Christos

The diffs in sound/soc/sunxi/hdmiaudio are almost like a rewrite of the driver, there are way too many changes in there so I guess they took care of it like they did in daudio (PCM/I2S). I've kept it simple and patched only the later and tested just for my own purposes.

Did a diff between tkaiser's link above and Armbian's sun8i legacy treesource on sound/soc/sunxi, created myself a patch and applied it to Igor's build.

"Houston, Tranquility Base here. The Eagle has landed." @tkaiser Thomas, a very big thank you!! Applied the driver files patch and everything works!! Got S24_LE working ok in 96K & 192K. Thanks again Christos

I understand. From a first glimpse, it shows that in this latest BSP they do have added handling of the 24bit resolution, its obvious from the diffs in sound/soc/sunxi. If the modifications in sound/soc drivers involve and require major other changes in different modules (eg dma or clock/timing), then I do not think I'm gonna get the whole of it done, its above me, if on the other hand changes are compartmentalized only to the driver files without any other dependants, then I'll give it a try.

Seen some VERY INTERESTING diffs from orangepi's sourcetree there!! I will give it a try, make a little patch on the relevant device files and apply it to Igor's build.. If that is for real and works.. then............

Thanks for the info, really appreciated. If you happen to have the name of the relevant IRC (or a link) for me to keep an eye on would be great. Christos

Ok Thomas, indeed needed the kernel clarification. It also eluded me that most likely the mainline devs couldnt care less for any legacy issues. On the other hand though, is there any way we can have audio in mainline for H3?? I'm not able to have audio drivers at vanilla in either OPi or NPi login as: root root@192.168.1.12's password: _ _ ____ _ _ _ | \ | | __ _ _ __ ___ | _ \(_) | \ | | ___ ___ | \| |/ _` | '_ \ / _ \| |_) | | | \| |/ _ \/ _ \ | |\ | (_| | | | | (_) | __/| | | |\ | __/ (_) | |_| \_|\__,_|_| |_|\___/|_| |_| |_| \_|\___|\___/ Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 4.7.6-sun8i System load: 0.44 Up time: 34 sec Memory usage: 8 % of 495Mb IP: 192.168.1.12 CPU temp: 26°C Usage of /: 7% of 15G Last login: Sat Oct 15 12:03:39 2016 from 192.168.1.6 root@nanopineo:~# aplay -l aplay: device_list:268: no soundcards found... root@nanopineo:~# Or is there any guide somewhere that we can enable even the onboard H3 audio? Christos

Hi, Initially this started by trying to have proper capture and playback in PCM/I2S port, but it looks like that ALL H3 audio drivers got the same problem, they cannot capture at 24bits, they cannot do HiFi recording despite the Allwinner's datasheet that they do have 24bits in plain audio port and up to 32bits in PCM/I2S/HDMI. I made a very simple test in another thread here and anyone with any H3 board without anything else can do it too -> http://forum.armbian.com/index.php/topic/759-tutorial-i2s-on-orange-pi-h3/?p=17595 Then it popped to my mind to do the most simple of the tests, in the included/onboard audio codec, wich according to datasheet it is working to 24bits, so not even a PCM/I2S enabled board is needed, just a stock one. login as: root root@192.168.1.10's password: ___ ____ _ ___ / _ \ _ __ __ _ _ __ __ _ ___ | _ \(_) / _ \ _ __ ___ | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | | | | | | '_ \ / _ \ | |_| | | | (_| | | | | (_| | __/ | __/| | | |_| | | | | __/ \___/|_| \__,_|_| |_|\__, |\___| |_| |_| \___/|_| |_|\___| |___/ Welcome to ARMBIAN Debian GNU/Linux 8 (jessie) 3.4.112-sun8i System load: 0.07 Up time: 2 hours Memory usage: 11 % of 494Mb IP: 192.168.1.10 CPU temp: 44°C Usage of /: 7% of 15G [ 2 updates to install: apt-get upgrade ] Last login: Sat Oct 15 08:21:07 2016 from 192.168.1.6 root@orangepione:~# cat /etc/asound.conf pcm.!default { type hw card 0 } ctl.!default { type hw card 0 } root@orangepione:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 root@orangepione:~# root@orangepione:~# alsacap/alsacap *** Scanning for playback devices *** Card 0, ID `audiocodec', name `audiocodec' Device 0, ID `SUNXI-CODEC sndcodec-0', name `', 1 subdevices (1 available) 1..2 channels, sampling rate 8000..192000 Hz Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE Subdevice 0, name `subdevice #0' Card 1, ID `sndhdmi', name `sndhdmi' Device 0, ID `SUNXI-HDMIAUDIO sndhdmi-0', name `', 1 subdevices (1 available) 1..8 channels, sampling rate 8000..192000 Hz Sample formats: S16_LE, S24_LE, S32_LE, S20_3LE Subdevice 0, name `subdevice #0' root@orangepione:~# As you see, this is a plain stock OrangePi One and got the onboard audio codec displayed. There is an error in the above system reporting, the codec according to datasheet is able to go up to 48KHz and not up to 192KHz, that is an indication that whoever did the driver implementation didnt do it properly.. Next, I did the same test as in the PCM/I2S post above, this time with the onboard codec Card 0, ID `audiocodec', name `audiocodec' root@orangepione:~# arecord -t wav -c 2 -f S24_LE -r 48000 -d 10 testrec.wav Recording WAVE 'testrec.wav' : Signed 24 bit Little Endian, Rate 48000 Hz, Stereo root@orangepione:~# Requested a 10 seconds recording at 24bits. As previously, the system took 20 seconds of a recording.. Then did the aplay of the recorded file root@orangepione:~# aplay testrec.wav Playing WAVE 'testrec.wav' : Signed 24 bit Little Endian, Rate 48000 Hz, Stereo root@orangepione:~# which again did squeeze the 20 seconds of initial recording into 10 seconds.. Thus, if I look at it correctly, we have a more generic audio issue in H3 audio drivers and not only to PCM/I2S that initially thought. Could be the DMA implemetnation or timing, dont know. @Igor and admins, do you think we can report this to linux sunxi for rectification? Christos