Beware upgrading to tw 20210222 if on nvidia GPU
Hi, I've just upgraded to snapshot 20210222 and my system doesn't boot anymore. I have success booting into kernel 5.10.12. No time to investigate now. cheers -- Daniele
Hello Daniele Am Mittwoch, 24. Februar 2021, 10:06:41 CET schrieb Daniele Granata:
I've just upgraded to snapshot 20210222 and my system doesn't boot anymore. I have success booting into kernel 5.10.12.
Thanks for the heads-up. I'm currently on TW 20210220 with Kernel 5.10.16, and everything works fine. No NVIDIA changes announced for snapshop 20210222 From which snapshot are you coming? Cheers Axel
Il giorno mer 24 feb 2021 alle ore 10:15 Axel Braun <axel.braun@gmx.de> ha scritto:
Hello Daniele
Am Mittwoch, 24. Februar 2021, 10:06:41 CET schrieb Daniele Granata:
I've just upgraded to snapshot 20210222 and my system doesn't boot anymore. I have success booting into kernel 5.10.12.
Thanks for the heads-up. I'm currently on TW 20210220 with Kernel 5.10.16, and everything works fine. No NVIDIA changes announced for snapshop 20210222 From which snapshot are you coming?
Cheers Axel
Hi Alex, I'm coming from the previous snapshot with kernel 5.10.16-1.2 that was removed. On my other system intel only I've had no trouble. On my laptop with intel gpu turned off the boot ends without graphic sddm login and on the terminal I can read a nvidia error. I apologize but i can't be more specific at the moment I'm very busy with my job. Maybe it's a fault of my system on its own. Cheers -- Daniele
Hi Daniele Am Mittwoch, 24. Februar 2021, 10:51:23 CET schrieb Daniele Granata:
Am Mittwoch, 24. Februar 2021, 10:06:41 CET schrieb Daniele Granata:
I've just upgraded to snapshot 20210222 and my system doesn't boot anymore. I have success booting into kernel 5.10.12.
Thanks for the heads-up. I'm currently on TW 20210220 with Kernel 5.10.16, and everything works fine. No NVIDIA changes announced for snapshop 20210222 From which snapshot are you coming?
I'm coming from the previous snapshot with kernel 5.10.16-1.2 that was removed. On my other system intel only I've had no trouble. On my laptop with intel gpu turned off the boot ends without graphic sddm login and on the terminal I can read a nvidia error. I apologize but i can't be more specific at the moment I'm very busy with my job. Maybe it's a fault of my system on its own.
Unfortunately I can confirm the issue with the latest snapshot. After zypper dup and reboot I end up in a terminal session more /var/log/Xorg.0.log | grep EE (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 69.552] (EE) Failed to load module "intel" (module does not exist, 0) [ 69.558] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 69.558] (EE) NVIDIA: system's kernel log for additional error messages and [ 69.558] (EE) NVIDIA: consult the NVIDIA README for details. [ 69.563] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 69.563] (EE) NVIDIA: system's kernel log for additional error messages and [ 69.563] (EE) NVIDIA: consult the NVIDIA README for details. [ 69.568] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 69.568] (EE) NVIDIA: system's kernel log for additional error messages and [ 69.568] (EE) NVIDIA: consult the NVIDIA README for details. [ 69.573] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 69.573] (EE) NVIDIA: system's kernel log for additional error messages and [ 69.573] (EE) NVIDIA: consult the NVIDIA README for details. [ 69.573] (EE) No devices detected. [ 69.573] (EE) [ 69.573] (EE) no screens found(EE) [ 69.573] (EE) [ 69.573] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 69.573] (EE) [ 69.591] (EE) Server terminated with error (1). Closing log file. journalctl -xb | grep nvidia Feb 24 12:08:45 X1E kernel: audit: type=1400 audit(1614164925.078:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=552 comm="app armor_parser" Feb 24 12:08:45 X1E kernel: audit: type=1400 audit(1614164925.078:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=552 com m="apparmor_parser" Feb 24 12:08:55 X1E suse-prime[1323]: Boot: setting-up nvidia card Feb 24 12:08:56 X1E suse-prime[1392]: trying switch ON nvidia: [bbswitch] NVIDIA card is ON Feb 24 12:08:56 X1E prime-select[1394]: modprobe: FATAL: Module nvidia_drm not found in directory /lib/modules/5.10.16-1-default https://bugzilla.opensuse.org/show_bug.cgi?id=1182666 Additionally, it is not possible the run prime-select intel from the command line, as the logout-waiter hangs https://bugzilla.opensuse.org/show_bug.cgi?id=1182667 Cheers Axel
Am Mittwoch, 24. Februar 2021, 13:01:17 CET schrieb Michael Pujos:
On 2/24/21 12:28 PM, Axel Braun wrote:
Additionally, it is not possible the run prime-select intel from the command line, as the logout-waiter hangs
You can also run prime-select from a vconsole, it should work.
No. the logout_waiter still hangs and does not switch the card BTW, tried to reinstall nvidia-G05 drivers w/o success Cheers Axel
On 2/24/21 5:41 PM, Axel Braun wrote:
You can also run prime-select from a vconsole, it should work. No. the logout_waiter still hangs and does not switch the card
BTW, tried to reinstall nvidia-G05 drivers w/o success
Cheers Axel
I meant it works from multi-user target , aka runlevel 3.
Axel Braun wrote:
Hi Daniele
Am Mittwoch, 24. Februar 2021, 10:51:23 CET schrieb Daniele Granata:
Am Mittwoch, 24. Februar 2021, 10:06:41 CET schrieb Daniele Granata:
I've just upgraded to snapshot 20210222 and my system doesn't boot anymore. I have success booting into kernel 5.10.12.
Thanks for the heads-up. I'm currently on TW 20210220 with Kernel 5.10.16, and everything works fine. No NVIDIA changes announced for snapshop 20210222 From which snapshot are you coming?
I'm coming from the previous snapshot with kernel 5.10.16-1.2 that was removed. On my other system intel only I've had no trouble. On my laptop with intel gpu turned off the boot ends without graphic sddm login and on the terminal I can read a nvidia error. I apologize but i can't be more specific at the moment I'm very busy with my job. Maybe it's a fault of my system on its own.
Unfortunately I can confirm the issue with the latest snapshot. After zypper dup and reboot I end up in a terminal session
So is this an optimus-only issue? I just dup'ed my desktop (GeForce GTX 980), using the standard nvidia repo, and all is fine here. The laptop is currently updating, so I'll see how that goes. But there I use bumblebee (and need to trigger dkms build myself). So far I don't expect issues with that. But I'll see. Just takes ages to download those 5438 packages :P
* Peter Suetterlin <pit@astro.su.se> [02-24-21 10:26]:
Axel Braun wrote:
Hi Daniele
Am Mittwoch, 24. Februar 2021, 10:51:23 CET schrieb Daniele Granata:
Am Mittwoch, 24. Februar 2021, 10:06:41 CET schrieb Daniele Granata:
I've just upgraded to snapshot 20210222 and my system doesn't boot anymore. I have success booting into kernel 5.10.12.
Thanks for the heads-up. I'm currently on TW 20210220 with Kernel 5.10.16, and everything works fine. No NVIDIA changes announced for snapshop 20210222 From which snapshot are you coming?
I'm coming from the previous snapshot with kernel 5.10.16-1.2 that was removed. On my other system intel only I've had no trouble. On my laptop with intel gpu turned off the boot ends without graphic sddm login and on the terminal I can read a nvidia error. I apologize but i can't be more specific at the moment I'm very busy with my job. Maybe it's a fault of my system on its own.
Unfortunately I can confirm the issue with the latest snapshot. After zypper dup and reboot I end up in a terminal session
So is this an optimus-only issue? I just dup'ed my desktop (GeForce GTX 980), using the standard nvidia repo, and all is fine here. The laptop is currently updating, so I'll see how that goes. But there I use bumblebee (and need to trigger dkms build myself). So far I don't expect issues with that. But I'll see. Just takes ages to download those 5438 packages :P
I also had difficulties, booted update provided reduced screen resolution. reinstalling nvidia-gfxG04-kmp-default corrected. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
Patrick Shanahan wrote:
* Peter Suetterlin <pit@astro.su.se> [02-24-21 10:26]:
So is this an optimus-only issue? I just dup'ed my desktop (GeForce GTX 980), using the standard nvidia repo, and all is fine here. The laptop is currently updating, so I'll see how that goes. But there I use bumblebee (and need to trigger dkms build myself). So far I don't expect issues with that. But I'll see. Just takes ages to download those 5438 packages :P
I also had difficulties, booted update provided reduced screen resolution. reinstalling nvidia-gfxG04-kmp-default corrected.
Just to confirm, you don't run primus/bumblebee, but just the plain nviia stuff from the nvidia repo? The laptop update meanwhile finished. Compiling the kernel modules went smooth, and the system runs as usual. I do however boot into the Intel-powered desktop (Skylake built-in) and only use bumblebee/optirun for accelerated stuff. But that works without issues here.
* Peter Suetterlin <pit@astro.su.se> [02-24-21 11:44]:
Patrick Shanahan wrote:
* Peter Suetterlin <pit@astro.su.se> [02-24-21 10:26]:
So is this an optimus-only issue? I just dup'ed my desktop (GeForce GTX 980), using the standard nvidia repo, and all is fine here. The laptop is currently updating, so I'll see how that goes. But there I use bumblebee (and need to trigger dkms build myself). So far I don't expect issues with that. But I'll see. Just takes ages to download those 5438 packages :P
I also had difficulties, booted update provided reduced screen resolution. reinstalling nvidia-gfxG04-kmp-default corrected.
Just to confirm, you don't run primus/bumblebee, but just the plain nviia stuff from the nvidia repo?
that is correct but my initial boot into the new kernel provided reduced screen resolution. after reinstallinng nvidia-gfxG04-kmp-default and restarting graphical target, full resolution was restored.
The laptop update meanwhile finished. Compiling the kernel modules went smooth, and the system runs as usual. I do however boot into the Intel-powered desktop (Skylake built-in) and only use bumblebee/optirun for accelerated stuff. But that works without issues here.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
Hi Peter, my HP Omen has the integrated GPU switched off so I don't use suse-prime or bumblebee. Regards Il giorno mer 24 feb 2021 alle ore 17:51 Patrick Shanahan <paka@opensuse.org> ha scritto:
* Peter Suetterlin <pit@astro.su.se> [02-24-21 11:44]:
Patrick Shanahan wrote:
* Peter Suetterlin <pit@astro.su.se> [02-24-21 10:26]:
So is this an optimus-only issue? I just dup'ed my desktop (GeForce GTX 980), using the standard nvidia repo, and all is fine here. The laptop is currently updating, so I'll see how that goes. But there I use bumblebee (and need to trigger dkms build myself). So far I don't expect issues with that. But I'll see. Just takes ages to download those 5438 packages :P
I also had difficulties, booted update provided reduced screen resolution. reinstalling nvidia-gfxG04-kmp-default corrected.
Just to confirm, you don't run primus/bumblebee, but just the plain nviia stuff from the nvidia repo?
that is correct
but my initial boot into the new kernel provided reduced screen resolution. after reinstallinng nvidia-gfxG04-kmp-default and restarting graphical target, full resolution was restored.
The laptop update meanwhile finished. Compiling the kernel modules went smooth, and the system runs as usual. I do however boot into the Intel-powered desktop (Skylake built-in) and only use bumblebee/optirun for accelerated stuff. But that works without issues here.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
-- Daniele
Am 24.02.21 um 10:15 schrieb Axel Braun:
I'm currently on TW 20210220 with Kernel 5.10.16, and everything works fine.
Same here: Snapshot 20210221 Kernel 5.10.16-1 NVIDIA GM204M [GeForce GTX 970M] driver: nvidia v: 460.39 All good, so I suspect it's something else for you Daniele. vinz.
I had the same problem. I rebooted to the previous kernel, reinstalled the nvidia-drivers (G04) with yast, ran mkinitrd, and rebooted. Now it is working again. Gr, Philip
On Thursday 25 February 2021, Philip Raets wrote:
I had the same problem.
I rebooted to the previous kernel, reinstalled the nvidia-drivers (G04) with yast, ran mkinitrd, and rebooted.
Now it is working again.
Gr,
Philip
Similar experience here. I have a 1650 Super and use the proprietary drivers installed via the "easy" route. After 20210222, sddm failed to start. I logged into a console and used the cursors version of Yast2 to reinstall (forced "Update") any already installed packages from the nvidia repo, rebooted and was back in business. I didn't have to do anything after running yast2, I did not manually mkinitrd. I poked around the logs a bit, but couldn't find any grumblings about modules, which I had seen under similar circumstances in the past (perhaps I was looking in the wrong places). Michael
I've updated with this snapshot and its worked fine with my Nvidia 3070 I use proprietary drivers and use their scripted install. Works fine. Cameron Seader Technology Strategist SUSE +1 208 420 2167 cs@suse.com www.suse.com ________________________________________ From: Michael Hamilton <michael@actrix.gen.nz> Sent: Wednesday, February 24, 2021 12:26 PM To: factory@lists.opensuse.org Subject: Re: Beware upgrading to tw 20210222 if on nvidia GPU On Thursday 25 February 2021, Philip Raets wrote:
I had the same problem.
I rebooted to the previous kernel, reinstalled the nvidia-drivers (G04) with yast, ran mkinitrd, and rebooted.
Now it is working again.
Gr,
Philip
Similar experience here. I have a 1650 Super and use the proprietary drivers installed via the "easy" route. After 20210222, sddm failed to start. I logged into a console and used the cursors version of Yast2 to reinstall (forced "Update") any already installed packages from the nvidia repo, rebooted and was back in business. I didn't have to do anything after running yast2, I did not manually mkinitrd. I poked around the logs a bit, but couldn't find any grumblings about modules, which I had seen under similar circumstances in the past (perhaps I was looking in the wrong places). Michael
On Thursday 25 February 2021, Cameron Seader wrote:
I've updated with this snapshot and its worked fine with my Nvidia 3070 I use proprietary drivers and use their scripted install. Works fine.
Cameron Seader Technology Strategist
SUSE +1 208 420 2167 cs@suse.com
www.suse.com
________________________________________ From: Michael Hamilton <michael@actrix.gen.nz> Sent: Wednesday, February 24, 2021 12:26 PM To: factory@lists.opensuse.org Subject: Re: Beware upgrading to tw 20210222 if on nvidia GPU
On Thursday 25 February 2021, Philip Raets wrote:
I had the same problem.
I rebooted to the previous kernel, reinstalled the nvidia-drivers (G04) with yast, ran mkinitrd, and rebooted.
Now it is working again.
Gr,
Philip
Similar experience here. I have a 1650 Super and use the proprietary drivers installed via the "easy" route. After 20210222, sddm failed to start. I logged into a console and used the cursors version of Yast2 to reinstall (forced "Update") any already installed packages from the nvidia repo, rebooted and was back in business. I didn't have to do anything after running yast2, I did not manually mkinitrd.
I poked around the logs a bit, but couldn't find any grumblings about modules, which I had seen under similar circumstances in the past (perhaps I was looking in the wrong places).
Michael
I don't know why it would work for some and not others. If "their scripted install" does not mean Yast, perhaps that's a factor. Clearly the reinstall of the nvidia rpm's did the right thing, but it's weird the update did not, especially since the previous update including a kernel bump worked just fine. Maybe it had something to do with the state of my machine or combo of displays and cards. I've look at the journalctl output for the boot that failed to start X11. Sddm did start, but did not identify any displays to add. Searching for nvidia failed to find any of normal kernel module load messages such as module license 'NVIDIA' taints kernel. The only nvidia related journal entries I could find was for audio/sound. For some reason the proprietary nvidia module wasn't included for boot - presumably it was missing from initrd. Michael
Maybe try my attachment script. Put your nvidia installer run package in a location the script can pick it up. I use this script when I'm docked to my eGPU and not on the road. I have an alternate script I run which converts my system back when i switch to going mobile. Let me know if your interested in my other script to go mobile. I think this script might fix up your problems. Cameron Seader Technology Strategist SUSE +1 208 420 2167 cs@suse.com www.suse.com ________________________________________ From: Michael Hamilton <michael@actrix.gen.nz> Sent: Wednesday, February 24, 2021 4:12 PM To: factory@lists.opensuse.org Subject: Re: Beware upgrading to tw 20210222 if on nvidia GPU On Thursday 25 February 2021, Cameron Seader wrote:
I've updated with this snapshot and its worked fine with my Nvidia 3070 I use proprietary drivers and use their scripted install. Works fine.
Cameron Seader Technology Strategist
SUSE +1 208 420 2167 cs@suse.com
www.suse.com
________________________________________ From: Michael Hamilton <michael@actrix.gen.nz> Sent: Wednesday, February 24, 2021 12:26 PM To: factory@lists.opensuse.org Subject: Re: Beware upgrading to tw 20210222 if on nvidia GPU
On Thursday 25 February 2021, Philip Raets wrote:
I had the same problem.
I rebooted to the previous kernel, reinstalled the nvidia-drivers (G04) with yast, ran mkinitrd, and rebooted.
Now it is working again.
Gr,
Philip
Similar experience here. I have a 1650 Super and use the proprietary drivers installed via the "easy" route. After 20210222, sddm failed to start. I logged into a console and used the cursors version of Yast2 to reinstall (forced "Update") any already installed packages from the nvidia repo, rebooted and was back in business. I didn't have to do anything after running yast2, I did not manually mkinitrd.
I poked around the logs a bit, but couldn't find any grumblings about modules, which I had seen under similar circumstances in the past (perhaps I was looking in the wrong places).
Michael
I don't know why it would work for some and not others. If "their scripted install" does not mean Yast, perhaps that's a factor. Clearly the reinstall of the nvidia rpm's did the right thing, but it's weird the update did not, especially since the previous update including a kernel bump worked just fine. Maybe it had something to do with the state of my machine or combo of displays and cards. I've look at the journalctl output for the boot that failed to start X11. Sddm did start, but did not identify any displays to add. Searching for nvidia failed to find any of normal kernel module load messages such as module license 'NVIDIA' taints kernel. The only nvidia related journal entries I could find was for audio/sound. For some reason the proprietary nvidia module wasn't included for boot - presumably it was missing from initrd. Michael
Thanks for sharing the script. Hopefully some others might find it useful. However, I don't think I need a solution along those lines. I have a fixed desktop system, I don't have any problems with the nvidia proprietary driver, and never have any need to switch it out. It's not a big hassle to reinstall the nvidia driver - it's an easy using Yast - but thought I comment here so that anyone who encounters the same update problem has an easy fix in the manner described by Philip, or by myself. It's also curious that not everyone with the proprietary drive is encountering the issue, which might be an issue in itself. Cheers, Michael On Thursday 25 February 2021, Cameron Seader wrote:
Maybe try my attachment script. Put your nvidia installer run package in a location the script can pick it up. I use this script when I'm docked to my eGPU and not on the road. I have an alternate script I run which converts my system back when i switch to going mobile. Let me know if your interested in my other script to go mobile. I think this script might fix up your problems.
Cameron Seader Technology Strategist
SUSE +1 208 420 2167 cs@suse.com
www.suse.com
________________________________________ From: Michael Hamilton <michael@actrix.gen.nz> Sent: Wednesday, February 24, 2021 4:12 PM To: factory@lists.opensuse.org Subject: Re: Beware upgrading to tw 20210222 if on nvidia GPU
On Thursday 25 February 2021, Cameron Seader wrote:
I've updated with this snapshot and its worked fine with my Nvidia 3070 I use proprietary drivers and use their scripted install. Works fine.
Cameron Seader Technology Strategist
SUSE +1 208 420 2167 cs@suse.com
www.suse.com
________________________________________ From: Michael Hamilton <michael@actrix.gen.nz> Sent: Wednesday, February 24, 2021 12:26 PM To: factory@lists.opensuse.org Subject: Re: Beware upgrading to tw 20210222 if on nvidia GPU
On Thursday 25 February 2021, Philip Raets wrote:
I had the same problem.
I rebooted to the previous kernel, reinstalled the nvidia-drivers (G04) with yast, ran mkinitrd, and rebooted.
Now it is working again.
Gr,
Philip
Similar experience here. I have a 1650 Super and use the proprietary drivers installed via the "easy" route. After 20210222, sddm failed to start. I logged into a console and used the cursors version of Yast2 to reinstall (forced "Update") any already installed packages from the nvidia repo, rebooted and was back in business. I didn't have to do anything after running yast2, I did not manually mkinitrd.
I poked around the logs a bit, but couldn't find any grumblings about modules, which I had seen under similar circumstances in the past (perhaps I was looking in the wrong places).
Michael
I don't know why it would work for some and not others. If "their scripted install" does not mean Yast, perhaps that's a factor.
Clearly the reinstall of the nvidia rpm's did the right thing, but it's weird the update did not, especially since the previous update including a kernel bump worked just fine. Maybe it had something to do with the state of my machine or combo of displays and cards.
I've look at the journalctl output for the boot that failed to start X11. Sddm did start, but did not identify any displays to add. Searching for nvidia failed to find any of normal kernel module load messages such as module license 'NVIDIA' taints kernel. The only nvidia related journal entries I could find was for audio/sound. For some reason the proprietary nvidia module wasn't included for boot - presumably it was missing from initrd.
Michael
Michael Hamilton wrote:
I don't know why it would work for some and not others. If "their scripted install" does not mean Yast, perhaps that's a factor.
AFAIK, the nvidia kmp package has a dependency on kernel-default-devel, and that one has a trigger script to (re)compile the module on install. This is what I see in my (zypper) log file: # 2021-02-24 14:04:46 kernel-default-devel-5.10.16-1.3.x86_64.rpm installed ok # Additional rpm output: .... and then follows the compile log I'm updating via 'zypper dup', not yast - maybe that's the difference for succeeds and fails?
On Friday 26 February 2021, Peter Suetterlin wrote:
Michael Hamilton wrote:
I don't know why it would work for some and not others. If "their scripted install" does not mean Yast, perhaps that's a factor.
AFAIK, the nvidia kmp package has a dependency on kernel-default-devel, and that one has a trigger script to (re)compile the module on install. This is what I see in my (zypper) log file:
# 2021-02-24 14:04:46 kernel-default-devel-5.10.16-1.3.x86_64.rpm installed ok # Additional rpm output: .... and then follows the compile log
I'm updating via 'zypper dup', not yast - maybe that's the difference for succeeds and fails?
I apologise, I should have said the original update was via zypper dup. From /var/log/zypp/history it does appear that the dup compiled the nvidia module for 5.10.16-1-default. Perhaps the module wasn't picked up for the initrd because no nvidia messages can be found in the journalctl output for the subsequent reboot into 5.10.16-1. There don't appear to be any relevant error message in any logs, even sddm didn't error, it just did not find any displays to manage. It was after this dup mystery that I used a yast to re-update the nvidia packages and that worked. I've not really had any unexpected issues with previous recent updates, it will be interesting to see what happens next time. For me, this is not really a big deal, I just wanted to confirm that Daniele's experience was not a lone occurrence. Michael
I don't want to open a new thread only to inform you that I've trapped in the same behaviour today. After a zypper dup system doesn't boot anymore, forced to choose kernel 5.11.2 and then reinstall nvidia blob via yast. Cheers -- Daniele
I also got put out of business on a couple of machines. Anxiously awaiting the correct nvidia driver for this kernel......... On Tue, Mar 16, 2021 at 4:20 AM Daniele Granata <denni.granata@gmail.com> wrote:
I don't want to open a new thread only to inform you that I've trapped in the same behaviour today. After a zypper dup system doesn't boot anymore, forced to choose kernel 5.11.2 and then reinstall nvidia blob via yast.
Cheers
-- Daniele
Is there a fairly easy or at least straight forward way to install older kernels with the current snapshot of Tumbleweed? I see newer options but not older options. Thanks! -- Nathan On Tuesday, 16 March 2021 12:10:08 EDT Chuck Davis wrote:
I also got put out of business on a couple of machines. Anxiously awaiting the correct nvidia driver for this kernel.........
On Tue, Mar 16, 2021 at 4:20 AM Daniele Granata <denni.granata@gmail.com> wrote:
I don't want to open a new thread only to inform you that I've trapped in the same behaviour today. After a zypper dup system doesn't boot anymore, forced to choose kernel 5.11.2 and then reinstall nvidia blob via yast.
Cheers
-- Daniele
participants (11)
-
Axel Braun -
Cameron Seader -
Chuck Davis -
Daniele Granata -
Michael Hamilton -
Michael Pujos -
Nathan Wolf -
Patrick Shanahan -
Peter Suetterlin -
Philip Raets -
Vinzenz Vietzke