got a laptop with an amd R5 gfx card (https://support.hp.com/emea_middle_east-en/document/c06041490) which is running leap 15.
it has a power draining issues though when shut down so for the bugzilla I wanted to install the latest kernel (tumbleweed) alongside leap 15 so I can test it with that.
So downloaded the tumbleweed installer and put it on the usb, it boots up, select installing in grub, the normal message scroll over the screen (you know found drives etc. etc) and then the screen turns black and that is it.
I tested this with the full install, the network install and the live cd and they all behave the same.
It all scroll by really fast but I think I see something like it starting the opensuse installer (or something along those lines) and then it goes black, it feels a lot like it wants to set a screen resolution or frequency which is not supported.
ctrl+alt F1 to F7 give no visible changes
Checked out the posts here like “Kernel 4.19.1 won’t boot (black screen)” which looked familiar and tried the idea’s posted there:
thank you for the answer, nomodeset got me into the ncurses installer with a message that the x-server could not be started.
installation is done but of course tumbleweed itself shows the same behavior, so it seems to be something with this kernel version 4.19.11 and the R5, will fiddle around a bit more
edit: see this in dmesg: [drm:amdgpu_init [amdgpu]] ERROR VGACON disables amdgpu kernel modesettings
1-Does the current kernel cmdline contain nomodeset, as was used to install? It’s only a crutch, a troubleshooting tool that allows a functional environment for performing repairs. It absolutely prevents use of competent X drivers. Specific cmdline parameters for amdgpu can’t do anything when nomodeset is blocking the X amdgpu driver.
2-Is xf86-video-amdgpu installed? It may be necessary.
3-Which R5 do you have? Output from ‘lspci -nnk | grep -A3 VGA’ would tell us, as would output from ‘inxi -Gxx’, and if you could get into X at all to run it in an Xterm it would report which X drivers are in use and available.
4-Have you tried disabling the GUI startup? Sometimes it causes black screens. Turn it off temporarily via the cmdline parameter plymouth.enable=0 appended to the linux line in the Grub menu. More permanently it can be done placing that parameter in /etc/default/grub and running grub-mkconfig or with yast2-bootloader. Uninstalling plymouth is another option, what I do always.
5-Is kernel-firmware installed? R5 needs it.
6-Note there are multiple layers of “driver”. First is kernel, built into it, but requiring kernel-firmware for full function. Next are the various potential X drivers, which include xf86-video-amdgpu, xf86-video-ati, and the modesetting driver integrated in the X server.
7-Having /var/log/Xorg.0.log to see will help us help you when you can get logged in. Easiest way is usually the susepaste cli command, which may or may not already be installed (inxi probably isn’t, but is easily installed once logged in: ‘zypper in inxi’).
just the laptop screen and no it did not help.
However this gave me an idea, so I hooked the laptop up to a monitor with an HDMI cable.
laptop screen stays black, but monitor showed a screen, the login prompt was on the laptop so did not see that, but after typing in password the KDE desktop showed up on the monitor, so when to KDE settings, screens and saw both the laptop and the monitor, the laptop screen was disabled, so enabled it and it worked just fine…
it wont survive a reboot but at least shows that the laptop screen is fine (as leap already showed)