Pi 5 with NVMe hat and 512GB drive.
Downloaded `2024-11-19-raspios-bookworm-arm64-lite.img` and used Pi Imager on Windows to write to SD.
Booted and the NVMe is there.
No idea what's on there already so repartitioned it and wrote the image(The Pi is the only thing I have that an NVMe fits into -- I have no other way of using it.)
Used `raspi-config` to set the boot order to NVMe first. However, it still boots from the SD card
Also appended `dtparam=nvme` to `/boot/firmware/config.txt`
There is no ` /var/log/syslog`
Tried to mount the partition but couldn't.How do you get it to boot from the MVMe?
Tried to write it a different wayAlso: somewhat disappointing that the NVMe hat uses all of the header pins making it impossible to use any other hat. Why does it need all of the header pins as well as the PCIe interface?
Downloaded `2024-11-19-raspios-bookworm-arm64-lite.img` and used Pi Imager on Windows to write to SD.
Booted and the NVMe is there.
Code:
$ lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSmmcblk0 179:0 0 233G 0 disk├─mmcblk0p1 179:1 0 512M 0 part /boot/firmware└─mmcblk0p2 179:2 0 232.5G 0 part /nvme0n1 259:0 0 476.9G 0 disk├─nvme0n1p1 259:1 0 100M 0 part├─nvme0n1p2 259:2 0 16M 0 part├─nvme0n1p3 259:3 0 476.2G 0 part└─nvme0n1p4 259:4 0 633M 0 partCode:
sudo parted /dev/nvme0n1 mklabel gptsudo parted -a opt /dev/nvme0 mkpart primary ext4 0% 100%sudo dd bs=1M if=2024-11-19-raspios-bookworm-arm64-lite.img of=/dev/nvme0n1p1Used `raspi-config` to set the boot order to NVMe first. However, it still boots from the SD card
Also appended `dtparam=nvme` to `/boot/firmware/config.txt`
Code:
$ lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTSmmcblk0 179:0 0 233G 0 disk├─mmcblk0p1 179:1 0 512M 0 part /boot/firmware└─mmcblk0p2 179:2 0 232.5G 0 part /nvme0n1 259:0 0 476.9G 0 disk└─nvme0n1p1 259:1 0 476.9G 0 partCode:
$ dmesg | grep nvm[ 1.990808] nvme nvme0: pci function 0000:01:00.0[ 1.995544] nvme 0000:01:00.0: enabling device (0000 -> 0002)[ 2.003661] nvme nvme0: Shutdown timeout set to 8 seconds[ 2.050842] nvme nvme0: allocated 64 MiB host memory buffer.[ 2.059714] nvme nvme0: 4/0/0 default/read/poll queues[ 2.070959] nvme nvme0: Ignoring bogus Namespace Identifiers[ 2.087161] nvme0n1: p1Code:
$ sudo mkdir /mnt/nvme$ sudo mount /dev/nvme0n1p1 /mnt/nvmemount: /mnt/nvme: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.Tried to write it a different way
Code:
$ sudo apt install rpi-imager...$ sudo rpi-imager 2024-11-19-raspios-bookworm-arm64-lite.img /dev/nvme0n1/tmp/.mount_rpi-im9HS4No/AppRun.wrapped: error while loading shared libraries: libGLX.so.0: cannot open shared object file: No such file or directoryStatistics: Posted by rwb — Thu Dec 19, 2024 12:53 pm — Replies 0 — Views 18