I found a thread in the forum discussing how their nouveau had been blacklisted causing problems for their multiple display set up. The dev handling my bug report also found that nouveau is not appearing in my lsmod.
I tried to follow the suggestions in the “blacklist” thread, but there was no similar file in which to unblacklist nouveau. My latest post on the bug report:
(https://forums.opensuse.org/t/nouveau-does-not-load-during-boot-up-after-leap-15-5-upgrade/167273/8)
Found a thread on the forum discussing nouveau being blacklisted by the system, I ran through some of the suggested commands and found:
[code]n01 # modprobe -c | grep nouveau
blacklist nouveau
alias pci:v000010DEd*sv*sd*bc03sc*i* nouveau
alias pci:v000012D2d*sv*sd*bc03sc*i* nouveau
n01 # grep -r nouveau /usr/lib/modprobe.d /etc/modprobe.d
/etc/modprobe.d/nvidia-default.conf:blacklist nouveau
[code]
[quote]KittyKatty
Student Penguin
Jun 2023
Thank you so much!
I have checked /lib/modprobe.d and found that in 09-nvidia-modprobe-bbswitch-G04.conf there was line that blacklisted nouveau. After commented it out, it seems to be working now!
I hope one day I will be able to use the actual nVidea drivers. [quote]
I had to navi to /lib/modprobe.d and in that directory there was no "09-nvidia-modprobe-bbswitch-G04.conf file. I believe that data is listed at the top of the new attachment.
I could not replicate the fix, but it appears that at some point, nouveau was blacklisted in my system . . . possibly resulting in this "non-revival from suspend" problem??
Looking for any hint or direction on how to unblacklist nouveau in my system, which seems to have been blacklisted at some point in Leap’s iteration, without my knowledge or choice . . . possibly this issue might be associated with the recurring “non-revival from suspend” in my Leap 15.6 system?
Alrighty, that does seem to have restored “revival from suspend” function in my machine. I’ll have to monitor it for longevity.
Thanks kindly for the data . . . problem has been following numerous iterations of Leap, now maybe a semblance of an idea as to the “why” of it . . . .
I don’t know if you read the linked other thread, where “kitty-katty” lost her ext monitors after an upgrade . . . in which, she also was using nouveau, and then after the upgrade, lost the ext monitors as well as finding that nouveau had been blacklisted. I think the dev on my bug report said something about, “this wasn’t supposed to happen on old chips like yours, just the new ones . . . .” So, the unamed devs knew about something upstream they had done for nvidia cards . . . without much in the way of notification??
In my recent case, over the time since Oct '23 I had problems with “non-revival from suspend” in TW, then Slow Roll, and then in Leap . . . . Years ago I figured out that proprietary runs into problems, so I always use nouveau or default (as you suggested at one point) . . . so I would not have installed Nvidia and then incompletely uninstalled it . . . .
And, in working on the bug report, the unamed dev saw that “nouveau was blacklisted” . . . but provided no further hints on that. I ran a google on those terms and found the linked thread . . . when I got the data on rm-ing the “nvidia.conf” file . . . and the subsequent “dracut” move . . . nouveau returned to lsmod . . . and in two attempts to test it . . . revival from suspend . . . !!! After a number of months of the problem . . . .
I suspect that something in some zypper upgrade, did something that blacklisted nouveau . . . I don’t know whether that was back in an earlier iteration of Leap . . . which I have been upgrading via editing the repos, OR in some recent zyppering . . . ???
@non_space that all depends on the status of the card manufacture date, for example Turing or later may get the open nvidia driver installed, so nouveau would be blacklisted. Bit like the radeon/amdgpu transition.
Well, I would assume that would be at installation of the system, the installer would run that check??
But, then, once installed should not be adjusting or blacklisting modules, once selected?? I can say w/o hesitation that nouveau was selected at install, but subsequently the “system” changed that ???
@non_space I surmise that the nvidia card is detected and does it’s foo on a dup post install ? From memory with my T400 it did that at some point, I have it locked so it doesn’t…
This non-revival from suspend problem hit hard on my SUSE based installs but not the Debian or Ubuntu-based . . . but recently did hit my Manjaro on the same machine. So seems like the SUSE systems are reviewing the card at intervals, but that is not happening in the others? I haven’t had time to get back to Manjaro to check lsmod in that system, yet. New problem for that system.
So, I don’t have to lock anything in those non-SUSE systems, but this has been a very time-consuming problem in the SUSE-land, so for them I would want to lock nouveau??
@non_space I locked nvidia-open-driver-G06-signed-kmp-default and kernel-firmware-nvidia-gsp-G06 I don’t use resume, hibernate or swap, so don’t see an issue
Hmm . . . OK, I did lock one of my SUSE’s at G05, because G06 did cause some problems in my TW? install?? Nouveau is showing fine in my TW install, and suspend works . . . .
It??? I’m assuming you mean your exact commands as written with the “G06”??? which would relate to the “G06” level of Nvidia firmware??
My machine is '12 with an aftermarket GTX780 . . . it seemed to hit problems when the “g06” packages came in, probably in my TW install, so I had to find the “nvidia-open-driver-G05 xxxx” and lock it there. But didn’t seem to hit problems in Leap with G06???
I’ll have to check both of them out to see if anything is applicable.
So, I booted TW and checked YaSt and I saw that it was indeed the “nvidia-open-driver-G06-signed-kmp-default” package that was marked as “locked” or “taboo.”
The “kernel-firmware-nvidia-gsp-G06” package appeared to be installed, so I deleted it, and now marked as “do not install” . . . .
