[SOLVED] nvidia drivers - and more

Sector11 · 2021-03-26 20:29:40

@ jeffreyC

I will save it for another day. Thank you

unklar · 2021-03-26 21:13:30

What does he say to

apt install nvidia-driver --no-install-recommends

with the 386 packages ?

Sector11 · 2021-03-26 21:16:21

I have absolutely NO IDEA what is going on.

1. went to root

sudo su -

2. I removed i386 programs:

apt-get purge ".*:i386"

3. I removed i386 architecture - will reinstall printer drivers later.

dpkg --remove-architecture i386

4. dropped to tty2

sudo su -
apt install nvidia-driver

all looked good, no i386 packages.

Got the notice about conflicting nouveau driver & best way to deal with it was reboot. GREAT I thought!

Watched the process to the end, no errors.

5. [Ctrl]+[Alt]+[F1]
6. OB menu - shutdown

Switched cable to video card

7. Rebooted
- BIOS Screen
- GRUB screen - Debian
8. tty1 asking for my login name | password
....

9. tty1 asking for my login name | password
....

10. tty1 asking for my login name | password
....
shut down .....
11. put graphics cable back on mobo graphic
- thinking: No nouveau driver - will need to reinstall
- OH JOY!!!!

12. REBOOTED <<<<<<<<
SAY WHAT? HERE i AM - CONFUSED LIKE THE DEVIL!

 26 Mar 21 @ 18:10:01 ~
   $ s11
System:    Host: sector11 Kernel: 4.19.0-14-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Openbox 3.6.1 dm: startx 
           Distro: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME A320M-K v: Rev X.0x serial: <filter> UEFI: American Megatrends v: 5603 
           date: 10/14/2020 
CPU:       Topology: Quad Core model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP arch: Zen 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 27947 
           Speed: 1827 MHz min/max: 1600/3500 MHz Core speeds (MHz): 1: 1827 2: 1872 3: 3036 4: 1900 
Graphics:  Device-1: NVIDIA GK208 [GeForce GT 710B] vendor: Gigabyte GK208B driver: nvidia v: 418.181.07 bus ID: 01:00.0 
           chip ID: 10de:128b 
           Device-2: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: ASUSTeK driver: amdgpu v: kernel 
           bus ID: 08:00.0 chip ID: 1002:15dd 
           Display: tty server: X.Org 1.20.4 driver: amdgpu,ati,modesetting,nouveau,nvidia unloaded: fbdev,vesa alternate: nv 
           compositor: compton resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.27.0 4.19.0-14-amd64 LLVM 7.0.1) v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: NVIDIA GK208 HDMI/DP Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:0e0f 
           Device-2: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio vendor: ASUSTeK 
           driver: snd_hda_intel v: kernel bus ID: 08:00.1 chip ID: 1002:15de 
           Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 08:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k4.19.0-14-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: e000 
           bus ID: 06:00.0 chip ID: 10ec:8168 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 40.26 GiB (4.3%) 
           ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB speed: 6.0 Gb/s serial: <filter> 
Partition: ID-1: / size: 27.37 GiB used: 5.93 GiB (21.7%) fs: ext4 dev: /dev/sda1 
           ID-2: /boot/efi size: 761.5 MiB used: 5.1 MiB (0.7%) fs: vfat dev: /dev/sda7 
           ID-3: /home size: 27.38 GiB used: 4.31 GiB (15.7%) fs: ext4 dev: /dev/sda2 
           ID-4: /media/10 size: 228.18 GiB used: 2.38 GiB (1.0%) fs: ext4 dev: /dev/sda4 
           ID-5: /media/11 size: 228.18 GiB used: 60.0 MiB (0.0%) fs: ext4 dev: /dev/sda5 
           ID-6: /media/12 size: 172.26 GiB used: 60.0 MiB (0.0%) fs: ext4 dev: /dev/sda6 
           ID-7: /media/5 size: 228.18 GiB used: 27.52 GiB (12.1%) fs: ext4 dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 40.4 C mobo: N/A gpu: amdgpu temp: 40 C 
           Fan Speeds (RPM): cpu: 0 
Weather:   Temperature: 23.3 C (74 F) Conditions: Clear sky Wind: from WNW at 0.5 m/s (2 km/h, 1 mph) Cloud Cover: 1% 
           Humidity: 83% Dew Point: 20.3 C (69 F) Pressure: 1004 mb (33 in) 
           Current Time: Fri 26 Mar 2021 06:10:04 PM -03 (America/Argentina/Buenos_Aires) Source: WeatherBit.io 
Info:      Processes: 183 Uptime: 17m Memory: 13.69 GiB used: 1.10 GiB (8.1%) Init: systemd v: 241 runlevel: 5 Compilers: 
           gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: terminator inxi: 3.0.32 
 
 26 Mar 21 @ 18:10:04 ~
   $

That's it I'm done with this.

- I put i386 architecture back and add my printer drivers.

Sector11 · 2021-03-26 21:40:44

unklar wrote:

What does he say to
apt install nvidia-driver --no-install-recommends
with the 386 packages ?

Too late now, nvidia-driver installed but something not right, see my last post.

 26 Mar 21 @ 18:38:43 ~
   $ sho nvidia-driver
alias = aptitude show filename
Package: nvidia-driver            
Version: 418.181.07-1
State: installed

DeepDayze · 2021-03-26 23:29:24

The nvidia driver is loaded:

driver: nvidia

You should disable the builtin graphics if you want to purely use the nvidia card, and plug in the monitor cable to the nvidia card. I have that same AMD chip in my system so I disabled onboard graphics via the BIOS.

Last edited by DeepDayze (2021-03-26 23:30:30)

unklar · 2021-03-27 09:05:28

^^You're going to destroy your whole system.... big_smile

In my opinion, you always confuse the 386 packages with those that nvidia installs in addition. But the 386-nvidia packages are only meant for people who want to play crappy M$ games via wine for example.
In this sense 386 has nothing in common with 386 on your system here.

Assuming you haven't already undone everything, you're standing here now, and you should after updating Xorg you should reinstall the driver.
Note: Also this tutorial is already 8 years old and I have NO nvidia wink
Please change above to en

By the way, I need the exact name of your printer, because it can't be that there are only 386 packages for it. hmm

Sector11 · 2021-03-27 14:22:34

DeepDayze wrote:

The nvidia driver is loaded:
driver: nvidia
You should disable the builtin graphics if you want to purely use the nvidia card, and plug in the monitor cable to the nvidia card. I have that same AMD chip in my system so I disabled onboard graphics via the BIOS.

That worked ... but I got three lines of errors at least 2 were BIOS ERRORS

I am on my: GeForce GT 710B card at the moment

How do I read the error logs of tty1 from tty2-7 ?

Because tty1 is my log in point.

Looks like "nouveau" is still there but "unloaded":

Graphics:  Device-1: NVIDIA GK208 [GeForce GT 710B] vendor: Gigabyte GK208B driver: nvidia v: 418.181.07 bus ID: 01:00.0 
           chip ID: 10de:128b 
           Display: tty server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           compositor: compton resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 418.181.07 direct render: Yes

Then I found this:
EDIT: Just noticed that the code above from inxi says the "nouveau" driver is unloaded so this does not apply, but will leave it:

You need to unload the nouveau driver before you can load the nvidia driver. However, the nouveau driver is currently in use by the X-server, so it cannot be unloaded yet. You have to stop the X-server first (but don't just re-start it, as then it will use the nouveau driver again).
So in short:
stop X-server: sudo service lightdm stop
unload the nouveau driver: sudo rmmod nouveau
load the nvidia driver: sudo modprobe nvidia
start the X-server: sudo service lightdm start

You might be out-of-luck and the framebuffer for the console is locking the nouveau driver as well. In this case I haven't found a way to unload the driver at all...

Obviously 1 and 4 in my case can be eliminated.
Does everyone in the world use lightdm?

Last edited by Sector11 (2021-03-27 15:19:53)

Sector11 · 2021-03-27 15:14:47

unklar wrote:

^^You're going to destroy your whole system....

My feeling exactly ... I was willing to leave it alone. But still got replies.

So what I did - AFTER getting the proper dkms installed:

removed all i386 programs (just my printer drivers anyway)
- sudo apt purge ".*:i386"
got rid of i386 architecture
- sudo dpkg --remove-architecture i386
dropped to tty2 and installed the nividia-driver
rebooted - have OOPS with card would not work
rebooted - with mobo graphics card
- sudo dpkg --add-architecture i386
re-installed printer drivers
- /media/10/Brother_HL1110/hl1110cupswrapper-3.0.1-1a.i386.deb
- /media/10/Brother_HL1110/hl1110lpr-3.0.1-1a.i386.deb

unklar wrote:

In my opinion, you always confuse the 386 packages with those that nvidia installs in addition. But the 386-nvidia packages are only meant for people who want to play crappy M$ games via wine for example.
In this sense 386 has nothing in common with 386 on your system here.

Exactly why I removed i386 this time before installing nvidia-driver.
See above and the post above this one to DeepDayze

unklar wrote:

Assuming you haven't already undone everything, you're standing here now, and you should after updating Xorg you should reinstall the driver.
Note: Also this tutorial is already 8 years old and I have NO nvidia
Please change above to en
By the way, I need the exact name of your printer, because it can't be that there are only 386 packages for it.

Printer is Brother: HL1112 (South American designation for HL1110)

The debian package does not support this printer.

   $ sho printer-driver-brlaser
alias = aptitude show filename
Package: printer-driver-brlaser   
Version: 4-1
State: not installed
Priority: optional
Section: text
Maintainer: Debian Printing Team <debian-printing@lists.debian.org>
Architecture: amd64
Uncompressed Size: 66.6 k
Depends: libc6 (>= 2.14), libcups2 (>= 1.4.0), libcupsimage2 (>= 1.4.0), libgcc1
         (>= 1:3.0), libstdc++6 (>= 5.2)
Conflicts: printer-driver-brlaser:i386
Description: printer driver for (some) Brother laser printers
 CUPS filter driver supporting (some) Brother laser printer. 
 
 This driver is known to support these printers: 
 * Brother DCP-7030 
 * Brother DCP-7065DN 
   
 This package contains the CUPS filter driver for the supported laser printers.
Homepage: https://github.com/pdewacht/brlaser

Sector11 · 2021-03-27 15:42:28

Box says:
GIGIBYTE NVIDIA
GEFORCE GT710
2GB DDRS

 27 Mar 21 @ 12:24:28 ~
   $ sudo lspci -v -s 01:00.1
[sudo] password for sector11: 
01:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)
	Subsystem: Gigabyte Technology Co., Ltd GK208 HDMI/DP Audio Controller
	Flags: bus master, fast devsel, latency 0, IRQ 56
	Memory at f6080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Endpoint, MSI 00
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

Or maybe I am: Xorg.0.log
lines 160 to 168:

[    46.367] (II) NVIDIA GLX Module  418.181.07  Sun Dec 27 18:55:20 UTC 2020
[    46.388] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[    46.388] (--) NVIDIA(0):     CRT-0 (boot)
[    46.388] (--) NVIDIA(0):     DFP-0
[    46.388] (--) NVIDIA(0):     DFP-1
[    46.392] (II) NVIDIA(0): NVIDIA GPU GeForce GT 710 (GK208) at PCI:1:0:0 (GPU-0)
[    46.392] (--) NVIDIA(0): Memory: 2097152 kBytes
[    46.392] (--) NVIDIA(0): VideoBIOS: 80.28.b8.00.6d
[    46.392] (II) NVIDIA(0): Detected PCI Express Link width: 8X

Last edited by Sector11 (2021-03-27 15:52:15)

unklar · 2021-03-27 16:18:54

^^Now it is correct (you must read like this) big_smile

...
Display: tty server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 

driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa

the Xorg also says lol

unklar · 2021-03-27 16:33:32

You are right, the "old carrot" HL 1112 is only available in 386.deb hmm

https://support.brother.com/g/b/downloa … dlang=true

Sector11 · 2021-03-27 17:39:15

unklar wrote:

^^Now it is correct (you must read like this) big_smile

...
Display: tty server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 

driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa

the Xorg also says lol

Yup ... but moving a window is "jerky" - 2GB RAM and not smooth. sad

unklar wrote:

You are right, the "old carrot" HL 1112 is only available in 386.deb
https://support.brother.com/g/b/downloa … dlang=true

This I knew smile

@ damo, if you are still reading - and all

Why not run nvidia-settings ?

DeepDayze · 2021-03-28 00:51:20

Sector11 wrote:

DeepDayze wrote:
The nvidia driver is loaded:
driver: nvidia
You should disable the builtin graphics if you want to purely use the nvidia card, and plug in the monitor cable to the nvidia card. I have that same AMD chip in my system so I disabled onboard graphics via the BIOS.
That worked ... but I got three lines of errors at least 2 were BIOS ERRORS
I am on my: GeForce GT 710B card at the moment
How do I read the error logs of tty1 from tty2-7 ?
Because tty1 is my log in point.
Looks like "nouveau" is still there but "unloaded":
Graphics:  Device-1: NVIDIA GK208 [GeForce GT 710B] vendor: Gigabyte GK208B driver: nvidia v: 418.181.07 bus ID: 01:00.0 
           chip ID: 10de:128b 
           Display: tty server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv 
           compositor: compton resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GT 710/PCIe/SSE2 v: 4.6.0 NVIDIA 418.181.07 direct render: Yes 
Then I found this:
EDIT: Just noticed that the code above from inxi says the "nouveau" driver is unloaded so this does not apply, but will leave it:
You need to unload the nouveau driver before you can load the nvidia driver. However, the nouveau driver is currently in use by the X-server, so it cannot be unloaded yet. You have to stop the X-server first (but don't just re-start it, as then it will use the nouveau driver again).
So in short:
stop X-server: sudo service lightdm stop
unload the nouveau driver: sudo rmmod nouveau
load the nvidia driver: sudo modprobe nvidia
start the X-server: sudo service lightdm start

You might be out-of-luck and the framebuffer for the console is locking the nouveau driver as well. In this case I haven't found a way to unload the driver at all...
Obviously 1 and 4 in my case can be eliminated.
Does everyone in the world use lightdm?

I get those same errors in BIOS as well but they are harmless on my setup and not interfering with system operation. Also you need to blacklist the nouveau driver like this:

Open “/etc/modprobe. d/blacklist. conf” in your favorite editor and add the following line to the end:

blacklist nouveau

Save and close the file. This will take effect on the next reboot.

Last edited by DeepDayze (2021-03-28 01:08:57)

Sector11 · 2021-03-28 02:34:07

This already exists, I did not create it:

/etc/modprobe. d/nvidia-blacklist-nouveau.conf

# You need to run "update-initramfs -u" after editing this file.

# see #580894
blacklist nouveau

My guess, part of the nvidia-driver install process.

I have done at least 2 reboots already.

I find moving windows is very jerky. sad

unklar · 2021-03-28 10:38:48

Sector11 wrote:

How do I read the error logs of tty1 from tty2-7 ?

For the future smile

1.Debian has a rescue tool that is not very well known. It comes with Systemd and is called debug-shell.service. It allows you to open a rescue shell on tty9 if you have problems with booting your system. The service file is pre-installed but not activated. So, to be able to use it when you need it. In this shell you are already root:

systemctl enable debug-shell.service

The system will set a symbolic link:

ln -s '/lib/systemd/system/debug-shell.service'
'/etc/systemd/system/sysinit.target.wants/debug-shell.service'

Please deactivate it again after work is done!

systemctl disable debug-shell.service

2. or, simply set it to tty1 and leave it open

sudo journalctl -af > ~/freeze.txt

Change to tty2, do the work and after logging in, logging out the log is in your ~/

Sector11 · 2021-03-28 11:41:32

Ooooo nice, thank you unklar.

Big8 · 2021-04-06 13:37:52

unklar wrote:

Sector11 wrote:
How do I read the error logs of tty1 from tty2-7 ?
For the future
1.Debian has a rescue tool that is not very well known. It comes with Systemd and is called debug-shell.service. It allows you to open a rescue shell on tty9 if you have problems with booting your system. The service file is pre-installed but not activated. So, to be able to use it when you need it. In this shell you are already root:
systemctl enable debug-shell.service
The system will set a symbolic link:
ln -s '/lib/systemd/system/debug-shell.service'
'/etc/systemd/system/sysinit.target.wants/debug-shell.service'
Please deactivate it again after work is done!
systemctl disable debug-shell.service
2. or, simply set it to tty1 and leave it open
sudo journalctl -af > ~/freeze.txt
Change to tty2, do the work and after logging in, logging out the log is in your ~/

Really thanks for me this was the solution .

Sector11 · 2021-04-06 20:19:50

All done - up and running.

It was a process though

NOTE: I do NOT have lightdm installed

IF you have i386 architecture" enabled on a 64 bit system.
And you can remove it for a while do so.
As I only needed it for my Brother Laser printer so:
1. went to root

sudo su -

2. I removed i386 programs:

apt-get purge ".*:i386"

3. I removed i386 architecture - will reinstall printer drivers later.

dpkg --remove-architecture i386

Now to get the update bug free version of "dkms" into Debian 10 Buster:
Because the dkms that comes with Buster is broken:

Parsing Found/Fixed information... Done
grave bugs of dkms (→ 2.6.1-4) <Resolved in some Version>
 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)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]

4. SO I grabbed

Debian SID: dkms (2.8.4-3)

5. And installed it locally:

 26 Mar 21 @ 11:24:08 ~
   $ sudo su -
[sudo] password for sector11: 
root@sector11:~# cd /media/10/DEBs/test-sid/
root@sector11:/media/10/DEBs/test-sid# sudo apt install ./dkms_2.8.4-3_all.deb

and that was in slick as a whistle!

 06 Apr 21 @ 16:35:57 ~
   $ sudo su -
[sudo] password for sector11: 
root@sector11:~# apt install nvidia-driver

and let it do it's work work.

And as damo said, do NOT run nvidis-config

And here I am <- my desktop.

My heartfelt thanks to everyone that helped here!
You're all great!

DeepDayze · 2021-04-07 12:59:30

Finally an end to quite an adventure. Now what happens when you re-enable i386 to reinstall your printer's driver?

Sector11 · 2021-04-07 15:37:44

DeepDayze wrote:

Finally an end to quite an adventure. Now what happens when you re-enable i386 to reinstall your printer's driver?

lol lol lol lol
My forgetter really is getting better, and ya had to point it out, didn't ya. wink

Well as soon as the nvidia-driver was in and I did a reboot I added i386 architecture:

dpkg --add-architecture i386

Then:

 $ sudo su -
 $ cd /media/10/Brother_HL1110/
 $bash hl1110cupswrapper-3.0.1-1a.i386.deb
 $bash hl1110lpr-3.0.1-1a.i386.deb

Instructions on this page - just stop the download.

Worked perfect!

BUT When this one dies: HP no more i386 for me.

But have no fear there will be another Sector11 Linux Adventure in the future I'm sure.

DeepDayze · 2021-04-07 19:07:44

Sector11 wrote:

DeepDayze wrote:
Finally an end to quite an adventure. Now what happens when you re-enable i386 to reinstall your printer's driver?

My forgetter really is getting better, and ya had to point it out, didn't ya.
Well as soon as the nvidia-driver was in and I did a reboot I added i386 architecture:
dpkg --add-architecture i386
Then:
 $ sudo su -
 $ cd /media/10/Brother_HL1110/
 $bash hl1110cupswrapper-3.0.1-1a.i386.deb
 $bash hl1110lpr-3.0.1-1a.i386.deb
Instructions on this page - just stop the download.
Worked perfect!
BUT When this one dies: HP no more i386 for me.
But have no fear there will be another Sector11 Linux Adventure in the future I'm sure.

Great to hear it all works now and yes HP's are worth getting as their drivers are quite robust compared to brother's. No i386 silliness for HP drivers smile

Once you move to Beryllium/Bullseye things should be working better with dkms.

Sector11 · 2021-04-08 16:23:42

DeepDayze wrote:

Great to hear it all works now and yes HP's are worth getting as their drivers are quite robust compared to brother's. No i386 silliness for HP drivers
Once you move to Beryllium/Bullseye things should be working better with dkms.

I may not be the brightest bulb in the room but I'm not totally burntout yet. smile

I struggle with a lot of things. And 'usually' get things working. I can do a lot on my own and when new things hit me, I try to find a fix. If I can't I'm here.

Bullseye will have the proper dkms, I'm running that version right now. Don't know why the Debian team can't bring it here as a bug fix? Does not make sense. BUT ...

I also read something about Bullseye and i386 architecture, forgot to bookmark it. Seems they are trimming it back, so an HP printer might be a thing before the 'Brother' dies.

And then there is this: Debian 'Bullseye' enters final phase before release as team debates whether it will be last to work on i386 architecture

To i386 or not to i386 that is the question,
But to HP is a given.

DeepDayze · 2021-04-08 16:39:41

I think it will be that i386 architecture will still be offered but i386 install media will no longer be available and the i386 packages will still be in the repos. There may be a time when i386 will be completely dropped however, but that will be a ways off as things like Steam still depend on 32 bit libs.

Last edited by DeepDayze (2021-04-08 16:41:20)

Sector11 · 2021-04-09 12:22:27

Hope for i386.
Hope for HP smile

#51 2021-03-26 20:29:40

Re: [SOLVED] nvidia drivers - and more

#52 2021-03-26 21:13:30

Re: [SOLVED] nvidia drivers - and more

#53 2021-03-26 21:16:21

Re: [SOLVED] nvidia drivers - and more

#54 2021-03-26 21:40:44

Re: [SOLVED] nvidia drivers - and more

#55 2021-03-26 23:29:24

Re: [SOLVED] nvidia drivers - and more

#56 2021-03-27 09:05:28

Re: [SOLVED] nvidia drivers - and more

#57 2021-03-27 14:22:34

Re: [SOLVED] nvidia drivers - and more

#58 2021-03-27 15:14:47

Re: [SOLVED] nvidia drivers - and more

#59 2021-03-27 15:42:28

Re: [SOLVED] nvidia drivers - and more

#60 2021-03-27 16:18:54

Re: [SOLVED] nvidia drivers - and more

#61 2021-03-27 16:33:32

Re: [SOLVED] nvidia drivers - and more

#62 2021-03-27 17:39:15

Re: [SOLVED] nvidia drivers - and more

#63 2021-03-28 00:51:20

Re: [SOLVED] nvidia drivers - and more

#64 2021-03-28 02:34:07

Re: [SOLVED] nvidia drivers - and more

#65 2021-03-28 10:38:48

Re: [SOLVED] nvidia drivers - and more

#66 2021-03-28 11:41:32

Re: [SOLVED] nvidia drivers - and more

#67 2021-04-06 13:37:52

Re: [SOLVED] nvidia drivers - and more

#68 2021-04-06 20:19:50

Re: [SOLVED] nvidia drivers - and more

#69 2021-04-07 12:59:30

Re: [SOLVED] nvidia drivers - and more

#70 2021-04-07 15:37:44

Re: [SOLVED] nvidia drivers - and more

#71 2021-04-07 19:07:44

Re: [SOLVED] nvidia drivers - and more

#72 2021-04-08 16:23:42

Re: [SOLVED] nvidia drivers - and more

#73 2021-04-08 16:39:41

Re: [SOLVED] nvidia drivers - and more

#74 2021-04-09 12:22:27

Re: [SOLVED] nvidia drivers - and more

Board footer