Mmmm you’re talking about key resellers. A full retail version costs $150. Keys from key resellers are notoriously unreliable. It might work forever, or it might stop working a week after you authenticated. It’s more or less a gamble.
Great if it works for you, sucks if someone just wasted money (however little) on something that’ll stop working - especially if it’s grandma’s machine.
Also, hedge your bets a little better, buy the ones that cost $10 or even $15. Historically speaking those are a safer bet.
Wayland on an Intel iGPU runs flawlessly and has for several years. However, that’s a matter of drivers. AMD is in the forefront regarding having dGPU support, while NVIDIA is playing catch-up.
Honestly, if you’re not using nix to deploy systems or need it to create reproducible environments across systems, then NixOS is a bit overkill.
I want to use NixOS for servers and embedded systems as well, so I run it on my laptop. But the user experience gives Gentoo a run for it’s money for being the most finnicky bastard in the distro world. They would both contend if there was a Razzy award for usability.
A part of me says I should, since I also feel responsible for abandoning my best friend, who missed his teenage goals of joining the 27 club by a few years.
The heroin epidemic took many of my friends as a teen and left me kind of traumatized. Seeing some of them again could help to spur growth, but I also suspect it might make me deeply depressed.
Firstly, check the logs directly to get a more concise error that we can analyse. journalctl is the standard systemd logging client you can use in the terminal. By specifying the unit (units can be socket files, timers, services) you can get logs specifically for said unit.
You can utelize flags such as -e to scroll to the end of a journal, -f to follow a journal in realtime and utelize the -p flag to set priorities like error, crit, warning (-o error) and others to filter away common journal entries so you don’t have to scroll through every line in the log.
Secondly, and this is gonna sound weird, but reboot into windows twice. The first time you boot windows run diskchk on the partition(s) in terminal/powershell/command as administrator. If it tells you it needs to do an offline scan, reboot and you’ll see an offline diskchk screen on boot before login. If not, reboot again into windows anyways, and then reboot into Linux.
The reason is that NTFS has a weird failsafe flag that NTFS on Linux considers a no-go, and it’s usually set if the system crashes more than twice, but not always. If Linux NTFS drivers see the flag, it won’t mount as a precaution. The only way to reset the flag is to reboot in windows twice. Not once, not three times, but twice.
This might be outdated info, but that was the fact some years ago. There might be a way to fix it with modern day Linux, but I don’t know, especially when I have no direct and informative errors to go by.
Lavar Burton is a goddamn treasure of a man. When you yanks rip down another one of those confederate statues, do me a solid and put up one of Lavar Burton in its place.