• 0 Posts
  • 153 Comments
Joined 3 years ago
cake
Cake day: June 6th, 2023

help-circle
  • Consoles have really been getting closer to more standard hardware over the last years. The WiiU was a mostly custom PowerPC box, with a proprietary version of wifi for the gamepad, and including hardware specifically to run Wii games. The Switch was a barely modified nvidia shield, with bluetooth wireless controllers. The PS3 had a fully custom CPU, and old models included PS2 hardware for backwards compatibility, the PS4 is x86_64 with a custom AMD GPU.

    For the PS4/PS5, the majority of effort on running Linux is in getting it to boot in the first place. While some hardware does require patches to existing drivers (like mesa on PS4), or sometimes fully custom drivers (like the CPU fan on PS4), other hardware is completely standard, over a standard interface. Like the HDD and Blu-Ray drives on the PS4.

    The big difference is that a game console is “allowed” to deviate from standards, as it does not need to be compatible with anything outside the control of the manufacturer. This results in often small differences that require changes to a kernel which wouldn’t work on any other device.

    The biggest reason why emulation is hard, is often no longer the custom hardware like it used to be, but the OS and other fully custom standards like a graphics API. The structure of games is completely different too. The old “ship the drivers on the game disc” like on the Wii no longer holds true on modern consoles, and emulators don’t need to ensure the exact timing of an optical drive matches to get a game to work.

    There have been some attempts to get modern console games to work through kernel patches and translation layers, see horizon-linux and fpPS4, proving just how close modern console hardware is to standard PCs.

    All that being said, I don’t think SteamOS on PS5 would work for multiple reasons. It’s extremely difficult to get the process simple enough for the average consumer, especially with Sony quickly patching any exploits required to boot it. It’s also not in Valve’s business interest to make it easier and explicitly supported to buy a cheaper and more powerful standardized machine. As they would just be creating a direct competitor to the Steam Machine.


  • I have a setup similar to this, but not for ddos protection. If I were to get ddossed at a network level, my home connection wouldn’t feel much of it, as my VPS quickly gets overloaded. I have been “ddossed” at an application level though, I hate AI web scrapers. Since the entire line from VPS to my home network is 1gbps, that alongside most of my server cpu resources got oversaturated with fake traffic.

    (I say ddosed in quotes, because I’m not sure of the intentions of these AI webscrapers. Thousands of requests per second on a server that’s usually seeing maybe 5 isn’t “normal” traffic either.)



  • Not OP but a couple things:

    • It’s a full controller, no “only one joystick” like the 2015 model.
    • The quality of the IO is great, like the TMR joysticks, good trackpads, gyro, and nice haptics.
    • If a PC runs Steam, it supports all the controllers features (in Steam). This isn’t always the case on DS5/xbox controllers.
    • The “puck”, despite looking insignificant, makes the experience much better. Unlike Xbox with AA batteries or DS5 with USB-C charging, and both of those with Bluetooth wireless connectivity (by default). The Steam Controller (2026) is fully “pick up and start playing”.

    Whether it’s worth the price depends on what you value in a game controller, and how much. For me, the “extra” inputs (mainly back pedals, touchpads, gyro) and accurate sticks (TMR instead of potentiometers) are worth it.












  • Lets ignore the “is it possible” and imagine what would happen if it was. Whatever entity forks AOSP would start off with (next to) no userbase. The platform “Android” will remain Google’s AOSP, including some proprietary components. Whenever Google decides, they can enforce apps on the Google Play Store to use a new version of the Android system API. This is often a breaking change; apps that update won’t work on older Android. There is nothing stopping Google from creating complex breaking changes that tie into their proprietary components, killing off any attempt at running Google Play Store apps on older or “fully FOSS” Android. Even if a hard fork of AOSP existed, it would not remain compatible with the vast majority of applications.

    So even if this could happen, it won’t. Nobody is going to invest in hard forking a project that is going to be killed off by Google’s monopoly.

    The much better (long term) option is to stay completely outside AOSP, like with mobile Linux distros such as postmarketOS. Right now, it is underdeveloped and not an option as a daily driver for most. But over time, this is the only feasible option that can give control back to the user.




  • Assuming this is malware, depending on the complexity it might be really hard to remove. The best course of action is much like on Windows; Backup your personal files, figure out how the malware got on your PC (so you can avoid it next time), then reinstall the operating system.

    For backing up personal files, stick to documents, media, etc. Do not include executables (like installed games), and be very careful with config files (and system files), basically only back these up if you know what’s in them is legitimate.

    You can find more about the process in the /proc/4212/ directory (this is the number on the left in top). By running ls -l, you should be able to see where the exe symlink points to, which tells you where the program is installed. This might give you a clue as to where it came from (or it might not, depending on how the malware is made). If you suspect it is not malware, due to information on your system, look it up online before trusting it. I have personally never seen a root-owned ““windows”” process, which is why I’m heavily leaning towards this being malware.

    If you feel like you know where the malware came from, or you’re stuck and are struggling to find out more, you should reinstall your operating system to get rid of the malware. Malware can have different levels of complexity, what you’re seeing on the surface might be the whole thing, or it could have more complex systems to reinstall itself after removal. Which is why reinstalling your operating system is the safer option.