I anticipate the used value for those gens is going to drop quicker than a Mercedes CL65AMG

…after knowing for damn sure it was a serious issue in two successive process generations.

There is no way this happened without a LOT of people knowing EXACTLY what was happening, and covering it up. The DoJ should really kick off an investigation into the situation, because it’s pretty obvious there was malfeasance at multiple levels. That, or their leadership and QC processes are both so categorically inept that one could argue the company should be straight up nationalized as a critical strategic asset.

Not to mention, iirc you should get a bit of a perf bump for the GPU due to AMD’s Infinity Cache, so long as you roll with (iirc) Zen2+ and RDNA2+

That all makes sense - I guess at this point, I’m simply trying to offer some constructive criticism about how to present nuanced problems that involve both hardware and software gremlins in a way that you’ll get the most productive conversation and interaction from the user base here.

Heh, we’re still on the X-Y problem to a degree.

I’d recommend another top-level reply to your post, or a new post, describing precisely how your hardware and ZFS pools are set up, alongside a description of the firmware/stability issues you’re seeing, and solutions you’ve tried already. We’re a bit far down a comment chain at the moment, so you’ll probably get more engagement that way. Not trying to be an ass - this actually sounds like an interesting (and, I’m sure, obnoxious) problem. Putting all the cards on the table will help people give you a more complete answer more quickly.

A bit of searching brought me here - would this suit your purposes?

Edit: amusingly, one of the replies to the original question also points out that this is yet another classical example of the X-Y problem

You are evidently missing the entire point of what the X-Y problem is.

What are you ACTUALLY trying to accomplish here? Why do (think) you need to throttle your USB speed to 50%?

Uh… are you not aware of the catastrophically bad lithography issues Intel has had lately across both the 13th and 14th gen, and the subsequent ass-tier fashion in which they handled it?

Do not buy a 13th or 14th gen Intel CPU.

amber lamps

Fair; I blame target fixation

Well sure, but the question was about gluetun, so I was trying to focus on that and the applications thereof. In terms of homelab stuff, I know a lot of people appreciate the containerized approach.

Now emulate the 4004 logic design in redstone on the 4004

Oh yeah you can do it that way too, but if you want it all containerized, that’s roughly how to do it. That’s all I meant.

It’s convenient if you want to see gluetun up as the only way a container (say, your torrenting container) can get to the open net, in the interest of avoiding getting directly pinged by DMCA rats. That way, if the VPN goes down, your torrent client isn’t just downloading stuff nakedly. Also, if you want to set up different VPN connections for different containers, it’s pretty easy to set a handful of replica containers for that too.

Then it should have no effect.

This is just a nice way to define file-discrete .rc scripts. Like, maybe you have one for shell stuff, one for your custom collection of command aliases, one for initializing pyenv+pyenv-virtualenv, etc. That way, you have domain-constrained .rcs, and it’s easier to scan through things to see if something funny is going on / is broken or whatever.

That’s gonna be a nope from me, dawg

I had an old T60p - yeah, Core 2 Duo baybeeeee. Iirc that was one of the last models that were made under IBM before Lenovo bought the Thinkpad brand. Since then, my primary personal laptop has ALWAYS been a thinkpad, simply because the keyboard IS that good. Seriously, I really do not think that any other laptop line offers a better keyboard, or is so consistently at the top of the pack.

Note: I’m talking specifically about Thinkpads, and particularly the X and T lines. Non-thinkpads are much more of a roll of the dice.

Note that some issue devices have VT-x disabled and the bios locked down by Corp IT for one reason or another, so a VM may not actually be possible from the work issue device here.

Tbh, just run the Ubuntu box headless and ssh into it. You can do anything you’d need to. Even better, swap it to Debian or something like that, because Ubuntu is unfortunately kinda undergoing gradual enshitification lately.

Tbh I don’t recommend Ubuntu to people anymore