deadbeef

I have two AMD Radeon cards for Linux that I'm pretty happy with that replaced a couple of Nvidia cards. They are an RX6800 and an RX6700XT. They were both ex mining cards that I bought when the miners were dumping their ethereum rigs, so they were pretty cheap.

If I had to buy a new card to fill that gap, I'd probably get a 7800XT, but if you don't game on them you could get a much lower end model like an RX7600.

Sorry to hear about that mess.

I posted here https://lemmy.nz/comment/1784981 a while back about what I went through with the Nvidia driver on Linux.

From what I can tell, people who think Linux works fine on Nvidia probably only have one monitor or maybe two that happen to be the same model ( with unique EDID serials FWIW ). My experience with a whole bunch of mixed monitors / refresh rates was absolutely awful.

If you happen to give it another go, get yourself an AMD card, perhaps you can carry on using the Nvidia card for the language modelling, just don't plug your monitors into it.

Oh not seriously, just making fun of the LTT vote which resulted in Linus using one for a bit.

A fairphone actually sounds pretty cool.

What you need is an LG Wing: https://en.wikipedia.org/wiki/LG_Wing

Your bridge isn't bridging properly. If Router B is sending a destination unreachable then the packets are being handled on it further up the stack at layer 3 by some sort of routing component rather than by a layer 2 bridging one.

Steam can do pretty well filling a tail circuit, probably better on average. But a torrent of a large file with a ton of peers when your client has the port forward back into the client absolutely puts more pressure on a tail circuit. More flows makes the shaping work harder.

Sometimes we see an outlier in our reporting and it's not obvious if a customer has a torrent or a DDoS directed at them for the first few minutes.

No, if two 300 megabit tails are shaped correctly, a third user shouldn't notice that the 1G backhaul has got a bunch of use going on.

If you do, there's something wrong or you aren't really getting the 1G for some reason. Not generally a concern in a carrier platform.

I build ISP and private data networks for a living.

A contention ratio for residential circuits of 3 to 1 isn't bad at all. You'd have to get pretty unlucky with your neighbors being raging pirates to be able to tell that was contended at all. Any data cap should scare the worst of the pirates away, so you probably won't be in that situation.

If you can feel the circuit getting worse at different times of the day then the effective contention ( taking into account further upstream ) is probably more like 30 to 1 than 3 to 1.

I've been using Linux for something like 27 years, I wouldn't say evangelical or particularly obsessed.

I started using it because some of the guys showing up to my late 90's LAN parties were dual booting Slackware it and it had cool looking boot up messages compared to DOS or Windows at the time. The whole idea of dual booting operating systems was pretty damn wild to me at the time too.

After a while it became obvious to me that Slackware '96 was way more reliable than DOS or Windows 95 at the time, a web browser like Netscape could take out the whole system pretty easily on Windows, but when Netscape crashed on Linux, you opened up a shell and killed off whatever was left of it and started a new one.

I had machines that stayed up for years in the late 90's and that was pretty well impossible on Windows.

Often on Linux group membership changes only take effect on login. So you could try logging out of your session and logging back in after your group changes to test that theory out.

The context of this post is Linux on AMD cards, is there any support at all for raytracing or upscaling of any sort on Linux on either AMD or Nvidia? Serious question.

A 2 gigabit event isn't big enough to be considered a real attack, a service like cloudflare can sink a 2 terrabit attack every day of the week.

Building a DDoS protection service ( that isn't just black holing traffic ) starts with having enough bandwidth to throw away the attack volume plus keep your desired traffic working and have a bit of overhead to work your mitigation strategies.

What this means is to DIY a useful service you start by buying a couple of terrabits of bandwith in 'small' chunks of a hundred gigabits or so in most peering locations around the globe and then you build a proxy layer like cloudflare on top of it with a team of smart dudes to automate outsmarting the bad guys.

I don't like cloudflare either, but the barriers to entry in this industry are epic.