Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
Classic-Start
Renamed to NeoClassic-UI then renamed to Open-Shell - https://github.com/Open-Shell/Open-Shell-Menu
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
I don't think it's your fault and I don't think you're using the wrong browser.
> I should be working out the dependency story and compiling some driver from Github myself.
no, nvidia _should_ make it easier for people using the 3rd most popular desktop OS to use their hardware. It would make them more competitive against AMD and Intel, which both support hardware video decoding.
That's probably not going to happen, so the next best option is to install a package from the package manager [0]. There might be some kind of compilation needed, but in my experience that's rarely an issue (aside from time), especially if it's coming out of the package manager for a popular distribution.
> It's just not a real option for maybe 99% of PC users.
well, 99% of PC users with Nvidia hardware. It's an important distinction since this problem is specific to Nvidia. If the solution is to installing a package from the package manager, it's only as difficult as installing the browser in the first place.
I do agree there's some extra questions that may make things difficult, or unfamiliar for the vast majority of people, though. Like how is someone supposed to know they need the nvidia-vaapi-driver package anyway?
[0] - https://github.com/elFarto/nvidia-vaapi-driver#package-manag...
I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom
It works on Windows also.
> spend hours on google to fix some crap
That's the Windows way. It's a bad fit for Linux, because there is no one true obsessively-backwards-compatible Linux.
The good news is we don't need it: Linux isn't a black box, so we don't need to guess or study its behavior. We can look it up instead. The goal here is to construct understanding from documentation, as opposed to deconstructing behavior from testing.
Some great starting points to get your bearings are:
- https://wiki.archlinux.org/
- https://wiki.gentoo.org/wiki/Main_Page
- man pages
FYI, Classic Shell is discontinued, long live the https://github.com/Open-Shell/Open-Shell-Menu
YMMV, but in my experience it works flawlessly.
If that fails there are chip specific tools you can use to read/write to the right partitions, such as the fantastic EDL tool for Qualcomm devices:
https://github.com/bkerler/edl