Nvidia graphics?

How much care did you take in getting a machine for running Linux? Did you get one specifically with that in mind? Or did you slap it on the machine you already had?

Endless raving about how painless and troubleshoot-free Linux is and then you try installing it on your very standard-built PC and face major glaring issues and then get told you're the idiot for not junking your perfectly good GPU from the most popular GPU maker and most valuable company on the planet.

I'm sure it's Nvidia's fault for whatever reason but Linux proselytizers need to stop being so dishonest about how pain-free switching is.

It is painless on hardware that's compatible. Nvidia issues are well known too.

It's like you running Windows 7 on a PC designed with Windows 11 in mind and expecting a good time. If you wanted a good Windows 7 experience you'd want a PC with parts that are actually compatible and have good drivers. Linux is the same.

So not painless then on perfectly normal PC builds. Got it.

It works fine on plenty of normal PC builds, just not EVERY PC build.

I’m aware

If you have all kinds of issues when installing Linux, “oh Linux bad”, “Linux not ready” etc. If you have the same with windows, it is normal, sometimes happens with certain hardware, it is manufacturer’s fault etc.

I used my perfectly normal PC that has absolutely bog standard components that any decent OS should run on. I’m not about to throw my whole computer out just to switch.

So you made zero effort got it. Try running PC-DOS on there instead. Should work fine with a "perfectly normal PC", everything should just "work".

This is the exact attitude that keeps people away from Linux. The moment someone points out practical problems with Linux, it's users get all defensive and elitist about it. Sigh, if at least this changed more people would use Linux.

lol, not throwing out my whole PC is “zero effort” - fuck off

You don't have to throw out your whole PC. Could you have waited for the next time you upgraded and thought about it then? Maybe if it's a desktop swapped out the GPU and kept the rest of the components?

It wasn't even clear from your original post that you even kept the same PC FFS. Nor did you clarify what "bog standard" PC components you used. Just expected perfection.

Doesn't even need to fit in the slot either. One of my Surface Pens is an older one that uses a AAAA battery and doesn't fit in the keyboard slot. It works just fine on my SP11 and older SPX. It just has less features and isn't as good as the newer Slim Pen 2.

Sometimes they are just impossible to use. For example I could not hit the button to use Steam Guard in the Steam app to log in on one device. The screen was just too small for what the app expected.

Kobo, Google Play Books, smaller niche sites like Baen, Humble Bundle, J-novel club, etc.

They let you download books with no DRM (or with DRM that works with any reader)?

In the worst case, you can always buy it from Amazon and download it from Annas Archive

Or buy the physical book, download from AA, and give the book to charity when you’re done.

I don't want to give Amazon money for its anticonsumer practices, though, so I'll need to find something else.

Some have no DRM, like Baen, most Humble Bundles and J-novel club. Most books on Kobo/Google Play have DRM but it's really really easy to remove.

Just buy a Kobo. You can get a new one, you don't have to jailbreak it to run Koreader, it already actually ePubs out of the box, they don't have as aggressive DRM either. And the hardware is good.

You ABSOLUTELY do not have to create a recovery drive from a Snapdragon based device. I've done it multiple times from x64 Windows for both a SPX and 11.

Hmm, thank you, that's good to know. Did you just apply the Snapdragon driver zip over the x64 recovery drive? It didn't work for me when my OS killed itself but I could easily have done something wrong in my panic over the machine not working. Since I only have the one Snapdragon device, I was making the assumption that it would have worked if I had a second one, but I didn't actually know that.

Yes, just copy the zip over like the instructions say.

Thanks again for this. Honestly, it may sway my choice on returning to x64 vs. sticking with ARM64 next time. The other issues are relatively minor and can be dealt with, but I didn't like thinking that I was one OS failure away from a bricked machine that I couldn't recover.

I thought it was playable on the LCD Deck. I did turn things down below what the Steam Deck preset was at. It certainly wasn't the smoothest 100% of the time but it was better than Fallout New Vegas on a PS3 IMO. It still holds up pretty well against the Switch 2 version in handheld mode.

https://www.youtube.com/watch?v=SvGQik3m6ag

Nope. Just more selfish choices. Resources are finite. The further we can move away from cars, THE better for kids. Less risk of them being run over by a 7 foot tall Dodge Ram, more chances for independence because actually going places doesn't require a car.

It can be both. A mistake in AD primitives can lead to theoretically incorrect derivatives. With the system I use I have run into a few scenarios where edge cases aren't totally covered leading to the wrong result.

I have also run into numerical instability too.

> A mistake in AD primitives can lead to theoretically incorrect derivatives

Ok but that's true of any program. A mistake in the implementation of the program can lead to mistakes in the result of the program...

That's true! But it's also true that any program dealing with floats can run into numerical instability if care isn't taken to avoid it, no?

It's also not necessarily immediately obvious that the derivatives ARE wrong if the implementation is wrong.

> It's also not necessarily immediately obvious that the derivatives ARE wrong if the implementation is wrong.

It's neither full proof or fool proof but an absolute must is a check that the loss function is reducing. It quickly detects a common error that the sign came out wrong in my gradient call. Part of good practice one learns in grad school.

You can pretty concretely and easily check that the AD primatives are correct by comparing them to numerical differentiation.

I haven't watched the video but the text says they're getting like 60+% error on simple linear ODEs which is pretty problematic.

You're right, but the scale of the problem seems to be the issue

You can still use the old Sysv init on modern distros if you want. KDE3 is sorta still around (TrinityDE), ditto Gnome 2 (MATE).