All Activity

@Tomi Skies XR819 shoud work. Can you post your dmesg log.

@Nick A I think this is the wifi chip?

@Tomi Skies can you change the log level to 7 in armbianEnv.txt on sdcard. I don’t see your wifi chip in the picture above. It might be on the other side of your board.

Thanks for the answer, @amazingfate! I guess there might be e bug in the driver. Once I have more time (if I have) I will issue a bug report to the kernel devs and will try ti test and send required info. Regards, Tano

@Nick A I tried the Armbian-unofficial_25.05.0-trunk_X96q-lpddr3_bookworm_edge_6.12.11_xfce_desktop.img I don't really know what I'm doing tbh, but it seems like mostly everything works except wifi. Don't know if this is of any interest, but here is a UART log of the first boot. 19:28:07.082 -> U-Boot SPL 2025.01-armbian-2025.01-S6d41-P7151-H8869-V004f-Bb703-R448a-dirty (Apr 02 2025 - 21:10:39 -0400) 19:28:07.159 -> DRAM:testing 32-bit width, rank = 2 19:28:07.159 -> DRAM:Store cfg 19:28:07.159 -> DRAM:1st writing pattern 19:28:07.159 -> DRAM:detecting column address bits 19:28:07.159 -> detected 10 columns 19:28:07.159 -> DRAM:restore cfg 19:28:07.159 -> DRAM:reconfigure for all active rows 19:28:07.159 -> DRAM:store cfg 19:28:07.159 -> DRAM:2nd writing pattern 19:28:07.192 -> DRAM:detecting row address bits 19:28:07.192 -> detected 14 rows 19:28:07.192 -> DRAM:restoring cfg 19:28:07.192 -> DRAM:end of auto detect dram size 19:28:07.192 -> MBUS port 0 cfg0 0100000d cfg1 00640080 19:28:07.192 -> MBUS port 1 cfg0 06000009 cfg1 01000578 19:28:07.192 -> MBUS port 2 cfg0 0200000d cfg1 00600100 19:28:07.192 -> MBUS port 3 cfg0 01000009 cfg1 00500064 19:28:07.192 -> MBUS port 4 cfg0 20000209 cfg1 1388157c 19:28:07.192 -> MBUS port 5 cfg0 00640209 cfg1 00200040 19:28:07.225 -> MBUS port 6 cfg0 00640209 cfg1 00200040 19:28:07.225 -> MBUS port 8 cfg0 01000009 cfg1 00400080 19:28:07.225 -> MBUS port 11 cfg0 01000009 cfg1 00640080 19:28:07.225 -> MBUS port 14 cfg0 04000009 cfg1 00400100 19:28:07.225 -> MBUS port 16 cfg0 2000060d cfg1 09600af0 19:28:07.225 -> MBUS port 21 cfg0 0800060d cfg1 02000300 19:28:07.225 -> MBUS port 22 cfg0 01000009 cfg1 00640080 19:28:07.225 -> MBUS port 25 cfg0 0064000f cfg1 00200040 19:28:07.225 -> MBUS port 26 cfg0 20000209 cfg1 1388157c 19:28:07.262 -> MBUS port 37 cfg0 01000009 cfg1 00400080 19:28:07.262 -> MBUS port 38 cfg0 00640209 cfg1 00200040 19:28:07.262 -> MBUS port 39 cfg0 20000209 cfg1 1388157c 19:28:07.262 -> MBUS port 40 cfg0 00640209 cfg1 00200040 19:28:07.262 -> 1024 MiB 19:28:07.308 -> Trying to boot from MMC1 19:28:07.819 -> NOTICE: BL31: v2.10.14(debug):armbian 19:28:07.852 -> NOTICE: BL31: Built : 18:07:43, Apr 2 2025 19:28:07.852 -> NOTICE: BL31: Detected Allwinner H616 SoC (1823) 19:28:07.852 -> NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 19:28:07.852 -> INFO: ARM GICv2 driver initialized 19:28:07.852 -> INFO: Configuring SPC Controller 19:28:07.852 -> INFO: PMIC: Probing AXP305 on RSB 19:28:07.852 -> ERROR: RSB: set run-time address: 0x10003 19:28:07.884 -> INFO: Could not init RSB: -65539 19:28:07.884 -> INFO: BL31: Platform setup done 19:28:07.884 -> INFO: BL31: Initializing runtime services 19:28:07.884 -> INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied 19:28:07.884 -> INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied 19:28:07.884 -> INFO: PSCI: Suspend is unavailable 19:28:07.884 -> INFO: BL31: Preparing for EL3 exit to normal world 19:28:07.928 -> INFO: Entry point address = 0x4a000000 19:28:07.928 -> INFO: SPSR = 0x3c9 19:28:07.928 -> INFO: Changed devicetree. 19:28:08.196 -> ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 19:28:08.238 -> 19:28:08.238 -> 19:28:08.238 -> U-Boot 2025.01-armbian-2025.01-S6d41-P7151-H8869-V004f-Bb703-R448a-dirty (Apr 02 2025 - 21:10:39 -0400) Allwinner Technology 19:28:08.238 -> 19:28:08.238 -> CPU: Allwinner H616 (SUN50I) 19:28:08.238 -> Model: hechuang,x96-q LPDDR3 19:28:08.238 -> DRAM: 1 GiB 19:28:08.318 -> Core: 58 devices, 20 uclasses, devicetree: separate 19:28:08.318 -> WDT: Not starting watchdog@30090a0 19:28:08.318 -> MMC: mmc@4020000: 0, mmc@4021000: 3, mmc@4022000: 1 19:28:08.362 -> Loading Environment from FAT... Unable to use mmc 0:1... 19:28:08.400 -> In: serial@5000000 19:28:08.400 -> Out: serial@5000000 19:28:08.400 -> Err: serial@5000000 19:28:08.400 -> No USB device found 19:28:08.400 -> Net: eth0: ethernet@5030000 19:28:08.400 -> starting USB... 19:28:08.400 -> No USB controllers found 19:28:08.439 -> Hit any key to stop autoboot: 1 0 19:28:09.465 -> switch to partitions #0, OK 19:28:09.465 -> mmc0 is current device 19:28:09.465 -> Scanning mmc 0:1... 19:28:09.465 -> Found U-Boot script /boot/boot.scr 19:28:09.465 -> 4641 bytes read in 2 ms (2.2 MiB/s) 19:28:09.498 -> ## Executing script at 4fc00000 19:28:09.498 -> U-boot loaded from SD 19:28:09.498 -> Boot script loaded from mmc 19:28:09.498 -> 202 bytes read in 1 ms (197.3 KiB/s) 19:28:09.498 -> Load fdt: /boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb 19:28:09.539 -> 37577 bytes read in 7 ms (5.1 MiB/s) 19:28:09.539 -> Working FDT set to 4fa00000 19:28:09.539 -> Failed to load '/boot/dtb/allwinner/overlay/sun50i-h616-fixup.scr' 19:28:10.920 -> 15484849 bytes read in 1362 ms (10.8 MiB/s) 19:28:14.642 -> 42621440 bytes read in 3744 ms (10.9 MiB/s) 19:28:14.642 -> Moving Image from 0x40080000 to 0x40200000, end=0x42b50000 19:28:14.909 -> ## Loading init Ramdisk from Legacy Image at 4ff00000 ... 19:28:14.950 -> Image Name: uInitrd 19:28:14.950 -> Image Type: AArch64 Linux RAMDisk Image (gzip compressed) 19:28:14.950 -> Data Size: 15484785 Bytes = 14.8 MiB 19:28:14.950 -> Load Address: 00000000 19:28:14.950 -> Entry Point: 00000000 19:28:14.950 -> Verifying Checksum ... OK 19:28:15.040 -> ## Flattened Device Tree blob at 4fa00000 19:28:15.040 -> Booting using the fdt blob at 0x4fa00000 19:28:15.040 -> Working FDT set to 4fa00000 19:28:15.040 -> Loading Ramdisk to 4913b000, end 49fff771 ... OK 19:28:15.073 -> Loading Device Tree to 00000000490c9000, end 000000004913afff ... OK 19:28:15.073 -> Working FDT set to 490c9000 19:28:15.073 -> 19:28:15.073 -> Starting kernel ... 19:28:15.073 -> 19:32:05.614 -> 19:32:05.614 -> x96q-lpddr3 login: root (automatic login) 19:32:05.614 -> 19:32:29.834 -> Last login: Thu Apr 3 01:16:15 UTC 2025 on tty1 19:33:10.979 -> 19:33:10.979 -> x96q-lpddr3 login: root (automatic login) 19:33:10.979 -> 19:33:10.979 -> Last login: Thu Apr 3 01:16:15 UTC 2025 on ttyS0 19:33:17.425 -> 19:33:17.425 -> Waiting for system to finish booting ... 19:33:25.662 -> Waiting for network startup to complete... 19:33:42.217 -> [H[J[3JWelcome to [1m[97mArmbian-unofficial[0m! 19:33:42.217 -> 19:33:42.217 -> Documentation: [1m[92mhttps://docs.armbian.com/[0m | Community support: [1m[92mhttps://community.armbian.com/[0m 19:33:42.263 -> 19:33:42.263 -> 19:33:42.263 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (6) 19:33:43.299 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (5) 19:33:44.298 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (4) 19:33:45.362 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (3) 19:33:46.358 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (2) 19:33:47.390 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (1) 19:33:48.451 -> [1A[KIP address: [92m[0m [1m[31mNetwork connection timeout![0m 19:33:49.462 -> 19:33:49.462 -> Create root password: 19:33:57.499 -> Armbian-unofficial 25.05.0-trunk Bookworm ttyS0 19:33:57.548 -> 19:33:57.548 -> x96q-lpddr3 login: [ 1858.394981] reboot: Power down 19:59:13.714 -> �

I have completed a build for the turing-rk1 SBC with an aim toward getting a functioning graphical console, and possibly installing desktop packages later. I built an image without issue that picked up kernel 6.17.2. git commit: 09160da3b9c1231cf20837e8c857f7e605130449 main branch Command used: ./compile.sh RELEASE=trixie CARD=turing-rk1 BRANCH=edge Image created: Armbian-unofficial_25.11.0-trunk_Turing-rk1_trixie_edge_6.17.2.img When booted, I get an error from dmesg about VOP drivers and HDMI video does not turn on. Is this normal for this board or am I doing something wrong? [ 0.965616] rckchip-drm display-subsystem: [drm:rockchip_drm_platform_probe] *ERROR* No available vop found for display-subsystem. The git commit that introduced this board in Armbian does appear to include GPU support, though I'm not really sure if that means the HDMI output should be working. https://github.com/armbian/build/commit/d564431dc2e2a16dff8d21391603702b43de06b1#diff-1d2956e936e3a376577f803ce53091b41ed47e906602165217f78912496eac63 Maybe I need to build w/ kernel 6.11.x to enable GPU support with these patches? Can someone clarify?

Maybe not? root@rp-satellite-01:~# for X in 0 1;do echo "mmcblk${X}: $(cat /sys/block/mmcblk${X}/device/type)";done mmcblk0: SD mmcblk1: SD root@rp-satellite-01:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdb 8:16 1 238.3G 0 disk └─sdb1 8:17 1 238.3G 0 part /media/usb mmcblk1 179:0 0 59.6G 0 disk └─mmcblk1p1 179:1 0 59G 0 part /var/log.hdd / mmcblk0 179:32 0 3.6G 0 disk └─mmcblk0p1 179:33 0 3.5G 0 part zram0 252:0 0 233.1M 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk root@rp-satellite-01:~#

Collabora is proud to sponsor this year's annual GStreamer conference, taking place in London, UK. Join us as we showcase the latest with machine learning analytics, WirePlumber, and more. View the full article

I was able to extend, thanks everyone for the support. I attached my final dts, I also changed from spi4 to spi1, because I double check the pinount and spi4 is not mapped. In the original pinout armbian spi1 = orange pi 5 pro spi4. rk3588s-spi1-5cs-spidev.dts

Thanks for your sharing! While I was trying to perform the upgrade for a Pine64, I happily notice that the latest release of armbian-config actually have an option for the distro upgrade. By following the wizard, Debian was upgrade to trixie.

Try an apt full-upgrade. The libraspberrypi packages have been deprecated recently (e.g. June/July) and recent RPI packages shouldn't depend on them, including raspi-firmware.

Hi, difficult task since there is no support for the whole chip family in the framework yet, but first steps are here:https://github.com/armbian/build/pull/8364 I suggest to start by getting familiar with the framework and how the mentioned pending pr it put together. moved

Hi everyone. I am a crappy user not helping armbian to survive. My apologies. However, because I'm studying more linux, arm technologies. I would like to give any help to armbian. I am poor, not rich. But if there is another way to donate thousand dollars I'm ready to help. So my question is How to help Armbian about the new Orange pi sbc, orange pi 6 plus? Modos can delete this post if it breaks rules. No any problem for me. My apologies, my english is bad.

Hello, I have installed NextcloudPi on my Raspberry PI5. Current OS is installed currently: Now, I would like to make an upgrade and get the following issue. What can I do? I am very grateful for any help.

Hello! I have an RPi5 8GB board that I bought off of AliExpress, along with a Waveshare PoE M.2 HAT+ ( https://www.waveshare.com/poe-m.2-hat-plus-b.htm ) Initially I tried to use the Noble XFCE image, by following the recommended installation procedure via rpi-imager via a USB drive, hoping to install the system to a Toshiba (Kioxia) NVMe drive. The RPI5 was connected to a CrowView Note. What I saw was that the firmware loaded up the necessary files from the USB drive (then later the micro-SD card), and the initramfs loaded up too, then systemd started up, and probably when the screen usually goes blank for a short time (probably switching to KMS), here, the signal completely drops, and apparently nothing happens. (The messages scroll too fast, and then disappear, and I can't make out anything from the screen content.) I tried looking on the network to see whether the RPi5 comes up at all, but no. Since then, I tried to eliminate elements from my setup to see whether that makes any difference: I removed the Waveshare HAT Swtiched to using a micro-SD card instead of the USB thumb drive Tried to boot it without the CrowView Note Tried using the Noble Server image to eliminate any possible problems with the graphical UI but none of these helped. I now have the bare RPi5 with an active heatsink, and it's still not booting properly. What should I try? Should I try to get serial console working so that I at least see the boot messages? Is there an activity LED on the RPI5 where I could at least configure a heartbeat so that I could check whether the OS is alive at all? Since the OS can't be installed, I can't really submit much diagnostic information.

@going Yes, git is a pain in ass. I think it's better to teach everyone the git commands. Maybe someone will learn from my instructions and contribute to the mainline Linux kernel and Armbian. Transpeed 8k618-t Tv box will always be supported because I learned how to use git commands and submit patches. I hope others will do the same. A lot of the patches are mainlined for h618. I don't think it will be too long before Armbian only needs a Transpeed 8k618 board config to build an image. But of course there's different variations of the same box. I hope this thread helps them because I won't be here forever.

The way the Debian .iso installer does it: sudo apt-get -o APT::Install-Recommends="true" install task-lxqt-desktop That will install a fully functional desktop with a minimal set of applications. If you set Install-Recommends to false, or any other way of installing it (i.e. lxqt), in my experience, the result may not be quite functional.

@remlei I'did uploading this imagem, is minimal, i hope help you! https://drive.google.com/file/d/1esroAyxq2D2kJ5XPB2_pofQ473B-h1_S/view

From a minimal image type this (If you are going to use it in English, skip the "l10n" commands or translations) sudo apt update sudo apt install task-lxqt-desktop papirus-icon-theme gvfs locales polkitd xdg-desktop-portal-lxqt sudo reboot sudo apt install gvfs-backends lxqt-l10n-es liblxqt-l10n qterminal-l10n pcmanfm-qt-l10n featherpad-l10n lxqt-panel-l10n lxqt-session-l10n lxqt-powermanagement-l10n lxqt-config-l10n lxqt-about-l10n lxqt-admin-l10n lxqt-archiver-l10n sudo apt install gvfs-backends liblxqt-l10n qterminal-l10n pcmanfm-qt-l10n featherpad-l10n lxqt-panel-l10n lxqt-session-l10n lxqt-powermanagement-l10n lxqt-config-l10n lxqt-about-l10n lxqt-admin-l10n lxqt-archiver-l10n sudo apt install lxqt-globalkeys-l10n lxqt-policykit-l10n lxqt-runner-l10n lxqt-sudo-l10n lximage-qt-l10n libfm-qt-l10n lxqt-openssh-askpass-l10n ls xdg-user-dirs sudo apt install pavucontrol-qt-l10n sudo apt install dmz-cursor-theme sudo apt install openbox sudo apt purge --remove xfwm4 sudo apt autoremove sudo apt install obconf-qt obconf-qt-l10n sudo apt search xterm sudo apt purge --remove xterm sudo apt install qpdfview qpdfview-translations sudo apt install screengrab

can someone please reupload the legacy images, all links aside from the armbian community github page returns a 404

Dont write that "fbi works correctly", when it is not. The display remains white, and the kernel doesn't show any errors. * Re-check your wiring * Disconnect the touch part of the LCD pins * Try reversing the polarity: dc-gpios = <&pio 2 6 1>; << change the 1 to 0 reset-gpios = <&pio 2 9 1>; << change the 1 to 0 If the CPU is successful sending the reset signal, the data/command, the chip select and any bytes through SPI, at least the LCD should turn black.

@Hqnicolas Thanks for your response and apologies being so slow to reply busy IRL and then I forgot I used Google to sign up to this site.... yeah... Okay thanks - I thought it would just be a changing of timing so to speak on x86. In this case if I plan to develop for something I also go for the lowest variant of it, ofc, at this time both were Android. Rather code closer to the "metal" than bringing a whole web browser in to say "hello world" The images came from a link on this thread; either yourself or another member. Yeah I noticed a certain lag on the ethernet with 1GBit connection -- it has all the resources available yet it pings hard and downloads fluctuate. My plans for this Armbian is WiFi Repeater (router is broadcom and no Open- or DD-WRT alternative) to relay the signal. I don't want mesh, I don't need a TPLink account. The box will provide some services to Orange/Raspberry Pi systems. Right. I'm against AI So last thing I'd do. A link was provided but as I said expired. I'm sure there's differences in SDCard holders so didn't want to order two of the wrong type! Ah obrigado! I think your link may have solved it. I'll look in to it a bit in the future. Amazing how an Firestick turned me to Chinese TV boxes which are quite capable once you get rid of the Spyware. What I will say is, I think these boxes may have poor solder joints on the WiFi sub board, was hoping it was a misconfiguration my 8G model no longer recognizes the Wifi board, when I get the SD card holders I'll reflow it ad see. dmesg, lsusb, lspci know nothing of it. my 2G box the WiFi is fine. Regards

@emor acid you could also edit the dts and compile a dtb. Then transfer it to your sdcard. https://stackoverflow.com/questions/21670967/how-to-compile-dts-linux-device-tree-source-files-to-dtb

I know this is older, but you need fping6 as well. See inside my install script for Zabbix server https://github.com/sgjava/install-zabbix/blob/589abd9527b1dbd505776a4c80afe8e515aef878/scripts/install.sh#L210

Can you use @Nick A instructions?