[SOLVED] Nouveau is laggy but official Nvidia drivers don't work

nazprim1442 · 2022-11-12 15:25:08

I have been using Geforce GT 710 for a year, since day 1 very laggy, usually crashing, while using Nouveau, so I decided to install official drivers and no problem until I once updated the kernel and it stopped working. The solution was to downgrade the kernel since I was told Nvidia doesn't update the drivers for my GT 710 anymore.

However, after a few months of upgrades (except for the kernel version), it stopped working again, but this time I couldn't fix it- and belive me, I tried very hard. I spent countless hours trying to find out what was the problem (gcc version, systemd version, blacklist files, grub configuration, modules, packages, etc) and not only that but Nouveau didn't work anymore after being reloaded, and the only solution I could find was to reinstall Arch. I tried numerous times after that, but with no results and having to reinstall again.

So I am quite lost, desesperate and confused. I would either fix Nouveau problems than having to go through the process of installing the official drivers, but I am open to anything. My computer runs smoothly in Windows and in Arch when I was using official Nvidia drivers.

What should I do?

Last edited by nazprim1442 (2022-11-15 18:25:43)

Slithery · 2022-11-12 17:11:47

nazprim1442 wrote:

What should I do?

We have absolutely no idea as you haven't provided us with any useful information.
https://bbs.archlinux.org/viewtopic.php?id=57855

seth · 2022-11-12 17:29:03

I was told Nvidia doesn't update the drivers for my GT 710 anymore.

https://aur.archlinux.org/packages/nvidia-470xx-dkms/
https://wiki.archlinux.org/title/NVIDIA#Installation

nazprim1442 · 2022-11-12 18:26:03

Slithery wrote:

nazprim1442 wrote:
What should I do?
We have absolutely no idea as you haven't provided us with any useful information.
https://bbs.archlinux.org/viewtopic.php?id=57855

I was posting on Windows and I neither know what was useful information. I cant even copy the logs to the NTFS Windows filesystem because of some weird "shutdown" problem that only allows me read-only use. My processor is Intel.

Anyways, decided to give it a try again to official drivers. First, went back to Kernel version 5.17.0, because after 5.18 the computer will just get stuck. Once done this, I tried to install official drivers through the website installer, but said that my gcc version wasn't the same as the one used for the kernel.
So, I downgraded the gcc and gcc-libs version to 11.2.0. Now the installer runs at first without no gcc check error but then fails again. I also tried using

yay -S nvidia-470xx-dkms

and it gives the same error log than the website installer:

cc1: error: incompatible gcc/plugin version
cc1: error: failed to initialize plugin ./scripts/gcc.plugins/structleak_plugin.so

Note: I copied that manually, I can't post the entire log for the already stated reasons.

So what I read is that this is related to different gcc versions, but again I checked:

cat /proc/version

returns

Linux version 5.17.0-arch1-1 (linux@archlinux) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils

And,

gcc -version

returns

gcc (GCC) 11.2.0

so everything seems fine at first. I am stuck then because I can't find anything on the internet about this situation.

Slithery · 2022-11-12 18:32:48

nazprim1442 wrote:

First, went back to Kernel version 5.17.0, because after 5.18 the computer will just get stuck. Once done this, I tried to install official drivers through the website installer, but said that my gcc version wasn't the same as the one used for the kernel.
So, I downgraded the gcc and gcc-libs version to 11.2.0. Now the installer runs at first without no gcc check error but then fails again.

A terrible idea. The wiki specifically tells you not to do this. The packages in the repositories are built for the current kernel version.
Downgrading random packages will just break your system even more than it already is.

nazprim1442 wrote:

I was posting on Windows and I neither know what was useful information. I cant even copy the logs to the NTFS Windows filesystem because of some weird "shutdown" problem that only allows me read-only use.

There's no need to copy the logs to your NTFS partition, just upload them directly to a link on the forum...
https://wiki.archlinux.org/title/List_o … n_services

nazprim1442 · 2022-11-12 18:42:41

Slithery wrote:

nazprim1442 wrote:
Once done this, I tried to install official drivers through the website installer
A terrible idea. The wiki specifically tells you not to do this.

It is not a terrible idea, it is the only idea since pacman installation basically fails.

Slithery wrote:

nazprim1442 wrote:
I was posting on Windows and I neither know what was useful information. I cant even copy the logs to the NTFS Windows filesystem because of some weird "shutdown" problem that only allows me read-only use.
There's no need to copy the logs to your NTFS partition, just upload them directly to a link on the forum...
https://wiki.archlinux.org/title/List_o … n_services

Thanks I didn't know about these applications.

I tried also downgrading gcc-d andd gcc-fortran according to https://bbs.archlinux.org/viewtopic.php?id=252685 but still, same error.

seth · 2022-11-12 18:45:59

So, I downgraded the gcc and gcc-libs version to 11.2.0
…
Linux version 5.17.0-arch1-1 (linux@archlinux) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils

after 5.18 the computer will just get stuck

Probably not. Stop flailing around
Boot the multi-user.target, in doubt also pass "nomodeset" to the kernel.
Update the system, in doubt switch to the lts kernel - partial downgrades are like partial upgrades and for you a recipe for disaster.
Then build nvidia-470xx-dkms (make sure the appropriate linux*headers package is installed)

It is not a terrible idea

Stop arguing - you have *obviously* no idea what you're talking or doing. That's all.

Last edited by seth (2022-11-12 18:47:40)

nazprim1442 · 2022-11-12 18:59:26

seth wrote:

So, I downgraded the gcc and gcc-libs version to 11.2.0
…
Linux version 5.17.0-arch1-1 (linux@archlinux) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils
after 5.18 the computer will just get stuck
Probably not. Stop flailing around
Boot the multi-user.target, in doubt also pass "nomodeset" to the kernel.
Update the system, in doubt switch to the lts kernel - partial downgrades are like partial upgrades and for you a recipe for disaster.
Then build nvidia-470xx-dkms (make sure the appropriate linux*headers package is installed)
It is not a terrible idea
Stop arguing - you have *obviously* no idea what you're talking or doing. That's all.

You don't have to be arrogant. And yes I admit I am not an expert but all those arch wiki links posted here I have already read them, I have spent days and days surfing the web and trying solutions, asking people around too. Updating the system is not the problem. https://forum.garudalinux.org/t/nvidia- … date/19923

I also downgraded linux-headers too. I know it is not a 'terrible idea' because in the past it was how I fixed it real quick, downgrade + website installation, pacman option didn't work for me (independently of the kernel version).

seth · 2022-11-12 19:04:26

I know it is not a 'terrible idea'

No you don't.
If you *knew*, you'd not be asking for help.
Take it or leave it.

https://forum.garudalinux.org/t/nvidia- … date/19923

So you're using garuda?

nazprim1442 · 2022-11-12 19:12:26

seth wrote:

I know it is not a 'terrible idea'
No you don't.
If you *knew*, you'd not be asking for help.
Take it or leave it.
https://forum.garudalinux.org/t/nvidia- … date/19923
So you're using garuda?

I ask for help because I can't find a solution not because I am not being rational, if pacman package for nvidia doesn't work and if the installer tells me the kernel and the installed gcc are a different version, it is logical to fix I belive.

And no I don't use Garuda I was just giving an example of other people with Nvidia having problems after upgrading to 5.18. If I use Nvidia official drivers in a version higher than 5.18, the computer will just get completely stuck on boot, not even being able to go to a different console.

seth · 2022-11-12 19:31:11

The error is because dkms is out of sync w/ the kernel.
Your GPU isn't supported by the nvidia drivers > 470xx and newer kernels likely run you into the IBT issue, see the blue note in https://wiki.archlinux.org/title/NVIDIA#Installation

Edit: ftr. this will affect any newer kernel and any nvidia driver - no matter how you install it - until nvidia fixes this.
And I'll again point out that the proper couch in any such situation is the LTS kernel, not downgrading an increasing amount of random packages.

seth wrote:

Stop flailing around
Boot the multi-user.target, in doubt also pass "nomodeset" to the kernel.
Update the system, in doubt switch to the lts kernel - partial downgrades are like partial upgrades and for you a recipe for disaster.
Then build nvidia-470xx-dkms (make sure the appropriate linux*headers package is installed)

Last edited by seth (2022-11-12 19:33:04)

nazprim1442 · 2022-11-13 02:00:43

seth wrote:

The error is because dkms is out of sync w/ the kernel.
Your GPU isn't supported by the nvidia drivers > 470xx and newer kernels likely run you into the IBT issue, see the blue note in https://wiki.archlinux.org/title/NVIDIA#Installation

Even with ibt=off as a kernel parameter or nvidia-open, after 5.18 it just won't boot unless I use nouveau. It will just get stuck.

nazprim1442 · 2022-11-13 03:05:40

seth wrote:

Edit: ftr. this will affect any newer kernel and any nvidia driver - no matter how you install it - until nvidia fixes this.
And I'll again point out that the proper couch in any such situation is the LTS kernel, not downgrading an increasing amount of random packages.

And linux-lts also gets stuck, just with a different output. It gets stuck at

Finished File System Check on /dev/disk/by-uuid/227E-45D7

Last edited by nazprim1442 (2022-11-13 11:57:53)

cfr · 2022-11-13 04:08:51

If you read through the Garuda thread you posted, you'll see there was supposed to be a fix in May. (I have no idea whether that's true, but I have no less reason to believe it than the rest of the thread.)

Did the system get stuck when you booted to the multi-user.target?

Did you fully update your system after installing the lts kernel?

Last edited by cfr (2022-11-13 04:10:33)

seth · 2022-11-13 08:14:54

Post a current xorg log, https://wiki.archlinux.org/title/Xorg#General and the journal of a "stuck" boot.

However, if you rebooted w/ a HW button it's likely not preserved - you should then try
1. the multi-user.target (which will likely boot because I expect a broken display server config)
2. switching the VT (ctrl+alt+F1,F2,F3,F4,… - which might fail if the graphical.target - your DM - is stubborn)
3. frenetically pressing ctrl+alt+del (because at some point systemd will interpret that as wish to reboot)
4. https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

nazprim1442 · 2022-11-13 11:52:06

seth wrote:

Post a current xorg log, https://wiki.archlinux.org/title/Xorg#General and the journal of a "stuck" boot.
However, if you rebooted w/ a HW button it's likely not preserved - you should then try
1. the multi-user.target (which will likely boot because I expect a broken display server config)
2. switching the VT (ctrl+alt+F1,F2,F3,F4,… - which might fail if the graphical.target - your DM - is stubborn)
3. frenetically pressing ctrl+alt+del (because at some point systemd will interpret that as wish to reboot)
4. https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Tried of all that, same result.

Xorg log returns:

[    15.786] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Nov 13 04:15:07 2022
[    15.788] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration

nazprim1442 · 2022-11-13 11:56:29

cfr wrote:

Did the system get stuck when you booted to the multi-user.target?
Did you fully update your system after installing the lts kernel?

Yes,

uname -r

returns 5.19.6-arch1-1.

seth · 2022-11-13 12:12:10

That is neither an xorg log, nor the system journal.

nazprim1442 · 2022-11-13 12:24:45

Okay guys, fixed now. I installed linux-lts and linux-lts-headers again (I had already tried this in the past but probably forgot to try also the aur nvidia drivers), then run

yay -S nvidia-470xx-dkms

but also

systemd set-default graphical.target

multi-user.target won't work for some reason and will get stuck.

seth · 2022-11-13 14:49:23

If the multi-user.target got "stuck", you'd not be able to reach the graphical.target either.
You're simply booting into a console login…

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2022-11-12 15:25:08

[SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#2 2022-11-12 17:11:47

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#3 2022-11-12 17:29:03

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#4 2022-11-12 18:26:03

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#5 2022-11-12 18:32:48

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#6 2022-11-12 18:42:41

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#7 2022-11-12 18:45:59

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#8 2022-11-12 18:59:26

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#9 2022-11-12 19:04:26

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#10 2022-11-12 19:12:26

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#11 2022-11-12 19:31:11

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#12 2022-11-13 02:00:43

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#13 2022-11-13 03:05:40

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#14 2022-11-13 04:08:51

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#15 2022-11-13 08:14:54

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#16 2022-11-13 11:52:06

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#17 2022-11-13 11:56:29

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#18 2022-11-13 12:12:10

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#19 2022-11-13 12:24:45

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

#20 2022-11-13 14:49:23

Re: [SOLVED] Nouveau is laggy but official Nvidia drivers don't work

Board footer