I already know I can run a useful system but this WAS a hobby purchase. Yes, I did know that this might not be all plain sailing. The best I can do to help is to tweak some of the settings in /boot if I knew what to tweak. if fails, turn off power, remove SD, reboot, working system again. shutdown, remove power, insert SD, reboot. It is not too hard to do this as my working system is on the eMMC storage. So I guess I will stick to the upgraded but working system based on the 4.9 (yes, my memory got that wrong) kernel and I will touch base with the Armbian nightly regularly to see if the boot issue resolves. I am not a Linux kernel guru although I was once a moderate FreeBSD kernel tweaker. Turning boot flag on also did nothing, where nothing in all cases, means absolutely no action on the monitor & the LED (near the power input) that usually goes green on a working system, stays red. The only thing I can add is that the image when burnt to SD has no flags set. I do notice the contents of the /boot directory are noticeably different from the supplied Orange Pi images (ie no uboot stuff for instance). I have dd-ed (which has always worked for me) & even used etcher but no change. I have moved the functioning Ubuntu above to the eMMC storage and am now trying SD card images burnt from but they just will not boot.
#OPENELEC CPUINFO UPGRADE#
However the kernel is a uboot kernel and stuck at Linux 4.19 with an unknown upgrade cycle through the Orange Pi servers. There are tons of syslog error messages due to the well-known dev nature of the kernel but for my purposes, the basic functions work. I have installed the Orange Pi supplied Ubuntu image (version 16.04) & successfully upgraded it to version 18.04 (with a few hacks to make that process work). It is almost dead so I decided to test myself with an Orange Pi as a low power replacement. I use a 15 year-old laptop with an unusable display to run as a Linux test/training/utility machine. I have had a Raspberry Pi for 3 years now with no major issues.
0 kommentar(er)
