SavvyBeardedFish

Pretty sure that information is stored in the driver, so you should be able to query it using monitoring software, i.e. see:

NVML-API

I know tooling like nvtop uses the API, but unsure whether it displays the maximum temperature

Maybe the LLMs they prompted didn't know about the built-in SSH support, hence still recommends PuTTY? 🤔

Der8auer's video is worth a watch, he got one of the Redditor's card:

https://youtu.be/Ndmoi1s0ZaY

The whole downside is that not everyone is a data horder with space for videos

Some media players allows for streaming directly using yt-dlp, e.g.;

mpv <youtube url>

Will use yt-dlp if installed

Sounds like you might just be max'ing out the capacity of the coax cable as well (depending on length/signal integrity). E.g. ITGoat (not sure how trustworthy this webpage is, just an example) lists 1 Gbps as the maximum for coax while you would typically expecting less than that, again depending on your situation (cable length, material, etc)

What's your situation into the wall? Depending on country/ISP/regulations they might give you up to 1000 Mbps under the assumption that it's a single line going to a single user, however quite often that line is shared with potentially a lot of different customers.

Some countries allows you to buy packages where you have a standalone line going to your wall, however at an additional cost

If I remember correctly the default sudo timeout is set to 5 minutes on Yay, you should be able to increase it to something more reasonable

No bios update, but you most likely received both microcode updates (which is what will fix/mitigate the Intel issue, the bios is only to ensure everybody gets the microcode update) and firmware updates (from linux-firmware)

Of course non-mainlined (i.e. not in the linux kernel) firmware is a bit more iffy, luckily it's getting slowly better with OEMs using fwupd for those scenarios

Could it be an issue with the Nvidia drivers, boot with acpi=off and then install the (proprietary) nvidia drivers and then reboot to see if it boots normally now?

Breaking Linux every week or every other week? That's almost impressive!

I've used: User Agent Switcher

Successfully using;

1. Whitelist mode
2. Domain = teams.microsoft.com
3. UserAgentString = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36

They support meetings in Firefox so it's a bit weird why they would block calls... They're effectively the same thing

Additionally, if you change your userAgent to be Chrome things are working pretty good in Firefox as far as I've tried it (not too extensively)