• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 5th, 2023

help-circle


  • I’ve been living on Tumbleweed KDE for about a year now, and I love it. My mum recently got a new laptop, so I decided to make it a dual boot of Windows 11 LTSC (no Copilot or forced MS accounts) and Fedora KDE.

    Apparently Windows doesn’t ship with the relevant network driver built-in, so that was fun to hunt down while Device Manager didn’t announce what network card was in there. The manufacturer’s site lists a certain driver as the “latest”, and that would “successfully” install without actually doing anything. Half an hour later, it turns out that pressing “more” on their website shows previous versions of the driver… and drivers for a totally different network card that also gets shipped with this laptop sometimes. Naturally, the hidden one worked first try. Most other drivers were borked too, so Windows Update had to fetch them.

    I then got to set up Fedora, which I chose because from what I heard it’s neither boring nor too bleeding edge, without Canonical’s controversial Snap shenanigans and with some relatively easy enabling of proprietary codecs (which I still need to verify) and with okay package management through Discover. The network card and everything else worked perfectly out of the box, but I have never installed Fedora before and forgot to partition the drive in Windows beforehand. Eventually I finish the install, install some apps and do some updates (while feeling uncomfortable with having to guess how package management works in dnf). I’m finally done, shut the laptop, bring it down to show her, open the lid, screen comes on…

    … and then it shuts off. Turns back on, flickers a couple times, then permanently shuts off. Turns out there’s a kernel bug around display power saving that’s causing this, and I don’t know when the fix will land on Fedora.

    It’s been real fun trying to explain to her that I didn’t just break her fancy new laptop every 15 minutes and that everything I did was just a conventional procedure that should be supported (I’m lying)


  • Someone I know recently showed me that extension. I replied to them with “why bother with a browser extension, just paste the DOI into Anna’s Archive and it’ll show up 99% of the time” and showed it to them on their computer. It then showed a message along the lines of “you can access this file, but not here. Go to this site instead”.

    They were signed into their university account. As you use that extension yourself, do you know if that’s normal behavior? I’m afraid the extension flagged this person at the campus IT department or something like that








  • It does? That explains why in the video the person was able to play incomplete dumps after some tweaking. I know that on their website they recommend you create a full backup that includes multiple cartridge-specific identifiers if you want to use “online mode”. From my limited outsider perspective I’d always assumed these were required to be present for the Switch to even recognize something was in the slot, as the slot uses a seperate circuit and chip to ensure validity before passing it through to the Switch. I never thought of the possibility of them including a (currently) valid ID for you!

    Unless the developers have managed to obtain an official private key from some publisher in order to digitally sign their certificates, this thing really isn’t gonna survive long, is it? Nintendo could ban the cert (or, if it’s bogus, enforce stricter verification) and/or flag everyone using it (maybe even retroactively?). Why would they even make it have an identifier in the first place, since they already want you to provide your own and all it does is give Nintendo something to ban?

    Sorry for my rambling by the way