Active threads

Couple of data points that may be helpful. Platform: BTT PI v1.2 D/C 2023.11.8 with the U2C CAN board Distro: Armbian 25.8.1 Bookworm Kernel: 6.12.43-current-sunxi64 Overlays: spidev0_0 1. Adding a sleep 5 hack did not work for me, however what does *seem* to work is inserting the following line to /etc/netplan/30-wifis-dhcp.yaml activation-mode: manual WiFi was still activated (which may be another bug) for at least 3 cold boots in a row (didn't have time to test more thoroughly). Here's a pastebin link from right after one such boot - https://paste.armbian.com/umijapukiy 2. The error from wpa_supplicant is CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 .Same error code (-1) is also reported when attempting a manual scan pi@jubilee:~$ sudo iw wlan1 scan command failed: Operation not permitted (-1) 3. Broken state of the WiFi driver seems to be correlated with mmc errors in dmesg [ 11.490708] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.490745] sunxi-mmc 4021000.mmc: send stop command failed [ 11.490856] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.490880] sunxi-mmc 4021000.mmc: send stop command failed [ 11.491071] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.491098] sunxi-mmc 4021000.mmc: send stop command failed [ 11.491224] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.491248] sunxi-mmc 4021000.mmc: send stop command failed These are not present if wifi was activated successfully. Here's a pastebin link from right after such boot - https://paste.armbian.com/xovixuniti I did run F3 on that SD card before installation so I doubt it's at fault, but I am currently running another test with armbianmonitor -c overnight just to be sure. 3. Reloading the kernel driver (8189fs) when it is already in a broken state is very slow and provokes a slew of mmc errors $ sudo /sbin/rmmod 8189fs pi@jubilee:~$ time sudo /sbin/modprobe 8189fs real 2m15.835s user 0m0.008s sys 0m0.048s $ dmesg .... [ 673.262192] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262286] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262379] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262471] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262563] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262656] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262716] ====>_BlockWrite 101 i:0 [ 673.262742] ====>_WriteFW 230 [ 673.263001] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.263088] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.263141] ====>_BlockWrite 101 i:0 [ 673.263162] ====>_WriteFW 230 Again the same problem is not present if WiFi was activated successfully after boot: Shutting down the interface and reloading the driver works just fine. Please let me know if there's anything else I can collect that can help to track this down. Given this is a fresh install and has no personal data in it yet, I can share my SD card image if that would be helpful.

What do you mean by that? You mean LCD screen on the device and HDMI monitor. This should probably work OOB on vendor 6.1.y kernel. It should also work with mainline, but I haven't tested that and I am not sure that this is included in latest stable build as it was added not long ago. Try build from sources, use EDGE kernel perhaps. It is very specific case - probably nobody asked for that before. At least I don't recall. Core features are based on SoC, so when you are looking for clues, look wider - Orange 5 *, Khadas Edge 2, Bananapi M7, ... all that carries RK3588 SoC. Best is to start with recommended Gnome image. That is most polished.

"*** Warning - bad CRC, using default environment" This is safe to ignore. It is strange why Ubuntu doesn't work, while Bookworm does. This could be some build infrastructure issue. https://docs.armbian.com/Developer-Guide_Build-Preparation/

Welcome to Armbian, I'm your emotional support, I'll give you all the support if you want to start developing a custom firmware for this device, we have all the time in the world, one day this will be ready and we will put your name on it, it will be cool, I believe you have the ability to start volunteering, get in touch

for Pi-Hole i'm using: "cbcrowe/pihole-unbound" https://hub.docker.com/r/cbcrowe/pihole-unbound For docker Containers I'm on Casa-OS curl -fsSL https://get.casaos.io | sudo bash pihole-unbound.yaml

for thoses who want to install sd to emmc, use this script (remove the line about haos near the end)

What you are reporting is quite common with tv boxes. The case markings often are different than the internals. What is it you are looking for? Your post didn't really ask for anything other than to report that you got a common tv box with internals that differ from the case.

No, i gave up compiling on Armbian, i installed the debian bookworm server image provided by orangepi instead

I was having some pretty substantial problems with several different builds before developing this hold pattern, Werner

moved. All boards using rk3588/s soc most likely work best with either vendor or edge kernel. Current has limited functionality since when this kernel became LTS only basic support was there. All further enhancements regarding hardware featureless were upstreamed later.

Yep... that looks like the method I had thought about: get the source from https://github.com/philipl/mpv.git#branch=v4l2request and compile it with the v4l2request option I have old experience making redhat rpms, but I need to learn how to make debian debs

Are there any chances to enable i2c? I use the tv-box as a 3d printing server (klipper) openvfb is working fine, and I also managed to configure the G-Code Shell Command to display the remaining print time. I want to connect the g-sensor via the i2c bus, please tell me if possible. klipper@transpeed-8k618-t:~$ dmesg | grep i2c [ 1.374462] mv64xxx_i2c 5002c00.i2c: can't get pinctrl, bus recovery not supported [ 1.683314] axp20x-i2c 2-0036: AXP20x variant AXP313a found [ 1.683791] axp20x-i2c 2-0036: AXP20X driver loaded klipper@transpeed-8k618-t:~$ sudo /sbin/i2cdetect -l klipper@transpeed-8k618-t:~$

Now the issue is it doesn't want to boot from SD (eMMC unplugged). I bought a brand new µSD as a last resort but nothing. I get a fast double blink on the status LED. Tried Armbian_community_25.5.0-trunk.131_Rockpi-4a_bookworm_current_6.12.16_minimal and Armbian_community_25.11.0-trunk.273_Rockpi-4a_trixie_current_6.12.49_minimal. Where can I find old Armbian-supported builds ? Because I'm sure those work. I'll try the last supported build and report. (can't delete this post)

It sounds like you're much more familiar with Linux than I am... especially on a deep level. It does have its strengths. I am grateful that it's a working alternative to anything from Microsoft or Apple. But I'm a firm believer that whether hardware or software (or any kind of design), simpler is better. Complication only arises from lack of clarity and understanding. One of the hallmarks of a good operating system is to provide complete support and essentially get itself out of the way - to make the computer an immediately usable tool for what you intend to use it for.... to be a clear conduit for that intention.

@Totof le Belge Is there any chance you could give an in-depth explanation of the user-overlay script? I'm trying to use a speaker that uses I2S with the GPIO pins.

@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

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.

@guenter Test Image: Armbian-unofficial_25.11.0-trunk_H96-tvbox-3566_bookworm_edge_6.16.10_gnome_desktop.xz data for H96 Max RK3566 Box: No external drivers, no external app, just pure mainline..... https://github.com/armbian/build/pull/8708

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: No external drivers, no external app, just pure mainline..... https://github.com/armbian/build/pull/8708 # 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 brightness device map_seg7 max_brightness message num_chars power scroll_step_ms subsystem trigger uevent # ls -l /sys/class/leds/ lrwxrwxrwx 1 root root 0 out 3 14:29 display -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display lrwxrwxrwx 1 root root 0 out 3 14:29 display::alarm -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::alarm lrwxrwxrwx 1 root root 0 out 3 14:29 display::colon -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::colon lrwxrwxrwx 1 root root 0 out 3 14:29 display::lan -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::lan lrwxrwxrwx 1 root root 0 out 3 14:29 display::pause -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::pause lrwxrwxrwx 1 root root 0 out 3 14:29 display::play -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::play lrwxrwxrwx 1 root root 0 out 3 14:29 display::usb -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::usb lrwxrwxrwx 1 root root 0 out 3 14:29 display::wlan -> ../../devices/platform/i2c-aux-display/i2c-7/7-0024/leds/display::wlan lrwxrwxrwx 1 root root 0 out 3 14:29 input3::capslock -> ../../devices/platform/fd000000.usb/xhci-hcd.1.auto/usb2/2-1/2-1:1.0/0003:17EF:6099.0002/input/input3/input3::capslock lrwxrwxrwx 1 root root 0 out 3 14:29 input3::numlock -> ../../devices/platform/fd000000.usb/xhci-hcd.1.auto/usb2/2-1/2-1:1.0/0003:17EF:6099.0002/input/input3/input3::numlock lrwxrwxrwx 1 root root 0 out 3 14:29 input3::scrolllock -> ../../devices/platform/fd000000.usb/xhci-hcd.1.auto/usb2/2-1/2-1:1.0/0003:17EF:6099.0002/input/input3/input3::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 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.

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

@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)