caro3 Posted February 10, 2018 Posted February 10, 2018 (edited) Hello, I installed the Ubuntu desktop image from: https://www.armbian.com/orange-pi-pc/ to the SD Card with: sudo dd bs=4M if=Armbian_5.38_Orangepipc_Ubuntu_xenial_default_3.4.113_desktop.img of=/dev/sdb conv=fsync The orange pi does not boot, it took some time and the red LED is flashing on the top side and the screen is black. Maybe I did something wrong? Regards, caro Edited February 10, 2018 by caro3
guidol Posted February 10, 2018 Posted February 10, 2018 2 hours ago, caro3 said: The orange pi does not boot, it took some time and the red LED is flashing on the top side and the screen is black. Maybe I did something wrong? normally a blinking led should show that the system has bootet (heartbeat led). Maybe you could try to use etcher for Linux or Windows to create the bootable sd-card?https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card 1
caro3 Posted February 10, 2018 Author Posted February 10, 2018 OK, i tried again and it seems that armbian starts booting, after "Starting Kernel ..." screen turns black.
Igor Posted February 10, 2018 Posted February 10, 2018 35 minutes ago, caro3 said: OK, i tried again and it seems that armbian starts booting, after "Starting Kernel ..." screen turns black. A stock display settings are set to 720p and if you have some extraordinary display, you need to login via serial or network and then use h3disp utility to set correct one, but first ... strictly follow procedures written in Getting started. SD card and power problems are very common and their symptoms can also show this way. Make sure you use Etcher for writing or check what you write. DD doesn't check and SD media is can be crap. Wait a minute and you should see a login prompt. You need to create a normal username if you want to run a desktop. When you do those things, desktop starts automatically. 1
caro3 Posted February 10, 2018 Author Posted February 10, 2018 This time, I copied the sd-card with etcher, so the sd should be fine and verified. The display is not extraordinary, I tried with two different screens, but both are using a HDMI -> DVI cable. Found these examples, I can try it later.
Igor Posted February 10, 2018 Posted February 10, 2018 48 minutes ago, caro3 said: The display is not extraordinary, I tried with two different screens, but both are using a HDMI -> DVI cable. If you have a DHCP powered network, you should get an IP and login via SSH. Does that work or you are not getting there? Edit: image you downloaded, boots fine: http://ix.io/FCI (my board is PC+ since I don't have a normal one, which is identical. It only lacks eMMC and wifi)
caro3 Posted February 11, 2018 Author Posted February 11, 2018 Quote shasum -a 256 -c sha256sum.sha Armbian_*.img Armbian_5.38_Orangepipc_Ubuntu_xenial_default_3.4.113_desktop.img: OK shasum: src/gcc-4.7.1.tar.bz2: src/gcc-4.7.1.tar.bz2: FAILED open or read shasum: src/newlib-1.20.0.tar.gz: No such file or directory src/newlib-1.20.0.tar.gz: FAILED open or read ^C why are errors coming during image verification? I managed to boot on the FullHD screen with h3disp -m 1080p60 -d but on the HD ready screen, it is stuck on a pink or black screen with h3disp -m 720p60 -d Maybe somehow incompatible?
guidol Posted February 12, 2018 Posted February 12, 2018 23 hours ago, caro3 said: but on the HD ready screen, it is stuck on a pink or black screen with h3disp -m 720p60 -d Maybe somehow incompatible? how about (if possible) with -d for HDMI2DVI-adapter: 576p use "-m 576p" or "-m 3" 720p50 use "-m 720p50" or "-m 4" or 'h3disp -m 720i' (1280x720@30Hz HDMI) see:
caro3 Posted February 12, 2018 Author Posted February 12, 2018 I already tried a few of these settings yesterday. Anyway is is now working with Quote h3disp -m 4 -d Sometimes after changing the screen settings, the pi wasn't rebooting after "reboot" and unreachable via network. Maybe I need to keep track of this.
Recommended Posts