Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. @Werner - When the Armbian Official Nobel upgrades it has the same issue.
  3. Today
  4. I modified the armbianEnv.txt file : verbosity=1 extraargs=coherent_pool=2M bootlogo=false overlay_prefix=rk322x fdtfile=rk322x-box.dtb rootdev=UUID=87d2bf72-4b91-4d33-8f77-284fa91fc3a7 rootfstype=ext4 extraargs=drm_kms_helper.edid_firmware=HDMI-A-1:edid/1920x1080.bin video=HDMI-A-1:1920x1080@60 drm.debug=0x4 overlays= usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u This is apparently preventing the tv box from booting, I lost access. I will have to flash it again with the multitool to get back in, and this will have to wait on monday, since I was remoting into it at the office. Thanks for your help!
  5. Can you check if you can pass drm.debug=0x4 to the kernel command line and see if you get more info ? If yes, paste here the boot log.
  6. Thanks for the hint Sirmalinton. Today, I could solve the problem. Here is a short summary that might be of use for people running into similar issues. Running lspci -k shows the "Non-Volatile memory controller" but it does not show the line "Kernel driver in use: nvme". Hence, I ran echo nvme > /sys/bus/pci/devices/0002\:01\:00.0/driver_override echo 0002:01:00.0 > /sys/bus/pci/drivers_probe where 0002:01:00.0 is from the output of lspci -k. That worked and made the disk appear as files /dev/nvme0*. To have a solution that works after reboot, I created a udev rule /etc/udev/rules.d/99-nvme-override.rules with the content: ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x144d", ATTR{device}=="0xa80d", ATTR{driver_override}="nvme" The vendor and device IDs are from lspci -nn. To trigger the probe, I created a systemd service /etc/systemd/system/nvme-rebind.service with the content: [Unit] Description=Rebind NVME controller to driver after override After=udev.service [Service] Type=oneshot ExecStart=/bin/sh -c "echo 0002:01:00.0 > /sys/bus/pci/drivers_probe" [Install] WantedBy=multi-user.target The service can be enabled via systemctl enable nvme-rebind.service. Maybe one reason it does not work in the first place is because /lib/systemd/system/nvmefc-boot-connections.service is not started. The reason is that the condition ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery is not met. Another reason, I can imagine is that the vendor/device ID combination is not registered to the nvme driver in the current kernel. As I mentioned before, it did work out of the box when I installed Armbian at first.
  7. Well, since this same edid file I use on the Libre Renegade board works perfectly fine with this same monitor, I think the file is ok. This link you provide is the one I followed, I tried most of the things in there, as well as a bunch of stuff I found from other users. Again, since this works on U-Boot, this points at something defective on Armbian and how the edid communication happens. This Armbian kernel that came with the armbian image I downloaded it from the armbian github as a part of the image I use on my device. I did not build it. I would think it was the Armbian team, correct?
  8. More like a kernel issue than Armbian. The Armbian supplied edid bin file probably does not match your monitor's. Take a look here on how to get the actual edid and force it: https://wiki.archlinux.org/title/Kernel_mode_setting#Forcing_modes_and_EDID
  9. Yes, The 1920x1080.bin file comes with Armbian. I use the multitool to flash https://github.com/armbian/community/releases/download/25.8.0-trunk.309/Armbian_community_25.8.0-trunk.309_Rk322x-box_bookworm_current_6.12.35_minimal.img.xz , this is the latesst build. On a Libre Renegade board I have (rk3328 CPU instead of rk3228 for this TV box), I have the same issue where it reverts to 1024x768, and adding the line extraargs=drm.edid_firmware=edid/1920x1080.bin to armbianEnv.txt fixes the issue, with the Armbian provided 1920x1080.bin file. To me, since it works fine under U-Boot, this hints at an Armbian bug.
  10. @Igor thank you for fixing overlay-prefix problem in current armbin-config now on OZPI V1 and V3 overlays in armbianEnv.txt are without prefix
  11. Do you actually have this edid file : edid/1920x1080.bin ? How did you generate it?
  12. Use `vendor` kernel and enable hdmirx overlay.
  13. Another good thing : previously, the A20 CPU load never goes below 1 due to something wrong in the kernel. It's now corrected. I can confirm also it is corrected : I upgraded my ArchARM BananaPI and the HDMI is back as well.
  14. Hello all! I have a radxa rock 5b (8GB, not the plus version) and am running armbian (bookworm) on it. The kernel version (uname -r) reports as 6.12.32-current-rockchip64. By and large almost everything seems to be working - video playback in VLC is fine, 3d acceleration is working (I get around 58-60fps in the game 'torcs' as an example). The only thing I can't seem to get working (and can't find much about it) is the hdmi input. I see some five devices listed in dev (from /dev/video0 to /dev/video4) although none of these seem to relate to the hdmi input. Does the hdmi input work on the 5b under armbian at all? thanks ljones
  15. Most Armbian systems use a file located at /boot/armbianEnv.txt. You can add kernel parameters using the extraargs line.
  16. thread about video in case anyone is looking for it and a recent 'success story'
  17. I juste installed it, and it's pretty working 🥰 # wget https://armbian.lv.auroradev.org/beta/pool/main/l/linux-6.12.35/linux-image-current-sunxi_25.8.0-trunk.346_armhf__6.12.35-S783c-Dbdda-Pf7b7-C34a1Hf8af-HK01ba-V014b-Ba566-R448a.deb # apt install ./linux-image-current-sunxi_25.8.0-trunk.346_armhf__6.12.35-S783c-Dbdda-Pf7b7-C34a1Hf8af-HK01ba-V014b-Ba566-R448a.deb My dashboard is back ! Trying to update my arch with the latest kernel ... ps: in addition, if someone knows how to disable cursor blinking on this HDMI, it would be fine (I already disabled getty on it, but the cursor remain).
  18. Can someone tell me if Linux 6.14.8 or 6.15.4 supports this hardware acceleration? I can play 1080p H264, but with 100% CPU, with 6.14.8... and I get "unsuppoerted hwdec: drm" everytime I start mpv
  19. It is now half a year later, this SD-card was put back into the RPi4 and no issues there. The RPi4 has been upgraded from Bookworm to Trixie in-place (just latest pre-release) so gets quite some writes. It still has Bookworm Btrfs snapshot as well, total of about 9GB excluding 2GB swap partition and 512MB bootFAT. Avarage Btrfs scrub speed 41MB/s. The ROCK3A has no SD-card inserted anymore, running fine, except that in the last 40 days I see: root@rock3a:~# uname -a Linux rock3a 6.1.115-vendor-rk35xx #1 SMP Fri May 30 01:18:17 UTC 2025 aarch64 GNU/Linux root@rock3a:~# dmesg | grep "page allocation failure:" [ 527.016616] dmcrypt_write/2: page allocation failure: order:0, mode:0x800(GFP_NOWAIT), nodemask=(null),cpuset=/,mems_allowed=0 [2879228.441453] dec0:0:hevc_rkm: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=user.slice,mems_allowed=0 [2879523.127829] dec0:0:hevc_rkm: page allocation failure: order:5, mode:0x40dc0(GFP_KERNEL|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=user.slice,mems_allowed=0 [3029341.482298] kworker/0:1: page allocation failure: order:0, mode:0x800(GFP_NOWAIT), nodemask=(null),cpuset=/,mems_allowed=0 The middle 2 is clear what source is, the others I do not know. I think I will first upgrade userspace to Trixie. I currently have no clue what the details w.r.t. page faults mean, so have to see and figure out what issue could be or maybe mitigate somehow.
  20. Does this happen with Bookworm or Noble? Plucky userspace is unsupported.
  21. Yes it is dead, that is why my comments between brackets. Start with http://beta.armbian.com then click with your mouse per sub object. Or wait until it is out of beta phase or modify your sources.list.d
  22. Currently using Armbian as a PiHole DNS server, it seems that after a few days the server just shuts itself down (Armbian 25.5.1 Noble 6.12). Not sure if it is a hardware related issue, I'll do some more tests and revert back to 25.2.2 Bookworm for now and see if the issue is replicated. Please note that my primary Armbian PiHole DNS does not encounter the same issue, though the version of it is Noble v25.2.3 / 6.12.30.
  23. @JuanEsf Yep, here it is a080ed7128c898bec1cad6ec68c57bae159169d2fa06fb18008100ad63e4445c
  24. You are right, this is a strange DTS issue. U-Boot is working, but the kernel can't initialize the SD card, which is why it drops to the initramfs shell. Unfortunately, I can't reproduce this specific error myself, but I agree with your analysis. I suspect this is the same reason why newer U-Boot versions initially failed to boot for me. I will start working on fixing the DTS next week. Thanks for finding this bug!
  25. @C127I just saw that @whywontitworkmessage and decided to try your image(0.3) directly in the sdcard ( emmc removed ) and that image does not boot. The UART is also stuck in starting kernel as mentioned by @whywontitwork, but I can get the HDMI output and the boot process drops to a initramfs shell because it can not find the root device. This is the console log. DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 ch0 ttot7 LPDDR5, 2400MHz channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch1 ttot7 channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch2 ttot7 channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB ch3 ttot7 channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB Manufacturer ID:0xff DQS rds:h1,l0 CH0 RX Vref:24.6%, TX Vref:22.0%,22.0% DQ rds:h5 h2 h1 h2 h1 h4 l0 h7, h1 h1 h3 h3 h1 h1 h7 l0 DQS rds:l0,h2 CH1 RX Vref:27.9%, TX Vref:21.0%,21.0% DQ rds:h4 l0 h2 h3 h6 l0 h7 l0, h7 h4 h4 h4 l1 h1 h6 h7 DQS rds:l0,h2 CH2 RX Vref:25.0%, TX Vref:21.0%,21.0% DQ rds:h1 l0 h2 l2 h1 h1 h5 h1, l1 h6 l1 h3 l2 h1 h1 h2 DQS rds:l0,h1 CH3 RX Vref:27.9%, TX Vref:20.0%,20.0% DQ rds:h3 h1 h2 h1 h4 h1 h1 h1, h4 h7 h2 h2 h3 h5 l0 h5 stride=0x2, ddr_config=0x6 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0x0 0x2400 0x44800 0x89000, rank_mask0 0x2000 change to F1: 534MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F2: 1320MHz ch0 ttot8 ch1 ttot8 ch2 ttot8 ch3 ttot8 change to F3: 1968MHz ch0 ttot6 ch1 ttot6 ch2 ttot6 ch3 ttot6 change to F0: 2400MHz ch0 ttot7 ch1 ttot7 ch2 ttot7 ch3 ttot7 out U-Boot SPL 2024.04-armbian-2024.04-S2504-Pa35d-H29de-Vbf83-Bb703-R448a (Jul 02 2025 - 19:31:47 +0000) Trying to boot from MMC1 ## Checking hash(es) for config config-1 ... OK ## Checking hash(es) for Image atf-1 ... sha256+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image fdt-1 ... sha256+ OK ## Checking hash(es) for Image atf-2 ... sha256+ OK ## Checking hash(es) for Image atf-3 ... sha256+ OK INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x13 INFO: code: 0x88 INFO: ext 32k is valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: bypass memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 INFO: dfs DDR fsp_params[0].freq_mhz= 2400MHz INFO: dfs DDR fsp_params[1].freq_mhz= 534MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1320MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1968MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 ns16550_serial serial@feb50000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.04-armbian-2024.04-S2504-Pa35d-H29de-Vbf83-Bb703-R448a (Jul 02 2025 - 19:31:47 +0000) Model: Xunlong Orange Pi 5 Pro DRAM: 16 GiB (effective 15.7 GiB) Core: 323 devices, 30 uclasses, devicetree: separate MMC: mmc@fe2c0000: 0 Loading Environment from nowhere... OK In: serial@feb50000 Out: serial@feb50000 Err: serial@feb50000 Model: Xunlong Orange Pi 5 Pro rockchip_dnl_key_pressed: no saradc device found Net: eth0: ethernet@fe1c0000 Hit any key to stop autoboot: 0 Scanning for bootflows in all bootdevs Seq Method State Uclass Part Name Filename --- ----------- ------ -------- ---- ------------------------ ---------------- Scanning global bootmeth 'efi_mgr': No EFI system partition No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables No EFI system partition Failed to persist EFI variables 0 efi_mgr ready (none) 0 <NULL> ** Booting bootflow '<NULL>' with efi_mgr Loading Boot0000 'mmc 0' failed EFI boot manager: Cannot load any image Boot failed (err=-14) Scanning bootdev 'mmc@fe2c0000.bootdev': 1 script ready mmc 1 mmc@fe2c0000.bootdev.part /boot/boot.scr ** Booting bootflow 'mmc@fe2c0000.bootdev.part_1' with script Boot script loaded from mmc 0:1 200 bytes read in 4 ms (48.8 KiB/s) 15754859 bytes read in 1321 ms (11.4 MiB/s) 39287296 bytes read in 3289 ms (11.4 MiB/s) 162018 bytes read in 28 ms (5.5 MiB/s) Working FDT set to 12000000 Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' ## Loading init Ramdisk from Legacy Image at 12180000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15754795 Bytes = 15 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 12000000 Booting using the fdt blob at 0x12000000 Working FDT set to 12000000 Loading Ramdisk to ebf92000, end ece9862b ... OK Loading Device Tree to 00000000ebf02000, end 00000000ebf91fff ... OK Working FDT set to ebf02000 Starting kernel ... Setting loglevel=8 and verbose=8 shows this is console: [ 2.028301] dwmmc_rockchip fe2d0000.mmc: IDMAC supports 32-bit address mode. [ 2.029020] dwmmc_rockchip fe2d0000.mmc: Using internal DMA controller. [ 2.029624] dwmmc_rockchip fe2d0000.mmc: Version ID is 270a [ 2.030163] dwmmc_rockchip fe2d0000.mmc: DW MMC controller at irq 84,32 bit host data width,256 deep fifo [ 2.031384] dwmmc_rockchip fe2d0000.mmc: allocated mmc-pwrseq [ 2.031921] mmc_host mmc2: card is non-removable. [ 2.217056] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 2.250531] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.376463] mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0) [ 2.409028] dwmmc_rockchip fe2d0000.mmc: Successfully tuned phase to 223 [ 2.423188] mmc2: new UHS-I speed SDR104 SDIO card at address 0001 [ 2.953845] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ 2.991412] mmc0: error -110 whilst initialising SD card [ 3.527479] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 4.257059] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ 4.271710] mmc_host mmc0: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 4.831481] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 5.560980] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000) [ 5.575632] mmc_host mmc0: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 6.140278] dwmmc_rockchip fe2c0000.mmc: Busy; trying anyway [ 6.869893] mmc_host mmc0: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
  26. Yes, it works correctly debian@orangepi5pro:~$ lsusb -t ... /: Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 001: Dev 002, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
  27. @C127I forgot to ask. Is USB3 port working for you in your kernel ?
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines