http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c1 --- Comment #1 from Alexander van Kaam --- Created attachment 794229 --> http://bugzilla.suse.com/attachment.cgi?id=794229&action=edit TW xorgs (blackscreen) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #794230|text/x-log |text/plain mime type| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c3 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS --- Comment #3 from Stefan Dirsch ---

radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1

/* stoney */ {0x1002, 0x98E4, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_STONEY|AMD_IS_APU}, Stoney is neither a SI nor a SIK model, so there is no need to force the amdgpu driver and disable radeon one. amdgpu is the default. It's not supported by radeon driver. According to X logfile you also don't do this ... Anyway, looks like a regression, if things were still working with kernel of Leap 15. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c5 --- Comment #5 from Alexander van Kaam --- hi, modeset glamor = blackscreen modeset none = blackscreen amdgpu noe = blackscreen amdgpu glamor = blackscreen I don't pretend to understand how it all works, but I got a feeling it goes wrong before X starts ? with nomodeset plymouth at least is able to show something (the 3 green blocks) without nomodeset (so normal) even plymouth is not able to show anything at all, it goes to black straight away. the machine also has leap running (although not updated to the last lvl as I worry it might happen there to then) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c7 --- Comment #7 from Alexander van Kaam --- now sure how to switch to a Leap Kernel, sorry. I did play around with tumbleweed cli, sadly it only goes back to 20181119 kernel 4.19.2-1 which shows the exact same behavior. I booted the laptop with a TW live usb last year, but it was with 4.18.9 A post on the forum gave me an idea though: I hooked the laptop up to a monitor with an HDMI cable. Booted up, selected TW at Grub, saw a few while lines of bootup text and screen went black, but after a few seconds the monitor showed the green TW background (with the gears) The login prompt was on the laptop so did not see that, but after typing in the password the KDE desktop showed up on the monitor. Went to KDE settings, screens: both the laptop and the monitor where there, monitor was enabled and set as default, the laptop screen was disabled. Enabled the laptop screen and set it as default and it worked just fine.... It wont survive a reboot but at least shows that the laptop screen is fine (as leap already showed) no idea if that helps of anything :) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c9 --- Comment #9 from Alexander van Kaam --- found this https://bugzilla.kernel.org/show_bug.cgi?id=200695 and tried amdgpu.dc=0 all works as it should now -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(a.vankaam@chello. | |nl) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.kernel.org | |/show_bug.cgi?id=200695 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c12 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(a.vankaam@chello. | |nl) --- Comment #12 from Stefan Dirsch --- Stoney (2016) is a refresh of Carrizon (2015), so rather new. I suggest to test once more with current TW kernel (4.20) (with dc=1) and if this still does not work, please report it upstream. bugs.freedeskop.org -> New -> DRI --> DRM/AMDgpu and let us know the bug number you've created, so we are aware and can add us to Cc of this upstream bugreport. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c14 --- Comment #14 from Stefan Dirsch --- Sorry, I somewhat missed the upstream bugreport. There's no need to open another one for the same issue. Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1121632 http://bugzilla.suse.com/show_bug.cgi?id=1121632#c16 --- Comment #16 from Alexander van Kaam --- I saw the upstream reports to, so I did not really think it was fixed, bupt updated TW install and then switched over to KOTD first booted with BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc8-1.g4ddf057-default root=UUID=fce8b6dd-98d6-4b86-a5d9-2812f3c1e242 splash=silent resume=/dev/disk/by-uuid/c9f35ed5-bdbe-413a-801b-7df1c8a64145 quiet worked... then booted with BOOT_IMAGE=/boot/vmlinuz-5.0.0-rc8-1.g4ddf057-default root=UUID=fce8b6dd-98d6-4b86-a5d9-2812f3c1e242 splash=silent resume=/dev/disk/by-uuid/c9f35ed5-bdbe-413a-801b-7df1c8a64145 quiet amdgpu.dc=1 and worked too. there is a load of new ACPI errors comming over the screen, something about bit offset length and such, but they don't seem to be an issue. so amazingly it works in 5.0.0-rc8-1 if you want I can test TW install image once that is over to 5.0 ? will also update upstream -- You are receiving this mail because: You are on the CC list for the bug.