unable to boot with kernel 5.7

English Install/Boot/Login
21

delete this please

22

The hardware should work well with openSUSE. Problems could be caused by poor consistency in maintenance. To find out boot from a current live system on USB stick.

23

This is exactly as the message says - audio controller on your platform needs working graphic (Intel) driver which is disabled by “failsafe” menu item (which includes “nomodeset”).

24

OK thanks for your translation because I was unable to understand !!!
BTW I realised that I did’nt know what OpenSuse failsafe mode was: I expected the graphic interface to load, which of course it can’t do with no graphic driver.

25

I thought the same as you, because I had other issues, but actually they might not be the signs of a corrupted system. E.g. konqueror won’t open, but this issue is reported by other users and it seems that it is no longer maintained.

And moreover my checking of Tumbleweed Live DVD failed : it leaves me with a black screen, while Leap 15.1 Live DVD works fine. I dug the web to try and find out what the problem was, and I had a look to my dmesg too, where I found the following lines :

   59.624982] i915 0000:00:02.0: GPU HANG: ecode 7:1:85ddfffd, in X [1323]
   59.624984] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
   59.624984] Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/intel/issues/new.
   59.624985] Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
   59.624985] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
   59.624985] The GPU crash dump is required to analyze GPU hangs, so please always attach it.
   59.624986] GPU crash dump saved to /sys/class/drm/card0/error

So I did what I was told to, and filed a bug with my dmesg and the crash dump file mentioned ; it has been marked as a duplicate, the original one is [i915] GPU HANG: ecode 7:1:8edcfc79, in systemd-logind [411] (#2024) · Issues · drm / intel · GitLab .

I fetched from the web other informations about Linux kernel problems related to Intel integrated GPU driver i915 (see for example https://linuxreviews.org/Linux_Kernel_5.5_Will_Not_Fix_The_Frequent_Intel_GPU_Hangs_In_Recent_Kernels ). Those kernels probably worked fine on my machine however, so I assume it’s something slightly different now, but still related to i915.

Finally I plan to keep my current installation and go on with kernel 5.6 untill I get my new AMD graphic card ! :\

26

This is definitely a problem with i915. I had a similar issue some years ago: Konsole With "su -" Freezing The System - Applications - openSUSE Forums Fixed it with i915.enable_rc6=0. Problem was gone when switching to the newer kernel of Tumbleweed. Some reading: Intel graphics - ArchWiki

27

I updated to TW 20200701 and 5.7.5 on a Haswell that hadn’t been updated since mid-April. It boots entirely normally AFAICT.

28

I am not sure if I am experiencing the same problem or not but two of my Intel machines are experiencing problems. The machine that concerns me the most is the a Dell Inspiron 20 3048 with a 4th Gen Intel. SDDM blanks out and I cannot log in. I followed some of the instructions here without success:
https://wiki.archlinux.org/index.php/intel_graphics

In the dmesg, I am getting i915 GPU Hang messages

The computer boots, I just cannot get a successful graphics display. I did a fresh install of Tumbleweed with a new user account and still no success. I am not sure where to go from here.

As an aside, I have another 4th Gen Intel that is a laptop and it is not experiencing any issues.

Any help is greatly appreciated and anything I can do to help would also be fantastic

29

Maybe modesetting DDX would behave differently.

https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-graphics-driver-primer

30

I am not sure on the execution of that. Would that be something I put in the modprobe.d folder or as a kernel parameter? I am just not sure how to invoke modesetting DDX.

Thanks again!

31

Method 1: Eliminate the optionals:[ol][li]Uninstall xf86-video-nouveau[/li][li]reverse NVidia’s proprietary driver installation process according to whatever instructions were provided at its installation[/li][li]clear /etc/X11/ of optional files:[ul][]xorg.conf[/li][li]xorg.conf.d/[20-50]-.conf (roughly speaking, those containing nvidia, nouveau, device, monitor and/or screen in uncommented lines)[/ul][/ol][/li]Method 2 is more complicated:[ol]edit /etc/X11/xorg.con* to remove references to the optional drivers
[li]explictly specify modesetting via a “Driver” line in one of such files, e.g. /etc/X11/xorg.conf.d/50-device.conf[/ol][/li]Additionally using either method, nomodeset and nouveau.modeset=0 must be excluded from linux lines in Grub, and nouveau must not be blacklisted.

32

Thank you for the detailed reply.

My xorg.conf.d/ folder ONLY has 00-keyboard.conf in it. There are no other devices.

I went into the modprobe.d folder and added nvidia, nv and nouveau blacklisting

blacklist nvidia
blacklist nouveau
blacklist nv

But that didn’t work either.

33

keyword: N O T, if either modesetting DDX or nouveau DDX is desired

34

I only have Intel on this machine, no discrete graphics at all.

Here are the errors. I had to take pictures of the screen.

https://cubiclenate.files.wordpress.com/2020/07/img_20200718_115919394.jpg
https://cubiclenate.files.wordpress.com/2020/07/img_20200719_095011656.jpg
https://cubiclenate.files.wordpress.com/2020/07/img_20200719_095034810.jpg

Not sure how useful that is.

Thanks again!

35

Hi
Did you have a look at reporting as a bug as per the link?
I see there are a few in here: Issues · drm / intel · GitLab

36

Text is much more useful:

sudo dmesg | susepaste -n futureboy
susepaste -n futureboy /var/log/Xorg.0.log
inxi -Gxx | susepaste

Ignore any error messages. The uploads should be found on SUSE Paste . The last of the bunch will provide the Device ID of the IGP that identifies which 4th generation 8086: device you have.

37

I had very few time to spend on this issue lastly (and in fact, very few computer activity!) so I decided just to wait for the graphic card I had ordered to arrive (I am in Reunion Island and due mostly to covid crisis, many goods are out of stocks), in the hope it would solve the problem if it were really related to intel integrated graphics driver i915.

And it did. I installed it today, and I’m running the last #5.7 kernel without any problem (I tried sometimes to do it, with a constant failure, and could only run 5.6.4). I thought it would be worth to report, as a confirmation.

38

Many thanks for reporting. Feedback always helps motivating folks willing to help.