All Oranges, Debian and Ubuntu images, updated 12.1.2019

tiras · Published in 2016-2-24 02:42:14

hello guys,

i am stuck here and lost hours for building the desktop environmen, please help.

i am running this on plus2 and ethernet works well. i installed gnome but startx returns with command not found error.

could you please advice me how to work start desktop.

yo2ldk · Published in 2016-2-24 03:16:37

hi,

I have OPI PC and I write image with rufus, and also with imagewriter, but my board not boot..
red LED is always off, please some tips... thank you

pmos69 · Published in 2016-2-24 06:26:03

Edited by pmos69 at 2016-2-24 06:28

yo2ldk replied at 2016-2-24 03:16
hi,

I have OPI PC and I write image with rufus, and also with imagewriter, but my board not boot ...

Try a diferent sdcard, especially if you are using an 8GB sdcard.
I have dificulties making any of my 8GB sdcards boot with some images.

Also, the red led doesn't come on with this image (yet).

igorpec · Published in 2016-2-24 14:48:25

rufik replied at 2016-2-23 10:46
I've installed Armbian 5.03 on OPI 2 and it looks like it's working quite well
Quick look - wifi ...

Will be checked why is this load so high. Last time i was running it, it was fine.

To checkup CPU frequncies and their usage parts type:

cpufreq-info

snowbody · Published in 2016-2-24 17:40:05

I've installed armbian 5.03 on an orange pi PC.

I had difficulties using the supplied imagewriter: I copied the imagexxx.raw to imagexxx.img and used w32diskimager instead.

I installed the desktop as described on http://www.armbian.com/documentation/
I tried to change the resolution by modifying the file  boot.cmd
# disp.screen0_output_mode=1920x1080p60 to set video mode
I uncommented it
disp.screen0_output_mode=1920x1080p60
and executed : mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr
....reboot .... resolution remains the same

(2)I tried to build the armbian image myself but I run into some errors (just for your information)

│ /usr/src/armbian/sources/linux-sun8i/h3-wip/scripts/package/builddeb: line │
│ /usr/src/armbian/sources/linux-sun8i/h3-wip/scripts/package/Makefile:99: r │
│ make[1]: *** [deb-pkg] Error 127                                        │
│ Makefile:1221: recipe for target 'deb-pkg' failed                         │
│ make: *** [deb-pkg] Error 2                                              │
└────────────────────────────────────────────────────────────────────────────┘

mv: missing destination file operand after ‘/usr/src/armbian/output/debs/’
Try 'mv --help' for more information.

yo2ldk · Published in 2016-2-25 02:10:38

pmos69 replied at 2016-2-24 06:26
Try a diferent sdcard, especially if you are using an 8GB sdcard.
I have dificulties making any of ...

thank you for reply,

it has exactly 8 Gb

I wait for another sd cards with 10 class.
after another 3 times writes on card, this somehow boot now, but is stop on command line, I make all update and upgrades,
installed again kde desktop but this not appear .
startx or xinit is not a command I receive

igorpec · Published in 2016-2-25 05:27:33

snowbody replied at 2016-2-24 10:40
I've installed armbian 5.03 on an orange pi PC.

I had difficulties using the supplied imagewriter: ...

Those images are still in developing phase as stated on download page so things might not work well. Also the documentation is not H3 ready. Resolution changing is done differently on those boards. We are in a process to make them the same on all boards but this takes time.

Please check armbian forum for detail information how to change screen resolution.

Building images can brake since patches are comming in daily ...

pmos69 · Published in 2016-2-26 09:22:27

Just pulled the code and built an image.
Was hoping the u-boot patch would solve by issues booting on crappy 8GB sdcards, but it's still the same.

On my 8GB sdcards, for some reason, it can never read the partition table.

U-Boot 2016.03-rc2-armbian (Feb 25 2016 - 22:15:28 +0000) Allwinner Technology
CPU: Allwinner H3 (SUN8I)
I2C: ready
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2051 bytes read in 485 ms (3.9 KiB/s)
## Executing script at 43100000
0 bytes read in 365 ms (0 Bytes/s)
12927 bytes read in 1243 ms (9.8 KiB/s)
** ext4fs_devread read error - block
** Can't read partition table on 0:0 **
** Invalid partition 1 **
** Can't read partition table on 0:0 **
** Invalid partition 1 **
Kernel image @ 0x46000000 [ 0x000000 - 0x49a760 ]
## Flattened Device Tree blob at 49000000
Booting using the fdt blob at 0x49000000
Using Device Tree in place at 49000000, end 4900627e
Starting kernel ...
Uncompressing Linux...

Copy code

...and it freezes here.

Compared to the same image copied to a 32GB sdcard:

U-Boot 2016.03-rc2-armbian (Feb 25 2016 - 22:15:28 +0000) Allwinner Technology
CPU: Allwinner H3 (SUN8I)
I2C: ready
DRAM: 1 GiB
MMC: SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: No ethernet found.
starting USB...
No controllers found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2051 bytes read in 343 ms (4.9 KiB/s)
## Executing script at 43100000
0 bytes read in 262 ms (0 Bytes/s)
12927 bytes read in 862 ms (13.7 KiB/s)
4826976 bytes read in 5258 ms (896.5 KiB/s)
Kernel image @ 0x46000000 [ 0x000000 - 0x49a760 ]
## Flattened Device Tree blob at 49000000
Booting using the fdt blob at 0x49000000
Using Device Tree in place at 49000000, end 4900627e
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Debian GNU/Linux 8 orangepih3 ttyS0
orangepih3 login:

Copy code

rufik · Published in 2016-2-26 17:31:07

igorpec replied at 2016-2-24 07:48
Will be checked why is this load so high. Last time i was running it, it was fine.

To checkup CPU ...

@igorpc I found built-in wifi not reliable (OPI 2), see simple ping results:

$ ping opi
PING opi (192.168.5.6) 56(84) bytes of data.
64 bytes from opi.lan (192.168.5.6): icmp_seq=1 ttl=64 time=181 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=2 ttl=64 time=298 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=3 ttl=64 time=1.36 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=4 ttl=64 time=342 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=5 ttl=64 time=1.34 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=6 ttl=64 time=183 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=7 ttl=64 time=1.35 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=8 ttl=64 time=1.42 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=9 ttl=64 time=1.38 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=10 ttl=64 time=273 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=11 ttl=64 time=1.42 ms
64 bytes from opi.lan (192.168.5.6): icmp_seq=12 ttl=64 time=318 ms
[...cut!...]
--- opi ping statistics ---
132 packets transmitted, 132 received, 0% packet loss, time 131185ms
<font color="#ff0000">rtt min/avg/max/mdev = 1.286/109.338/868.235/137.288 ms</font>

Copy code

Wifi disconnects from time to time, see syslog and dmesg:

Feb 26 09:03:41 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
Feb 26 09:13:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
Feb 26 09:23:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
Feb 26 09:33:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
Feb 26 09:43:41 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
Feb 26 09:53:41 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
Feb 26 10:03:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
[Fri Feb 26 09:03:41 2016] RTL871X: send eapol packet
[Fri Feb 26 09:03:41 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP
[Fri Feb 26 09:13:40 2016] RTL871X: send eapol packet
[Fri Feb 26 09:13:40 2016] RTL871X: set group key camid:6, addr:64:70:02:67:60:33, kid:2, type:TKIP
[Fri Feb 26 09:23:40 2016] RTL871X: send eapol packet
[Fri Feb 26 09:23:40 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP
[Fri Feb 26 09:33:40 2016] RTL871X: send eapol packet
[Fri Feb 26 09:33:40 2016] RTL871X: set group key camid:6, addr:64:70:02:67:60:33, kid:2, type:TKIP
[Fri Feb 26 09:43:40 2016] RTL871X: send eapol packet
[Fri Feb 26 09:43:40 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP
[Fri Feb 26 09:53:40 2016] RTL871X: send eapol packet
[Fri Feb 26 09:53:40 2016] RTL871X: set group key camid:6, addr:64:70:02:67:60:33, kid:2, type:TKIP
[Fri Feb 26 10:03:40 2016] RTL871X: send eapol packet
[Fri Feb 26 10:03:40 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP

Copy code

Some workaround is having network traffic, i.e. continous ping in screen. Then wifi is looks better I think:

--- opi ping statistics ---
733 packets transmitted, 733 received, 0% packet loss, time 732988ms
<font color="#2e8b57">rtt min/avg/max/mdev = 1.152/18.216/938.857/77.553 ms</font>

Copy code

igorpec · Published in 2016-2-26 17:42:47

pmos69 replied at 2016-2-26 02:22
Just pulled the code and built an image.
Was hoping the u-boot patch would solve by issues booting o ...

https://github.com/igorpecovnik/ ... 76d0b822bca6de736e8

This patch is not yet included to Orange pi H3 building process, since we force to use latest uboot for other reasons.

Did you manully indlude it? Otherwise it could not make things better.