NVMe Tuning
#11
@Redbeard,
Does the new setting survive a reboot?
Does the new setting survive a power cycle?

If it does, then perhaps that drive does not need the saving option.

If it does not save it, you can always add a startup script to make it semi-permanent. (Obviously, on a desktop it's not that critical. I am referring to if you used the same NVMe drive in a Pinebook Pro.)
--
Arwen Evenstar
Princess of Rivendale
#12
(01-11-2020, 10:27 PM)Arwen Wrote: @Redbeard,
Does the new setting survive a reboot?
Does the new setting survive a power cycle?

If it does, then perhaps that drive does not need the saving option.

If it does not save it, you can always add a startup script to make it semi-permanent. (Obviously, on a desktop it's not that critical. I am referring to if you used the same NVMe drive in a Pinebook Pro.)

Unfortunately it doesn't survive a power cycle.   I suspect the smaller capacity versions of the same drive listed in the wiki and discussed in the forum have the same limitation.   If I end up using that drive in the PBP I'll set up a startup script as you suggest.  I've never set one up but I assume I can pretty easily Google how to do so.  It would have to run as root.  Do you know if that is an issue?
#13
@Redbeard, yes, startup scripts need to run as root, and that's not a problem.
The exact nature of the the startup script varies depending the OS.
--
Arwen Evenstar
Princess of Rivendale
#14
(01-12-2020, 11:32 PM)Arwen Wrote: @Redbeard, yes, startup scripts need to run as root, and that's not a problem.
The exact nature of the the startup script varies depending the OS.

Thanks again.

I just got this working by creating a cron job at boot.  From the terminal, I typed: 


Quote:sudo crontab -e

In the editor, I added the following line to the end of the file (just past the last commented line):


Quote:@reboot sudo nvme set-feature /dev/nvme0 -f 2 -v 2

I then exited, saving the edit.  After a reboot I ran the following to confirm that it worked:


Quote:sudo nvme get-feature /dev/nvme0 -f 2

It came back with:


Quote:get-feature:0x2 (Power Management), Current value:0x000002

Which shows that it is working.  I tested this after both a restart and a boot after shutting down entirely, and it worked both ways.  

One thing I did find is that if I used the -s switch in this situation not only does it throw an error that it can't process the save, but the entire command appears not to function.  I originally made the mistake of including the -s switch when I first edited crontab, and when I did that the power state wasn't set after reboot.  So if someone tries this and it comes back with "Current value:00000000" after rebooting, double check that the -s switch isn't included in the crontab line.
#15
nice work redbeard
Linux n00b trying to learn.
Brute force and ignorance sometimes works!
| Pinebook Pro + Toshiba OCZ RC100 240GB |


Possibly Related Threads…
Thread Author Replies Views Last Post
  NVMe drives not detected mattpenn 12 2,944 03-05-2022, 04:53 AM
Last Post: mattpenn
  NVme intall usage? tkudog 2 842 03-04-2022, 01:29 AM
Last Post: Tazdevl
  Anyone selling a spare NVMe adapter in Europe? tom.tomasz 1 543 01-03-2022, 07:57 AM
Last Post: tom.tomasz
  NVMe-related crashes and instability, plus a solution simonsouth 13 7,260 12-10-2021, 07:47 PM
Last Post: josmo
  NVMe SSD testing methodology halogen 1 1,201 07-22-2021, 05:57 PM
Last Post: calinb
Question Battery stops charging and NVMe and other media disconnect randomly Eey0zu6O 4 2,056 07-09-2021, 08:45 PM
Last Post: moonwalkers
  nvme drive disappears after about an hour of uptime codebreaker 25 18,099 02-09-2021, 11:32 PM
Last Post: dsimic
  NVME SPI Update not booting SD Card WZ9V 5 3,498 10-18-2020, 08:36 PM
Last Post: wdt
  Possible to upgrade PBP with NVMe M.2 1TB SSD from Sabrent? kkdao 15 11,185 08-22-2020, 05:20 AM
Last Post: kkdao
  LTE adapter via NVMe grego 2 3,247 07-08-2020, 01:37 PM
Last Post: manawyrm

Forum Jump:


Users browsing this thread: 1 Guest(s)