Avatar Ng
Members
-
Joined
-
Last visited
-
Inspired by Bazzite OS, and remind me of experience on Armbian (not just armbian), basically on Orange PI 5/ OPI5+, it'll be solid OS if update failure/ anything went wrong can rollback to previous safe copy. Pain-point: I just want to use the system, not keep re-flashing OS. nixOS is good, but I don't want to re-learn everything ... and giving up my Ubuntu eco-system. Sorry I'm still testing out, and failing with existing Armbian-Config approach, I'm trying my own appraoch, Iknew the rules here, wait until I success I'll share it here. (note: or anyone did it before, can give me some direction) Inspired by Bazzite OS, and remind me of experience on Armbian (not just armbian), basically on Orange PI 5/ OPI5+, it'll be solid OS if update failure/ anything went wrong can rollback to previous safe copy. Pain-point: I just want to use the system, not keep re-flashing OS. nixOS is good, but I don't want to re-learn everything ... and giving up my Ubuntu eco-system.
-
Created another standalone version of script for this ... https://gist.github.com/avatar21/e0deca347665bd620d0ea3f9f299028e I believe we need to compile our own armbian/ Kernel 6.13 (or above? because as @elvis claimed user driver is only 1/2 of the equation) before running this script ya? all copy/ flatten to a temp/fake root folder (where I understand the chroot sdcard means, build to a fakeroot not patching existing OS) and repackage as an img file ya? Or better still, can someone compile the whole thing? start from burning image ... Correct me if I’m wrong…
-
-
I'll give it a try, here you go ... https://paste.armbian.com/waqaquzihu (the debug log) Booting no hdmi display support, SSH is working fine. And something just for fun ~$ vulkaninfo Cannot create Vulkan instance. This problem is often caused by a faulty installation of the Vulkan driver or attempting to use a GPU that does not support Vulkan. ERROR at ./vulkaninfo/vulkaninfo.h:649:vkCreateInstance failed with ERROR_INCOMPATIBLE_DRIVER
-
Yeah, don't know what Tencent is thinking, I don't like the experience at all, I reason I bought it simply because it's the most affordable and available hardware around at that point of time. I never notice this one coming --"RK3576", I'll keep my eye on this, thanks for sharing this, very interesting.
-
@Szymon_Zy the way it works is you create a new thread in the "TVBox section" (refer to Fig. 1.1.) of this forum, named "H96 max" and "v58" separately (if they do not already exist), you may cross-reference each other. References: - Figure 1.1. https://forum.armbian.com/forum/24-tv-boxes/
-
Tried to flash it with common Rockchip Box technique with no luck (tried some roms from Armbian, firefly, and some OpenWRT method ... refer Fig. 1.5, 1.6). Anyone who can give some pointer will be much appreciate. Known techniques: - enter recovery mode = plug in the HDMI, use screw driver to poke the inner "hidden button" in audio jack, and plug power - working - another way of getting into the recovery mode = using the command "adb reboot recovery" from either network or USB type C - not able to flash - enter bootloader mode = using the command "adb reboot bootloader" from either network or USB type C - don't know how this work - enter mask rom mode = plugin the HDMI, use screw driver to poke the inner "hidden button" in audio jack, and plug USB mal-to-male cable to PC - not working - another way, is only accesible via old fashion tty usb through the TX, RX, GND pins (top right of Fig 1.3.), need to open up the box and do some soldering, to directly read and command from the system. References: - Figure 1.1. - Figure 1.2. - Figure 1.3. - Figure 1.4. - Figure 1.5. official rockchip Wiki: https://opensource.rock-chips.com/wiki_Boot_option - Figure 1.6. OpenWrt Wiki: https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R6S
