Drakoh

As the title says, my OpiPC don't want to boot. It starts to boot, with UART console I can see u-boot loading and doing its job, but just when it would start the kernel the console gets borked with non-ascii characters. After this, the board just hangs there. I've tested with 3 different images (written out by Etcher), checked the images checksum and checked the SDcard with F3. This setup worked fine a month ago, when I last had the time to play with it. Since than, the board was just lying on my desk, turned off.

Thanks, this was the missing piece. After this I managed to play around with SELinux, but sadly, its support on Jessie is pretty much lacking, but there is hope it will be better in Stretch.

Sorry for necroing, but I've just had time to tinker with MAC. AppArmor seems to be working with @davidahoward 's options, although I'm more interested in SELinux. I've built the kernel with these options: root@orangepipc:~# grep -i selinux /boot/config-4.10.3-sun8i CONFIG_SECURITY_SELINUX=y CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1 # CONFIG_SECURITY_SELINUX_DISABLE is not set CONFIG_SECURITY_SELINUX_DEVELOP=y CONFIG_SECURITY_SELINUX_AVC_STATS=y CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=0 CONFIG_DEFAULT_SECURITY_SELINUX=y CONFIG_DEFAULT_SECURITY="selinux" root@orangepipc:~# Despite this, selinux is not running: root@orangepipc:~# check-selinux-installation ../proc/1 kernel.. SELinux is not enabled. The init process (PID 1) is running in an incorrect domain. Old style ttys were found. FSCKFIX is not enabled - not serious, but could prevent system from booting... root@orangepipc:~# sestatus SELinux status: disabled root@orangepipc:~# What I'd like to do is to pass the "selinux=1 security=selinux" options to the kernel, but since I'm noob to u-boot and arm in general, I don't know how to do it. I've tried adding them ot /boot/armbianEnv.txt, but it doesn't make any difference, so I'm sure I'm missing something. Here are the current kernel options: root@orangepipc:~# cat /proc/cmdline root=UUID=7bf2e6bb-0bd8-4e0e-9f25-72f2b9788556 rootwait rootfstype=ext4 console=tty1 console=ttyS0,115200 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=d8287bc5-01 ubootsource=mmc sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 root@orangepipc:~# Any idea/comment is appreciated.

@cpwtech you can always create an Ubuntu 16.04 VM with KVM or VirtualBox. From there, the build script will do all the hard work. 4.10 runs happily on my OpiPC.

You'll need mainline kernel for that. Luckily, it can be easily build using the Armbian build tool: https://docs.armbian.com/Developer-Guide_Build-Preparation/ Once you're done with that, you can install Docker from the official ARM Debian Jessie repo: https://apt.dockerproject.org/repo/dists/debian-jessie/ That's it.

I'm running 4.9 on my OpiPC (the original one, without emmc) and it boots/works without hdmi attached. I've built the image on Dec. 19. and as I can see, megous pushed some changes to the kernel repo in the meantime, some even related to hdmi. link But then again, Igor's build contains all this newer stuff, so it shouldn't cause trouble.

Some kind of MAC (either AppArmor or SELinux) would be great. I was thinking about trying to make SELinux work, but haven't found the time for messing around with it and my board is in "prod" anyway.

@martinayotte: from whose source if I may ask? megous' 4.9 branch or montjoie's sun8i-emac-wip-v5?

Keep in mind, that 4.9 is till in work-in-progress state. My OpiPC runs on megous' 4.7 kernel for some time now and the ethernet works fine. The last time I tried 4.9, it doesn't even booted, but it was back around rc2. In the meantime, he also updated/switched the ethernet driver to montjoie's one, which is also a "wip" source tree. As you can see, a lot of "work-in-progress" code is present in the currently available 4.9 kernels, so some breakage can be expected. I'll test the 4.9 kernel once Linus decides it is stable enough and after the sunxi guys do their magic to patch it for my Opi.

So you want to change the display resolution. I'm using Armbian without GUI so I can't help you much, but the H3-based board have a utility called h3disp. From the documentation: # Example to set resolution to 1920 x 1080, full colour-range and DVI h3disp -m 1080p60 -d -c 1

Hi there. Could you please describe you problem as much as you can? How did you burn the image to the sdcard? Do you have console access to your board? Normally you wouldn't have to press anything. Burn the image to the sdcard, boot from it, log in via SSH.

@zador.blood.stained thanks for the fast feedback.

Could you please upload your image (or at least the 4.9 kernel) somewhere? The build issue has been solved by a cleanup as you suggested with zador.blood.stained, but the 4.9 kernel just doesn't want to work for me. I've build both the 4.9 and the 4.9-hdmi branch, tried with Armbian 5.21 and 5.23 but the boot always stops at this line: <... everything is fine until here, no error, etc ...> Starting Copy rules generated while the root was ro... Starting LSB: Set preliminary keymap... Starting LSB: Tune IDE hard disks... [ OK ] Started Copy rules generated while the root was ro. [ OK ] Started LSB: Tune IDE hard disks. <... after this point, it just hangs ...>

Does the opipc image with 4.9-hdmi still builds for you? I got these errors: [ o.k. ] Creating board support package [ orangepipc dev ] [ .... ] Fingerprinting [ o.k. ] Building package [ linux-jessie-root-dev-orangepipc ] [ o.k. ] Starting rootfs and image building process for [ orangepipc jessie ] rm: cannot remove '/home/drakoh/armbian/output/cache/sdcard/tmp/debs': Device or resource busy [ o.k. ] Extracting jessie-ng-armhf.e52...1d9.tgz [ 0 days old ] jessie-ng-armhf.e52...1d9.tgz: 91.4MiB [4.68MiB/s] [===========================================================================================>] 100% [ o.k. ] Applying distribution specific tweaks for [ jessie ] sed: can't read /home/drakoh/armbian/output/cache/sdcard/etc/ssh/sshd_config: No such file or directory [ o.k. ] Applying common tweaks sed: can't read /home/drakoh/armbian/output/cache/sdcard/etc/default/console-setup: No such file or directory [ o.k. ] Installing kernel [ linux-image-dev-sun8i ] [ o.k. ] Installing u-boot [ linux-u-boot-dev-orangepipc ] [ o.k. ] Installing headers [ linux-headers-dev-sun8i ] [ o.k. ] Installing board support package [ orangepipc ] sed: can't read /home/drakoh/armbian/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory sed: can't read /home/drakoh/armbian/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory sed: can't read /home/drakoh/armbian/output/cache/sdcard/etc/lirc/hardware.conf: No such file or directory cp: cannot create regular file '/home/drakoh/armbian/output/cache/sdcard/etc/lirc/lircd.conf': No such file or directory [ o.k. ] Installing extra applications and drivers [ o.k. ] Merging and packaging linux firmware [ @host ] [ o.k. ] Merging and packaging linux firmware [ @host ] [ o.k. ] Checking git sources [ armbian-firmware-full/lib/firmware master ] [ .... ] Creating local copy [ .... ] Fetching updates remote: Counting objects: 1420, done. remote: Compressing objects: 100% (963/963), done. remote: Total 1420 (delta 436), reused 1345 (delta 401) Receiving objects: 100% (1420/1420), 68.00 MiB | 402.00 KiB/s, done. Resolving deltas: 100% (436/436), done. From https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware * branch master -> FETCH_HEAD * [new branch] master -> origin/master [ .... ] Checking out [ o.k. ] Installing linux firmware [ 5.23 ] [ o.k. ] Building deb [ armbian-tools ] [ o.k. ] ... downloading sources [ temper ] [ o.k. ] ... downloading sources [ BT utils ] [ o.k. ] ... compiling [ temper ] [ error ] ERROR in function compiling [ tools.sh:70 ] [ error ] Error building [ temper ] [ o.k. ] Process terminated rm: cannot remove '/home/drakoh/armbian/output/cache/sdcard/tmp/debs': Device or resource busy [ error ] ERROR in function unmount_on_exit [ debootstrap-ng.sh:569 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated

Thanks for testing it out. Now I definitely give it a spin tomorrow. Maybe the bug that causes the panic with containerized torrent client is fixed. But obviously it is a pretty niche use-case, so I won't hold my breath.

Thanks for the heads-up, I've checked the changelog, but failed to notice it. : / This was my plan for tomorrow, guess I go ahead with it then.

I've seen the updates in the repo, but after an apt-get update and reboot my OpiPC doesn't boot. I've built an image from the latest sources (Armbian_5.23_Orangepipc_Debian_jessie_4.8.3.img) but still no dice. Reflashed the previous image (Armbian_5.21_Orangepipc_Debian_jessie_4.7.6.img), the one from which I tried to update at first and it booted successfully. Does anybody else experiences this?

I'd like to add another method which I found "cleaner" and "easier". Debian provides an easy way to set sysfs values after reboot via the /etc/sysfs.conf file and the /etc/sysfs.d/ directory. (This is basically the same as the relation between the /proc/sys and sysctl.conf and sysctl.d.) My use-case: I wanted to set the red light on my OpiPC to the heartbeat effect. This can be set manually with: # echo heartbeat > /sys/class/leds/orangepi\:red\:status/trigger The sysfs files format is really simple: # the path omits the /sys/ path/to/the/settings = value So all I had to do was: # echo "class/leds/orangepi\:red\:status/trigger = heartbeat" > /etc/sysfs.d/red_led.conf One can modify the sysfs.conf itself, but it's more pluggable/manageable via .conf files under the sysfs.d directory.

At this point my only advice is a faster sdcard. Your other option would be a to seriously hack Armbian or build your own distro, but these are obviously not "noob-friendly" options. Maybe somebody else can help you out more.

AFAIK, with these settings systemd starts your service as soon as it can. One thing I still don't get is, you said you use your orangepi as a server, how often do you reboot your server?

After the kernel, a lot of things have to be started in order to get a system on which applications can run. How do you start the service now?

Systemd starts services in parallel as soon as they can be started. What exactly are you trying to achieve?

After u-boot loads the kernel, it boots under 2 sec, I don't see much stuff in there that you should disable., it's pretty lean as it is. How often do you reboot it anyway? Even if you reboot it everyday for some reason, saving 1sec wouldn't gain too much. Anyway, the faster the sdcard, the faster the OS can boot.

iSCSI?

If you mount the remote filesystem under /var/lib/docker than everything docker-related (images,containers,networks,etc) will be on your NAS.