𝒍𝒆𝒎𝒂𝒏𝒏

Hey 👋 I’m Lemann: mark II

I like tech, bicycles, and nature.

Otherwise known as; @lemann@lemmy.one and @lemann@lemmy.world

Dancing Parrot wearing sunglasses

  • 1 Post
  • 60 Comments
Joined 6 months ago
cake
Cake day: December 22nd, 2023

help-circle
  • ASMedia is the only controller IC manufacturer that can be trusted for these IME. They also have the best Linux support compared to the other options and support pass-through commands. These are commonly found in USB DAS enclosures, and a very small fraction of single disk SATA enclosures

    Innostor controllers max out at SATA 2 and lock up when you issue pass-through commands (e.g. to read SMART data). These also return an incorrect serial number. These are commonly found in ultra cheap desktop hard drive docks, and 40pin IDE/44pin IDE/SATA to USB converters

    JMicron controllers (not affiliated with the reputable Micron) should be avoided unless you know what you are doing… UASP is flaky, and there are hacky kernel boot time parameters required to get these working on Raspberry Pi boards. Unfortunately these are the most popular ones on the market due to very low cost




  • I used to use MQTT, static_status and Healthchecks.io, and have that data passed through to Home Assistant, but it started to get pretty cumbersome as the amount of machines I had grew.

    I now use just Zabbix and HealthchecksIO. I did need to spend some time writing new templates for some additional data I wanted to collect (like SMART data for SSDs that provide health metrics in non-standard attributes, and HealthchecksIO so I could see the status of various checks on my zabbix dashboard)

    Zabbix also has some additional features I found appealing, like proxies that can continue recording data when the main server is down, and built in encryption. Some checks like open ports/icmp responses etc can be checked using either the local agent, the remote server, or both, which helps quickly diagnose things like firewall config issues.

    I did look at some other solutions, but I wanted something integrated to hit the ground running. Mobile apps are very limited, and there is no official one to my knowledge. I use Moobix which I don’t believe is FOSS - but I could be wrong there

    Try each solution out and see what works best for you!




  • Install steam. Run in big picture mode. Done. That’s a steam machine. I don’t get what you think a dedicated machine is going to do any differently. There is a reason Steam abandoned the idea themselves.

    Big picture mode on my windows PC and the gamescope-focused UI on the Deck look similar, but offer very different capabilities IME.

    To name a handful: FSR support for all games - including those that don’t support it, per-game hardware performance profiles, excellent hardware integration - not just limited to the instant sleep and instant wake. With the third party Decky Store you can also configure the fan profile to your liking, control music apps running in the background on the Deck, and more. On the PC BPM these sadly do not exist

    I 100% prefer playing on the deck any day of the week - the OS simply makes it so straightforward to jump into a game and forget about needing to also think about maintaining a desktop: no Windows updates, no telemetry service CPU spiking, and no Windows resetting my customized settings or forcing Edge browser defaults after an update.

    That said, I don’t particularly have an interest in a full blown Steam Machine - for me the Deck works just fine when docked.













  • If anyone is interested in mitigation, the only way around this AFAIK is to start with a brand new domain, only use wildcard certs (with DNS validation), and don’t bundle multiple renewals into a single cert.

    Also, don’t enter your domain or related IP address into dns reverse engineering tools (like dnsdumpster), and check certificate transparency logs (https://crt.sh) to see what information related to your cert renewals has been published.

    This won’t stop automated bots from scanning your ip for domains, but should significantly reduce the amount of bots that discover them


  • Some TL;DR from the Verge’s coverage of this:

    • Leadership has connections to CyanogenOS and an ex-Playstation CEO
    • Ayaneo is looking into releasing a device with this OS at the end of 2024 (free salt grains here)
    • A handful of celluar providers are interested in connected hardware running this OS
    • No desktop mode
    • Beta releasing in the next 60 days
    • Target audience is likely casual gamers - those who may consider a Switch instead of a Deck

    The following is my response copied from the original post in the Linux Gaming community:


    Sounds very interesting, but I can’t shake the feeling that this company is looking to profit from Valve and the OSS community’s contibutions to Linux gaming without contributing much back.

    On the plus side, at least the Box86 developer and a couple others they’ve hired from various Linux gaming projects are now getting paid for their contributions 👍. They also managed to get The Witcher 3 running on an ARM device which is pretty cool.

    Playtron hasn’t quite decided just how open source it’ll be, though, and how much it will cater to Linux power gamers versus the next hundred million that Playtron hopes to bring into the fold.

    Seems likely that Playtron would follow Valve’s apprach where the client application/shell is proprietary IMO, with the rest of the OS remaining open source.

    There’ll be no Linux desktop mode.

    Hard pass for me, since the deck is also a partial laptop replacement in my case. The article also mentions wanting power users to debug the alpha version of the OS they’ll be releasing in 2 months or so - not too sure how they expect that to happen if they’re not providing a DE besides their Playtron shell.

    I’ll be following the progress of their OS though, will be interesting to see if they’ll aim for Valve’s pretty tight hardware integration or whether they’ll keep things on the more generic side like we see with the current Windows handhelds

    Edit: Fix quotes