[Bug 1186648] New: Intel GPU UHD 630 - no install possible
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 Bug ID: 1186648 Summary: Intel GPU UHD 630 - no install possible Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: n.moendjen@vodafone.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 849811 --> http://bugzilla.opensuse.org/attachment.cgi?id=849811&action=edit Machine information Install Media from Leap 15.2 up to actual tumbleweed just blank out after grub. you can make the install media work with the kernel parameter nomodeset. Than they install just fine in grubs resolution. After install you must keep the nomodeset setting. If not the screen blanks out again at start. With nomodeset, no resolution change is possible and on Leap i915 is not loading, on tumbleweed i915 is loaded by X but without audio support and also no resolution change possible. As info: The newer *buntus are installing and running just fine on it. The picture shows the machine. It is taken on kubuntu. I think some kernel patches are missing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 Norbert M�ndjen <n.moendjen@vodafone.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |n.moendjen@vodafone.de Hardware|Other |x86-64 Severity|Normal |Critical -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None CC| |tiwai@suse.com Flags| |needinfo?(n.moendjen@vodafo | |ne.de) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Please don't touch the priority field on Bugzilla. It's changed only by devs side. It's possible that Leap 15.2 kernel doesn't support your chip. Please retest rather with Leap 15.3 instead. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c2 --- Comment #2 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Takashi Iwai from comment #1)
Please don't touch the priority field on Bugzilla. It's changed only by devs side.
It's possible that Leap 15.2 kernel doesn't support your chip. Please retest rather with Leap 15.3 instead.
As I write not even tumbleweed is working. And 15.3 neither. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c3 --- Comment #3 from Takashi Iwai <tiwai@suse.com> --- (In reply to Norbert M�ndjen from comment #2)
(In reply to Takashi Iwai from comment #1)
Please don't touch the priority field on Bugzilla. It's changed only by devs side.
It's possible that Leap 15.2 kernel doesn't support your chip. Please retest rather with Leap 15.3 instead.
As I write not even tumbleweed is working. And 15.3 neither.
TW and Leap 15.3 are completely different. TW is based on currently 5.12 kernel, and the early 5.12 kernel had some serious issues in i915 driver, and it's possible that some regression appears on TW while Leap 15.3 might work (that is based on 5.9+ based DRM code). So you tested 15.3 installation image, and it didn't work, failed in the same way (i915 driver wasn't loaded)? Please elaborate what you've tested. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c4 --- Comment #4 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Takashi Iwai from comment #3)
(In reply to Norbert M�ndjen from comment #2)
(In reply to Takashi Iwai from comment #1)
Please don't touch the priority field on Bugzilla. It's changed only by devs side.
It's possible that Leap 15.2 kernel doesn't support your chip. Please retest rather with Leap 15.3 instead.
As I write not even tumbleweed is working. And 15.3 neither.
TW and Leap 15.3 are completely different.
TW is based on currently 5.12 kernel, and the early 5.12 kernel had some serious issues in i915 driver, and it's possible that some regression appears on TW while Leap 15.3 might work (that is based on 5.9+ based DRM code).
So you tested 15.3 installation image, and it didn't work, failed in the same way (i915 driver wasn't loaded)? Please elaborate what you've tested.
I want to try it with a fresh image from https://get.opensuse.org/testing/#download But the server tells me that there is nothing to download. Not the net install and also not the full iso. Can you give me a link to the net install? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- http://download.opensuse.org/distribution/leap/15.3/iso/ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c6 --- Comment #6 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Takashi Iwai from comment #5)
Exactly the same result. Directly after some inits it blanks out. See the video: https://photos.app.goo.gl/wjr5vB7pKYkX3YYP9 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c7 --- Comment #7 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Norbert M�ndjen from comment #6)
(In reply to Takashi Iwai from comment #5)
Exactly the same result. Directly after some inits it blanks out. See the video: https://photos.app.goo.gl/wjr5vB7pKYkX3YYP9
If you need some information which I can extract from the running kubuntu than let me know it. I have finished the preparations and must sent it out tomorrow to my colleague. He needs it for work. So than it is gone. Sorry for that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c8 --- Comment #8 from Takashi Iwai <tiwai@suse.com> --- OK thanks. Then my wild guess is that it's a problem in the upstream driver, and Ubuntu might have some downstream workaround or such. Could you try to boot with video=1024x768 option or such to enforce the resolution? The blank screen could be no hang but just the invalid mode set. Also, if you've already installed TW or Leap 15.3 with nomodeset option (i.e. having a running system), could you try to reboot without nomodeset boot option but with drm.debug=0x1e option, and get the kernel boot log? Reboot again with nomodeset and get the previous kernel log, and upload to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c9 --- Comment #9 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Takashi Iwai from comment #8)
OK thanks. Then my wild guess is that it's a problem in the upstream driver, and Ubuntu might have some downstream workaround or such.
Could you try to boot with video=1024x768 option or such to enforce the resolution? The blank screen could be no hang but just the invalid mode set.
Also, if you've already installed TW or Leap 15.3 with nomodeset option (i.e. having a running system), could you try to reboot without nomodeset boot option but with drm.debug=0x1e option, and get the kernel boot log? Reboot again with nomodeset and get the previous kernel log, and upload to Bugzilla.
Sorry that is not anymore possible. The system is now completely configured for my colleague. With all bells and whistles. So no chance for any installation tests anymore. I just don't have the time anymore to do it a second time. But I read something that the patches from Ubuntu have their root in the arch environment. Maybe you find something there. It has something to do with the modeset driver and some pins or ports which gotten different positions or numbers. But my knowledge is not going so far. I just read all of that as I was trying to make it work with Opensuse. We bought this small pc or nuc (small not cheap) from Tuxedo and even they warned us that Opensuse will not work. Tuxedo is specialized in Linux compatible computers. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c10 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX Flags|needinfo?(n.moendjen@vodafo | |ne.de) | --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- Hrm, it's a pity that we have too short time for debugging. Unless we get a test hardware, it's impossible to debug and fix it. Hopefully it'll get fixed in the upstream, then TW will work out of the box. Closed as WONTFIX for now. Feel free to reopen if you have a chance to test/debug again. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c11 --- Comment #11 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Takashi Iwai from comment #10)
Hrm, it's a pity that we have too short time for debugging.
Unless we get a test hardware, it's impossible to debug and fix it. Hopefully it'll get fixed in the upstream, then TW will work out of the box.
Closed as WONTFIX for now. Feel free to reopen if you have a chance to test/debug again. Thanks.
Maybe you could just check the patches which is ubuntu putting on the original kernel or xorg tree? Sorry that I could not help you more. But this one is for business I can't hold it back. Except I want my boss to rip my head off. :-) And keep it im mind, this platform is new. So maybe more reports may be coming in. Wish you a nice day Greetings -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c12 --- Comment #12 from Norbert M�ndjen <n.moendjen@vodafone.de> --- (In reply to Takashi Iwai from comment #10)
Hrm, it's a pity that we have too short time for debugging.
Unless we get a test hardware, it's impossible to debug and fix it. Hopefully it'll get fixed in the upstream, then TW will work out of the box.
Closed as WONTFIX for now. Feel free to reopen if you have a chance to test/debug again. Thanks.
Please inform the maintainers of 15.4 and TW. So they know about it. For 15.3 it is maybe to late. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186648 http://bugzilla.opensuse.org/show_bug.cgi?id=1186648#c13 --- Comment #13 from Takashi Iwai <tiwai@suse.com> --- Well, as long as it's an upstream problem, the bug should be reported to the upstream bug tracker, gitlab.freedesktop.org Issues. Then it'll cover all distros in future. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com