Freeze after update to Snapshot 20181112 / Radeon Vega and amdgpu on Athlon 200GE

loewe19 · November 14, 2018, 11:59pm

Hi, I recently updated to the latest snapshot with Kernel 4.19 as mentioned above- unfortunately the system is now unbootable and stucks on start - No Graphics output at all.

While updating, I noticed some messages concerning the amdgpu driver firmware for Radeon Vega Graphics - I have an AMD Athlon 200GE with built in Radeon Vega GPU on a B350 Chipset.

My Guess there is an issue with this driver (?)

The Snapshot before with Kernel 4.18 runs perfectly .

Any help or suggestions will be appreciated.

Kind Regards, Thomas

knurpht · November 15, 2018, 12:46am

Wait for the new amdgpu packages to be rebuilt

loewe19 · November 15, 2018, 1:28am

Hi Knurpht,

thanks very much for Your superfast reply, this helps a lot

Looking forward to the new kernel with new amdgpu driver.

Kind regards, Thomas

MirceaKitsune · November 15, 2018, 1:28am

I’m getting this too: Kernel 4.19.1 freezes on a black screen when booting with the amdgpu driver, however it does manage to boot with the radeon driver. My card is a GCN 2.0, my mother’s computer has a GCN 1.0: Mine has this issue whereas her does not, thus I think this has to do with a bug in the GCN 2.0 architecture. I’ll follow the advice above and wait a bit longer since 4.19.2 is on its way also… if that doesn’t fix it either there is a bigger problem.

loewe19 · November 15, 2018, 1:48am

Glad to hear I am not the only one, thanks !

Nevertheless - as a long term user I will stick to opensuse or tumbleweed. In my opinion the BEST Distros on Earth

malcolmlewis · November 15, 2018, 1:59am

Hi
GCN 2.0 (Mullins R3) and 3.0 (Dual GPU’s Carrizo/R7) all working fine here on Xorg and Wayland with the GNOME DE…

Do you get to the login screen, tried iceWM? Running Wayland or Xorg? Else pop out to a VT (ctrl+alt+F1) if your running Xorg and login as your user and check the ~/.local/share/xorg/Xorg.0.log

MirceaKitsune · November 15, 2018, 2:29am

Off-topic but glad someone else agrees: openSUSE is the best OS for me, especially Tumbleweed which makes it so convenient to stay up to date

In my case at least, no: I get to a black screen from which I’m unable to either use a different runlevel or do anything other than a hard restart. https://bugzilla.opensuse.org/show_bug.cgi?id=1116106

It might not be GCN 2.0 or all cards with that architecture in that case. Some cards are definitely affected however.

malcolmlewis · November 15, 2018, 2:45am

Hi
Do you have previous boot logs?


journalctl --list-boots

Else look at setting to boot to multi-user mode, boot from the old kernel;


systemctl set-default multi-user.target

Then reboot into the new kernel.

loewe19 · November 15, 2018, 7:14pm

malcolmlewis:

Hi
Do you have previous boot logs?
journalctl --list-boots
Else look at setting to boot to multi-user mode, boot from the old kernel;
systemctl set-default multi-user.target
Then reboot into the new kernel.

Hi malcolmlewis, thank you very much for your reply.
I only found one boot log from today. I am now booting the previous tumbleweed Installation from my Grub boot menu.
BUT i have found the zypper.log. Maybe someone can do some further investigation.

Here’s a snippet of my zypper.log from yesterday, after i did a

zypper dup --no allow vendor change:

2018-11-14 22:29:09 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.19.1-1-default 4.19.1-1-default
2018-11-14 22:29:10 <1> linux-rz0a(2962) ] RpmPostTransCollector.cc(executeScripts):128 dracut: dracut module ‘lvm’ will not be installed, because command ‘lvm’ could not be found!
2018-11-14 22:29:10 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: dracut module ‘lvm’ will not be installed, because command ‘lvm’ could not be found!
2018-11-14 22:29:11 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: bash ***
2018-11-14 22:29:11 <1> linux-rz0a(2962) ] RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: systemd ***
2018-11-14 22:29:11 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: warpclock ***
2018-11-14 22:29:11 <1> linux-rz0a(2962 RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: systemd-initrd ***
2018-11-14 22:29:11 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: i18n ***
2018-11-14 22:29:11 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Could not find FONT_MAP none!
2018-11-14 22:29:11 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: drm ***
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_gpu_info.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_asd.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_sos.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_asd.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_sos.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_rlc.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_mec2.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_mec.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_me.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_pfp.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_ce.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_rlc.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_mec2.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_mec.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_me.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_pfp.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_ce.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_sdma1.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_sdma.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_sdma1.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_sdma.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_uvd.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_uvd.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_vce.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_vce.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega20_smc.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Possible missing firmware “amdgpu/vega12_smc.bin” for kernel module “amdgpu.ko”
2018-11-14 22:29:12 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: plymouth ***
2018-11-14 22:29:13 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: btrfs ***
2018-11-14 22:29:13 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: kernel-modules ***
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: resume ***
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: rootfs-block ***
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: suse-xfs ***
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: terminfo ***
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: *** Including module: udev-rules ***
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Skipping udev rule: 40-redhat.rules
2018-11-14 22:29:20 <1> linux-rz0a(2962) RpmPostTransCollector.cc(executeScripts):128 dracut: Skipping udev rule: 50-firmware.rules

malcolmlewis · November 15, 2018, 8:45pm

loewe19:

Hi malcolmlewis, thank you very much for your reply.
I only found one boot log from today. I am now booting the previous tumbleweed Installation from my Grub boot menu.
BUT i have found the zypper.log. Maybe someone can do some further investigation.

Here’s a snippet of my zypper.log from yesterday, after i did a
zypper dup --no allow vendor change:

Hi
So what is the exact model card you have?


/sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"

The kernel-firmware package is installed?

loewe19 · November 15, 2018, 10:16pm

Hi, kernel-firmware package 20181001-1.1 is installed. GPU is a AMD Athlon 200GE Dual Core.
I bought this CPU about one month ago because of its energy efficiency. Mainboard is Asus Prime B350 Plus

Here’s the output:

/sbin/lspci -nnk | egrep -A3 “VGA|Display|3D”
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb)
Subsystem: ASUSTeK Computer Inc. Device [1043:876b]
Kernel driver in use: amdgpu
Kernel modules: amdgpu

Thanks a lot for your support !

malcolmlewis · November 15, 2018, 10:37pm

Hi
OK, so it’s a Raven, so the kernel-firmware has this and your card is picking the right driver…

So you get to grub and soon after booting, just a black screen, no cursor visible? If after you boot and press the esc key, do you get output? When the screen does go blank, if you press ctrl+alt+F1 do you get to a VT?

If you edit the grub boot option for the 4.19.1 kernel, on the line that has quiet on it, can you add


plymouth.enable=0

See how that goes.

loewe19 · November 15, 2018, 11:21pm

malcolmlewis:

Hi
OK, so it’s a Raven, so the kernel-firmware has this and your card is picking the right driver…

So you get to grub and soon after booting, just a black screen, no cursor visible? If after you boot and press the esc key, do you get output? When the screen does go blank, if you press ctrl+alt+F1 do you get to a VT?

If you edit the grub boot option for the 4.19.1 kernel, on the line that has quiet on it, can you add
plymouth.enable=0
See how that goes.

Hi, i just gave it a try and added the boot option plymouth.enable=0, then I booted the system… the first 2 seconds I saw the boot messages (standard vga res) , but then everything disappeared, black screen, monitor shows message “no signal”. No VT switch with ctr+alt+F1 and also no reset possible. Only hard power off can help so far.
My guess: when trying to switch a to higher screen resolution the system freezes completely.

BUT I have a fully functional previous tumbleweed with Kernel 4.18 in my boot menu - so the issue is not that tragical for me. I think I will wait for a newer release as Knurpht already suggested.

Dear malcolmlewis, Thanks a lot for your patience, competence and helpfulness :)

malcolmlewis · November 16, 2018, 1:00am

Hi
No worries, glad to be of help

If you have another computer/smart phone(?) around and can log in via ssh to the computer then could probably get a better idea of what’s happening.

One thing you need to do if it jumps to a newer kernel to configure zypper and multi-version to keep that 4.18 kernel around just in case 4.19.2 doesn’t work either and it removes the 4.18 one.

malcolmlewis · November 16, 2018, 2:08am

On Thu 15 Nov 2018 09:46:03 PM CST, malcolmlewis wrote:

loewe19;2886466 Wrote:
> Hi, kernel-firmware package 20181001-1.1 is installed. GPU is a AMD
> Athlon 200GE Dual Core.
> I bought this CPU about one month ago because of its energy
> efficiency. Mainboard is Asus Prime B350 Plus
>
> Here’s the output:
>
>
>
> Thanks a lot for your support !
Hi
OK, so it’s a Raven, so the kernel-firmware has this and your card is
picking the right driver…

So you get to grub and soon after booting, just a black screen, no
cursor visible? If after you boot and press the esc key, do you get
output? When the screen does go blank, if you press ctrl+alt+F1 do you
get to a VT?

If you edit the grub boot option for the 4.19.1 kernel, on the line that
has quiet on it, can you add

Code:

plymouth.enable=0

See how that goes.

Hi
And just a followup to those dracut warnings, that firmware doesn’t
exist in the kernel-firmware tree yet…
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

loewe19 · December 2, 2018, 11:40am

Hello,

thx a lot for this !

Today I tried to do a new install with Tumbleweed snapshot 20181129. I downloaded the Iso Image.

The Installer alone still crashes at bootup, same phenomenon as mentioned above (black screen with freeze) - NO chance for an installation.
So I guess the Radeon Vega / Raven Ridge Firmware for Athlon 200GE still has not found its way into the Kernel 4.19 yet.

I will still use my old Tumbleweed 4.18 setup, which is working and supporting my Graphics perfectly.

Does anyone know where I can verify, when this Firmware will be available in the new Kernel 4.19 ?