On modern versions of common distros, it’ll probably work just fine if you install the driver from your distro’s repos. Don’t touch NVIDIA’s downloadable .run installer.
It’s getting better for Nvidia support on Linux, but there’s more edge case problems than with AMD or Intel graphics.
For me, Microsoft’s original sin was removing the Start menu and the Classic and Aero themes in Windows 8. I wanted something better than questionable UxTheme patches that broke with every major update, and it was during that search that I learned there is more to the world than macOS and Windows.
But it was the invasive telemetry and bloatware that finally made me take action. I’m sure the spike in blood pressure and heart rate whenever I had to undo the asinine default settings on every new install and major update was not good for my health. All of the debloat utilities felt like putting lipstick on a pig.
The ability to customize the interface to my heart’s content also got me to learn about and appreciate the inner workings of Linux. I now have a couple setups on Chicago95 XFCE and a couple on AeroThemePlasma KDE. Despite how much I like the familiar UI of Windows, I wouldn’t ever look back to using Windows itself.
This is for a SeaBIOS system without functional TPM.
Bypassing either password challenge for simplicity’s sake is just defeating the purpose of having LUKS on the full disk anyway. Just encrypt your home of that’s a problem for you and simplify things.
Could you explain this? I do not see how it would compromise the security model since the lock screen would be dismissed only after the LUKS password is entered. The screenlocker is only relevant when suspended to RAM as the LUKS key is no longer in RAM once hibernated.
Killing your lock screen from the session manager is going to cause all kinds of problems, so that’s not going to help. It’s not JUST a plain old process to kill, it’s the session manager. You kill it, and it’s going to ask you again anyway, and likely destroy your existing session.
I am using slock, which is separate from my session manager (startx in ~/.profile), and in my testing, I was able to kill it without issue.
Sometimes I want to create my own products and sell them as a side hustle. Sometimes I doubt it’ll work. But other times I am reminded how long MALIBAL has been kicking around. Ironically inspiring.
Thanks for the explanation. And you’re right - it’s was a nice learning exercise and a “satisfying” stopgap while I figure out how to compile either Libreboot, which has a variant of GRUB patched with proper LUKS2 and Argon2 support, or TianoCore, which is rather involved and scantily documented for the old X230 hardware.
This was the way on my UEFI desktop, but I gave up getting UEFI to work with Coreboot on the X230, so I settled for the next best thing.
I wonder what desktop environment they are using, perhaps Equinox Desktop Environment?
Along this vein, a used e-reader with a large screen has cut down my printing needs by about half. Don’t have to burn out my retinas on a backlit screen, but don’t need to print out and carry stacks of paper either.
HP Laserjets are usually decent. Ironically, I’ve had a better time with consumer lasers since the enterprise variants take ages to boot.
Quite lucky, I’d say. Could also come down to some print heads being designed better than others. I rigged my old inkjet up to a refilling tank system and I’d have to run a few cleaning cycles in a row if I didn’t print for a couple of weeks. This was in a room with around 50 to 70% humidity.
Anything but inkjets, unless you are keen on printing photos. The amount of time I’ve saved on maintenance since I switched to a laser printer is astounding. Currently using an old Brother MFP I bought for $30 at the local thrift store, then $30 for a two-pack of third-party toner on eBay.
As for wireless printing, I set up an old thin client as a discrete print server.
By its limited scope of just initializing the chip, it seems a lot more benign than Intel ME, which would be a jucier target than the FSP. But no independent audit has been completed on it to my knowledge. Purism got started with an attempt to reverse-engineer it (legitimately without the leaked code!), but Intel told them to take it down, which is a bit troubling.
Still, when im forced to use windows I see how bad its become, so im sticking with linux!
That’s the right attitude. A lot of the comfort of Windows comes down to habit and mere exposure. Every Windows user who dives beyond the surface also spends a lot of time learning, but with the added burden of having to sift through every forum post suggesting sFc /ScAnNoW. And if you keep the same hardware for a few years, the Linux experience ages like a fine wine as drivers improve and features get some subtle polish.
Sometimes I wonder if my health takes a toll each time I help someone set up Windows. I can literally feel my heart rate increase as I go through the privacy-related settings.
Learned to make use of this the hard way when transferring a directory over a FAT32 USB drive messed up the permissions.
Nice! Glad to hear it worked out for you
Active Desktop for Linux! But seriously, ever since I ditched desktop icons, I’ve thought about making the desktop useful by having it display a HTML dashboard of sorts. Now I can.
I think we can safely rule out anything on the hardware side since accessing any internal component of the Surface Go is tantamount to destroying it.
Assuming Microsoft’s UEFI implementation is somewhat standard, Grub2Win should set you on the right path. Have you inspected the underlying grub.cfg? Make sure the entry for the ISO doesn’t make any attempt to boot from network.
Pot, meet kettle