Active threads

@Werner I agree that it's more convenient for everyone, but it took me some time to find out how and testing it in an image. https://github.com/armbian/build/pull/8707/commits

I transferred it on two consoles using armbian-config. There were no problems.

Hi @Dominik Wójt, Thank you for your time looking into this. I was really stuck in a loop looking for solutions and this is the conclusion I also came to: The issue is with the kernel, not with DTBs, config, distro, monitor or anything else. I got the output to work on a regular image by installing "linux-image-edge-meson" but still no access to NAND and the device does not run smoothly. Best experience I've had was with an old image with kernel 3.10.108 which had everything working and running smoothly. I would like to try these patches you mentioned but unfortunately I don't have the knowledge on how to do so, then how to put this into armbian during the build process... I've now given up on this. Installed LibreELEC with and old kernel and donated the box away. Though I want to thank you again for your suggestions and for your help.

I will rename it from ../../devices/platform/i2c-display/i2c-6/6-0024/leds/display-controller to ../../devices/platform/i2c-display/i2c-6/6-0024/leds/display an try again........

Werner : thanks for you best effort, will try it as soon as im back home ,cheers

Laibsch, I was running bookworm, though I updated to trixie to see if that solved the issue. I applied the fix from the github issue. Fancontrol service is running on trixie now, though the fan is still at 100%. Georges, I did not post on the Odroid forum, since I'm running Armbian and I assume they won't be able to help us. Thank you both for your help!

there are many good works being done thos days by the community kernel.zip data for H96 Max RK3566 Box # lsmod | grep i2c tm16xx_i2c 12288 0 tm16xx 16384 1 tm16xx_i2c i2c_gpio 16384 0 i2c_algo_bit 12288 1 i2c_gpio # ls /sys/bus/i2c/devices/ 0-001c 0-0020 7-0024 i2c-0 i2c-6 i2c-7 # ls /sys/class/leds/display-controller brightness device map_seg7 max_brightness message num_chars power scroll_step_ms subsystem trigger uevent # ls -l /sys/class/leds/ total 0 lrwxrwxrwx 1 root root 0 out 3 10:06 display-controller -> ../../devices/platform/i2c-display/i2c-6/6-0024/leds/display-controller lrwxrwxrwx 1 root root 0 dez 31 1969 input1::capslock -> ../../devices/platform/fcc00000.usb/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:17EF:6099.0002/input/input1/input1::capslock lrwxrwxrwx 1 root root 0 dez 31 1969 input1::numlock -> ../../devices/platform/fcc00000.usb/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:17EF:6099.0002/input/input1/input1::numlock lrwxrwxrwx 1 root root 0 dez 31 1969 input1::scrolllock -> ../../devices/platform/fcc00000.usb/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:17EF:6099.0002/input/input1/input1::scrolllock lrwxrwxrwx 1 root root 0 dez 31 1969 led-power -> ../../devices/platform/leds/leds/led-power lrwxrwxrwx 1 root root 0 dez 31 1969 led-status -> ../../devices/platform/leds/leds/led-status lrwxrwxrwx 1 root root 0 dez 31 1969 mmc1:: -> ../../devices/platform/fe310000.mmc/leds/mmc1:: I will rename it from ../../devices/platform/i2c-display/i2c-6/6-0024/leds/display-controller to ../../devices/platform/i2c-display/i2c-6/6-0024/leds/display an try again........

I use Balena Etcher on my laptop running Linux Mint. It never let me down before. I understand balena Etcher on an Arm SBC is not recomended. Ernst-Jan

it's a headless unit, Werner. if i can't ssh in then i just use an older build.

I think this "unsupported version" thingy when doing initramfs update is just a cosmetical thing. The script comes from upstream and checks for version string included in upstream (directly from Raspberry to say) kernels. However I believe this has been worked around by our own bsp which is silently executed right after. Cannot tell for sure if that's the issue I remember it is since I don't have access to hw atm.

Basically you as heads-up for upcoming kernel bump in this branch and everyone else for attention getting this merged (or not)

Good evening all and thanks @Igor for the suggestions. I managed to connect to my Cubox-i4 from my laptop via USB with sudo picocom -b 115200 -r -l /dev/ttyUSB0 and now I have lots of messages, but no success with booting the Ubuntu 24.04 Noble minimal image. In particular, there is a complaint about a CRC error. I've attached the text generated by letting the boot process run for awhile. I decided to try the Bookworm minimal image, and I'm up and running right away with that. So I guess I will stick with Bookworm for now. If anyone generates a new Ubuntu 24.04 image they would like me to try, happy to give it a go. Or of course any other suggestions! booting_ubuntu_cubox-i.txt

@amazingfate Do you know if its possible to use tha latest mali blob with wayland and vulkan support (g24p0-wayland-gbm) and at the same time use the rkmpp on vendor 6.1.115? I got everything compiled and seemingly working but when I try to connect to a stream, all I see is black screen. This is with the moonlight-qt client and an orange pi 5 plus (rk3588)

Having the same issue however your solution doesn't seem to work for me for whatever reason.

With the errant icon, yeah that kind of thing can be really frustrating with linux design. I'm not that deeply familiar with it. Usually when I experience something like that, I look it up in a search engine. What I can say is that many settings are stored in hidden directories under the user home folder. Hidden files start with a period. Go to your home directory: ls -la ...but which one to explore and what to look for... You'll probably find what you're looking for with a search engine. And on your rant, yes I've sensed our views of the computing world to be similar as well. Punching holes in cards - yes! You really would have to think and get it right the first time. And it's not so hard to do. You set the standard, practice it and make it a habit. My second computer was a Commodore 64, back in the early-mid '80s. I played lots of games on there. Even though I'd started programming in BASIC before that, I learned more to program on that computer, in BASIC, and in assembly language. I experienced from others' software and what I could do on my own, to be resourceful, and that creating software that is highly functional and can do "a lot" really doesn't require much more than a tiny program. There's no excuse for complicated software. Also others and myself created it right the first time without any "patches" or "software updates" BS - once it was done, it was done right! I almost never encountered bugs from others' software on my C64. I think there was one game than had bugs in it - that's it, it was an outlier. But that computer, you'd turn it on and get the prompt within maybe 200ms. There was no "boot up" BS. And its user interface is always immediately responsive. It was never sluggish. My first experience with the extremeness of bloating was with my first x86 PC around 1991 i think. It ran MS-DOS 5.0, which took up around 7 or 8 MB as I recall, on the hard drive (or was that Windows 3.1?). And to create an assembly language program that was just a "hello world", an executable .com of that would be around 30 bytes or so, but an executable .exe was around 784K or something crazy like that. 99% of that was .exe format overhead junk! And for today's operating systems and their functionality, there really is no excuse why the total size of the complete operating system on the hard drive should exceed a megabyte (or half that), let alone several gigabytes. The bloating of today is so far beyond reason it's way off in another galaxy. A minimum of 10,000 to 1. So much software today is based on scripting languages and run-time interpreters. Plus the linux operating system was originally designed back in the 1960s!!! ...as unix, before it was ported to personal computers as linux. Apparently, they've got layer upon layer upon layer of patches and changes and different ideas and outdated models all enmeshed in a galactic-sized mess. I've also seen how the MB, GB, and TB have been hijacked by a crooked industry which has redefined those terms to be powers of 1000 rather than the truth that they're powers of 1024. Even with that, the amount delivered on memory and storage devices, in may cases, falls short even of that crooked re-definition. Now an actual GB or MB is called "GiB" or "MiB", while what is often now called a MB or GB is a bold-faced lie! What the computer hardware and OS development needs is to throw away the existing model and create a new one from scratch. As a software engineer, I have done that numerous times on my own projects, and the result is always a spectacular improvement because I can apply what I learned from the previous iteration in developing the new foundation. And that's always a simple, creative and enjoyable process. It does take a some time to do, but the results are more than worth it, and the resulting accelerated pace of development later more than makes up for it. The Orange PI 5 Plus is my first ARM board. What I'm more looking forward to though is getting into RISC-V. I'm not to familiar with it yet, but It's completely open and apparently values simplicity. That might be a really great development environment for something genuinely new.

@Faheem328 Do you have free time? how much free time do you have exactly? we are looking for someone like you with a RK3528 box we are depending on him finding a weekend to dedicate to the community https://github.com/ilyakurdyukov/rk3528-tvbox he will help us by taking this repository and including it in armbian with a wonderful pull request let's talk?

@rockamal maybe you’ll have better luck with x96q lpddr3 https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build pico patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch Change @@ -0,0 +1,191 @@ to @@ -0,0 +1,192 @@ add this to the bottom of the patch "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" Then you need to include the secure boot patch. pico patch/u-boot/u-boot-h616/secure-boot.patch create the secure boot patch. you can find it here.

sorry for the delay, @mvpwar for RK3566 NPU you can use the original armbian DTB that enables NPU support: https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr5.1/arch/arm64/boot/dts/rockchip/rk3566-h96max-v56.dts I think you will take fragments from ancient builds like this: https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/16/#findComment-211031 I don't know what the status is in version 6.17 but we are still required to use vendor 6.1

Thank you for that additional information, Igor. The lack of desktop images is only a minor inconvenience, I'd say. Easy enough to install the required packages after installation of the base image to the SBC itself.

HW (features are determined by kernel used in the image) related issues are shared among all variants, desktop, cli, minimal, Debian or Ubuntu.

@Fredrik thank you for the reply. I wonder what's Gnome doing to initialize the audio that's different from a regular (non-graphical) boot. FWIW I installed also Pipewire/Wireplumber and tried to test the audio through the PW ALSA emulation, but that didn't work either. Just out of curiosity, does speaker-test work from the CLI once booted into Gnome or is it just the sound test in Gnome settings that's working ?

I troubleshooted my problem! So for some reason (I'm not sure if this is for all x88 pro 10's), the SD card needed to be under pressure on it to read Multitool. So, throughout the entire Multitool process, I needed to hold down the SD card with my thumb. I did hurt a bit, but it flashed to the EMMC

I retried that image now but with a different installation method, booting into OOWOW (?) via the Function+Reset button, control via serial debug console. I then wget the image from my local server and dd out to /dev/mmcblock0. Subsequent boot was indeed successful.

The three holes could be access to a serial console if necessary. Ground Transmit Receive. If you want to try this, baudrate is most likely 115200 like all Allwinner SoCs.

the current filogic kernel has no info [in github] for where it was forked from, and trying to apply incremental patches from kernel.org I found it contains pieces of 6.14 in an ostensibly 6.12 branch. @chainsx might you be able to divulge where you forked it from?