Definitely agree. Had a couple of them and loved some of the ideas (touchpad sticks, gyro to mouse aim, all of the Steam Input flexibility) but they never really eclipsed my rechargeable Dualshocks in terms of feeling right. Taking some of the Deck’s refinements and giving it another spin is welcome.
I had no idea that this was coming out, and it sort of makes me want a PS5… And then I check the price and I think I can wait a couple of years until it’s on PC.
In a weird way this makes Linux a microkernel. They’re “macro” but isolated and cooperative. Coolest patch set I’ve read about in a while.
Yeah, I also have this question. I loved playing 1 and 2 co-op but 3 and pre-sequel didn’t hold my attention at all. I’m happy to see good reviews but I’d like to hear a review from someone that doesn’t lose their access if they pan it…
You are getting this from Xwayland, so you’re running a rootless X server in the background. It’s nice that it works seamlessly, but it’s not really Wayland doing anything but managing the X window.
This is about Linux kernel driver maintainership… It’s all open source.
I don’t have experience with MSI recently, but I’d be really surprised if you couldn’t flash a new BIOS off the system partition or FAT32 USB. You may not be able to update from Linux directly, but almost all motherboards I’ve seen support doing it from the BIOS interface.
Yes. It has basically the same issue that any compatibility layer is going to have. It will either faithfully reproduce X11 so well it will bring all of the nonsense Wayland was meant to do a way with (everything not directly related to displaying graphics, like font and geometry rendering from the '80s, network transparency, insecure event handling) OR it will attempt to get a reasonable subset working for modern X apps and it won’t be compatible with dusty old binaries and X forwarding etc.
Right now it looks like a shim for Xwayland so it’s the first one, but as it matures we’ll see.
Intel has been struggling overall, and lately has been letting some of its Linux engineers go. Nothing absolutely fundamental has been affected yet (AFAICT) but I guess Clear Linux didn’t make the cut.
It would allow SSH if the desktop is locked, they’re separate. If you can get in via SSH then you can poke around logs like dmesg and see what’s up. There will probably be some messages to give you something more specific to search with.
I couldn’t find the specific reasoning for this change, but I feel like QEMU is probably just too holistic to be appropriate for this kind of project.
QEMU needs to be able to emulate all the ARM hardware with enough fidelity to boot a naive operating system. For the purposes of running userspace applications almost all of that is not required, you really just need to convert one ABI to the other and translate the instructions. No need to handle firmware, the MMU, interrupts, disks etc.
Yes! It used to be so hit or miss with Wine, but I played WoW in it around the same time and it was crazy that it worked (at least most of the time).
There’s just no reason to do this work. Even if you ignore the fork’s controversial maintainer, and just favor the fact that it’s maintained at all (which is what the proposal’s author is suggesting) just… Why?
X11 is basically over at this point, why throw a last minute wrench into the existing, working Xorg infrastructure?
When we dropped XFree86 back in the day there were license issues, packaging issues and a real alternative didn’t exist - all justifying the effort to switch. None of these are a problem today.
Unless you can launch offensive weapons at other racers or eat shrooms to speed up or literally launch your car off of a vertical ramp into the sky and it turns into a glider in Forza, I’m pretty sure these games aren’t even in the same genre.
I agree. I have become more amenable to things like Flatpak or Podman/Docker to keep the base system from being cluttered up with weird dependencies, but for the most part it doesn’t seem like there’s a huge upside to going full atomic if you’re already comfortable.
Hell yeah, congrats! I get back into DCSS every few years but I have only escaped with the orb once, a lucky MiFi run. Just getting there is huge!
GNOME 3 introduced the current shell paradigm where you don’t really have a start menu but a variety of searches, integrated indicators, per-app desktops with a dock etc.
Before, it was far more conventional experience like Plasma/Windows/Cinnamon are now. GNOME 2 was forked to be the MATE desktop if you want to check it out.
Basically just start with what you’re aiming to enable and work backwards (as you’ve started to do). With judicious use of grep find out where that symbol is defined. If it’s in arch configs for other arches but not your own, it’s probably that.
There may be better tools out there to do this, but in my experience just sleuthing it out a bit will answer your question. The Kconfig system can be complex, but the files are pretty readable.
It’s possible that it’s not supported on your arch.
I agree, but I can envision scenarios where you are integrating into someone else’s workflow/machine and they (or their build system etc.) are expecting a shell script. Python is ubiquitous but sometimes you just want to work like everything else.