Well I didn't expect to be this interested in the details. Quite a few things I don't know about.
Is suspend to RAM the same as hibernate or something else?
It isn't clear to me but is the author indicating that Linux kernel support for 2.5GbE is still early stages, would it be better to wait a while before getting a motherboard with 2.5?
There's a diff being presented between two lshw outputs? How is that diff shown?
> It isn't clear to me but is the author indicating that Linux kernel support for 2.5GbE is still early stages, would it be better to wait a while before getting a motherboard with 2.5?
If you want to play it safe, waiting longer before buying new hardware is always a good strategy. As I wrote, though, aside from needing a new firmware package, I did not notice any issues with the 2.5G support in the end.
> There's a diff being presented between two lshw outputs? How is that diff shown?
I ran lshw > lshw-intel-285k-asrock.txt when I used the ASRock board and lshw > lshw-intel-285k-asus.txt when I used the ASUS board. Then I ran diff -u lshw-intel-285k-asrock.txt lshw-intel-285k-asus.txt and copy&pasted (parts of) the output into the blog post.
Suspend to ram is same as sleep. Hibernate dumps ram contents to disc and completely turns off. Waking up from sleep (suspend to ram) is fast, from hibernation you need to read the whole file back to memory.
This is true, but I'd like to point out that hibernation to NVMe is almost as fast as sleep. The lines between memory and storage are blurred these days.
I have had pretty good luck with Realtek's 2.5gb chipset (PCIe card and USB 3 dongle) in TrueNAS, PopOS and Arch. I think the driver situation is pretty stable now.
I have had an Intel V225 fail on me but the V226 replacement has been working.
Well I didn't expect to be this interested in the details. Quite a few things I don't know about.
Is suspend to RAM the same as hibernate or something else?
It isn't clear to me but is the author indicating that Linux kernel support for 2.5GbE is still early stages, would it be better to wait a while before getting a motherboard with 2.5?
There's a diff being presented between two lshw outputs? How is that diff shown?
> It isn't clear to me but is the author indicating that Linux kernel support for 2.5GbE is still early stages, would it be better to wait a while before getting a motherboard with 2.5?
If you want to play it safe, waiting longer before buying new hardware is always a good strategy. As I wrote, though, aside from needing a new firmware package, I did not notice any issues with the 2.5G support in the end.
> There's a diff being presented between two lshw outputs? How is that diff shown?
I ran lshw > lshw-intel-285k-asrock.txt when I used the ASRock board and lshw > lshw-intel-285k-asus.txt when I used the ASUS board. Then I ran diff -u lshw-intel-285k-asrock.txt lshw-intel-285k-asus.txt and copy&pasted (parts of) the output into the blog post.
Cheers fella
Suspend to ram is same as sleep. Hibernate dumps ram contents to disc and completely turns off. Waking up from sleep (suspend to ram) is fast, from hibernation you need to read the whole file back to memory.
This is true, but I'd like to point out that hibernation to NVMe is almost as fast as sleep. The lines between memory and storage are blurred these days.
I have had pretty good luck with Realtek's 2.5gb chipset (PCIe card and USB 3 dongle) in TrueNAS, PopOS and Arch. I think the driver situation is pretty stable now.
I have had an Intel V225 fail on me but the V226 replacement has been working.