Hi all,
I recently bought a board which is used to connect NVMe to PCIe of the RPi5b. I wrote 20260209 image of the Tumbleweed then I connect NVMe to RPi5b. My main goal was use fastest disk possible on RPi5b. With only NVMe plugged, power on the RPi5b and U-Boot appeared and newer gone any far.
So I write same image to SD card (mmcblk …) then boot RPi5b both NVMe and SD card plugged. Then I notice that swap and EFI partitions in NVMe are used. Then I reboot again and checked lsblk
it was like this :
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mmcblk0 179:0 0 14.5G 0 disk
├─mmcblk0p1 179:1 0 64M 0 part
├─mmcblk0p2 179:2 0 500M 0 part
└─mmcblk0p3 179:3 0 13.9G 0 part
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 64M 0 part /boot/efi
├─nvme0n1p2 259:2 0 500M 0 part [SWAP]
└─nvme0n1p3 259:3 0 953.3G 0 part /
it was using NVMe all the time. My home directory was on the NVMe.
Behavior can be tested as fallow:
- Write 20260209 Tumbleweed image to NVMe and SD card.
- Plug both SD card and NVMe to RPi5b
- Boot first time.
- login as root/… and issue a commnad “reboot”
- since then I got above lsblk every time I boot. All EFI SWAP and root partitions are in NVMe.
İt might be due to same UUID on both SD card and NVMe… But RPi5b is a lot faster then just SD card. Then 20260223 update came along and broke every thing. 20260223 released and I made distro up. It Updated KDE and others but the kernel stayed the same.
Now I wonder is it future or bug? İf it is a future it needs to be redesigned if it is a bug it needs to be fixed.