zjd

@wizetek Do u see cursor flickering with this? Even though I believe this is valid workaround.

@Efe ÇetinI am using xorg, mostly with KDE, sometimes xfce. Cursor disappear issue is not always reproduced, but more likely after idle for some time, monitor was turned off, when it was turned on by key stroke or mouse movement, cursor no longer appeared, starting from lock screen. I can see cursor is still there as when it moved to max/min button of a window, the button was highlighted so it is just a display issue. Thanks!

Thanks! I reverted this change and cursor looks OK so far, at least usable. But I think there is cursor flickering issue with sw cursor. It would be better to fix HW cursor though.

I still found that cursor disappears occasionally, enabling 3d or not, mostly when coming back after long idle. I am using 23.02.0-trunk.0152. I suspect that it is related to enabling HW cursor in this patch https://github.com/armbian/build/blob/master/patch/kernel/rockchip-rk3588-legacy/2009-OrangePi5-HDMI-Improvements.patch, that is, HW cursor might have issue. --- a/arch/arm64/boot/dts/rockchip/rk3588s-orangepi.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3588s-orangepi.dtsi @@ -578,19 +578,29 @@ &vepu { &vp0 { rockchip,plane-mask = <(1 << ROCKCHIP_VOP2_CLUSTER0 | 1 << ROCKCHIP_VOP2_ESMART0)>; rockchip,primary-plane = <ROCKCHIP_VOP2_ESMART0>; + cursor-win-id = <ROCKCHIP_VOP2_CLUSTER0>; }; &vp1 { rockchip,plane-mask = <(1 << ROCKCHIP_VOP2_CLUSTER1 | 1 << ROCKCHIP_VOP2_ESMART1)>; rockchip,primary-plane = <ROCKCHIP_VOP2_ESMART1>; + cursor-win-id = <ROCKCHIP_VOP2_CLUSTER1>; }; &vp2 { rockchip,plane-mask = <(1 << ROCKCHIP_VOP2_CLUSTER2 | 1 << ROCKCHIP_VOP2_ESMART2)>; rockchip,primary-plane = <ROCKCHIP_VOP2_ESMART2>; + cursor-win-id = <ROCKCHIP_VOP2_CLUSTER2>; }; &vp3 { rockchip,plane-mask = <(1 << ROCKCHIP_VOP2_CLUSTER3 | 1 << ROCKCHIP_VOP2_ESMART3)>; rockchip,primary-plane = <ROCKCHIP_VOP2_ESMART3>; + cursor-win-id = <ROCKCHIP_VOP2_CLUSTER3>; +}; I am trying to revert this change but not family with armbian building. Where can I pull a kernel tree to apply patches and build a dtb? I am familiar with kernel but am wondering if there is a more convenient way for armbian.

If you can't boot from SD either, you should be able to goto maskrom mode (there is a hw button for that) and erase SPI then booting from SD. Here is Rock 5B reference https://wiki.radxa.com/Rock5/install/spi. OPi5 manual has similar information too.

@royk Yeah, rootdev is armbianEnv.txt should be updated to correct UUID of bootfs in NVMe. I used lazy way to do that too: rootdev=/dev/nvme0n1p1 😀 too

You probably have to wait for @Efe Çetin 's PR merged to have ready-to-use image. Or you can download these 2 debs to OPi5, run "dpkg -i <deb name>" to install and copy /boot/* to /dev/nvme0n1p1.

@royk I didn't try your method: -- Modify rootdev in armbianEnv.txt is the same as your boot.cmd change and is preferred way to customize boot parameter. -- I did try dd image directly to NVMe SSD and it worked. Now I have some data on rootfs of SSD, I prefer to use separate partition for testing, by selecting different one when running armbian-install.

@wizetek > 4. In 1920x1080 everything looks abnormally scaled and huge. Decreasing DPI below the "default" 96 in Xfce helps a little but it still doesn't look right. In appearance setting, default window scaling is 2, change to 1 can get normal look. Not sure why it is 2 by default.

Found one issue, mouse cursor sometimes disappeared, just not shown, still move around OK. Not always reproducible.

@Marco Schirrmeister Yeah, this is pretty much the same as I did. Just hope the manual steps will be incorporated into scripts soon!

@Efe Çetin Thanks! This works for me with 2K display! Is this included in latest image? Also bootfs is not auto-mount as /boot, it is a bit inconvenient to update files in bootfs.

Here is what I did to use NVMe SSD with Armbian image: 0) Prepare NVMe SSD You need at least 2 partitions: boot partition: /dev/nvme0n1p1, formatted as vfat rootfs: /dev/nvme0n1p2. as ext4. It actually can be other partition, not necessary the 2nd one. You can use fdisk/parted/... to create these partitions when booting from SD 0.1) (Optional) if you played with official image, SPI might have incomparable bootloader for Armbian, try erase it before using Armbian SD image sudo dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1 (1MiB looks good enough to disable previous bootloader) 1) Boot from Armbian image. I was using jammy-xfce image. Remember to finish up the setup. For some reason, it didn't detect my monitor properly, when screen is full, it doesn't scroll up, Had to press enter a lot to scroll screen and input correctly. Hope it can be fixed. (FYI. I am using 2K monitor) 2) In a terminal, run "armbian-install" Select "4) "boot from SPI, system on SATA, USB or NVMe" Select the partition for rootfs, format as EXT4 (didn't try btrfs) It will copy rootfs to that partition. Then it installs bootloader to SPI (mtdblock0) It will ask to reboot in the end, don't do it for now. 3) The script updates armbianEnv.txt with new rootfs config in current /boot, which is 1st partition in SD. Apparently boot partition in NVMe needs update. sudo mount /dev/nvme0n1p1 /mnt sudo cp -r /boot/* /mnt # You can also update armbianEnv.txt manually with "rootdev=/dev/nvme0n1p2" to point to correct NVMe rootfs partition. # FAT doesn't support symbol link cd /mnt sudo cp -r dtb-5.10.110-rockchip-rk3588 dtb sudo cp uInitrd-5.10.110-rockchip-rk3588 uInitrd sudo cp vmlinuz-5.10.110-rockchip-rk3588 Image 4) Now we can shutdown OPi5. Take out SD and boot to NVMe I haven't spent time to look into armbian-install, even though it is better than the script in official instruction, it needs improvements -- Need automatically update boot partition in NVMe, and armbianEnv.txt as well -- Maybe it is bootrom limitation, boot partition of NVMe can't be EXT4, therefore, symbol link is not available. It will require manual steps if future apt upgrade changes kernel/dtb/initramfs. Note that SD image does have EXT4 boot partition and it works fine. -- After running on NVMe, /boot partition is not automatically mounted as /boot, instead, /boot dir of rootfs will be updated if kernel/dtb/initramfs is updated. Manual update of boot partition is required. PS. I can only get 1080p GUI for now.