Please select To the mobile version | Continue to access the desktop computer version

OrangePi

 Login            
 Register            
Search
Hot search: orangepi
Author: igorpec

All Oranges, Debian and Ubuntu images, updated 12.1.2019

  [Copy link]

3

Threads

8

Posts

37

Credits

Novice

Rank: 1

Credits
37
Post time 2016-2-24 02:42:14 | Show all posts
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.

3

Threads

39

Posts

189

Credits

Registered member

Rank: 2

Credits
189
Post time 2016-2-24 03:16:37 | Show all posts
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

0

Threads

21

Posts

112

Credits

Registered member

Rank: 2

Credits
112
Post time 2016-2-24 06:26:03 | Show all posts
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).

9

Threads

632

Posts

4274

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
4274
 Author| Post time 2016-2-24 14:48:25 | Show all posts
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

12

Threads

30

Posts

150

Credits

Registered member

Rank: 2

Credits
150
Post time 2016-2-24 17:40:05 | Show all posts
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.







3

Threads

39

Posts

189

Credits

Registered member

Rank: 2

Credits
189
Post time 2016-2-25 02:10:38 | Show all posts
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

9

Threads

632

Posts

4274

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
4274
 Author| Post time 2016-2-25 05:27:33 | Show all posts
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 ...

0

Threads

21

Posts

112

Credits

Registered member

Rank: 2

Credits
112
Post time 2016-2-26 09:22:27 | Show all posts
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.
  1. U-Boot 2016.03-rc2-armbian (Feb 25 2016 - 22:15:28 +0000) Allwinner Technology

  2. CPU:   Allwinner H3 (SUN8I)
  3. I2C:   ready
  4. DRAM:  1 GiB
  5. MMC:   SUNXI SD/MMC: 0
  6. *** Warning - bad CRC, using default environment

  7. In:    serial
  8. Out:   serial
  9. Err:   serial
  10. Net:   No ethernet found.
  11. starting USB...
  12. No controllers found
  13. Hit any key to stop autoboot:  0
  14. switch to partitions #0, OK
  15. mmc0 is current device
  16. Scanning mmc 0:1...
  17. Found U-Boot script /boot/boot.scr
  18. 2051 bytes read in 485 ms (3.9 KiB/s)
  19. ## Executing script at 43100000
  20. 0 bytes read in 365 ms (0 Bytes/s)
  21. 12927 bytes read in 1243 ms (9.8 KiB/s)
  22. ** ext4fs_devread read error - block
  23. ** Can't read partition table on 0:0 **
  24. ** Invalid partition 1 **
  25. ** Can't read partition table on 0:0 **
  26. ** Invalid partition 1 **
  27. Kernel image @ 0x46000000 [ 0x000000 - 0x49a760 ]
  28. ## Flattened Device Tree blob at 49000000
  29.    Booting using the fdt blob at 0x49000000
  30.    Using Device Tree in place at 49000000, end 4900627e

  31. Starting kernel ...

  32. Uncompressing Linux...
Copy the Code

...and it freezes here.

Compared to the same image copied to a 32GB sdcard:
  1. U-Boot 2016.03-rc2-armbian (Feb 25 2016 - 22:15:28 +0000) Allwinner Technology

  2. CPU:   Allwinner H3 (SUN8I)
  3. I2C:   ready
  4. DRAM:  1 GiB
  5. MMC:   SUNXI SD/MMC: 0
  6. *** Warning - bad CRC, using default environment

  7. In:    serial
  8. Out:   serial
  9. Err:   serial
  10. Net:   No ethernet found.
  11. starting USB...
  12. No controllers found
  13. Hit any key to stop autoboot:  0
  14. switch to partitions #0, OK
  15. mmc0 is current device
  16. Scanning mmc 0:1...
  17. Found U-Boot script /boot/boot.scr
  18. 2051 bytes read in 343 ms (4.9 KiB/s)
  19. ## Executing script at 43100000
  20. 0 bytes read in 262 ms (0 Bytes/s)
  21. 12927 bytes read in 862 ms (13.7 KiB/s)
  22. 4826976 bytes read in 5258 ms (896.5 KiB/s)
  23. Kernel image @ 0x46000000 [ 0x000000 - 0x49a760 ]
  24. ## Flattened Device Tree blob at 49000000
  25.    Booting using the fdt blob at 0x49000000
  26.    Using Device Tree in place at 49000000, end 4900627e

  27. Starting kernel ...

  28. Uncompressing Linux... done, booting the kernel.

  29. Debian GNU/Linux 8 orangepih3 ttyS0

  30. orangepih3 login:
Copy the Code


2

Threads

16

Posts

203

Credits

Intermediate member

Rank: 3Rank: 3

Credits
203
Post time 2016-2-26 17:31:07 | Show all posts
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:
  1. $ ping opi
  2. PING opi (192.168.5.6) 56(84) bytes of data.
  3. 64 bytes from opi.lan (192.168.5.6): icmp_seq=1 ttl=64 time=181 ms
  4. 64 bytes from opi.lan (192.168.5.6): icmp_seq=2 ttl=64 time=298 ms
  5. 64 bytes from opi.lan (192.168.5.6): icmp_seq=3 ttl=64 time=1.36 ms
  6. 64 bytes from opi.lan (192.168.5.6): icmp_seq=4 ttl=64 time=342 ms
  7. 64 bytes from opi.lan (192.168.5.6): icmp_seq=5 ttl=64 time=1.34 ms
  8. 64 bytes from opi.lan (192.168.5.6): icmp_seq=6 ttl=64 time=183 ms
  9. 64 bytes from opi.lan (192.168.5.6): icmp_seq=7 ttl=64 time=1.35 ms
  10. 64 bytes from opi.lan (192.168.5.6): icmp_seq=8 ttl=64 time=1.42 ms
  11. 64 bytes from opi.lan (192.168.5.6): icmp_seq=9 ttl=64 time=1.38 ms
  12. 64 bytes from opi.lan (192.168.5.6): icmp_seq=10 ttl=64 time=273 ms
  13. 64 bytes from opi.lan (192.168.5.6): icmp_seq=11 ttl=64 time=1.42 ms
  14. 64 bytes from opi.lan (192.168.5.6): icmp_seq=12 ttl=64 time=318 ms
  15. [...cut!...]
  16. --- opi ping statistics ---
  17. 132 packets transmitted, 132 received, 0% packet loss, time 131185ms
  18. <font color="#ff0000">rtt min/avg/max/mdev = 1.286/109.338/868.235/137.288 ms</font>
Copy the Code


Wifi disconnects from time to time, see syslog and dmesg:
  1. Feb 26 09:03:41 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
  2. Feb 26 09:13:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
  3. Feb 26 09:23:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
  4. Feb 26 09:33:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
  5. Feb 26 09:43:41 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
  6. Feb 26 09:53:41 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]
  7. Feb 26 10:03:40 opi wpa_supplicant[380]: wlan0: WPA: Group rekeying completed with 64:70:02:67:60:33 [GTK=TKIP]

  8. [Fri Feb 26 09:03:41 2016] RTL871X: send eapol packet
  9. [Fri Feb 26 09:03:41 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP
  10. [Fri Feb 26 09:13:40 2016] RTL871X: send eapol packet
  11. [Fri Feb 26 09:13:40 2016] RTL871X: set group key camid:6, addr:64:70:02:67:60:33, kid:2, type:TKIP
  12. [Fri Feb 26 09:23:40 2016] RTL871X: send eapol packet
  13. [Fri Feb 26 09:23:40 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP
  14. [Fri Feb 26 09:33:40 2016] RTL871X: send eapol packet
  15. [Fri Feb 26 09:33:40 2016] RTL871X: set group key camid:6, addr:64:70:02:67:60:33, kid:2, type:TKIP
  16. [Fri Feb 26 09:43:40 2016] RTL871X: send eapol packet
  17. [Fri Feb 26 09:43:40 2016] RTL871X: set group key camid:5, addr:64:70:02:67:60:33, kid:1, type:TKIP
  18. [Fri Feb 26 09:53:40 2016] RTL871X: send eapol packet
  19. [Fri Feb 26 09:53:40 2016] RTL871X: set group key camid:6, addr:64:70:02:67:60:33, kid:2, type:TKIP
  20. [Fri Feb 26 10:03:40 2016] RTL871X: send eapol packet
  21. [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 the Code


Some workaround is having network traffic, i.e. continous ping in screen. Then wifi is looks better I think:
  1. --- opi ping statistics ---
  2. 733 packets transmitted, 733 received, 0% packet loss, time 732988ms
  3. <font color="#2e8b57">rtt min/avg/max/mdev = 1.152/18.216/938.857/77.553 ms</font>
Copy the Code


9

Threads

632

Posts

4274

Credits

Moderator

Rank: 7Rank: 7Rank: 7

Credits
4274
 Author| Post time 2016-2-26 17:42:47 | Show all posts
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.
You have to log in before you can reply Login | Register

Points Rules

Archiver|Mobile edition|Darkroom|OrangePi En ( 粤ICP备14086627号-2

2020-6-3 19:57 GMT+8 , Processed in 0.032910 second(s), 20 queries .

Powered by Discuz! X3.2

© 2014-2015 orangepibbs en.

Quick Reply To Top Return to the list