Raspberry Pi 5 Support

[br6]

Will you be adding RPI5 Support?

thanks

[Sulphy77]

Yes please.... I am also eager to know if pinn will be updated to support RPi5

[jaca2300]

Please,,,

[procount]

Sorry, github has stopped sending me notifications so I missed many messages - I will have to fix that.
Anyway, I have been working on PI5 for several months. Finally I am seeing light at the end of the tunnel. It will still be a little while yet, but it's coming....

[Macrobiotic]

Just chasing for an update on Pi5 compatibility. Version 3.8.9 seems to get as far as letting us install OS-es, but when booting into one of them the Pi5 appears to reboot. Any work-around?

Using a micro SD from Samsung (512 Pro Ultimate).

[procount]

It is essenrial to upgrade your firmware, as detailed in the release post https://forums.raspberrypi.com/viewtopic.php?p=2173713#p2173713

[Macrobiotic]

Many thanks for the quick reply.
I've shared this info with the discussion thread under this YouTube video: https://www.youtube.com/watch?v=WVCNPCHN4xU

The video is all about trying to get PINN working on a Pi 5.

[Macrobiotic]

The readme file in the rpi-eeprom-recovery.zip indicates it's intended for Raspberry Pi 4 specifically.
Is it safe to run it on Pi 5?

[procount]

Yes. they (RPL) probably forgot to update the readme.
It is essential to get multi-boot working. A small regression when they were getting Power Delivery sorted.

Thanks for adding the comment to Leepsvideo. I tried to add my own comment with a link, but It wasn't very satisfactory.

[Macrobiotic]

Got it. I'll give it a try.
Thanks for the quick reply.

[Macrobiotic]

Yep, that one works. Successful boot into Ubuntu 23.10.
Hope RPL get around to releasing a fixed firmware.

[procount]

I don't know their timescale, but it will eventually make it into a future apt-update; apt full-upgrade

[lurch]

It looks like it was fixed in the pieeprom-2023-12-14 release raspberrypi/rpi-eeprom@3f325bd
But the most recent "full release" was rpi-boot-eeprom-recovery-2023-12-06-2712 https://github.com/raspberrypi/rpi-eeprom/releases (and the latest tag was also v2023.12.06-2712 https://github.com/raspberrypi/rpi-eeprom/tags ).

So as you say, hopefully it won't be too long for things to get updated in apt too.

EDIT: rpi-boot-eeprom-recovery-2024-01-05-2712 now includes the relevant fix https://github.com/raspberrypi/rpi-eeprom/releases (and is also in apt).

[olly69]

Has anyone managed to get PINN working on a pi 5 booting from NVMe? I'd like a dual boot 64 and 32 bit Rasp os...

Thanks!

[procount]

It should be OK if it is connected over USB, but I assume as you mention the PI5 you are referring to an NVME connected to the PCIE connection? It should work, but I would also be interested to hear some feedback to make sure I have the right drivers loaded in the kernel for it. 😉

[Sulphy77]

I have a pineberry hat top that should be coming this weekend, so ill give it a try... am sure you already know if this hat, but here is the link just in case :)
https://pineberrypi.com/products/hat-top-2230-2240-for-rpi5
Will give PINN a go ... and report back! Thanks again!

[Poopi]

I use NVM connected to Rpi5 via PiHat.
I've installed Ubuntu and Pi OS. Pi boots to busybox but it is not finding the root partition. Ubuntu cannot even unpack rootfs. See attached screenshots.
Without PINN I can boot NVM with either Ubuntu or PiOS without any issues.
Any suggestions for further analysis?

[ardoviniandrea]

I've been testing the PIMORONI NVME base with PINN.

So far:

• raspiOS works perfectly
• lineage20 ATV works perfectly (even the TWRP recovery)
• ubuntu 23, as poopi reported, stops at boots.

I'm happy to do more testing whenever needed, and I'll continue to play around myself and report here if I find something that's not working properly

[Poopi]

Hmmm. It should not be that different from what I'm doing. So let me start messing around with configs ...

[procount]

Regarding Ubuntu, please download the attached partition_setup.sh script (You will need to unzip it)
partition_setup.zip
Copy it to the SETTINGS partition ( maybe /dev/nvme0n1p5 ? ) into the /os/ubuntu2310 folder, overwriting the existing file.

Then in PINN, go to the maintenance menu, select (tick the checkbox next to) ubuntu, Click the Fix-up button and choose to "re-run partition_setup script." If that succeeds, then try booting into Ubuntu.

[ardoviniandrea]

Hello procount

Can you please provide a bit more detail on your last comment?
I have connected my PINN SSD to a NVME reader so I have access to all partitions.

I do not see a SETTING partition and the RECOVERY partition has an empty /os/ folder

I have a lot images installed (and all the Project Spaces for future plans and tests), so it's possible I'm getting confused between folders.
I have attached a screenshot of my partitions.

[procount]

@ardoviniandrea - Are you viewing this on an Apple device? I am not familiar with those. As you have all the other partitions visible, and you can boot PINN, then the settings partition must be there. Perhaps Apple devices don't show partitions named "SETTINGS" ? I know that many OSes (e.g. Ubuntu) don't show partitions named "RECOVERY".

From the RPi forums, I have discovered that Ubuntu 23.10 seems to have problems with some USB hubs on the Pi5. May be the same issues are happening with NVME, so this partition_setup script may not make any difference.

Anyway, as a workaround, I suggest you copy the partition_setup.sh script to the RECOVERY partition and boot PINN on that device on your RPi. Press Shift when prompted so that you go into the recovery menu.
From the recovery menu press [CTRL]-[ALT]-F2 to open a terminal and login with root/raspberry.
From here, the settings partition should already be mounted as /settings. so type:

cd /settings/os/ubuntu2310
mv partition_setup.sh partition_setup.bak
cp /mnt/partition_setup.sh .

(Don't miss the dot/period in the last command! Please check the above for spelling/accuracy etc. as I am recounting this from memory!)

Return to PINN by pressing [CTRL]-[ALT]-F1
Go to the maintenance menu.
Tick the box next to Ubuntu to enable the Fixup button.
Select the Fix button
tick the box to re-run the partition_setup.sh and press OK.
Hopefully it will complete successfully, and then you can try and boot Ubuntu. (Probably won't make any difference but worth a try)

[procount]

An empty /os folder on RECOVERY is to be expected.

[procount]

@Poopi

Any suggestions for further analysis?

Could you post copies of /settings/installed_os.json along with copies of cmdline.txt from your Ubuntu boot partition and /etc/fstab/ from your Ubuntu root partition?

[Poopi]

files.tgz
Please find attached. Interestingly when I connect the NVMe via USB dongle then Ubuntu boots like a charm... I also checked the configs for Ubuntu when I installed it to NVMe directly and they are identical.

[Sulphy77]

So i got my pineberry hat top, and after MANY attempts, finally managed to get booting from the nvme to stick! I had to re-image the sd card quite a few times... as well as the nvme drive... setting the boot config etc... as the nvme would install raspios just fine... but if i did a system update from the prompt for first login... when rebooting, it would just drop me right into the busybox cmd screen (which i have no clue what to do with btw!!! n00b) ... re-image PINN... bootup from sd card... redo boot config etc.... last night tho, and this morning... i managed to get it working as expected, multiple reboots later... and still good!
So, long story short, at least in my case, do not run the updater when prompted on first boot! reboot a few times first... then do the update via ssh/terminal! Looking forward to the next version of Pinn!!!

PS: Would be awesome if it could support wubuntu or zorin (i know they arent pi compatible... just wish they were :D )

[procount]

That's good news!
So what is your setup?
Have you got PINN on the sd card that you've used to install Raspios on your nvme?

[Sulphy77]

Thanks man! So, essentially, i have managed to get PINN installed on the nvme (no sd card, or usb anymore :) ) ... then installed raspios onto the nvme as well! much neater. I have always had bad luck with sd cards!!!!
Am still blown away at the speed of this pi5... especially now... bootup takes just a few seconds!

As i am in experimental mode with this setup... if there is anything you want me to test... feel free to use me as a guineapig!!

[procount]

Thanks.
I don't have any nvme drives, so I appreciate any help in testing them and documenting any special instructions to get an OS working on them.
It would be really good to test all the Pi5 OSes that I have provided to see if any of them don't work or if I need to do some extra work for them.

[Sulphy77]

Sure thing, i will install them all... document each one as i go through them... and report back! Gimme a few days to play as and when i can, i mess about with the pi5 in between work!

[ardoviniandrea]

Some updates here.

I've tested what procount shared in the previous comment.
The Fix run successfully but as anticipated, didn't solve the issue for Ubuntu that still stops here immediately after the boot.

I did test most of the other OSes and I can report that all of these works correctly when booting from PINN on NVME:

• RaspOS arm64
• kde2lee64
• AOSP14-rpi5 (although I managed to brick it somehow and required to reinstall it)
• lineage20-rpi5 (with TWRP and successfully installing Gapps)
• lineage20-rpi5-ATV (with TWRP and successfully installing Gapps)
• mxlinux
• LibreELEC_RPi5
• recalbox5 (boots fine, but I haven't try any games for so far, so I cannot report the full funcionality)
• ProjectSpace --> I've initially installed all 8 possible, and already used/swapped a few without any issues.

2 notes I want to report, other than Ubuntu not working:

• HDR, HDR+ and HVEC content in KODI in LineageOS (even ATV) plays with washed out / grey colors, but plays normally in LineageOS.
  I looked around a bit and looks like it could be related to codec issue, but haven't been able to identify more than this
• PINN boot related, very minor but I am not able to re-order the OSes in the boot menu using the UP and DOWN buttons. Every time I do it and either boot or turn off the RPI, the order comes back to the initial one the next boot.

Happy to keep testing new thing procount, if you have anything in mind

[Fredfars]

Hi, I have the same issue with my Crucial P3 Plus connected to a Pimoroni Base NVMe
And i found this about last kernel.
raspberrypi/linux#5873
Thanks for your job! I’m impatient to have dual boot (PiOS et Ubuntu) on my Pi5 :)

[theofficialgman]

Post updated.

@procount I don't see any edits on the initial post https://forums.raspberrypi.com/viewtopic.php?f=63&t=142574

Last edited by procount on Thu Dec 28, 2023 2:35 pm, edited 96 times in total.

[procount]

Must have forgotten to press submit. Updated again.

[JanSykor]

My new RPi 5 - Instaled Raspios, libreelec ang project space on 32GB card, and all working good.
Only eeprom update was necessary.
Thanks for your good job @procount
P.S. Do you have some plan for the update (Czech language etc.)?

[procount]

I have added the Czech translations to the main program and will include these changes in the next Pi5 beta.

[Dent2024]

Hello everyone, please tell me how to set up Pinn on the Raspberry Pi 5. I am using the website https://pinn.mjh.nz/ to create the Pinns recovery.cmdline. When I then copy the pinn-lite.zip to the SD card, Pinns does not start. I also get a message that the DTB file for the Pi 5 is missing. Thank you very much!

[procount]

You need to read the announcement post as it is still in beta:
https://forums.raspberrypi.com/viewtopic.php?p=2173713#p2173713

[mann1x]

@Dent2024
The instructions on the website are not updated for the Pi 5.

Donwload the latest pinn-lite BETA version, you get the DTB error cause it's not the right version supporting the Pi 5.

https://sourceforge.net/projects/pinn/files/beta/

Rename the recovery.cmdline from the mjh.net website as cmdline.txt and put it in the root file of the SDCard, overwrite the existing one.

[k2helix]

I just installed PINN in my Raspberry Pi 5 I'm having trouble with some issues which I haven't read here.

First of all, PINN ignores the bootmenutimeout option in the cmdline file, booting to the same OS every time.

In addition, if the Raspberry isn't connected via HDMI (or the device to which it's connected is turned off) and the power supply was not plugged in, when plugging the power in it doesn't boot to any OS. If then the HDMI cable is connected, the screen is entirely black. I need to power off the Pi by holding the power button and then power it on to make it boot.

Also, there were some issues with Android TV which I commented here

[procount]

It sounds like you have ticked one of the checkboxes alongside one of your OSes in the boot menu. This is a Sticky Default and forces this behaviour. Press Shift on next boot of PINN to get into the menu, press ESC, then untick the box.

I often run my PINN installations headless, but haven't specifically noticed this issue. Can you try commenting out the dtoverlay in config.txt that loads the KMS and see if that improves the situation?

The RPi does not support hotplugging of HDMI monitors in general. It expects them to be powered up on boot so that it can read the EDID information out of them and configure the display accordingly.

You can force the display into an appropriate mode by specifying the video parameters.
If using KMS add e.g. video=HDMI-A-1:1280x800@60 to cmdline.txt
If not using KMS, use the older config.txt settings of e.g. hdmi_group=2 and hdmi_mode=28
These are just examples - choose resolutions appropriate to your monitor.

I have permission from Konsta to distribute his Lineage builds, but he won't support any issues with multi-booting. However, the issues you mention seem to be general issues that are independent of PINN.

[k2helix]

It sounds like you have ticked one of the checkboxes alongside one of your OSes in the boot menu. This is a Sticky Default and forces this behaviour. Press Shift on next boot of PINN to get into the menu, press ESC, then untick the box.

According to the README, shouldn't the boot selection be shown for the configured time? The notes at the Sticky tab say that the bootmenutimeout may be used to show the boot selection menu.

I often run my PINN installations headless, but haven't specifically noticed this issue. Can you try commenting out the dtoverlay in config.txt that loads the KMS and see if that improves the situation?

I'll try that, thanks. However I cannot do it until next Friday as I'm not at home.

The RPi does not support hotplugging of HDMI monitors in general. It expects them to be powered up on boot so that it can read the EDID information out of them and configure the display accordingly.

You can force the display into an appropriate mode by specifying the video parameters.
If using KMS add e.g. video=HDMI-A-1:1280x800@60 to cmdline.txt
If not using KMS, use the older config.txt settings of e.g. hdmi_group=2 and hdmi_mode=28
These are just examples - choose resolutions appropriate to your monitor.

I see. I expected that if no HDMI is plugged in the raspberry would work as usual just that headlessly. By doing this, will the raspberry boot even when no HDMI cable is present? Or is this for being able to hotplug the HDMI cable?

I have permission from Konsta to distribute his Lineage builds, but he won't support any issues with multi-booting. However, the issues you mention seem to be general issues that are independent of PINN.

Where should I report it/ask for help? It makes the OS barely usable if there's no sound output. I'm not able to check if it works without PINN as I'd have to reformat the SD card and I set some docker containers which I cannot remove and would prefer not to touch.

Thanks for your help!

[procount]

1. I see your misinterpretation.

bootmenutimeout=: Changes the default timeout allowed before an OS is booted without any selection. (If this option is provided with a default sticky OS selected, the menu boot time will be respected, allowing you to choose another OS for this boot only). A value of 0 will wait indefinitely.

This is correct, WHEN THE BOOT SELECTION DIALOG IS DISPLAYED. However,.....

Sticky Default OS
Each OS entry in the boot selection dialog has a checkbox next to it, allowing users to select it as a sticky default OS. If an OS is checked, PINN will operate as if that were the only OS installed (booting it automatically, without showing the boot selection dialog). This permits a slightly faster boot up time when one OS is used regularly.

So if you have selected a sticky OS, you must press Shift to enter the recovery menu, then Esc to enter the boot selection dialog in order for it to have an effect. Otherwise the boot selection dialog is bypassed as if only one OS had been installed.
If you don't want to boot quickly into the same OS each time, then don't tick the sticky box. You will then get the boot selection menu for the bootmenutimeout length of time. If you don't do anything it will boot into the LAST OS you booted into.

2. I seem to recall this blocking of booting has been mentioned in the forums before in relation to Raspios/KMS. I've not really come across it myself.

3. I have taken LineageOS (booted via PINN of course) as my media player on holiday on a Pi400. The HDMI sound does work. It's probably a configuration issue somewhere in LineageOS, or possibly a HDMI_DRIVE=2 setting in config.txt, or maybe even your HDMI cable. PINN should not affect the HDMI sound output of LineageOS.

[Dent2024]

@Dent2024 The instructions on the website are not updated for the Pi 5.

Donwload the latest pinn-lite BETA version, you get the DTB error cause it's not the right version supporting the Pi 5.

https://sourceforge.net/projects/pinn/files/beta/

Rename the recovery.cmdline from the mjh.net website as cmdline.txt and put it in the root file of the SDCard, overwrite the existing one.

Hi mann1x, thank you for the hint and sorry for the late response.
Now I could make it running, but no system is starting, it runs in a bootloop!
I installed LibreElec and Recalbox, the installation was running correctly (I repeat the whole installation two times, same result).
Any ideas?

[mann1x]

@Dent2024 The instructions on the website are not updated for the Pi 5.
Donwload the latest pinn-lite BETA version, you get the DTB error cause it's not the right version supporting the Pi 5.
https://sourceforge.net/projects/pinn/files/beta/
Rename the recovery.cmdline from the mjh.net website as cmdline.txt and put it in the root file of the SDCard, overwrite the existing one.

Hi mann1x, thank you for the hint and sorry for the late response. Now I could make it running, but no system is starting, it runs in a bootloop! I installed LibreElec and Recalbox, the installation was running correctly (I repeat the whole installation two times, same result). Any ideas?

I don't know...
Been a while since I used it last time.
Are you sure you didn't touch keyboard or mouse during the bootup? That caused me very weird issues.
I would avoid also touching them while installing.

[procount]

@Dent2024
You should read the announcement notice I pointed you at again: https://forums.raspberrypi.com/viewtopic.php?p=2173713#p2173713
It explains that if you keep rebooting into PINN then you need to update your Pi5 firmware. It includes a link to the necessary firmware and instructions on how to update it.

[Dent2024]

@Dent2024 You should read the announcement notice I pointed you at again: https://forums.raspberrypi.com/viewtopic.php?p=2173713#p2173713 It explains that if you keep rebooting into PINN then you need to update your Pi5 firmware. It includes a link to the necessary firmware and instructions on how to update it.

Thank you very much and sorry, I missed that.

[Dent2024]

Note from @procount : This procedure is now out of date. Please install PINN from the Rpi Imaging Utility under Misc Utility Images)

Here a noob How-To "How to install Pinns on Raspberry Pi 5".

1. make sure, you're running an up-to-date firmware
   1.a) read how to update the firmware here (https://forums.raspberrypi.com/viewtopic.php?p=2173713#p2173713 )
   1.b) or use this command on e.g. under the raspberry OS "sudo rpi-eeprom-update -a"

2. Load the beta Pinns e.g. /archive/pinn-389e.zip here (https://sourceforge.net/projects/pinn/files/beta/)
   -> direkt URL: https://sourceforge.net/projects/pinn/files/beta/archive/pinn-389e.zip/download

3. Call the pinns website (https://pinn.mjh.nz/) and download only the recovery.cmdline
   3.1) rename the recovery.cmdline to cmdline.txt

4. unzip the "pinn-389e.zip" into a folder
   4.1) copy the cmdline.txt into that folder
   4.2) copy the whole content of that folder to a formated sd-card

Hint: to format the sd-card use Raspberry Pi Imager

[Lexforce]

Thank you @Dent2024. I got PINN up and installed Recalbox + LibreElec on my RP5 with that little guide.
However, while Recalbox boots great, LibreElec does not:
Error in mount_flash: mount_common: Could not mount UUID=2504-0815
Error in mount_sysroot: mount_common: Could not mount /flash/SYSTEM
And so on and so forth. 32 gb sd with equal partition split.
Anyone has any idea?
Thx for all the great stuff

[procount]

@Lexforce - Pi5 support is now included in the released version of PINN, although I still class it as beta because there are some minor issues to sort out, but mostly it works.
So now it is a lot easier to install.
Just run RPi Imager software, go to the Misc Utility Images and install PINN 3.9.2 directly to your SD card. No formatting needed. No need to go to Matt's pinn.mjh.nz anymore as you can determine partition size within PINN.
I have just installed LIbreElec with it without any problem, so maybe your issue was using the old beta?

[Lexforce]

@procount Did not know PINN was there, nice.
Most likely was the beta as you said, works so far (batocera + libreelec) with the version from RPi Imager SW.
Thanks again!

[echophil11]

This is the best NEWS I have heard all year. Thank you for all that you guys do. So when using Pie imager after selecting PINN to proceed it always asks to format and the only options are yes or no. How do I go about making it work without formatting please. Newbie here I did try to search but came up with no good results. Thank you SO MUCH in advance guys.

[procount]

@echophil11 - Can you explain a bit more about what it is you want to do?
Are you asking about Rpi Imager wanting to format, or PINN?

[echophil11]

Rpi imager wanting to format.

[echophil11]

I think I understood wrong I apologize guys. So i have an Batocera image that I usually write to the microsd with Rpi imager. My thought was that I could add PINN without formatting the Microsd so i can dualboot for times that I dont want Batocera to boot. But with Rpi imager its either PINN or The batocera image that I have i think ?

[procount]

No it doesn't work like that. Rpi imager only installs a single OS at a time. But if that OS is PINN, then you can subsequently use PINN to install multiple OSes. Batocera can be one of those. You must install all the OSes you want at the same time since PINN expands them to fill up the whole of your drive. You can install a dummy ProjectSpace to reserve space if you are not sure. You can replace OSes or ProjectSpaces later with others (within limits)

[echophil11]

Thank you so much for breaking this down this way. Going to give it a shot.

[J-Arnold]

Hi, I used the instruction to install from Dent2024 on Apr 25 "Here a noob How-To "How to install Pinns on Raspberry Pi 5""
But pinn updated to the newes version

I heve a Raspberry Pi 5 8GB with the orginal M.2 bord witha 1TB M.2.
Instalation was working from USB but when the final system is booting it is not starting.
In the rasberry boodloader I get the folowing output:

Is there any solution that can fix the issue?

[procount]

1 there is no need to install the beta anymore. Just use rpi imager to install pinn 3.9.2 or later from the misc utility images category. Maybe boot Raspberry pi os from sd or usb and use rpi imager to install pinn to your nvme instead. Or you could do a net install.

2. This looks like a bootloader issue that it can't recognise your nvme. Have you booted any OS from your nvme at all? Depending on your nvme you might have to alter your rpi-eeprom-config.

[J-Arnold]

Hi,
Thanks for the hint. What I have done
I booted Rasbery OS from USB and use the copy programm to move it to M.2. It is then booting from M.2 Perfectly !!
Than I used the RPI imager selecting PINN and install it to USB. Chagin cmdline.txt the to:
runinstaller quiet ramdisk_size=65536 root=/dev/ram0 init=/init vt.cur_default=1 elevator=deadline no_group no_default_source select="allnetwork" disablesdimages alt_image_source=http://pinn.mjh.nz/os_list.json?raspios_arm64_full=65536&ubuntu2404=65536&libreelec_rpi5=10250&recalbox5=10250&raspios_arm64_lite=65536&projectspace-1=65536&projectspace-2=65536&projectspace-3=65536&projectspace-4=65536&projectspace-5=65536&datapartition=408917 loglevel=2 sdhci.debug_quirks2=4
Pinn Version is v3.9.2
Insterlation done but on Boot I get the same output::

I updated the eeprom to the lates version: (Rasbery OS was booting from the M.2 even with the old version)

[procount]

OK I think (hope?) I see your issue.

I booted Rasbery OS from USB and use the copy programm to move it to M.2. It is then booting from M.2 Perfectly !!
Than I used the RPI imager selecting PINN and install it to USB. Chagin cmdline.txt the to:

PINN is not just an OS installer. It is also the Boot selector. PINN can only boot OSes on the same drive as itself. Therefore it must be present on the drive you boot from.

If you installed PINN to USB, booted it, and installed your OSes to NVME, then your NVME won't boot. You have ended up in a hybrid situation where PINN and all your OS boot partitions are on the USB drive and only the OS rootfs partitions will be on the NVME. If you change your boot_order to f641, then this will probably work but you will always need to have your USB drive attached. I don't think this is what you intended. (Maybe you could do a quick check to confirm this hypothesis?)

What you need to do is to install PINN to your NVME drive.

There are a couple of ways to do this:

Method 1. - Netinstall

If you remove your USB drives and SD card, but have keyboard and wired ethernet connected, then boot your pi, you should get the red/white netboot screen. If you then hold Shift, the firmware will download RPi Imager. You can use this to install PINN to your NVME drive.

Method 2. - Raspberry Pi OS

Install the desktop version of Raspberry Pi OS to your SD card or USB drive in the usual manner (e.g. use RPi Imager on a PC to install Raspios to your drive.).
Boot up Raspios. In the startup menu under Accessories, choose Imager and use that to install PINN to your NVME drive.

Once PINN is installed, remove any SD card or USB drives and boot PINN from your NVME drive (adjusting your BOOT_ORDER as required. You do not need to modify your cmdline.txt file as PINN now includes the ability to adjust partition sizes like the pinn.mjh.nz website did.

Now you can use PINN to install other OSes to your NVME drive.