http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c1 Felix Miata changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrmazda@earthlink.net --- Comment #1 from Felix Miata --- You may be able to workaround this by removing the unofficially deprecated xf86-video-intel driver. I have no such problem with modesetting on Kaby Lake: # inxi -bxx System: Host: gb250 Kernel: 4.19.7-1-default x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: IceWM 1.4.2 dm: XDM Distro: openSUSE Tumbleweed 20181213 Machine: Type: Desktop System: Gigabyte product: B250M-D3H v: N/A serial: N/A Mobo: Gigabyte model: B250M-D3H-CF v: x.x serial: N/A UEFI: American Megatrends v: F9 date: 04/10/2018 CPU: Dual Core: Intel Core i3-7100T type: MT MCP arch: Kaby Lake speed: 800 MHz min/max: 800/3400 MHz Graphics: Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: 1920x1200~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.1.7 compat-v: 3.0 direct render: Yes Info: Processes: 173 Uptime: N/A Memory: 15.55 GiB used: 212.6 MiB (1.3%) Init: systemd v: 239 runlevel: 5 target: multi-user.target Compilers: gcc: 8.2.1 alt: 8 Shell: bash v: 4.4.23 running in: xterm inxi: 3.0.28 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c4 Tejas Guruswamy changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(masterpatricko@gm | |ail.com) | --- Comment #4 from Tejas Guruswamy --- Yep, issue still exists with kernel-default-4.20.rc7-1.1.g4731528.x86_64 from Kernel:HEAD . The ratio of screen on to off time seems to vary boot-to-boot, but the repeatable indicator of this issue is that I see the UEFI image again after GRUB instead of the usual splash screen. (Some sort of gfx memory issue? I have no idea). This never happens under kernel 4.18 and always happens for >= 4.19 in my testing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c6 David Rosky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dave.rosky@gmail.com --- Comment #6 from David Rosky --- I've been debating whether to file a new bug report, but the issue I'm having is similar enough to this, that it could be a manifestation of the same problem, so I'll post some info here for now. Symptoms: 1. Tumbleweed install can't bring up graphical installer on a new machine with a z390 chipset and i9-9900k and Intel graphics. It falls back to text install, so I do a text install. 2. After text install, X won't start (I installed with default runlevel for console and then use "startx"). 3. The quick summary: The installer doesn't even install xf86-video-intel, so Xorg generates a "module not found" error, then falls back to Vesa, which hangs and fails. I'm not sure why Vesa fails, but maybe it doesn't support the 4k mode or something. I deleted the vesa driver, then X falls back to framebuffer, and X finally runs in the framebuffer, but horribly slow, far slower than either Ubuntu or Arch with framebuffer. 4. If I force install xf86-video-intel, the module is found, but it can't find a display: i915 seems to be having trouble connecting to the hardware. 5. Ubuntu 18.10 liveCD: same problem - falls back to framebuffer, but Ubuntu's framebuffer is significantly faster than Tumbleweed's. Arch: Same problem - X won't start, removing xf86-video-intel causes fallback to vesa, which fails. Removing vesa causes fallback to framebuffer, which works, at about the same speed as the Ubuntu framebuffer. Some additional info: This seems to be a known problem with an upstream fix in a weird place. Check out this Arch bug report: https://bbs.archlinux.org/viewtopic.php?id=242465 Someone referred the OP to a "drm-tip" kernel, which worked for the OP. In Arch, there is a AUR packagebuild for this, and I tried it, and it worked on my system as well. Here is the drm-tip project referred to in the thread: https://github.com/freedesktop/drm-tip This drm-tip kernel is based on 4.20-rc6, BUT, the 4.20-rc6 kernel in the OpenSuSE kernel:HEAD repository does not work for me. The drm-tip kernel must have additional, bleeding-edge drm development code that works properly on newer processors and chipsets. My suggestion is that if it is desired that Tumbleweed work on the newest hardware, the OpenSuSE kernel developers may want to look at the drm-tip kernel and backport whatever changes are necessary. One more additional piece of info: While the Ubuntu 18.10 liveCD does not work (it works, but falls back to framebuffer), the Ubuntu 19.04 BETA liveCD *does* work. So far, that's been the only out-of-the-box version of either Ubuntu, OpenSuse, or Arch that has worked. It seems the Ubuntu devs have possibly backported the necessary changes for a functional Intel graphics system. NOTE: If this is determined to be a different issue, I would be happy to post this information into a new bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c8 --- Comment #8 from David Rosky --- Tejas, thanks for the comment. The older, 4.18 kernel did not improve things. Also, the installer did not install xv86-video-intel, so it is apparently doing the right thing by not installing it. The modesetting driver does get loaded, but X still cannot connect to the card. It is starting to sound like this is a different issue, so I'll start a new bug. Thanks.. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c10 --- Comment #10 from Tejas Guruswamy --- (In reply to Takashi Iwai from comment #9)

Can anyone try to open a bug report on the upstream bugzilla.freedesktop.org? Feel free to put me (tiwai@suse.de) to Cc, so that I can follow / help. Thanks.

Reported as https://bugs.freedesktop.org/show_bug.cgi?id=109215 and added you as cc, thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c13 sep hoogzaad changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seppe.hoogzaad@gmail.com --- Comment #13 from sep hoogzaad --- I have (had) the same problem. Kernel 4.19 did boot, but no screen, just some flashes. No text or graphic screen. I did see the tumbleweed logo, but that was it. Also noting strange in the log files. I just had a new computer. Installing tumbleweed did not work because the kernel of the installer image did not boot properly. I therefore installed openSUSE Leap 15.0 first, then upgraded to tumbleweed. Then i got in the same problem like described here. I previous got the live tumbleweed image (version 20181224) working by setting the kernel option "xvideo=1920x180". This also resulted in flickering screens, but that was related to wayland, recording to the journal. So choosing Xorg would keep me out op those problems. I therefore was not expecting problems when upgrading to tumbleweed. I had the 4.12 kernel from Leap 15.0, which worked, so i have kept this to boot the system, which worked. I also booted the 4.19 kernel and uses ssh to log in remotely. This to find a difference in the log, but the only difference between a working kernel and 4.19 i found is below. Kernel 4.12: [ 3.626842] [drm] Initialized i915 1.6.0 20171222 for 0000:00:02.0 on minor 0 [ 4.426469] [drm:intel_dp_start_link_train [i915]] *ERROR* [CONNECTOR:58:eDP-1] Link Training failed at link rate = 270000, lane count = 2 Kernel 4.19: [ 3.393198] [drm] Initialized i915 1.6.0 20180719 for 0000:00:02.0 on minor 0 (note the different date on the i915) Using the "xvideo=1920x180" kernel parameter was not recommended, so i did not tried this. I looked at this bug, since it described my problem. I just found that (for me) the option "i915.fastboot=1" solved my problem with the 4.19 kernel. It now boots properly, suspend works. May be this can help some others. Information about my machine, running the 4.19.11-1 kernel:

inxi -bxx System: Host: linux-6axq Kernel: 4.19.11-1-default x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: Xfce 4.12.4 tk: Gtk 2.24.32 wm: xfwm4 dm: LightDM Distro: openSUSE Tumbleweed 20181224 Machine: Type: Desktop System: GOOGLE product: Lulu v: Pilot serial: <root required> Chassis: type: 3 serial: <root required> Mobo: N/A model: N/A serial: N/A BIOS: coreboot v: N/A date: 03/28/2016 Battery: ID-1: BAT0 charge: 49.2 Wh condition: 70.0/67.0 Wh (104%) volts: 11.8/11.4 model: SMP-LIS DELL MJ serial: 0340 status: Discharging CPU: Dual Core: Intel Core i3-5005U type: MT MCP arch: Broadwell speed: 798 MHz min/max: 500/2000 MHz Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1616 Display: x11 server: X.Org 1.20.3 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2) v: 4.5 Mesa 18.3.1 compat-v: 3.0 direct render: Yes Network: Device-1: Intel Wireless 7260 driver: iwlwifi v: kernel port: 1840 bus ID: 01:00.0 chip ID: 8086:08b1 Drives: Local Storage: total: 111.79 GiB used: 9.58 GiB (8.6%) Info: Processes: 254 Uptime: 5h 33m Memory: 3.79 GiB used: 944.8 MiB (24.4%) Init: systemd v: 239 runlevel: 5 target: graphical.target Compilers: gcc: N/A Shell: bash v: 4.4.23 running in: xfce4-terminal inxi: 3.0.29

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c17 --- Comment #17 from Tejas Guruswamy --- (In reply to Takashi Iwai from comment #14)

The boot logo carried from EFI is the intentional behavior, BTW. This is a new feature for "flicker-less" boot on the recent kernel, enabled via CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER option.

Ugh, mine is ugly! But ok, thanks, I guess that is a red herring then. (based on this hint I found "fbcon=nodefer" restores the old behaviour) (In reply to sep hoogzaad from comment #15)

This is with kernel version 5.0.0, r2. The problem was the same, like in the 4.20.3 kernel. With "i915.fastboot=1" booting correct. Without this kernel parameter: no screen, just some flickering.

"i915.fastboot=1" indeed fixes the black screen/flickering problem on 4.20 and 5.0rc, thank you for the suggestion. I will pass this info on to my upstream bug (https://bugs.freedesktop.org/show_bug.cgi?id=109215). Any advice on providing more useful logs would be appreciated. Still don't see any errors in the expected places. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c25 --- Comment #25 from Takashi Iwai --- (In reply to Tejas Guruswamy from comment #24)

I finally had a chance to test again. Summary is unfortunately kernel-default-4.20.5-1.1.ge544b4e.x86_64 from home:tiwai did not fix my problem. i915.fastboot=1 still works though.

Thanks for testing. That's what I was afraid of :-< So apparently we're looking at multiple issues.

Note that fastboot=Y appears to be the default in 4.20.6 and drm-tip.

Really? I couldn't find anything that changed the default in the kernel source. In theory we can flip fastboot=y as default. It's been disabled due to the regression seen on a Chromebook with some funky firmware. But it's no right "fix", and the option can be given easily via boot option, let's try to track the right cause for now. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1119621 http://bugzilla.opensuse.org/show_bug.cgi?id=1119621#c29 Tejas Guruswamy changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #29 from Tejas Guruswamy --- (In reply to Jiri Slaby from comment #28)

So the issue is fixed by this commit: commit 21635d7311734d2d1b177f8a95e2f9386174b76d Author: Jani Nikula Date: Fri Apr 5 10:52:20 2019 +0300

drm/i915/dp: revert back to max link rate and lane count on eDP

I assume?

If not, please reopen.

No, unfortunately this is a different bug. It started in 4.19 most likely because of a99790bf5c7f3d68d8b01e015d3212a98ee7bd57 : r8169: Reinstate ASPM Support and I can still reproduce on 5.1-rc5 with fastboot=0 and max_cstate=9. -- You are receiving this mail because: You are on the CC list for the bug.