nvme Fun with Pinebook Pro

got an nvme adapter for the pinebook pro and a patriot P300 (256GB). installation was pretty straightforward. put the nvme on the adapter, screw it down into the case on the bottom around where the trackpad is. connect the included ribbon cable (be careful with this thing) to the connectors. don’t forget to lift the tiny tabs up before trying to shove it into the ports. side note: not sure if this is the same for everybody but my ribbon cable sort of stands up a little. this isn’t a major issue but don’t expect it to sit perfectly flush when you put it in. and be weary of that sticker that’s connected to the “no battery” cabling. it will stick to the ribbon cable. this happened to me so i guess it’s a forever cable because i don’t think i can get that sticker off of it anymore. i should have taken that sticker out when i had the chance but it was connected to the other ribbon cable. whatever.

pretty much worked out the box. the only thing that sort of sucks is that you can’t keep the adapter in the pinebook pro without the nvme on it because it locks into place by using a small golden “nut” by screwing it in from the bottom (trackpad side) up and not downward. so the nvme must go into it prior to mounting it onto the pinebook pro.

another thing discovered is that the nvme can draw too much power and should be power limited. there are instructions on the pinebook pro wiki that explain how to do this. when i have time i’ll see if i can write up how this is added as a service. some nvme can save this onto the drive itself; some cannot. mine cannot. so i need to run a service that does this on boot. i didn’t notice much of a drop in the speed when limiting the power. i have been using it as the /home dir for a manjaro install booting from emmc. (128GB module). works great.

swap Fun with Proxmox

so i set up proxmox a while back and its installer doesn’t partition disks for swap space. so i used a zvol to create swap. i noticed that some containers just absolutely lose it for some reason when they begin swapping. it makes no sense and i haven’t quite figured out the reason why. it seems related to older posts about proxmox losing swap control because cgroup2 was not implemented but later it seems that this was supposed to be fixed. swapping is typically abnormal anyways. the solution was to just give the main culprit more ram and disable swap. this seems to be doing the trick but i would like to sort out exactly why this is happening. i don’t want to bump into oom (out of memory) issues in the container (which has been given 16GB of my 64GB in my awesome ryzen proxmox server).