Bug 1180609 - i915: No picture in Gnome/Wayland after booting to kernel v5.10.4
Summary: i915: No picture in Gnome/Wayland after booting to kernel v5.10.4
Status: RESOLVED DUPLICATE of bug 1180543
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-06 09:57 UTC by Libor Pechacek
Modified: 2021-01-06 13:12 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Boot log from v5.10.4 (no picture) (200.15 KB, text/x-log)
2021-01-06 09:57 UTC, Libor Pechacek 		Details
Boot log from v5.10.3 (works fine) (217.72 KB, text/x-log)
2021-01-06 09:58 UTC, Libor Pechacek 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Libor Pechacek 2021-01-06 09:57:46 UTC 
Created attachment 844879 [details]
Boot log from v5.10.4 (no picture)

After kernel upgrade to v5.10.4 there is no picture in my graphical desktop (Gnome+Wayland). Screen backlight is lit but there is no picture on neither the laptop display nor the HDMI attached external display. Booting back to v5.10.3 fixes the issue.

Hardware: Dell Inspiron 7373
Comment 1 Libor Pechacek 2021-01-06 09:58:29 UTC 
Created attachment 844880 [details]
Boot log from v5.10.3 (works fine)
Comment 2 Frank Krüger 2021-01-06 10:10:28 UTC 
Cf. https://bugzilla.suse.com/show_bug.cgi?id=1180543#c3
Comment 3 Michael Hirmke 2021-01-06 10:51:43 UTC 
Kernel parameter snd_hda_codec_hdmi.enable_silent_stream=0 helped her for my DLE XPS.
Comment 4 Libor Pechacek 2021-01-06 13:12:44 UTC 
Thanks, gentlemen! The kernel command line option indeed helped and the current Kernel:stable has the fix. I'm marking this bug report as a duplicate.

*** This bug has been marked as a duplicate of bug 1180543 ***