[SOLVED] nvidia drivers - and more

Sector11 · 2021-03-18 14:10:40

EDIT: - Waiting for bug fix

EDIT 2: - SOLVED.
_____________________

nvidia-detect says:

It is recommended to install the
    nvidia-driver
package.

My questions are:

2. what is the "xx" in the nvidia-legacy-390xx-driver package
- - and how do I find out if there is a way to do so?
3. exactly at what stage do I remove the nouveau driver?

--- WHAT i DID ---
I was here:
https://wiki.debian.org/NvidiaGraphicsD … buster-390

 18 Mar 21 @ 10:38:16 ~
   $ nvidia-detect
Detected NVIDIA GPUs:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)

Checking card:  NVIDIA Corporation GK208 [GeForce GT 710B] (rev a1)
Your card is supported by the default drivers and legacy driver series 390.
It is recommended to install the
    nvidia-driver
package.

I have reached #2 of this, sources list already had contrib non-free:

For support of GeForce 400 series and newer GPUs (supported devices).

  1.  Add "contrib" and "non-free" components to /etc/apt/sources.list, for example:

    # Debian 10 "Buster"
    deb http://deb.debian.org/debian/ buster main contrib non-free

  2.  Update the list of available packages, then we can install the nvidia-legacy-390xx-driver package, plus the necessary firmware:

    # apt update
    # apt install nvidia-legacy-390xx-driver firmware-misc-nonfree

  3.  DKMS will build the nvidia module for your system, via the nvidia-legacy-390xx-kernel-dkms package.
    Restart your system to load the new driver.

   $ lspci -nn | egrep -i "3d|display|vga"
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1)
08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8)

Currently I am using nouveau with the onboard-no memory video graphics, the 2nd in the list up there. I want to use the card that has 2GB of dedicated memory.

I repeat:
My questions are:
1. nvidia-detect says:

It is recommended to install the
    nvidia-driver
package.

but later I see:

2. what is the "xx" in the nvidia-legacy-390xx-driver package
- - and how do I find out if there is a way to do so?
3. exactly at what stage do I remove the nouveau driver?

OR: Did I miss something obvious?
I really do not want to bork the system

====================
====================
====================

EDIT: DUH!!!!!!!

 18 Mar 21 @ 11:16:48 ~
   $ ser nvidia-legacy-390xx-driver
alias ser = aptitude search
p   nvidia-legacy-390xx-driver                                 - NVIDIA metapackage (390xx legacy version)                           
p   nvidia-legacy-390xx-driver:i386                            - NVIDIA metapackage (390xx legacy version)                           
p   nvidia-legacy-390xx-driver-bin                             - NVIDIA driver support binaries (390xx legacy version)               
p   nvidia-legacy-390xx-driver-bin:i386                        - NVIDIA driver support binaries (390xx legacy version)               
p   nvidia-legacy-390xx-driver-libs                            - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) (390xx legacy ver
p   nvidia-legacy-390xx-driver-libs:i386                       - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries) (390xx legacy ver
v   nvidia-legacy-390xx-driver-libs-i386                       -                                                                     
p   nvidia-legacy-390xx-driver-libs-i386:i386                  - NVIDIA metapackage (OpenGL/GLX/EGL/GLES 32-bit libraries) (390xx leg
p   nvidia-legacy-390xx-driver-libs-nonglvnd                   - NVIDIA metapackage (non-GLVND OpenGL/GLX/EGL/GLES libraries) (390xx 
p   nvidia-legacy-390xx-driver-libs-nonglvnd:i386              - NVIDIA metapackage (non-GLVND OpenGL/GLX/EGL/GLES libraries) (390xx 
v   nvidia-legacy-390xx-driver-libs-nonglvnd-i386              -                                                                     
p   nvidia-legacy-390xx-driver-libs-nonglvnd-i386:i386         - NVIDIA metapackage (non-GLVND OpenGL/EGL etc. 32-bit libraries) (390

OK so do I:
1. install nvidia-legacy-390xx-driver
2. remove nouveau
3. shutdown
3. switch cable from mobo graphics connector to card connector
4. reboot
5. PRAY!

NOW I feel silly!

Last edited by Sector11 (2021-04-06 19:34:53)

damo · 2021-03-18 16:43:33

Generally the process I use is:

1 Switch to tty and stop the lightdm service
2 Change to root

sudo su -

3 apt-get nvidia-driver
4 Let the install handle the nouveau blacklist. There should be some ncurses dialogs.
5 DO NOT run nvidia-xconfig
5 Restart lightdm.service
6 Back to tty7

Sector11 · 2021-03-19 11:31:13

Hi damo

damo wrote:

Generally the process I use is:
1 Switch to tty and stop the lightdm service
2 Change to root
sudo su -
3 apt-get nvidia-driver
4 Let the install handle the nouveau blacklist. There should be some ncurses dialogs.
5 DO NOT run nvidia-xconfig
5 Restart lightdm.service
6 Back to tty7

Step 1 - switch to which tty?
- - I do not use lightdm, I log in directly from tty1

How do I disable x since I do not use lightdm?
- seems everything I read says "stop lightdm"

I'm guessing I'd go back to tty1

did not realize the install blacklists nouveau.

When does one run nivida-xconfig?

Sector11 · 2021-03-19 11:48:23

On tty2:

sector11 login:
password:
sector11@sector11: ~$sudo su -
[sudo] Password for sector11:
root@sector11:~# apt-get nvidia-driver
E: invalid operation nvidia-driver
root@sector11:~#

Hmmm maybe
apt-get install nvidia-driver ?

But I still have a GUI environment running on tty1

tknomanzr · 2021-03-19 15:40:28

I usually just run nvidia-settings before I relog and it handles setting up the X config.

Sector11 · 2021-03-20 02:43:09

Thing is I will have to shut down and change my cable from the Mobo Graphics to the Graphics Card.

So I guess it is: "nvidia-settings" after I reboot.

Sector11 · 2021-03-20 02:54:11

OK new problem:

apt-get install nvidia-driver

Wanted to install both 64bit and i386 programs

I only need i386 for my Brother Printer.

Any advice appreciated.

damo · 2021-03-20 03:11:45

A common experience is that running nvidia-xconfig is a very good way of borking your X server, at least on a Debian system.

In the past I had to use a Live disc to go in and restore the overwritten files in order to get past the infamous black screen with flashing cursor.

rbh · 2021-03-20 08:03:29

damo wrote:

borking

From https://www.urbandictionary.com/define.php?term=Borking

Borking
A meme way of saying "barking".
The term borking is usually used when a photo of a dog/doggo/pupper is shown.
The word borking comes from 'bork' which sometimes dogs are captioned saying 'bork'.
The word is mostly used on Tumblr where most of the weird memes are born.

Help me understand the meaning you was using.

damo · 2021-03-20 08:20:02

It's a common term on these forums.

bork

to cause to malfunction, especially computer hardware or software.

Sector11 · 2021-03-20 12:39:12

There were 2 "critical bugs" and while at:

root@sector11

In one of the critical bugs it said "You have to be root to install" ? as well as info on the bug.

Thie idea On HOLD

unklar · 2021-03-20 12:58:10

Sector11 wrote:

There were 2 "critical bugs" and while at:
root@sector11
In one of the critical bugs it said "You have to be root to install" ? as well as info on the bug.
Thie idea On HOLD

^This is
sudo su -
?

(cheers to those who invented sudo) 8)

PackRat · 2021-03-20 15:04:59

Sector11 wrote:

Step 1 - switch to which tty?
- - I do not use lightdm, I log in directly from tty1

You mean you auto login to an X session when you log in to the computer? If so, comment out those lines so log into tty1 when you log in. Once nvidia drivers are installed you can un-comment the lines and go back to auto login to X no problems.

Sector11 · 2021-03-20 15:32:54

unklar wrote:

Sector11 wrote:
There were 2 "critical bugs" and while at:
root@sector11
In one of the critical bugs it said "You have to be root to install" ? as well as info on the bug.
Thie idea On HOLD
^This is
sudo su -
?
(cheers to those who invented sudo) 8)

Yes I did this, but in tty2, where I cannot copy here:

 20 Mar 21 @ 11:49:05 ~
   $ sudo su -
[sudo] password for sector11: 
root@sector11:~# apt-get install nvidia-driver

and it wanted to install almost 500MB of files as they were doubled. 64bit and i386.

With 2 critical errors. One was a conflict with another file? Maybe it i386 counterpart.

Tried something:

 20 Mar 21 @ 11:49:05 ~
   $ sudo su -
[sudo] password for sector11: 
root@sector11:~# apt-get install nvidia-driver>>nvidia-driver.txt

And here's everything it wanted to install:
/root/nvidia-driver.txt

Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  dkms gcc-8-base:i386 glx-alternative-mesa glx-alternative-nvidia
  glx-diversions libatomic1:i386 libbsd0:i386 libc6:i386 libdrm-amdgpu1:i386
  libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386
  libedit2:i386 libegl-mesa0:i386 libegl-nvidia0 libegl-nvidia0:i386
  libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386
  libgcc1:i386 libgl1:i386 libgl1-mesa-dri:i386 libgl1-nvidia-glvnd-glx
  libgl1-nvidia-glvnd-glx:i386 libglapi-mesa:i386 libgles-nvidia1
  libgles-nvidia1:i386 libgles-nvidia2 libgles-nvidia2:i386 libgles1
  libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0
  libglx-nvidia0:i386 libglx0:i386 libidn2-0:i386 libllvm7:i386 libnvidia-cbl
  libnvidia-cfg1 libnvidia-eglcore libnvidia-eglcore:i386
  libnvidia-fatbinaryloader libnvidia-glcore libnvidia-glcore:i386
  libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-ml1
  libnvidia-ptxjitcompiler1 libnvidia-rtcore libopengl0 libopengl0:i386
  libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libtinfo6:i386
  libunistring2:i386 libvulkan1:i386 libwayland-client0:i386
  libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdamage1:i386
  libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386
  libxxf86vm1:i386 nvidia-alternative nvidia-driver-bin nvidia-driver-libs
  nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386 nvidia-egl-common
  nvidia-egl-icd nvidia-egl-icd:i386 nvidia-installer-cleanup
  nvidia-kernel-common nvidia-kernel-dkms nvidia-kernel-support
  nvidia-legacy-check nvidia-modprobe nvidia-persistenced nvidia-settings
  nvidia-support nvidia-vdpau-driver nvidia-vulkan-common nvidia-vulkan-icd
  nvidia-vulkan-icd:i386 update-glx xserver-xorg-video-nvidia zlib1g:i386
Suggested packages:
  python3-apport glibc-doc:i386 locales:i386 lm-sensors:i386 vulkan-utils
  vulkan-utils:i386
The following NEW packages will be installed:
  dkms gcc-8-base:i386 glx-alternative-mesa glx-alternative-nvidia
  glx-diversions libatomic1:i386 libbsd0:i386 libc6:i386 libdrm-amdgpu1:i386
  libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386
  libedit2:i386 libegl-mesa0:i386 libegl-nvidia0 libegl-nvidia0:i386
  libegl1:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgbm1:i386
  libgcc1:i386 libgl1:i386 libgl1-mesa-dri:i386 libgl1-nvidia-glvnd-glx
  libgl1-nvidia-glvnd-glx:i386 libglapi-mesa:i386 libgles-nvidia1
  libgles-nvidia1:i386 libgles-nvidia2 libgles-nvidia2:i386 libgles1
  libgles1:i386 libgles2:i386 libglvnd0:i386 libglx-mesa0:i386 libglx-nvidia0
  libglx-nvidia0:i386 libglx0:i386 libidn2-0:i386 libllvm7:i386 libnvidia-cbl
  libnvidia-cfg1 libnvidia-eglcore libnvidia-eglcore:i386
  libnvidia-fatbinaryloader libnvidia-glcore libnvidia-glcore:i386
  libnvidia-glvkspirv libnvidia-glvkspirv:i386 libnvidia-ml1
  libnvidia-ptxjitcompiler1 libnvidia-rtcore libopengl0 libopengl0:i386
  libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libtinfo6:i386
  libunistring2:i386 libvulkan1:i386 libwayland-client0:i386
  libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386
  libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386
  libxcb-sync1:i386 libxcb-xfixes0:i386 libxcb1:i386 libxdamage1:i386
  libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386
  libxxf86vm1:i386 nvidia-alternative nvidia-driver nvidia-driver-bin
  nvidia-driver-libs nvidia-driver-libs:i386 nvidia-driver-libs-i386:i386
  nvidia-egl-common nvidia-egl-icd nvidia-egl-icd:i386
  nvidia-installer-cleanup nvidia-kernel-common nvidia-kernel-dkms
  nvidia-kernel-support nvidia-legacy-check nvidia-modprobe
  nvidia-persistenced nvidia-settings nvidia-support nvidia-vdpau-driver
  nvidia-vulkan-common nvidia-vulkan-icd nvidia-vulkan-icd:i386 update-glx
  xserver-xorg-video-nvidia zlib1g:i386
0 upgraded, 106 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/97.8 MB of archives.
After this operation, 496 MB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.

I have been searching for a way to try installing "nvidia-driver" without the i386 packages - seems to be a no go: It's all or nothing.

Ditching my Brother Laser Printer and getting an HP Laser Printer would eliminate the need for i386.

And expensive proposition for a cleaner 64bit Linux install.

Sector11 · 2021-03-20 15:41:06

PackRat wrote:

Sector11 wrote:
Step 1 - switch to which tty?
- - I do not use lightdm, I log in directly from tty1
You mean you auto login to an X session when you log in to the computer? If so, comment out those lines so log into tty1 when you log in. Once nvidia drivers are installed you can un-comment the lines and go back to auto login to X no problems.

No I do not auto login.

At "tty1" I am asked for my username and password, just not using a GUI to log in.

And I have no idea where I would go to comment out those lines anyway.

lightdm is not installed:

   $ sho lightdm
alias = aptitude show filename
Package: lightdm                  
Version: 1.26.0-4
State: not installed
Priority: optional
Section: x11
Maintainer: Debian Xfce Maintainers <debian-xfce@lists.debian.org>
Architecture: amd64
Uncompressed Size: 849 k
Depends: adduser, dbus, logind | consolekit, lightdm-gtk-greeter |
         lightdm-greeter, lsb-base (>= 3.0-6), debconf (>= 0.5) | debconf-2.0,
         libaudit1 (>= 1:2.2.1), libc6 (>= 2.14), libgcrypt20 (>= 1.7.0),
         libglib2.0-0 (>= 2.39.4), libpam0g (>= 0.99.7.1), libxcb1, libxdmcp6
Recommends: xserver-xorg
Suggests: accountsservice, upower, xserver-xephyr
Conflicts: lightdm:i386
Provides: x-display-manager
Description: simple display manager
 An X display manager that: 
 * Has a lightweight codebase 
 * Is standards compliant (PAM, ConsoleKit, etc) 
 * Has a well defined interface between the server and user interface 
 * Fully themeable 
 * Cross-desktop (greeters can be written in any toolkit) 
   
 Additional software can be useful along with LightDM: 
 * xserver-xephyr can be used to add a nested X display by calling 
  'dm-tool add-nested-seat`
 * upower can be used to suspend the computer from the display manager 
 * accountsservice is used to populate a user list with addition information.
Homepage: https://launchpad.net/lightdm
Tags: interface::graphical, interface::x11, role::program

ALSO:
I am not going to install nvidia-driver as long as I see those 2 critical bugs.

Sector11 · 2021-03-20 15:54:39

According to : Reduce Debian at this section

I can

REMOVE:
xserver-xorg-video-all
xserver-xorg-video-ati
xserver-xorg-video-fbdev
xserver-xorg-video-intel
xserver-xorg-video-qxl
xserver-xorg-video-radeon
xserver-xorg-video-vmware

and KEEP:
xserver-xorg-video-amdgpu
xserver-xorg-video-nouveau
xserver-xorg-video-vesa

maybe that would help.

EDIT: INTERESTING:

 20 Mar 21 @ 13:05:40 ~
   $ sremv xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vmware
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libxatracker2 libxvmc1
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-qxl
  xserver-xorg-video-radeon xserver-xorg-video-vmware
0 upgraded, 0 newly installed, 7 to remove and 1 not upgraded.
Remv xserver-xorg-video-all [1:7.7+19]
Remv xserver-xorg-video-ati [1:19.0.1-1]
Remv xserver-xorg-video-fbdev [1:0.5.0-1]
Remv xserver-xorg-video-intel [2:2.99.917+git20180925-2]
Remv xserver-xorg-video-qxl [0.1.5-2+b1]
Remv xserver-xorg-video-radeon [1:19.0.1-1]
Remv xserver-xorg-video-vmware [1:13.3.0-2]
 
 20 Mar 21 @ 13:05:54 ~
   $ aremv libxatracker2 libxvmc1
[sudo] password for sector11: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  libxatracker2* libxvmc1* xserver-xorg-video-all* xserver-xorg-video-intel* xserver-xorg-video-vmware*
0 upgraded, 0 newly installed, 5 to remove and 1 not upgraded.
After this operation, 7,253 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 160754 files and directories currently installed.)
Removing xserver-xorg-video-all (1:7.7+19) ...
Removing xserver-xorg-video-vmware (1:13.3.0-2) ...
Removing libxatracker2:amd64 (18.3.6-2+deb10u1) ...
Removing xserver-xorg-video-intel (2:2.99.917+git20180925-2) ...
Removing libxvmc1:amd64 (2:1.0.10-1) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
(Reading database ... 160703 files and directories currently installed.)
Purging configuration files for libxvmc1:amd64 (2:1.0.10-1) ...
Purging configuration files for xserver-xorg-video-intel (2:2.99.917+git20180925-2) ...
 
 20 Mar 21 @ 13:10:26 ~
   $

-------------------------
simulating again I get a shorter list:

 20 Mar 21 @ 13:10:26 ~
   $ sremv xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-qxl xserver-xorg-video-radeon xserver-xorg-video-vmware
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'xserver-xorg-video-all' is not installed, so not removed
Package 'xserver-xorg-video-intel' is not installed, so not removed
Package 'xserver-xorg-video-vmware' is not installed, so not removed
The following packages will be REMOVED:
  xserver-xorg-video-ati xserver-xorg-video-fbdev xserver-xorg-video-qxl xserver-xorg-video-radeon
0 upgraded, 0 newly installed, 4 to remove and 1 not upgraded.
Remv xserver-xorg-video-ati [1:19.0.1-1]
Remv xserver-xorg-video-fbdev [1:0.5.0-1]
Remv xserver-xorg-video-qxl [0.1.5-2+b1]
Remv xserver-xorg-video-radeon [1:19.0.1-1]
 
 20 Mar 21 @ 13:11:16 ~
   $

_________________
NTF: 1 not upgraded = conkyv1.9 on hold

Last edited by Sector11 (2021-03-20 16:05:11)

unklar · 2021-03-20 17:39:24

When I read your whole text again....

- you start with .xinitrc
So you don't have to worry about that.
xinitrc will only "take effect" AFTER your login on tty1. The step with ligthdm is omitted.

- the thing with the duplicate packages, I think you need to temporarily comment out this repo for your printer.

what says

Edit:
the 386 packages come because of this

Last edited by unklar (2021-03-20 18:38:11)

Sector11 · 2021-03-21 02:10:25

unklar wrote:

When I read your whole text again....
- you start with .xinitrc
So you don't have to worry about that.
xinitrc will only "take effect" AFTER your login on tty1. The step with ligthdm is omitted.
- the thing with the duplicate packages, I think you need to temporarily comment out this repo for your printer.

there is no repo, I added the i386 architecture then installed the file from Brother website.

unklar wrote:

what says
Edit:
the 386 packages come because of this

OH DUH!!!! because I have i386 on that package got added by nvidia-driver (the 64bit package)

So: Startpage (I don't do Google outright)

unix|linux stop apt from installing a file

and I see:
Three Ways to Exclude/Hold/Prevent a Specific Package from an apt Upgrade

So I put it on hold:

 20 Mar 21 @ 23:12:16 ~
   $ shld
conky-all
nvidia-driver-libs:i386
 
 20 Mar 21 @ 23:12:20 ~
   $

Now we'll see, on hold before installed ...

Sector11 · 2021-03-21 02:19:03

@ unklar - you are a genius!!!!!!

Put that package on hold and the results are:

installing "nvidia-driver" installs ±45 files @ 50MB not a single i386 file in the lot and approximately 500MB less in installed files.

Now - let's see if I get the 2 critical errors.

X fingers everyone.

Sector11 · 2021-03-21 02:52:36

Down to 1 error (bug) ... wrote it all down:

Debian GNU/Linix 10 sector11 tty2

sector11 login: sector11
Password:
 {blah}
 {blah}
sector11@sector11: sudo su -
[sudo] password for sector11:~#
root@sector11:~# apt-get install nvidia-driver
 {blah}
 {blah} long list of files etc . . .
Need to get 0B/50.1MB
 ... 100+MB on disk {blah blah}
Do you want to continue (Y|n) y
 {blah}
 {blah}
Grave byg of dkms(→ 2.6.1-4) <resolved in some versions>
b1 - #956245 - /etc/kernel/header_postinst.d/dkms: error! You must be root to use this command (fixed dkms/2.8.2-1 dkms/2.8.2-2)
Summary;
dkms(1 bug)

You did not see this damo?

"I" must be bugged!

I really do not want to mess with this bug

#1 2021-03-18 14:10:40

[SOLVED] nvidia drivers - and more

#2 2021-03-18 16:43:33

Re: [SOLVED] nvidia drivers - and more

#3 2021-03-19 11:31:13

Re: [SOLVED] nvidia drivers - and more

#4 2021-03-19 11:48:23

Re: [SOLVED] nvidia drivers - and more

#5 2021-03-19 15:40:28

Re: [SOLVED] nvidia drivers - and more

#6 2021-03-20 02:43:09

Re: [SOLVED] nvidia drivers - and more

#7 2021-03-20 02:54:11

Re: [SOLVED] nvidia drivers - and more

#8 2021-03-20 03:11:45

Re: [SOLVED] nvidia drivers - and more

#9 2021-03-20 08:03:29

Re: [SOLVED] nvidia drivers - and more

#10 2021-03-20 08:20:02

Re: [SOLVED] nvidia drivers - and more

#11 2021-03-20 12:39:12

Re: [SOLVED] nvidia drivers - and more

#12 2021-03-20 12:58:10

Re: [SOLVED] nvidia drivers - and more

#13 2021-03-20 15:04:59

Re: [SOLVED] nvidia drivers - and more

#14 2021-03-20 15:32:54

Re: [SOLVED] nvidia drivers - and more

#15 2021-03-20 15:41:06

Re: [SOLVED] nvidia drivers - and more

#16 2021-03-20 15:54:39

Re: [SOLVED] nvidia drivers - and more

#17 2021-03-20 17:39:24

Re: [SOLVED] nvidia drivers - and more

#18 2021-03-21 02:10:25

Re: [SOLVED] nvidia drivers - and more

#19 2021-03-21 02:19:03

Re: [SOLVED] nvidia drivers - and more

#20 2021-03-21 02:52:36

Re: [SOLVED] nvidia drivers - and more

Board footer