apt install firmware-nvidia-graphics firmware-nvidia-gsp nvidia-alternative nvidia-kernel-dkms nvidia-modprobe nvidia-settings nvidia-xconfig

# glxinfo | grep NVIDIA
server glx vendor string: NVIDIA Corporation
client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce MX250/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 535.216.01
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL version string: 4.6.0 NVIDIA 535.216.01
OpenGL shading language version string: 4.60 NVIDIA
OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 535.216.01

Tue Mar 11 11:37:10 2025: Loading kernel module nvidia-drm.
Tue Mar 11 11:37:11 2025: modprobe: ERROR: could not insert 'nvidia_current_open': No such device
Tue Mar 11 11:37:11 2025: modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe -i nvidia-current-open ' for module nvidia: retcode 1
Tue Mar 11 11:37:11 2025: modprobe: ERROR: could not insert 'nvidia': Invalid argument
Tue Mar 11 11:37:11 2025: modprobe: ERROR: could not insert 'nvidia_current_open_modeset': No such device
Tue Mar 11 11:37:11 2025: modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe nvidia ; modprobe -i nvidia-current-open-modeset ' for module nvidia_modeset: retcode 1
Tue Mar 11 11:37:11 2025: modprobe: ERROR: could not insert 'nvidia_modeset': Invalid argument
Tue Mar 11 11:37:11 2025: modprobe: ERROR: could not insert 'nvidia_current_open_drm': No such device
Tue Mar 11 11:37:11 2025: modprobe: ERROR: ../libkmod/libkmod-module.c:1047 command_do() Error running install command 'modprobe nvidia-modeset ; modprobe -i nvidia-current-open-drm ' for module nvidia_drm: retcode 1
Tue Mar 11 11:37:11 2025: modprobe: ERROR: could not insert 'nvidia_drm': Invalid argument

> The login system gets deleted and replaced by a Microsoft ID thing that prioritizes your Microsoft username over Github's username system, resulting in everyone having their @names taken away by random name squatters belonging to a 6 year old, unused Outlook account.

> At the same time, Github support gets outsources to Microsoft Support, which is already outsourced to the most rural parts of India, resulting in @name restoration requests recieving "I'm sorry, Sir. I am unable to do the needful." responses.

> A few months later, following a rather cryptic announcement by Microsoft regarding plans to "improve enterprise issue tracking", everyone suddenly finds Github's issue tracking system being replaced with an <iframe> reading to Microsoft's new, revolutionary Office 365 issue tracking system that serves an ample amount of 503's and has an average latency of 6 - 18 seconds. But don't worry, purchasing Github 365 Premium resolves all these problems, at an affordable $99 per year per repo.

> A few months after that, Microsoft's CEO announces that he "understands the frustrations" of the new Office 365 issue tracking system, especially when hosting multiple repos. Therefore Microsoft is now rebuilding Github to be leaner and better, and offering better Office 365 integration. This is followed by yet another announcement on Github's website that they are changing how repos work. Free account users can now only have 1 repo per account, "to avoid unnecessary resource usage, ensuring that Office 365 issue tracking will work better than ever", as the announcement put it.

> A year later, Microsoft announces an exciting new look for Github. The only problem is that it requires JavaScript. A lot of JavaScript. So attempting to access Github with JavaScript turned off simply presents you with a blank page saying "Please turn on JavaScript" with a sad octopus next to it. In the same announcement they also quickly mention that free account users can no longer use use "external apps" to get or push things to/from their repo. The only solution is to upgrade to Github 365 Premium, or use a "Microsoft Certified App", such as Visual Studio 2019, for development.

> Yet another year later Microsoft announces proudly that Github is now part of Office 365, ensuring that every enterprise will have their own, integrated, simple source code managing tool. No other info is given, aside from marketing buzzwords talking about SUCCESSFUL and REVENUE. Free users is suddenly presented with a "This account does not have an active Office 365 subscription. Click here to buy." when they attempt to login. Attempts at backing up or migrating their account fails with 403 errors, since you now need an Office 365 subscription to access any Github page.