All Activity

I don't have a working board to add yet. I followed the documentation on creating a ~/build/config/boards/sv06ace.csc file but got lost about how to bring in the rk-kernel.dts values into the build.

Per the title, I was able to extract an ftb file and convert it to dtb and dts file. I would like to use the community build framework and build Armbian for SV06 Ace. The initial plan was to base the new board/*csc files on other rk3308b boards; sakurapi and rock-s0 and then pull configuration values from the OEM dts file. I'm confused about the dts structure in Community builds and the proper locations for defconfig, dts and dtsi files. I've worked with the files in OpenWRT where they are rigidly structured - something that would be a monumental task for Armbian community builds. The OEM dts file does not use any includes/dtsi files. If successful, I would like to publish on github similiar to @Torte https://github.com/torte71/armbian-mksklipad50 Can someone point me to the relevant documentation for Armbian dts files?

If you installed the Armbian 25.11.1 Edge Image the earlier post fixed the HDMI audio issue. However, if you upgrade with the command sudo apt update && sudo apt upgrade you will break both HDMI audio and WiFi. Here is the new fix: 1. The Wi-Fi Fix (Rebuild DKMS) Since the kernel updated, we just need to force the system to recompile the missing Wi-Fi driver for the new kernel version. Run this command in your terminal: Bash sudo dpkg-reconfigure aic8800-usb-dkms Wait a minute or two for it to finish compiling. Your Wi-Fi will be restored upon your next reboot. 2. The HDMI Audio Fix (Restore Qualcomm Configs) The HDMI audio broke because the system is now missing the Use Case Manager (UCM) profiles for the QCS6490 chip. We need to pull the newest configurations directly from the ALSA project repository and put them in the right folders. Run these commands one by one: Bash # Install the base UCM configurations sudo apt install -y alsa-ucm-conf # Download the latest master branch configs to your temporary folder cd /tmp curl -sL "https://github.com/alsa-project/alsa-ucm-conf/archive/refs/heads/master.tar.gz" | tar xz # Copy the specific Qualcomm configs and dependencies to your system sudo cp -r alsa-ucm-conf-master/ucm2/Qualcomm/qcs6490 /usr/share/alsa/ucm2/Qualcomm/ sudo cp -r alsa-ucm-conf-master/ucm2/conf.d/qcs6490 /usr/share/alsa/ucm2/conf.d/ sudo cp -r alsa-ucm-conf-master/ucm2/lib /usr/share/alsa/ucm2/ sudo cp -r alsa-ucm-conf-master/ucm2/codecs /usr/share/alsa/ucm2/ # Restart your audio server to apply the changes systemctl --user restart pulseaudio Once you've run those, give your board a quick sudo reboot.

poweroff doesn't work on any of my boxes either. Does reboot work correctly for you? It does on my boxes, and I usually issue a reboot and then time a power disconnect when the drives have spun down and before they restart.

Change the dp dm and gave this. sudo dmesg | grep tty [ 0.471034] console [tty0] enabled [ 633.797008] usb 1-1.4.1.3: cp210x converter now attached to ttyUSB0 [ 1159.103497] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 2713.702725] usb 1-1.4.1.2: cp210x converter now attached to ttyUSB0 [ 3812.350749] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 3812.351220] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 3812.447580] cp210x ttyUSB0: failed set request 0x12 status: -19 [ 3812.447593] cp210x ttyUSB0: failed set request 0x0 status: -19 [ 3812.447923] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 4077.235990] usb 1-1.4.1.2: cp210x converter now attached to ttyUSB0 [ 4098.361943] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 5224.734896] usb 1-1.4.1.3: cp210x converter now attached to ttyUSB0 [ 5248.927091] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 5250.665687] usb 1-1.4.1.3: cp210x converter now attached to ttyUSB0 [ 5600.550201] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 5600.550539] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 5601.154463] cp210x ttyUSB0: failed set request 0x12 status: -19 [ 5601.154476] cp210x ttyUSB0: failed set request 0x0 status: -19 [ 5601.154818] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 5725.698091] usb 1-1.4.1.3: cp210x converter now attached to ttyUSB0 GNU/Linux When pass → sudo screen /dev/ttyUSB0 115200 Only has cursor blinking.

Only a guess, but the first thing I would look at is how this is connected to your t box as it seems to not be connecting correctly. Maybe some pictures of your connection points?

If you installed the Armbian 25.11.1 Edge Image the earlier post fixed the HDMI audio issue. However, if you upgrade with the command sudo apt update && sudo apt upgrade you will break both HDMI audio and WiFi. Here is the new fix: 1. The Wi-Fi Fix (Rebuild DKMS) Since the kernel updated, we just need to force the system to recompile the missing Wi-Fi driver for the new kernel version. Run this command in your terminal: Bash sudo dpkg-reconfigure aic8800-usb-dkms Wait a minute or two for it to finish compiling. Your Wi-Fi will be restored upon your next reboot. 2. The HDMI Audio Fix (Restore Qualcomm Configs) The HDMI audio broke because the system is now missing the Use Case Manager (UCM) profiles for the QCS6490 chip. We need to pull the newest configurations directly from the ALSA project repository and put them in the right folders. Run these commands one by one: Bash # Install the base UCM configurations sudo apt install -y alsa-ucm-conf # Download the latest master branch configs to your temporary folder cd /tmp curl -sL "https://github.com/alsa-project/alsa-ucm-conf/archive/refs/heads/master.tar.gz" | tar xz # Copy the specific Qualcomm configs and dependencies to your system sudo cp -r alsa-ucm-conf-master/ucm2/Qualcomm/qcs6490 /usr/share/alsa/ucm2/Qualcomm/ sudo cp -r alsa-ucm-conf-master/ucm2/conf.d/qcs6490 /usr/share/alsa/ucm2/conf.d/ sudo cp -r alsa-ucm-conf-master/ucm2/lib /usr/share/alsa/ucm2/ sudo cp -r alsa-ucm-conf-master/ucm2/codecs /usr/share/alsa/ucm2/ # Restart your audio server to apply the changes systemctl --user restart pulseaudio Once you've run those, give your board a quick sudo reboot.

Thank you again for your reply. I am facing an issue though. When i try to shut down the device (either by issuing the poweroff comand or picking the "Exit" on screen menu item), the shut down process does not complete. I can see the dots spinning on the screen for about 5-10 seconds, but then they freeze and the device stays on... The only way to shut it down is to disconnect the device from the power supply, but, because of that, of course the hard drive can not reach the sleep mode as I can hear it is still spinning. Can I try something to solve this and have a clean power off?

Any idea about this → sudo dmesg | grep tty [ 0.471034] console [tty0] enabled [ 633.797008] usb 1-1.4.1.3: cp210x converter now attached to ttyUSB0 [ 1159.103497] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 2713.702725] usb 1-1.4.1.2: cp210x converter now attached to ttyUSB0 [ 3812.350749] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 3812.351220] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32 [ 3812.447580] cp210x ttyUSB0: failed set request 0x12 status: -19 [ 3812.447593] cp210x ttyUSB0: failed set request 0x0 status: -19 [ 3812.447923] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 4077.235990] usb 1-1.4.1.2: cp210x converter now attached to ttyUSB0 [ 4098.361943] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 GNU/Linux sudo screen /dev/ttyUSB0 115200. [screen is terminating]

Sorry for the late reply to your request. I still have the image; let me know where to upload it if you're still interested.

Hi, eselarm. i did not have time to delete the topic. Somehow it started working. Thank you for your time.

https://github.com/armbian/linux-rockchip/pull/448 Was able to reproduce this issue and get it fixed.

in the root of the rootfs do: find . -name platform_install.sh find . -name u-boot-sunxi-with-spl.bin essentially construct correct dd arguments somethings else might be wrong though, so make sure you have a serial console/debug able with loglevel=7

@shexplorer I am in the same situation with my x88pro13 box not booting and I do not manage to go in Maskrom mode. Any progress on your side ?

Hello everyone, I am new to Armbian and need some help. I tried to install Armbian 26.2.0-trunk (https://www.armbian.com/nanopi-neo/#collapse-widget-5-0-0-0) on a NanoPi NEO Core SBC. I used Armbian Imager and wrote the latest official image (the only one available) to the SD card. After writing the image, I see only one partition on the SD card named armbi_root. When I insert the card into the device and power it on, nothing happens — there are no boot messages or logs. I think the image is missing a bootloader. So my questions are: 1) If I’m right that the bootloader is missing, how can I add a bootloader to the image? 2) How can I apply OverlayFS to this setup? 3) Do you have a link to a good article or tutorial on these topics? Thanks in advance!

Unless they have changed something very recently, you can login as root via ssh on first-run. I double checked /etc/ssh/sshd_config on an armbian install image I had downloaded, and: # Authentication: #LoginGraceTime 2m PermitRootLogin yes #StrictModes yes #MaxAuthTries 6 #MaxSessions 10 PubkeyAuthentication yes <snip> # To disable tunneled clear text passwords, change to no here! #PasswordAuthentication yes #PermitEmptyPasswords no And inside /etc/shadow (default 1234 passwd): root:$y$j9T$SAPCtO/l2ZIj6A2frqTza/$.Z8dP41gzqRHoIS8PvXFn9fghf9rgkGqAWgXVRW4dg6:20234:0:99999:7::: So that should not be an issue here. (and there are keys inside /etc/ssh that I assume can be used at first login, I have never tried) Sounds more like a faulty sd-card that gets mounted read-only, that can cause stuff like this happening. (as mentioned earlier by Igor) Try with a different sd-card (and use armbian-imager instead of balena) and see if the same happens on another card.

I managed to do it thanks

Hello averyone I'm trying to download the multitool.img.xz can someone please help me find it or share a valide link?

The paste armbian URL displays nothing (anymore?) so without any (new) info from you, no-one can help you. AFAIR, 4K via HDMI connector is only recently available (on RK3588, not sure about RK3399), so make sure you can manage various combinations of U-Boot, kernel, rootfs. So sort of act like a developer, als make sure you have a serial console (debug) cable, else you cannot get any step further. Use a 26.2 based U-Boot and 6.19 rockchip64 kernel I would say, then see what happens.

@ag123 thank you for your response. I donated to the project in the past (search my messages, peytote was an awesome guy that helped with some specific SPI issue i had many years ago on a Orange PI i think), i am donating to few open source projects (Like FreeCAD) , will make recurring donations to Armbian for sure. Yeah i am not using any OrangePi with their original OS, no way. I need a more powerful board than OPi Zero 3, will look into the maintained and supported ones here on Armbian. Thanks for your reply.

If I understand you correctly: root via ssh is not allowed by default I usually setup (new) SBC's in a different way, but last time testing 2 of my boards with 26.2 minimal/IoT fresh image was via serial console, have not used ssh and certainly not putty. If no (serial) console, you might also have sme networking firewall issues somewhere in Windows or so, although would be vary rare. Have you setup a normal user first via (serial) console first?

I'll add my 2 cents with my more recent findings. Mind that I am using an Orange PI 5 Plus, your mileage might vary with other models. I started booting the official Orange PI (Arch) distro to clear the SPI bootloader, as suggested by @Igor sudo pacman -Syy sudo pacman -S mtd-utils sudo flash_erase /dev/mtd0 I've tried multiple flavours of the available downloads for Armbian, but I've found that all versions with kernel 6.12.58 would fail to load (the LED stays red, instead of flashing red & blue). This includes both Debian trixie and Ubuntu noble, with their desktop and minimal editions. Back in December 20204 @Igor V described similar boot issues that got resolved with kernel 6.1.75, the one that was highlighted in green at the time. So that led me to try with kernel 6.1.115 instead, and that has worked just fine. Not sure if this is an issue introduced with the newer kernel, or whether it's to be expected as it has not been officially stabilised yet. Anyway, I thought I'd share in case this can help others in the future.

having the same issiue , would like to improve the situation since most of the monitor that i use come in 16:10 format, and those resolution seem not easily available. also read here on a site it should be capable of 4k output. https://www.electromaker.io/blog/article/pine64-rockpro64-review-a-beefy-single-board-computer

I tried it with a desktop PC, but couldn't select a resolution higher than 1024x768. I read that there's a bug in newer kernel versions that's already been fixed. However, I couldn't find out if the fix is included in the downloaded image. Then I tried an older imager with kernel 4.4, and with that one, I was able to select higher resolutions. @jock I only tested it with Wi-Fi. You could also try a version with an older kernel.

If you want to add new board with its own device tree, this is a good example: https://github.com/armbian/build/pull/9423 Remember to add pictures - this way https://github.com/armbian/armbian.github.io/pull/236