Active threads

Hello, My pet labubu and I got the most recent onecloud/odroid c1 versions fully working on my horrid former Oriental TV box, the TVPad 4 (previously brought up by user @daniyo). Everything works perfectly, except I want to finish my building by installing to eMMC. None of the recent builds I can find come with an install.sh script, and I cannot see the eMMC (or NAND if it's NAND) in lsblk or any of the installers. Does anyone have any clues or suggestions that can help the poor long suffering Labubu fix this issue? He just wants to watch IPTV and play little games

I was extremely excited to read this. My issue currently is that I'm dealing with S805 and H3 builds which had builds dominated by the megalomaniacal user whose name starts with "B" (really not a fan of their behavior but extremely impressive work). For some reason, these builds never come with the install.sh scripts that Amlogic builds normally come with, and I can only write S805 builds to eMMC using builds with the 5.7/3.10 kernel to eMMC because they come with an install.sh. I really want to "finish" the builds by writing them. I'm hoping to use dd to write to the eMMC but it doesn't come up with lsblk at all (except with the 3.10 kernel). Does anyone have any suggestions about how to get around this?

I agree, it would be a small adjustment that is hopefully easy. I don't know how to do it myself but the inbuilt eMMC is definitely not big enough for the kind of files I want to serve from the board. And I apologize, I didn't realize that random people can upload builds like that; I meant that it appeared to be a listed frequently updated board.

Are you twwn on github, @tast ky? As mentioned in the bug tracker, you need to try a different image. Please keep the discussion of run-time issues in the forum. This is where run-time bug triage happens. Until the time one can essentially make a PR with a clear code fix, the forum is where we discuss run-time problems.

Not a problem. Just please do not give up I have 5 units of those waiting for a newer kernel LoL

I'd say try flashing again with a different image, possibly one that worked in one of your other boards. Verify the download and the flash process with checksums.

Yes, your list of questions is a bit long (understatement) and as such comes off demanding. I would say armbian or an SBC is not for you if you require a great amount of handholding and that's the vibe I am getting from your laundry list of questions for everything under the sun. I guess you want to be thorough before taking the plunge, but you need to take armbian with a different attitude, I guess; be happy when it runs, get down to help fixing it when it doesn't. We are NOT selling you a product.

You are running with a broken firmware: Your version is also quite outdated: A current firmware log looks like this:

please provide the output of "apt policy armbian-bsp-cli-rock-5b" and "sudo cat /etc/apt/preferences.d/*"

Chromium is not the best for playing videos. Try mplayer or mpv or something alike. I doubt you'll get great performance beyond 720p though. Might not even get it in some cases with 720p? If I wanna use an SBC as a media player, I either use LibreELEC or CoreELEC and don't use Alllwinner, but Amlogic. Good luck.

If you can still return the item for a refund, go ahead and do so. If you can still leave a bad review for this bad seller, go ahead and do so. This person has quite the gall to take your money but send you to us for the costly support. Buy cheap, buy twice.

Hello and welcome to the Armbian community. I have a Banana Pi M2+ that I use as a small 24/7 home server.

I am not entirely sure if those sensors are always accurate. In the case of my BPi M2+, I have some serious doubts.

I have not personally modified armbianEnv.txt, I do not know how to. As I say I think the machine has been messed around with, i.e. it has been hacked.As I say I am trying to work out how to reenable /dev/mmcblk1.

Weird its doing it on all distros and builds have tried so far including Debian. I can only think it must be the boards firmware ?

I would try the cma=256M argument anyway... this kernel argument eliminated my video glitches and dma errors. I don't know how a dtsi or dtbo parameter (loaded after linux is started) would override a kernel argument (given before the linux kernel is started).

It exists and has been working for a long time , why does someone change it while it does't hinder you? Who changed it , and who should rollback, yes, we're community. Thank you.

moved

https://docs.armbian.com/User-Guide_Autoconfig/

You're right - the dtb is gxbb-p200. However, actual RAM is 1 GB total. Booting Emuelec 4.3 will show you that info. But that particular game-stick does not have an Android boot-loader so maybe that's why Armbian is unable to boot. 🤔

Well other option is the upstream broke somehow. KDE neon is based on their testing branch so if there is a faulty package uploaded desktop breaks. Though we won't dive into this since KDE is no officially supported desktop environment by us. We mostly do GNOME and XFCE only. We don't have resources to deal with more while we wish we would/could.

Hello, I have a NanoPi R6S and have just attempted the presented adjustment on my Armbian Install but it looks like udev fails to rename the interfaces at boot due to the fact that the kernel is doing that before ? I don't really have a lot of experience here but becaus of this the NetworkManager vlan mapping and IP addresses get mangled up thus resulting in my device not working as intended. Could there be something that I am doing wrong ?

I didn't have that much time to look at my Orange Pi board. On work, i have to deal with similar issues, but regarding another Soc (imx8mp with vivante GPU). But on work i have support from other people / offices. Meanwhile the grafik looks like to work, but also with lot of kernel patches and fixing involved (we have a yocto based build, and even Qt is somehow patched to work with our yocto base, wtf) on my orange pi board testet out some kernels. tried the official debian / ubuntu kernels (from orangepi.org) the version 5.10 kernels versions are booting (from sd) but no Grafik support ... the version 6.1.43 kernels are not even booting .... wtf 😞 i tried a SPI flushing, no change the armbian Kernels are booting !!! yay ! but : Armbian 25.5.1 with 6.1.115 (vendor kernel) looks like it has gpu support ! yay ! at least glxinfo shows the gpu string 🙂 but no emmc support 😞 even with booting from sd the kernel does not find /dev/mmcblk0 (mmcblk1 is detected as the sd card) 😞 Desktop images with Armbian Linux v6.12: it detects the emmc, so booth /dev/mmcblk0 and /dev/mmcblk1 are present, yay ! 🙂 but no grafik card support 😞 what do Im missing ? on the newer kernel Im need the device tree overlay for panthor (gpu_panthor) right? But didnt manage to get the gpu up ... mesa always fail to create the context and than switching back to the software renderer (regarding glxinfo logs) So im stuck atm .... and yes, its frustrating!

Hi all, Sorry for such a kiddy question but I couldn’t find the answer. I have a bit another device than expected. I have Banana Pi 3 device with Armbian-bpi-SpacemiT 24.5.0-trunk Noble and i'm trying to install a new kernel to it. I've installed linux-allwinner kernel 6.8.0-60.63.1 and all the stuff with it. linux-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed] linux-headers-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed,automatic] linux-image-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed,automatic] linux-tools-allwinner/noble-security,noble-updates,now 6.8.0-60.63.1 riscv64 [installed] And current boot kernel looks like ``` # mkimage -l /boot/Image FIT description: Linux 6.1.15-legacy-k1 Created: Wed May 1 17:17:59 2024 Image 0 (kernel) Description: Linux 6.1.15-legacy-k1 Created: Wed May 1 17:17:59 2024 Type: Kernel Image Compression: uncompressed Data Size: 32397312 Bytes = 31638.00 KiB = 30.90 MiB Architecture: RISC-V OS: Linux Load Address: 0x01400000 Entry Point: 0x01400000 Hash algo: crc32 Hash value: f571b82e Default Configuration: 'conf-default' Configuration 0 (conf-default) Description: Generic Linux kernel Kernel: kernel ``` The question is - How to make from vmlinuz-6.8.0-60-generic a kernel with the same format like above ? When I try to make it like this `mkimage -A riscv -O linux -T kernel -C none -a 0x01400000 -e 0x01400000 -d /boot/vmlinuz-6.8.0-60-generic /tmp/Image` I have another kernel format. ``` Created: Fri Jul 18 15:49:58 2025 Image Type: RISC-V Linux Kernel Image (uncompressed) Data Size: 38608384 Bytes = 37703.50 KiB = 36.82 MiB Load Address: 01400000 Entry Point: 01400000 ```

I got a radxa rock 5t and trying to install armbian(https://www.armbian.com/radxa-rock-5t), arimbian NOT boot and I can see the indicator light on the board is showing a steady green light. I boot with the official image https://docs.radxa.com/en/rock5/rock5t/low-level-dev/maskrom/linux and insert the sd card(with armbian img), and run such command, then I can boot armbian from SD card sudo dd if=/dev/mmcblk0 of=working_idbloader.img bs=512 skip=64 count=8000 sudo dd if=/dev/mmcblk0 of=working_u-boot.itb bs=512 skip=16384 count=8000 sudo dd if=working_idbloader.img of=/dev/mmcblk1 bs=512 seek=64 conv=notrunc sudo dd if=working_u-boot.itb of=/dev/mmcblk1 bs=512 seek=16384 conv=notrunc BTW, it seems there's no rock-5t tag, so I selected the 5b one