<sphalerite>
gchristensen: I think the appropriate solution to the randomness problem is putting haveged in the initrd and starting it before you need the randomness
<sphalerite>
but it's not randomness in this case is it?
<sphalerite>
or rather lack of randomness
<sphalerite>
thefloweringash: samsung evo 128GB, supposedly U3 speed class
<thefloweringash>
I have the evo+ 64gb. Let me know how it goes!
<sphalerite>
oh yeah might have been evo+
<clever>
Model Number: Samsung SSD 960 EVO 500GB
<clever>
Total NVM Capacity: 500,107,862,016 [500 GB]
<clever>
from my laptop
<thefloweringash>
I wish I had the choice of a real storage device and not a microSD card
Thra11 has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 245 seconds]
Acou_Bass has quit [Ping timeout: 260 seconds]
<Dezgeg>
gchristensen: yeah I have seen that. maybe with luck you can set deterministic uuids and stuff to avoid the getrandom calls
<Dezgeg>
or yes this haveged thing but having custom code for that in the initrd is kind of annoying probably
<Dezgeg>
or actually, if the hisi-rng module works for that hardware, then include that on the initrd
sphalerite has quit [Ping timeout: 252 seconds]
sphalerite has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 252 seconds]
Acou_Bass has joined #nixos-aarch64
orivej has quit [Ping timeout: 252 seconds]
<gchristensen>
my life is compiling kernels now
<gchristensen>
Dezgeg: the hisi-rng seems to have improved it! now fixing no networking due to missing MLX modules.
<Dezgeg>
ok, great
<gchristensen>
do you not sleep much, Dezgeg?
<Dezgeg>
depends... it's like afternoon here right now