deadbeef

If you go back a bit further, multi monitor support was just fine. Our office in about 2002 was full of folks running dual ( 19 inch tube! ) monitors running off matrox g400's with xinerama on redhat 6.2 ( might have been 7.0 ). I can't recall that being much trouble at all.

There were even a bunch of good years of the proprietry nvidia drivers, the poor quality is something that I've only really noticed in the last three or so years.

The support for larger numbers of monitors and mixed resolutions and odd layouts in KDE vastly improved in the ubuntu 23.04 release. I wouldn't install anything other than the latest LTS release for a server ( and generally a desktop ), but KDE was so much better that it was worth running something newer with the short term aupport on my desktops.

We aren't too far off the next LTS that will include that work anyway I guess. I'm probably going to be making the move to debian rather than trying that one out though.

It isn't something that is in the distro vendors control. Nvidia do not disclose programming info for their chipsets. They distribute an unreliable proprietry driver that is obfuscated to hell so that noone can help out fixing their problems.

If you use an AMD card it will probably work fine in Windows and Linux. If you use an Nvidia card you are choosing to run windows or have a bad time in Linux.

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

I had a Brother black and white laser (I think a HL1240?) for almost 10 years and then we started having to print a ton of education related stuff for our kid and colour made sense, so I got the closest thing that I could to the colour one that I use at work which ended up being a DCPL3551CDW.

Printing a little in Windows and Linux, but more often from apps on my Android phone and my partners iPhone.

I absolutely hate printers, but they have been fine.

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.