Active threads

It has been tried several times with similar results : On stable 6.12.35 The lwfinger/rtl8821au driver causes kernel exceptions (oops/panics) It doesn't survive simple lsmod. On kernel 6.15.4 : It fails inserting : root@orangepiplus:~# sudo cp /var/lib/dkms/rtw88/0.6/build/*.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless/realtek/rtw88/ root@orangepiplus:~# ls -al /lib/modules/$(uname -r)/kernel/drivers/net/wireless/realtek/rtw88 total 23744 drwxr-xr-x 2 root root 4096 Aug 24 15:13 . drwxr-xr-x 6 root root 4096 Aug 21 21:02 .. -rw-r--r-- 1 root root 961676 Aug 24 15:13 rtw_8703b.ko -rw-r--r-- 1 root root 415924 Aug 24 15:13 rtw_8723cs.ko -rw-r--r-- 1 root root 991580 Aug 24 15:13 rtw_8723d.ko -rw-r--r-- 1 root root 416088 Aug 24 15:13 rtw_8723ds.ko -rw-r--r-- 1 root root 419968 Aug 24 15:13 rtw_8723du.ko -rw-r--r-- 1 root root 492256 Aug 24 15:13 rtw_8723x.ko -rw-r--r-- 1 root root 929420 Aug 24 15:13 rtw_8812a.ko -rw-r--r-- 1 root root 424112 Aug 24 15:13 rtw_8812au.ko -rw-r--r-- 1 root root 1271964 Aug 24 15:13 rtw_8814a.ko -rw-r--r-- 1 root root 420676 Aug 24 15:13 rtw_8814au.ko -rw-r--r-- 1 root root 900128 Aug 24 15:13 rtw_8821a.ko -rw-r--r-- 1 root root 422752 Aug 24 15:13 rtw_8821au.ko -rw-r--r-- 1 root root 1025348 Aug 24 15:13 rtw_8821c.ko -rw-r--r-- 1 root root 415504 Aug 24 15:13 rtw_8821cs.ko -rw-r--r-- 1 root root 421624 Aug 24 15:13 rtw_8821cu.ko -rw-r--r-- 1 root root 1217480 Aug 24 15:13 rtw_8822b.ko -rw-r--r-- 1 root root 415504 Aug 24 15:13 rtw_8822bs.ko -rw-r--r-- 1 root root 425156 Aug 24 15:13 rtw_8822bu.ko -rw-r--r-- 1 root root 1734256 Aug 24 15:13 rtw_8822c.ko -rw-r--r-- 1 root root 415504 Aug 24 15:13 rtw_8822cs.ko -rw-r--r-- 1 root root 420196 Aug 24 15:13 rtw_8822cu.ko -rw-r--r-- 1 root root 666896 Aug 24 15:13 rtw_88xxa.ko -rw-r--r-- 1 root root 7900876 Aug 24 15:13 rtw_core.ko -rw-r--r-- 1 root root 575660 Aug 24 15:13 rtw_sdio.ko -rw-r--r-- 1 root root 560804 Aug 24 15:13 rtw_usb.ko root@orangepiplus:~# sudo depmod -a $(uname -r) root@orangepiplus:~# sudo modprobe rtw_8821au modprobe: ERROR: could not insert 'rtw_8821au': Exec format error Aug 24 15:14:25 orangepiplus kernel: module rtw_core: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time

hello @Nick A, have you read the last post i posted? When i was messing around on my box, i saw that the box only have 1200mhz freqency (note that this is allwinner h313) while h313 max freq is 1350mhz, and mine is 1200mhz, is the h313 nerfed by the firmware? Or anything else? edit: full cpu formation here

Find a DTS that uses compatible="waveshare,rpi-lcd-35" and try again (I don't use that LCD, so I am not sure... but I know it is special because it contains a SPI-to-parallel chip)

Thanks for the suggestion, I appreciate it. Unfortunately it didn't do anything. I've tried the args one at a time, combined, still nothing. One thing I noticed, I can consistently get the nvme to properly show up, during the first boot of radxa's image. (ie. flashing the radxa image to an SD, booting for the first time to the desktop, the nvme will be detected and work properly). Rebooting after that is a hit or miss and generally only cold boots sometimes work. I also tried the args you suggested in the radxa official image and still the same. Btw for everything I mention, the armbian SPI image was installed. My only assumption is that some irrelevant delay related to the first boot, gives time for the nvme to initialize? On subsequent boots I get "pcie link fail" during boot, and again, lspci works, lsblk doesn't. Also I would like to use armbian ubuntu desktop which I can't at the moment, since the noble gnome image doesn't boot at all.

https://linux-sunxi.org/Tanix_TX1 Piotr's github is easy enough to google for those who need it.

https://paste.armbian.com/ehuwawexih v25.5.1 image (Debian Bookworm minimal) runs on my Cubox i4, but HDMI out is untested ... images were released, only because I manage to spent some time testing and as I found out that build actually works.

I also encountered this trouble with image corruption. Here's my small research I've made: 1. This appears to be for newer images witch use GPT schema instead of MBR one. I've tried to flash same SD cards (Transcend 1x A1 & 2x A2 class) with orangepi zero2w image from community support build which still comes with MBR schema and had no trouble at all. I've used Rufus 4.9, USBImager and dd from WSL2 for tests. Whoever, images for orangepi 3b & orangepi 5plus already comes with GPT partition schema and flashing them with any software in all combinations of eject time or way (safe or not) always lead to broken GPT table and initramfs on SBC boot. 2. I'm using WSL2 with Ubuntu 24 LTS and usbipd for linking USB devices. After SD flash on Windows side with Rufus or USBImager I'm attach SD card to WSL2 and check it state immediately (on attach windows side does not see usb device anymore). Here's log of this actions (I'm out of free SD cards so first part with image will be from regular USB flash drive). Rufus output: Opened \\.\PhysicalDrive2 for exclusive write access Requesting logical volume handle... ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Opened \\.\PhysicalDrive2 for shared write access Timeout while waiting for logical drive Found USB 3.0 device 'Kingston DT microDuo 3C USB Device' (0951:16AE) No logical drive found (unpartitioned?) 1 device found No volume information for drive 0x82 Disk type: Removable, Disk size: 64 GB, Sector size: 512 bytes Cylinders: 7538, Tracks per cylinder: 255, Sectors per track: 63 Partition type: GPT, NB Partitions: 1 Disk GUID: {61DF6BA5-465D-4529-80C4-5D4BB9D0852F} Max parts: 128, Start Offset: 1048576, Usable = 62007524864 bytes Partition 1: Type: Linux Boot Partition (ARM64) Name: 'rootfs' Detected File System: ext4 ID: {22DE0E86-86CD-4366-AF3C-07E25D0E77FA} Size: 5.9 GB (6382682112 bytes) Start Sector: 32768, Attributes: 0x0000000000000000 WSL2 bind & attach process: PS C:\Users\mevep> usbipd list Connected: BUSID VID:PID DEVICE STATE 2-8 0403:6001 USB Serial Converter Not shared 2-23 0951:16ae USB Mass Storage Device Shared PS C:\Users\mevep> usbipd bind --busid 2-23 PS C:\Users\mevep> usbipd attach --wsl --busid=2-23 usbipd: info: Using WSL distribution 'Ubuntu-20.04' to attach; the device will be available in all WSL 2 distributions. usbipd: info: Loading vhci_hcd module. usbipd: info: Detected networking mode 'nat'. usbipd: info: Using IP address 172.21.16.1 to reach the host. Rufus output after attach to WSL2: 0 devices found WSL2 sudo parted -l output: /mnt/c/Users/mevep$ sudo parted -l Error: The primary GPT table is corrupt, but the backup appears OK, so that will be used. OK/Cancel? OK Model: Kingston DT microDuo 3C (scsi) Disk /dev/sdg: 62.0GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 16.8MB 6399MB 6383MB ext4 rootfs Trying to mount: /mnt/c/Users/mevep$ sudo mount /dev/sdg1 /mnt/mp mount: /mnt/mp: special device /dev/sdg1 does not exist. dmesg(1) may have more information after failed mount system call. gdisk output: /mnt/c/Users/mevep$ sudo gdisk /dev/sdg GPT fdisk (gdisk) version 1.0.10 Caution! After loading partitions, the CRC doesn't check out! Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: OK Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Recovery/transformation command (? for help): v Problem: The CRC for the main partition table is invalid. This table may be corrupt. Consider loading the backup partition table ('c' on the recovery & transformation menu). This report may be a false alarm if you've already corrected other problems. Warning: There is a gap between the main metadata (sector 1) and the main partition table (sector 2016). This is helpful in some exotic configurations, but is generally ill-advised. Using 'j' on the experts' menu can adjust this gap. Identified 1 problems! Output after gdisk r c w commands (everything is ok now): Recovery/transformation command (? for help): c Warning! This will probably do weird things if you've converted an MBR to GPT form and haven't yet saved the GPT! Proceed? (Y/N): Y Recovery/transformation command (? for help): W Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): Y OK; writing new GUID partition table (GPT) to /dev/sdg. The operation has completed successfully. /mnt/c/Users/mevep$ sudo parted -l Model: Kingston DT microDuo 3C (scsi) Disk /dev/sdg: 62.0GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 16.8MB 6399MB 6383MB ext4 rootfs /mnt/c/Users/mevep$ sudo mount /dev/sdg1 /mnt/mp /mnt/c/Users/mevep$ ls /mnt/mp bin boot etc lib lost+found mnt proc run sbin.usr-is-merged snap sys usr bin.usr-is-merged dev home lib.usr-is-merged media opt root sbin selinux srv tmp var Also I have UART logs of trying to boot from SD card SBC without any changes after image burn, but nothing interesting there - it just goes initramfs after kernel boot start process. Added log file to this post for orangepi 3b. Same appears for orangepi 5plus. Image built with armbian-build commit 1d89b0e1e0e6a8b053a94a41a8d0b961f38a9fae by me. COM6_2025_08_21.txtCOM6_2025_08_21.txt 3. After SD card recovery everything boots and works fine. Tested on custom build images with armbian-build commit 1d89b0e1e0e6a8b053a94a41a8d0b961f38a9fae for orangepi 3b & 5plus. 4. I'm on Windows 11 24H2 Maybe it will help somehow :^)

This is an orange Pi zero with an H3 chip. I can't make sense out of the part numbers. But it's a zero, it is square, it has an ethernet and wifi, and has an H3 chip right on the top of the thing. The device tree says model = "Xunlong Orange Pi PC Plus"; compatible = "xunlong,orangepi-pc-plus\0allwinner,sun8i-h3"; The build I was running is the latest I could find [ 0.000000] Linux version 6.12.35-current-sunxi (build@armbian) (arm-linux-gnueabihf-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Fri Jun 27 10:11:46 UTC 2025 So whatever it says in the boot log and in the armbian monitor (which I included as a link in my original post) is what this is. And there is no ethernet or wifi on it, nor has there ever been since I bought it maybe 4 or 5 years ago. Every few years I try the latest build and check to see if that fixes it, and it never seems to happen. arbmianmonitor.log bootmaybeowkring.log

bananaoi-m5, Armbian 25.8.1 bookworm installed I can login via ssh as first user, gene, and sudo -i just fine. Buuuttttttt, at reboot the local screen ask's for the pw for amandabackup, a user lock down tightly which has never had a pw assigned. as its intended to be pw--less for the amanda backup system. What miss-configure can cause this????? Also I ordered 2 more of the keyboard/mouse combo''s which are the same as I'm using with a similar install for klipper running a 3d printer, but the dongle doesn't init when plugged in ack dmesg output, refusing its on discovery assigned address. So no keyboard/mouse is locally possible. I'll unpack the 2nd identical copy and see if its also broken. Switching back to an ultra- micro sized keyboard with a touchpad mouse works fine. And the second keyboard/mouse works as expected. The pw gizmo ask's for amandabackup's pw, I gave it my first user pw which it accepted logging me in normally. So I typed whoami and it responded gene. So wth is confusing the login requester????????? Many Thanks for any assistance. And why do I have to say solved in order to post when its not solved?? Counter productive to other readers.

That is basically what I have been doing. I reconstructed image/partitions to have bootfs and rootfs separated. Typically format bootfs as simple FAT where you can fix things even on Windows computers maybe when SD-cards. For new fast SBCs I just have many partitions on NVMe where various Linux distros rootfs are and just copy or rename armbianEnv.txt which is then essentially only a UUID of a rootfs. When I know the SBC well enough, it is more the kernel only that matters, so i made a extlinux.conf generator so I can select a kernel via U-Boot serial console. I don't see what A+B brings me as I use Btrfs for rootfs and use snapper to make 'last-known-good' snapshots and also transfer those to NAS or so. If you want totally unattended, then A+B is an option, look at Android as well I would say. But more towards PC like systems, one can put efi bootloader (efi-grub) on the bootFAT, that allows you to select last-known-good more or less if you deploy snapshots. I usually do update in-place, so more like rolling release, but you can also do updates on a new read-write snapshot and fallback if it would fail to boot, see https://kubic.opensuse.org/documentation/man-pages/transactional-update.8.html for example how that works. U-Boot also has options I think to get to last-known-good automatically, but I don't know how that would work. For my stuff at home, it is good enough that I can quickly go back to older snapshot and that works for more than a decade on my PCs, so I do the same on SBCs/embedded, as long as they have a serial console cable (or HDMI,keyboard). For the NanoPi-NEO I also had Btrfs capable U-Boot, so then U-Boot can directly boot a certain rootfs partition, but it is not really default, so I keep an extra bootFAT.

Fresh Orangepi 5 image, this one: https://netcup-01.armbian.com/incoming/efectn/orangepi5/archive/Armbian_25.8.1_Orangepi5_noble_vendor_6.1.115_gnome_desktop.img.xz Your setup could be broken to some degree, but hard to tell what is missing.

Yes, I did read that. I was also thinking maybe the decompression on-the-fly could be a point of failure. Just now, I installed USBImager and wrote the image to a uSD. No presets applied (.not_looged_in_yet) First boot went smoothly. I updated with armbian-upgrade and rebooted and all looked OK. 🤷🏻‍♂️ Since I changed 2 things (using USBImager and no presets) I can't say what helped.

You need an overlay for that camera and 6.1.115-vendor-rk35xx does not have that AFAIR, older legacy 5.10 has it AFAIR. Look for something called RPi camera v1 or that sensor name.

armbian-config : System > Storage > "STO001 - Install" or directly nand-sata-install You will get │ │ 1 Boot from SD - system on SATA, USB or NVMe │ │ │ │ 2 Boot from eMMC - system on eMMC │ │ │ │ 3 Boot from eMMC - system on SATA, USB or NVMe │ │ │ │ 4 Boot from MTD Flash - system on SATA, USB or NVMe │ │ │ │ 5 Install/Update the bootloader on SD card (/dev/mmcblk1) │ │ if you select boot from eMMC I think the installer will replace RoobiOS u-boot (and I guess Roobi Boot Menu) with Armbian U-Boot. I still need to experiment with Roobi OS (i.e. if there is a bootloader in SPI flash like on PC instead of only on eMMC). But you might want to try "boot from SD - system on NVME" and keep the Armbian bootloader on SD with the SD card kept plugged. If you install the bootloader on the eMMC likely you won't get the Roobi Boot menu anymore. About the boot priority, I guess it is written in the Radxa doc. It depends on how they configured their U-Boot.

Ok, that draft was way more complicated than it should and there's an easier way, also we need to logout and login again for the extension to show. Is it a problem if we restart GNOME shell during install? Here's a better script: 1 #!/bin/bash 2 git clone --depth=1 https://github.com/fthx/no-overview.git 3 NO_OVERVIEW=$(jq -r .uuid no-overview/metadata.json) 4 gnome-extensions pack no-overview 5 gnome-extensions install $NO_OVERVIEW.shell-extension.zip 6 # Restart GNOME shell 7 gnome-extensions enable $NO_OVERVIEW in line 6, I found the following: https://github.com/brunelli/gnome-shell-extension-installer/blob/4357903be8646d940902852bf3e150f625e350e6/gnome-shell-extension-installer#L288 This is not doable in Wayland from what I read around... so this will install, and the user will have to enable it manually.

Any luck? my tx1 is in the mail.

@Nick AI tried to extract the dts from the working image, cloud you help me find any clues. Thank you. I was able to gain access to the os that works, this is the dmesg: dmesg | grep eth [ 8.550757] libphy: 5020000.eth: probed [ 8.568109] sunxi-gmac 5020000.eth eth0: eth0: Type(8) PHY ID 001cc916 at 0 IRQ poll (5020000.eth-0:00) [ 12.765916] sunxi-gmac 5020000.eth eth0: Link is Up - 1Gbps/Full - flow control off [ 12.775526] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready I also upload the pic of ethernet chip. dts.zip

That part of the instructions is clear. It's the steps involving the "wipe_part" file that supposedly erases partitions on the eMMC and the flashing of the second loader file that I can't make out. It looks like the instructions were edited to make them unusable. Nicolas has had the same issue in the H96 subforum with bad instructions and people asking for help due to the lack of clarity. I was able to make the board boot from SD card after flashing it with the YYT provided Debian 11 image, but only to Armbian Noble. No Debian distros work. When a Debian SD is inserted, the board boots then enters a systemd-devd shell with error messages about a UUID not being found. All Debian images do the same, I think it has to do with the eMMC memory not being seen because it is still formatted and not cleared. I have never seen a shell like this. Armbian Noble still boots properly, but only Noble. I need a Debian minimal distro in order to install OpenMediaVault and save my friend's files.

Try with one additional parameter: EXTRAWIFI="no"

@Piotr syou can try this build it’s based on the 6.14 kernel. Only issue I know of is audio using the a/v port. https://github.com/NickAlilovic/build/tree/v20250407

@ARx8if need help fixing the sd card. Login to IRC and ask the sunxi guys. https://oftc.catirclogs.org/linux-sunxi/2025-08-20

@Trung Nguyễn git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "x98h" choose "edge" rest is up to you. Your image should be in output/images directory.

Outdated kernel. overlays were probably added later https://github.com/armbian/linux-rockchip/tree/rk-6.1-rkr5.1/arch/arm64/boot/dts/rockchip/overlay

@darcyg @ Hqnicolas rk3576-h96-m9s.dts rk3576 -h96-m9s-linux.dtsi armsom-sige5-rk3576_defconfig 1.Reset button in UBOOT OK 2. video acceleration OK work.。kodi video acceleration Armbian-unofficial_25.11.0-trunk_H96-m9_bookworm_vendor_6.1.115-backported-mesa.img https://drive.google.com/drive/folders/1lzLwm9NhxZ_0_mghKG4A0XQ6NNsU9sn-?usp=drive_link kodi https://github.com/armsurvivors/kodi-rockchip-deb 3. When turning off the box, the lights are still on. Probably - it is not really turned off. 4. No wifi No Bluetooth

Never too late to express gratitude and say "Thank you for sharing your findings"