[Bug 1190186] New: Cannot get to console with newer kernel and nvidia driver
http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 Bug ID: 1190186 Summary: Cannot get to console with newer kernel and nvidia driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: fred.blaise@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 852296 --> http://bugzilla.opensuse.org/attachment.cgi?id=852296&action=edit dmesg Hi, Since 5.13.12-2-default, my boot sequence does not get to console anymore (I start my i3 desktop with startx). Same now 5.13.13-1-default. Everything worked fine with what I think was 5.13.8, which of course got delete today when I did a zypper dup... need to find that puppy again. Somewhere after I type my home partition encryption password, the screen freezes and never gets to the prompt. I can however ssh to the box. Everything looks normal then. My home partition is mounted. Just my console display seems stuck. Attached my dmesg and a picture of my frozen console. Removing the nvidia driver - thus using nouveau - it works ok. Just lacking vulkan api and graph performance. I know the nvidiadriver is a never ending debate, but here it is anyways. Wondering what changed in between 5.13.8 and .13. Maybe the delta is small enough that it triggers something in someone's mind. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 http://bugzilla.opensuse.org/show_bug.cgi?id=1190186#c1 --- Comment #1 from Fred Blaise <fred.blaise@gmail.com> --- Created attachment 852297 --> http://bugzilla.opensuse.org/attachment.cgi?id=852297&action=edit picture of frozen boot sequence on console -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 http://bugzilla.opensuse.org/show_bug.cgi?id=1190186#c2 --- Comment #2 from Fred Blaise <fred.blaise@gmail.com> --- And maybe that's another thing and bug but zypp.conf has: multiversion.kernels = latest,latest-1,running nevertheless, my running kernel dissapeared with zypper dup. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 http://bugzilla.opensuse.org/show_bug.cgi?id=1190186#c3 --- Comment #3 from Fred Blaise <fred.blaise@gmail.com> --- Actually, 5.13.12-2 gets the system to boot even if it's stuck. Waiting long enough, I�end up at the "Give root password for maintenance". 5.13.13-1 is frozen, no ssh afterwards. -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1190186 http://bugzilla.opensuse.org/show_bug.cgi?id=1190186#c4 Fred Blaise <fred.blaise@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Fred Blaise <fred.blaise@gmail.com> --- Getting to emergency mode in fact because the console is not taking my input to unlock my encrypted home. Sorry for the many comments, getting afk then not, then... :-/ So the nvidia driver did not get modprobed. The latest nvidia driver is the repo is 470.63.01. I�downloaded and installed manually from nvidia directly 465.31. I�could successfully modprobe it and get to X under kernel 5.13.12 and 5.13.13. So I�am guessing a nvidia driver issue. Sorry for the noise. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com