Hey sorry for a delayed reply I’ve been very busy. For my order of attempting to fix this, I went into the boot configuration text file and set PCIE to gen 3 for my nvme drive, that’s the only way I can get the pi to detect the kioxia nvme ssd I have, if I leave it on gen 2 speed the drive never sends and receives data to the pi. I can get the pi to boot from an sd card fine and I can use the m.2 as additional bulk storage since it detects with the config file change. However, when I try to boot directly from the m.2 the bootloader fails to detect the m.2. The only thing I’ve gotten to work is I deleted the main partition off the sd card so the sd card just has the 500mb boot partition and the bootloader picks up the sd card and starts Ubuntu but then it boots the Ubuntu install off of the nvme card since that’s the only drive with a main Ubuntu partition. It’s basically tricking the pi into booting the nvme using the sd card boot files, and it shows in Ubuntu as the boot files are being used from the sd card but Ubuntu is running and saved on the m.2. I’m okay with this janky setup since it’s still running the os off the m.2, but once Ubuntu is booted off the m.2 Bluetooth and WiFi are disabled and not even listed as options and I can’t figure out how to fix this. Their files aren’t listed in the boot files at all that are saved on the sd card. I also can’t run commands to install anything since that requires wifi.
Statistics: Posted by Tsnow8896 — Wed Jan 01, 2025 7:08 pm
