Boot to black screen

New install. Half of the times Leap boot to a black screen and I need to do a restart

  1. power on
  2. grub menu shows up
  3. I leave as it is
  4. screen goes black and that’s it

sudo journalctl -p 3 --since=today

-- Logs begin at Mon 2019-10-28 07:20:03 PDT, end at Mon 2019-10-28 07:28:19 PDT. --
Oct 28 07:20:04 linux-wy8o kernel: amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Oct 28 07:20:11 ethelbert kernel: sp5100_tco: I/O address 0x0cd6 already in use
Oct 28 07:20:18 ethelbert chronyd[1151]: Could not open IPv6 command socket : Address family not supported by protocol
Oct 28 07:20:24 ethelbert NetworkManager[1110]: <error> [1572272424.7807] device (eth0): addrconf6: failed to start neighbor discovery: failure creating libndp socket: Address family not supported by protocol (97)
Oct 28 07:21:16 ethelbert pulseaudio[2575]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

inxi -FxxxZ

System:    Host: ethelbert Kernel: 4.12.14-lp151.28.20-default x86_64 bits: 64 gcc: 7.4.1
           Desktop: KDE Plasma 5.12.8 (Qt 5.9.7) dm: sddm,sddm Distro: openSUSE Leap 15.1
Machine:   Device: desktop Mobo: MSI model: 970A-G46 (MS-7693) v: 2.0 serial: N/A
           BIOS: American Megatrends v: V2.8 date: 01/08/2016
CPU:       Octa core AMD FX-8350 Eight-Core (-MCP-) arch: Bulldozer rev.0 cache: 16384 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 64002
           clock speeds: min/max: 1400/4000 MHz 1: 4000 MHz 2: 4000 MHz 3: 4000 MHz 4: 4000 MHz 5: 4000 MHz
           6: 4000 MHz 7: 4000 MHz 8: 4000 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
           bus-ID: 01:00.0 chip-ID: 1002:67df
           Display Server: x11 (X.Org 1.20.3 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa,radeon)
           Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
           OpenGL: renderer: Radeon RX 570 Series (POLARIS10, DRM 3.27.0, 4.12.14-lp151.28.20-default, LLVM 7.0.1)
           version: 4.5 Mesa 18.3.2 Direct Render: Yes
Audio:     Card-1 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
           driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1002:4383
           Card-2 Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
           driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aaf0
           Sound: Advanced Linux Sound Architecture v: k4.12.14-lp151.28.20-default
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 04:00.0 chip-ID: 10ec:8168
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: d4:3d:7e:29:97:4e
Drives:    HDD Total Size: 6001.2GB (37.0% used)
           ID-1: /dev/sda model: WDC_WD30EFRX size: 3000.6GB serial: WD-WCC4N3TA43RK
           ID-2: /dev/sdb model: WDC_WD30EFRX size: 3000.6GB serial: WD-WCC4N1EFVRS2
Partition: ID-1: / size: 755G used: 5.5G (1%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 2.0T used: 513G (28%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 20.91GB used: 0.00GB (0%) fs: swap dev: /dev/sda4
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 215 Uptime: 0:10 Memory: 984.8/11887.0MB
           Init: systemd v: 234 runlevel: 5 default: Gcc sys: N/A
           Client: Shell (bash 4.4.231 running in konsole) inxi: 2.3.40 

sudo lspci | grep -i vga

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)

What can I do?


Strike the E key when the Grub menu appears, move to the end of the wrapped line that began with linu, and append a space and plymouth.enable=0 before proceeding with boot. Does it help?

I will try that tonight and will report tomorrow


No, that didn’t work this morning.

What I noticed is that:

  • The black screen after the grub menu happens more often in a cold boot, the computer being turned off for a while. I would say around 1/2 of the time.
  • The black screen after the grub menu happens a lot less often in a warm boot, the computer being turned off for a short time. I would say around 1/4 of the time.

Anything else I should try?


Update Mesa 3D with a Full repository Vendor change.
Or install AMD drivers.

As anyone should be able to infer reading all the way through that thread, that’s not an option in any recent release of any distro. AMD stopped releasing its proprietary drivers quite some time back, instead investing its effort making the FOSS amdgpu drivers that ship with openSUSE work.

What should work purely for troubleshooting purposes and allowing access to YaST and zypper instead of getting black screened is to boot with nomodeset, to ensure needed packages are installed. The amdgpu drivers depend on modesetting to work, so nomodeset cannot be depended upon. At the basic level you should have xf86-video-ati not installed, and should have xf86-video-amdgpu installed.

Which mesa packages are or cmdline options that might be required with Polaris GPUs I don’t know.

Does the same problem occur if you use a different video cable of same type or different type, or connect the PC to some other display?

For trouble shooting purposes, on your first boot using nomodeset on cmdline, please upload /var/log/Xorg.0.log.old to or or equivalent for our examination. There should be clues in that file as to what is going wrong, lines containing (EE).

I replied earlier this morning, but I don’t see my reply. I’m sure I clicked on submit reply but the peanut must be becoming mush…

I have removed them all except for the xf86-video-amdgpu

Yes, I took my computer to a neighbour and it also hanged. The screen was an old 19" boob-tube.

I have found what the problem is, but I don’t know how to fix it. It’s not xorg. It dies long before that.

    2.843560] fb: switching to amdgpudrmfb from VESA VGA            <<<<<<<<<<<<<<<<<<<<<<
    2.865051] ehci-pci 0000:00:13.2: irq 17, io mem 0xfeb07000
    2.868806] Console: switching to colour dummy device 80x25
    2.869138] [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1462:0x341B 0xEF).
    2.869149] [drm] register mmio base: 0xFEA00000
    2.869153] [drm] register mmio size: 262144
    2.869164] [drm] add ip block number 0 <vi_common>
    2.869168] [drm] add ip block number 1 <gmc_v8_0>
    2.869171] [drm] add ip block number 2 <tonga_ih>
    2.869174] [drm] add ip block number 3 <powerplay>
    2.869178] [drm] add ip block number 4 <dm>
    2.869181] [drm] add ip block number 5 <gfx_v8_0>
    2.869184] [drm] add ip block number 6 <sdma_v3_0>
    2.869188] [drm] add ip block number 7 <uvd_v6_0>
    2.869191] [drm] add ip block number 8 <vce_v3_0>

It dies at switching the frame buffer. What I’m showing is dmesg from a successful start. When the start fails, it dies at the switching to amdgpudrmfb.

Is there a way of stopping that or disabling it?


Is libdrm_amdgpu1 installed?

Other cmdline parameters to try instead of nomodeset:


I don’t know much about troubleshooting recent AMD GPUs. My newest AMD GPU is nearly a decade old. If these don’t help you really need one of our AMD experts to weigh in here.

I’m running Tumbleweed as it did work better with the my Volcanic Island card(s) which is the same generation as the OP…

pinxi -Gxx
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard driver: amdgpu 
           v: kernel bus ID: 00:01.0 chip ID: 1002:9874 
           Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] vendor: Hewlett-Packard driver: amdgpu 
           v: kernel bus ID: 04:00.0 chip ID: 1002:6900

I’m not sure if the iommu options will help, but worth a try, the other one to try as a boot option is amdgpu.dc=0

Else perhaps try the latest stable kernel (and firmware etc) from kernel:stable repository.

It was more complicated than that, like I said the problem was the switching to the frame buffer, by disabling it, so far it’s working. Here are my boot parameters

> cat /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-4.12.14-lp151.28.20-default root=UUID=4a4ea269-bb7b-4c98-9ef1-042cdbe43847 resume=/dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3TA43RK-part4 ipv6.disable=1 sysrq_always_enabled=1 plymouth.enable=0 fbcon=map:1

fbcon=map:1 makes the frame buffer to be “nowhere”, therefore it doesn’t stay there (the black screen)


  • I don’t want to use ipv6
  • I want to be able to do a alt-sysrd if I need

Thank you for the help, it’s very appreciated.