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.