Yeah, but Timeshift uses the Ubuntu style subvolume naming, @ for root, @home for /home, so you have to create them that way, otherwise, it won’t work. It can work if you tell it to ignore home, but checks for @ as root on start up.
I know how to do that, you set the subvolume as the default one, thus, when mounting, if no options are passed, it always mounts that subvolume as root.
But, you have to disable that. Sure, I set it during install, cuz installers are stupid (if you tell it to install in /@, it will most probably moan), but disable it after first run (set the real root as the default subvol, i.e. mount point) and just add subvol mount options in fstab.
It’s just extra steps I have to do now 😒, that’s why the rant.
That might also be a general network drivers vs. kernel version problem as well. I’ve had that on some Ubuntu falvors on various cards, it isn’t specific to just wi-fi, it happened on lan as well (just disconnects for a few ms and then connects again).
And yeah, one of the many reasons why I usually buy second hand hardware as well. One, it’s a lot cheaper, two, drivers for Linux are usually not a problem 😁.
There are some oddball cards out there that need the linux firmware xxx (insert manufacturer instead of xxx) binary blobs in order to work, but yes, those cards are rare nowadays and mostly older hardware uses that (as you mentioned, hardware from 10+ years ago).
Yeah, the Chinese stuff seems to work better under Linux… for some reason 😂. I one based on a Realtek chip (I think 🤔) and I couldn’t get passed a few hundred KB in Windows. Linux fried that baby, it did 1.5MB 😂.
Every god damn time! (infosec.pub)
It's OK if you cry (infosec.pub)
NNN ended two days ago and I thought letting you all know this was important (lemmy.world)
Sony Steals Customers' Purchased Content - Piracy is COMPLETELY JUSTIFIED! (odysee.com)