Barmaleykin Posted February 12 Share Posted February 12 Hi all! I have a problem with Armbian images on kernel 5.10.160 (jammy & bookworm Armbian_23.11.1_Orangepi5-plus_***_5.10.160.img) When starting from the SD card the nvme device is not visible root@orangepi5-plus:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk1 179:0 0 58G 0 disk ├─mmcblk1p1 179:1 0 256M 0 part /boot └─mmcblk1p2 179:2 0 57.1G 0 part /var/log.hdd / mmcblk0 179:32 0 233G 0 disk mmcblk0boot0 179:64 0 4M 1 disk mmcblk0boot1 179:96 0 4M 1 disk zram0 254:0 0 7.7G 0 disk [SWAP] zram1 254:1 0 50M 0 disk /var/log but some other distros for opi5+ see nvme fine (official img, from Joshua-Riek, etc..) After playing with different distros, I noticed that the latest builds of the 5.10.160 kernel do not see it, but early kernel builds work quite well with nvme. I still haven’t been able to get the board to start from nvme on any distribution. The SPI is flashed correctly. I can start only from SD or eMMC Has anyone encountered a similar problem on opi5+/16GB ? 0 Quote Link to comment Share on other sites More sharing options...
ozacas Posted March 27 Share Posted March 27 Maybe sudo armbianmonitor -u might help shed some light about what is going on - perhaps there is an issue with the device or driver? But no problems for me with the arm64 uefi image on my opi5+ 16GB - acas@opi:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS zram0 252:0 0 7.7G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk nvme0n1 259:0 0 1.8T 0 disk ├─nvme0n1p1 259:1 0 259M 0 part /boot/efi └─nvme0n1p2 259:2 0 1.8T 0 part /var/log.hdd / 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.