Active threads

Hello! I am quite new to using Armbian, and I have been having some trouble trying to boot into Multitool. Before I explain my problem, I will describe what I have been using, which is an RK3328 X88 Pro 10. The image I tried using alongside Multitool was Armbian_23.11.1_RK3328-Box_jammy_current_6.1.63.img. First off the bat, Multitool was only 377 MB, even though the min SD I was using is 117 GB, which I am not sure if that was done on purpose, but I made it more difficult to find an image that fit. Next, when Mulitool booted in, I was greeted with the Terms of Software page, which would only let me scroll up and down. If I try any other keyboard keys (I do not have the remote; it has been lost for years). A black box from the bottom of the screen, opening some kind of terminal, saying "Line 17: command not found" when it opens, all I can do is type like a text editor where hitting enter does not get a response from the software. I don't know what to do at all, so I hope one of you guys could understand the predicament I'm in

If you're still able to boot from microsd (which should be prefered over emmc if Armbian uboot is used) you can chroot into the system on eMMC and downgrade packages, either manually (apt/dpkg) or with armbian-config.

No clue, sorry. Maybe the driver might be optimized to work best with wayland. Maybe there is a fix pending or already merged into newer Linux version.

Addendum: An Easy Way To Bypass Grub's Self-Centric Orientation & Eliminate The Need For OS-Prober 1. Assuming you already have your EFI partition set up, for any OS that's mounting the EFI partition, stop that. In the /etc/fstab file, comment out (with a #) the line where it's mounted (i.e. as /boot/efi/). 2. Install grub on each OS. You can keep the /boot/grub/ directory on the same partition as root. Each installed OS will just update its own grub.cfg whenever it's needed. # If the your OS doesn't have a /boot/efi/ directory, create one. mkdir /boot/efi # Install grub. This will force it to install even though it won't detect a genuine EFI. grub-install --efi-directory /boot/efi --force Remember if you need to disable os-prober (recommended), just comment-out its line in /etc/default/grub. 3. Optional: Eliminate the pesky EFI Firmware menu entry in each OS this way: cd /etc/grub.d mkdir skip.d mv 30_uefi-firmware skip.d/ 4. Update Grub with your current kernels update-grub 5. Create a small partition for grub. 64 MB will suffice. 6. Choose an OS's grub, and copy all files from /boot/grub/ to that small grub partition. 7. On that grub partition, create a new grub.cfg. Here is a sample: set timeout=10 # Load Modules insmod all_video insmod part_gpt insmod ext2 insmod png # Setup Background loadfont unicode terminal_output gfxterm background_image /grub-16x9.png set color_normal=white/black set color_highlight=black/white # Menu Entries menuentry 'Orange PI Bookworm' { search.fs_uuid df078711-12a0-4637-9264-bac72ee25e4c root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Debian Trixie' { search.fs_uuid 1b6add1b-05ac-4568-bf54-1f920a6f8e3e root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Armbian 25.8.1 Bookworm' { search.fs_uuid ecb0ae86-8f5c-477e-bcd0-bc77ee5ebee9 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Armbian 25.8.1 Trixie' { search.fs_uuid 6f2d1972-8868-4fb2-bde4-e14325ea4d31 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Armbian 25.8.1 Noble (Ubuntu 24.04)' { search.fs_uuid d974e989-b201-48c6-b74b-f9ab5dfdfdae root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } Of course, change the menu entry titles and UUIDs to your own. 8. Copy the background image you'd like to use to your grub partition. On Debian, background images for grub are typically stored some place like this: /usr/share/desktop-base/emerald-theme/grub Note in the sample grub.cfg file, grub-16x9.png is the background image named. If you want to use a .jpg instead of a .png, change the insmod png to insmod jpeg. 9. In your EFI partition, modify the grub.cfg to be as follows: search.fs_uuid 3D53-E216 root set prefix=($root)'/' configfile $prefix/grub.cfg ...changing the UUID to that of your grub partition. Usage Select the OS you want. That will take you to the OS's own grub menu, which will likely show you two options, the main boot option and "Advanced" boot options. If you select an operating system and wish to change your mind, the ESCAPE key will return you to your previous menu. Problems I did this and everything worked well except the Armbian Noble (Ubuntu) entry. I coped Debian Bookworm's grub to my grub partition, and either Ubuntu's grub is buggy or apparently Ubuntu's grub used language in its grub.cfg that Debian's grub didn't like. It boots into Ubuntu automatically, but it doesn't show any boot menu. I set its timeout for 10 seconds, so it sits with a blank screen for 10 seconds before it boots. Update: I replaced the grub files on my grub partition with those from Debian Trixie. Same results with Armbian Noble (Ubuntu).

Thank you for replying so fast, really appreciate it. No factory reset will solve this? Best regards and thanks again

Hi there, I ran octoprint and klipper on a orangepi zero (not at the same time). Octoprint from docker and klipper I cannot remember. Octoprint ran fine but it did have some issues when the CPU got overloaded with loading a new gcode file while printing for example. If you do things one by one it should be OKish. Btw i ran octoprint in a 512MB version, not on the 256MB one. Groetjes,

So I looked into this, and unfortunately, no dice. I am happy to investigate further, if you so wish, but I'm happy enough with the way it works currently (auto patching the dtb after a kernel update) so am unlikely to go exploring further on my own. To let you know what I did: copied the dtbo to /boot/dtb/amlogic/overlay/meson-gxl-s905w-tx3-mini-openvfd.dtbo Added to /boot/extlinux/extlinux.conf: fdtoverlays /dtb/amlogic/overlay/meson-gxl-s905w-tx3-mini-openvfd.dtbo (I also tried with /boot prepended to the path as well, but same issue) note: I assume FDTOVERLAYS is a typo from the armbianEnv.txt days, so I went with the lowercase as that is standard for extlinux The device would not come up on the network. I plugged in an HDMI monitor and found that it would hang at: ethernet end0: renamed from eth0 Which is.... odd. I suspect one of 2 things: My entry in extlinux.conf is incorrect (entirely plausible, I'm struggling to find documentation, I've just gone on what you've said, and also changed the capitalisation!) U-Boot overlays are applied differently than fdtoverlay in Linux. It’s possible U-Boot leaves something unaligned or adds an unexpected property, and the kernel hits a corner case. I realise that the above is noway near enough information, however, connecting directly to serial is not realistic at this stage, but I can attach a netconsole if needs be, as we are reaching the kernel, and provide further output. Like I say though, I will only do this if you think there is value in it. Whilst my method might not be the preferred way, it does work, at least.

@pochopsp You would need to use the information in that readme and patch and apply it to a newer u-boot (i.e port the patch to a newer u-boot) and build then a newer u-boot than the 2020.07 currently shipped.

@DiplDi I was doing some experiments on Armbian 25.8.1 Trixie, and I decided to do a quick try of installing the XFCE desktop (along with some others): sudo apt-get -o APT::Install-Recommends="true" install task-xfce-desktop It works under X, but not under Wayland. I found out that its Wayland support is experimental, and that if you install the labwc package, that will get it running (very very badly) under Wayland. But it does work well under X. It's possible a different wayland compositor (than labwc) will work better? I also tried with the Vendor kernel (with the Panthor GPU overlay), and the edge kernel. Edge GPU performs seemingly not at all under X, but vendor with Panthor overlay performs well in X. I initially logged in via the SDDM display manager, but I switched to LightDM, and that worked as well, although with a hiccup.

That change is already merged into Armbian for the orange pi zero LTS. It was such a long time ago, I don't remember how to use it right now. https://github.com/armbian/build/blob/9ef5b99b220c5e77b55514136e025008c16ccbfd/patch/kernel/archive/sunxi-6.12/patches.armbian/enable-TV-Output-on-OrangePi-Zero-LTE.patch#L8 https://github.com/armbian/build/commit/41260ac309b487d241fec97ffbdeced730bc2d04 Partial progress log https://forum.armbian.com/topic/22226-orange-pi-zero-lts-tv-out-in-2022/#findComment-162035

Is it the 128x160 1.8" red screen? Combine the knowledge of https://forums.raspberrypi.com/viewtopic.php?t=380704&hilit=ST7735S#p2275556 and https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/ To use the panel-mipi-dbi-spi driver, which is more universal for SPI screens Warning: you will not get the spidev, and the linux OS will handle all the rendering. Also, X11 may have a problem with Linux 6.14, unless someone fixes a bug

Abandoned vendor-provided BSP roadblocks can be overcome when mainline Open Source projects like the Linux kernel are integrated directly. Get your upstreamed BSPs from day one. View the full article

I tested the upstream Debian and I only got 4GB as well, I don't know if that was stable or not. Actually some upstream Debian images I tried didn't work at all at first. Then I upgraded the firmwares on my board, following these instructions: https://forum.rvspace.org/t/visionfive-2-debian-image-released/994/75 Bu I was more precise than that, first I used the sdcard image and fimware files from 2.6.0 (said to work in that page): https://github.com/starfive-tech/VisionFive2/releases/tag/VF2_v2.6.0 Note: I had no display, I ran the firmware update commands over SSH. Then I rebooted, using the sdcard image from 2.11.5 (arbitrary chosen): https://github.com/starfive-tech/VisionFive2/releases/tag/VF2_v2.11.5 But I used the latest (5.11.3) firmware files to update the firmware: https://github.com/starfive-tech/VisionFive2/releases/tag/JH7110_VF2_515_v5.11.3 After that, I flased the latest image (202409), for sdcard: starfive-jh7110-202409-SD-minimal-desktop-wayland.img The whole 8GB is displayed and everything looks stable, the board is running since 9 hours without problem. But one problem is that this Debian image is based on an now-old Debian Trixie/Sid snapshot, which is painful to deal whit. I'll try again the Armbian image later to see if the firmware update fixed the memory size problem and the stability.

S905W2 I didn't find a solution to my problem on the forum.

Armbian 25.8.1 Noble XFCE (mainline Kernel: 6.16.6-edge-rockchip64) + PanVk - mesa 23.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.7 (https://ryanfortner.github.io/box64-debs/) + wine-10.15-staging-tkg-ntsync-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.15) + DXVK-stripped v2.7.1 ~30fps@720p Dark Souls 2 - SotFS

I've just been through this process myself. Those instructions are not close to working, and I'm not sure they ever worked. I have documented how I got the LCD display working on the T3-Mini here:

My brief experience in trying out a USB-C display wasn't great. I was never able to get any video at all until / unless I was fully booted into an OS, and even then it was shotty. Both USB-C connectors on the Orange PI 5 Plus (on mine anyway) are poorly made and intermittently lose connection if moved around at all. I recently read that's a real problem with SBCs in general that get their power over USB-C... clearly a very poor design. I also read somewhere that a similar board required proprietary drivers for USB-C display output to function. My experience indicates at least something like that likely applies here as well. Dysfunctional hardware design.

@laibsch thank you for reaching out. I apologize for the delay in responding. I want to inform you that I am actively seeking assistance from the community and am willing to contribute by developing code to address the issues I've observed on this board. However, despite my efforts to engage with the community, I have not received any responses and am not sufficiently experienced to thoroughly troubleshoot and resolve these problems on my own. Although I have some knowledge of programming languages, I am not well-versed in Linux. For example, this morning, I suggested a potential solution to the Bluetooth issue on the IRC channel but received no feedback. For the GPU, it appears that acceleration is now present, as the CPU is no longer at 100%. However, I am unable to set the resolution to 4K without encountering screen artifacts, and I can only achieve Full HD resolution.

Next week, Collabora will be taking part in the 2025 edition X.Org Developer's Conference! Taking place in Vienna, our engineers will be presenting 6 talks and a workshop to help local students discover the embedded graphics stack! Join us! View the full article

@blood like a charm dude

Kernel packages comes from the same (main) repository. This won't cause you problems, if you upgrade from bookworm to trixie, but we can't guarantee for packages that comes from Debian. You might try this way: https://docs.armbian.com/User-Guide_Armbian-Config/System/#stable-distro-upgrade Note that you might need to download updated Armbian key: wget -qO - https://apt.armbian.com/armbian.key | gpg --dearmor | \ sudo tee /usr/share/keyrings/armbian.gpg > /dev/null cat << EOF | sudo tee /etc/apt/sources.list.d/armbian-config.sources > /dev/null Types: deb URIs: https://github.armbian.com/configng Suites: stable Components: main Signed-By: /usr/share/keyrings/armbian.gpg EOF

Hard to tell without any logs whatsoever In general it works on x86 since a few month ago I used it to move the OS from an old NUC-like pc from sd to built-in emmc which was flawless (besides I had to get rid of Ventoy since it messes up Armbian boot).

has any progress been made toward fixing this

here is my dts for android rkr7.1 sdk 6.1.141 with everything working usb2 host usb3 otg/host hdmi ethernet 3.5mm spdif IR + wakeup wifi BT collect info for adding your remote to dts echo 1 > /sys/module/rk_pwm_remotectl/parameters/code_print m9.dts

Hi @jock, Thanks for suggestion, led me to dig down and found your update on R29 GPIO. Since multitool hdmi was working, I used it's bash to mount emmc and add overlays=led-config7 to armbianEnv.txt. It worked!!!! Thanks a lot for all your contribution!