Not being bristly at all. Your comments seem to assume: 1) People don’t already know (check the thread you’re in) 2) Valve is doing something wrong, and/or 3) They are somehow at fault for something, like stolen valor or not giving credit where credit is due.

You suggested your comment was pedantic, and I confirmed, and it’s because of your tone. I’m not rage replying to your comments, just correcting the context because I feel you have the wrong take.

Nope. Anything ARM. Meaning tablets can run x86 games with Proton+FEX if that be the case. Also getting the MacOS segment back into the fold. ARM laptops, hell, maybe even Apple portable devices, who knows.

It’s not just about their own hardware, but my thinking is that the Deck 2 will be ARM for power consumption reasons, so this all makes a lot of sense. The Frame isn’t really just a VR devices, it’s also going to be SteamOS, so that means a virtual desktop and all the usual Linux apps and such. I’m sure it will sell on its own as a productivity device as much as a gaming device. No reason it can’t fill the market gap that awful Apple headset screwed up so poorly.

Yes, pedantic. Wine existed before Proton, and Valve made it more suitable for use in its own ecosystem with funding and developer time, but also still open and usable for the community writ large.

They’ve also been funding FEX since it’s inception, and likewise commiting development resources for the same purpose, to further their product reach on a wider array of devices.

They aren’t simply gobbling up these fledgling FOSS projects for use in their products as you seem to suggest, they’ve had a long term plan to make milestones and goals that have gotten them to where they are now. That’s the point.

They aren’t gatekeeping anything. They simply have the resources to give these projects they are interested in a boost.

This is specifically about ARM64 if you read the posting. The only other ARM hardware out there that runs Proton are these random Chinese brands that make emulation focused handhelds. That’s not a segment of the user base that EA would care about.

Now, Valve is turning the entire ARM ecosystem on its end by building out an entire suite of tools to make an emulation layer that makes running Proton on ARM almost entirely possible for the full range of games that already run on Steam, which is huge. That means any ARM device can now run Steam, Proton, AND FEX without much in the way of a barrier. This brings Steam on mobile potentially into olac, MacOS back to the table…etc.

It’s not about Linux users and SteamOS singularly, but the coming expansion into the ARM space.much larger than 4-8%.

This is certainly driven by upcoming Valve hardware. I don’t think any of the smaller devices out in the wild really sell enough units to make them go this far.

If you’re specifically asking because of memory use, there is no need. Memory management in Linux is extremely efficient, and since everything is a process, a properly killed process doesn’t block reclaim of that memory as you see a lot in Windows. You may see your “free” memory as being low, but that’s kind of a misnomer as you should be paying attention to claimed vs unclaimed/cached memory, which will be “recycled” into other processes that request it. If you run into memory issues on Linux or BSD, you’ll know it.

That being said, if your machine isn’t suspending or cleeping, then you’re just wearing your components out by leaving them on 24/7, so shutting down or suspending would be good practice to extend the general lifespan of your machine.

Well, you’re now blaming the OS. You chose Nobara, and that’s a “you” problem.

If this was running in Windows, you’d have the guarantees that everything works all the time? Same with MacOS, BSD, Android…it’s software. You don’t seem to get that.

If you’re unable to debug and tell what’s going on , and expect that to NOT be the norm…buddy, you’re in the wrong place.

Go back to Windows or whatever you previously using and be happy…oh wait…you don’t do that because of your higher standards.

It’s free software, ma’dude. You work it like any other software. When you have regressions, you go back to a working version.

You expecting everything to work all the time and being bitchy about is entitled as hell.

Just go back to the working version then?

There have been rumblings about this for a year or so, and it’s interesting because Nvidia doesn’t have any large hardware inclusions in the gaming space, aside from Switch 2. Nvidia has NVM as an API abstraction for their hardware, so I assume this job is about working on improving performance or support on that end.

Now, the big question is…why? It’s unlikely they would do this to squeeze about more performance out of their existing hardware for PC and Switch users alone. I think the general speculation would be that they are planning a product launch of some sort, and from the sound of the posting, I’m guessing they’ve got something to compete with AMD in the handheld market that isn’t Tegra.

They’ve also been saying for years they intend to hop into the ARM space, but keep fumbling it with delays. Their N1X(?) is supposed to finally launch “soon”, but with component prices the way they are right now, I’d expect them to delay again. Their Grace chips were kind of a joke, and they didn’t come anywhere near the power efficiency of other SoC options in the market.

All this to say: I think they’re hiring a small dedicated team to improving mobile or ARM gaming chips for…something, and that’s what these jobs are for. They need to squeeze some more juice from these chips to make them attractive at market.

Instead of writing a novel here, tried to find a post to explain what I think is happening.

Try this

Out of curiosity, does this machine in question have a hostname that falls under the domain you’re using for DNS resolution?

Also, what are the contents of /etc/nsswitch.conf and /etc/resolv.conf?

Switch those CNAME records to A records, clear your cache, then see how it works.

I can promise you this is not a resolved issue. If it was, you’d be seeing posts like this everywhere. It’s behaving as it should.

Your setup on the Firewalls is not what I would call a “standard” setup. There is both a proper DNS forwarded, AND what they are calling “DNS Filtering” at play with that service. I can’t see your record setup, but depending on which gives the defacto answers when you make a request, you may get conflicting responses, so I would just do away with any kind of non-A records in your setup and see what happens since their docs specifically say it’s only meant for those records and not CNAME or Alias.

CNAME gives you no benefit to what you’re doing here anyway since you only have the couple machines and not MANY records pointing to various places or using named hosts requests or something.

Yes, because it would actually as an accidental Round-Robin return in the case that there is a conflict with a wildcard A record, and a CNAME which isn’t supposed to be working.

This is a combo of your DNS setup being misconfigured, and DNS caching working differently on Windows vs Linux.

Resolution is just fixing your DNS to work properly.

From the docs you linked it specifically says it only works for A or AAAA records. Don’t know how your other machines are somehow working as you thought they would.

You probably have debug logging enabled somewhere.

You’re not wrong on your initial points at all, and I said as much above, so we’re in agreement.

You seem to be thinking Valve is shutting down Deck as a product, and I never said that at all. They just have more important irons in the fire. There is also an obvious benefit in them pivoting Deck 2 to an ARM SoC in the next version, and they’ve literally said as much. AMD already quietly announced their ARM-based SoC (sort of by accident), so it’s not weird at all for a company like Valve to: 1) Focus on the pivot they are currently making and 2) Focus on the development of Deck 2.

On your other point: nobody, including Valve said they were discontinuing anything. People are freaking out because they’re out of stock. So what? They have bigger fish to fry. If they do another production run, they may do it after launch of the new hardware just to see where things lie, but who knows.

If you’re familiar with Valve’s history in hardware, you know they don’t officially discontinue anything, they just stop selling it in between hardware revision releases. There is absolutely nothing weird happening here that is inconsistent with their history of this.

My personal bet is they are guessing that Frame will be in direct competition with Deck, and they want people to buy that instead. Running out of stock of one during a product push for the other just seems like they care less about producing a dated product, but have the option to make another production run if they see things going that way.

We also don’t even have the insights into how well Deck is selling at this point. Maybe it just doesn’t make fiscal sense to make another production run right now. Who knows 🤷

If you’re familiar with the logistics of the components industry, you might understand.

You’re completely glossing over the connection between these things. New hardware line coming out this month-ish(?). They also want it to be successful. The product overlap is with the Frame, Switch 2, Arm devices at large, and the myriad other handhelds trying to copy the success of Deck.

Now, if you’re Valve, your bread and butter isn’t the devices, it’s platform lock-in. More devices running Steam means more money, regardless of the device itself. This is why they’ve taken the time to make sure SteamOS was portable enough to run on a bunch of other devices, which is the big note here.

They’re thinking platform, you’re only concerned with a single piece of hardware that had a miniscule impact on their bottom line. They make BILLIONS in pure profit every year ust from platform engagement. Deck made them millions over four years. That’s the difference.

So what makes more sense? More Deck models, or more devices spreading into a larger ecosystem to gain further footholds into platform engagement?

Deck honestly doesn’t factor much into that. Frame and FEX however is going to be monumental shift into a massive expansion of Steam on ARM, and will probably ultimately mean if there is another Deck, it’s also going to be ARM. It’s a much bigger picture than all the comments in here are putting together.

PXE is unnecessary unless you’re going to be creating a reusable boot image. Just faster to use LiveUSB.

What did you getaid off, and what are you trying to apply to? Maybe help to understand on what you’re trying to learn.

Just for your own sanity, just install Talos on the 3 machines, understand how to join them to a cluster, then deploy some stuff around the cluster. Get a feel for the basics before you get into the mess of trying to do it all in VMs.

I’d also check some comparisons on the various flavors of different lube stacks: k3s, microk8s, kubedge…etc. Theres so many now it’s hard to track.

Because you’re being rate limited. Don’t let these tools constantly hammer Github’s API in mass fits and starts or you may get a back off from GH.