Can’t say I have. Haven’t used hibernation mode for years even. Sleep mode is just too good nowadays for me to use it, so I guess we could chalk that up to a fault of the setup.
According to ReadTheDocs (BTRFS, swapfile) it’s possible under certain circumstances, but requires the 6.1 kernel to do it in a relatively easy way.
I blame Discovery and Picard. I tried watching Discovery the other day. I desperately tried, you guys. I quit - and I won’t be watching Picard. I reject the callous and hamfisted writing, so I’ve personally rejected it as cannon at this point.
Star Trek Shorts was kind of okay, and Brave New World was definitely a step in the right direction. I’ll watch that soon because I’m rewatching most of the shows in chronological order (based on this IMDB list). Also, Prodigy is actually pretty great. I’m glad it didn’t get cancelled. It’s a kids show, but the Prodigy writers show they actually care.
But my god. The writers for Discovery and Picard really screwed the pooch. I won’t even blame direction or acting, like at all. What I blame is the paint by numbers forced progressivism, which pisses me off, because it shouldn’t feel forced. It’s Star Trek FFS. It used to be the platform for progressive subjects.
Star Trek has been a playground for masters of the powerplay, for subtext, allusion and theme. It was a progressive platform already, but did so through writing methods which has been employed by writers for thousands of years to convey stories and characters, tried and true methods that yield good quality story telling. All of that went out the window with Discovery and Picard. The writing in those shows is the storytelling equivalent of smashing the square through the circle shape.
When it comes to the Orville? It shows that McFarlane really has a love for Star Trek and that he could have helped to modernize it, in a much better way than what the production team did with Discovery and Picard. But much like with the Flintstone’s reboot, he got shafted. But at least he got bawled out by Tucker in Enterprise while playing the role of an enson. So he’s apart of cannon in some way?
Well yes, it can, but it requires power. Vast amounts of energy. It’s still about the energy, even in the distant future, because I swear to the prophets, it never ends. It just doesn’t stop not stopping.
“Contrived” is a better word I guess. I don’t feel like many of the arcs have been fleshed out, leading to conclusions that are ill deserved Burnham as a character arc is a perfect example of this. I think she gets everything served to her on a silver platter, that the action setpieces are not enough to justify the order of things. This might be an issue with cutting for time, but still.
Easy because the combined shine from our skulls would manifest into a cataclysm causing deathray. If you see two bald people fighting, throw a wig on one of them to save the world.
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.
Generally speaking, and I’m not talking about your Raspberry Pi’s, but even there we find some limitations for getting a system up and booting - and it’s not for lack of transistors.
But say if you take a consumer facing ARM device, almost always the bootloader is locked and apart of some read only ROM - that if you touch it without permission voids your warranty.
Compare that with an x86 system, whereby the boot loader is installed on an independent partition and has to be “declared” to the firmware, which means you can have several systems on the same machine.
Note how I’m talking about consumer devices and not servers for data centres or embedded systems.
I kind of agree, in that ARM is even more locked down than x86, but if I could get an ARM with UEFI and all computational power is available to the Linux kernel, then I wouldn’t mind trying one out for a while.
But yes, I can’t wait for RISC-V systems to become mainstream for consumers.