[Bug 1134475] New: X11 not starting - Tumbleweed - After Kernel update (5.0.9 +) - radeon
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475 Bug ID: 1134475 Summary: X11 not starting - Tumbleweed - After Kernel update (5.0.9 +) - radeon Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: james.roulston.1@gmail.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0 Build Identifier: After updating Tumbleweed to latest kernel 5.0.9 (5.0.11 Current) the system would freeze during boot although there was still hard drive activity. I could successfully boot using 'Nomodeset' in the kernel parameter. I could startx but in some fallback mode so quite slow. I could load in the correct driver by doing 'modprobe -v radeon modeset=1'. this started X correctly. It seems to be loading 'radeonfb' instead of 'radeon' I fix for this will be in the additional info area. Video details below VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8470D] [1002:9996] Subsystem: Hewlett-Packard Company Device [103c:2b60] Kernel driver in use: radeon Kernel modules: radeon Reproducible: Always Steps to Reproduce: 1. Update system using zypper dup with new kernel 2. reboot 3. Actual Results: The screen hangs with no X display, the keyboard shortcuts ctrl+alt+Fn keys don't work but ctrl+alt+del reboots. Expected Results: X window manager should start. I fixed the issue by doing the following. On the terminal i go into /etc/modprobe.d I created a file called 'blacklist.radeon.conf' in that file I added the line 'blacklist radeon' I then ran 'mkinitrd' when I rebooted the issue was still the same so I changed the line to 'blacklist radeonfb' but did not run mkinitrd. I rebooted and everything works again. I have to re-edit the 'blacklist.radeon.conf' file with 'blacklist radeon' then mkinitrd and then re-edit that file to 'blacklist radeonfb' I have to repeat these steps on every Kernel Update since 5.0.9. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c1
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c2
--- Comment #2 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
Thomas Zimmermann
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c3
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c4
--- Comment #4 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c5
--- Comment #5 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c6
--- Comment #6 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c7
--- Comment #7 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c8
--- Comment #8 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c9
--- Comment #9 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c10
--- Comment #10 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c11
--- Comment #11 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c12
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c13
--- Comment #13 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c14
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c15
--- Comment #15 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c16
--- Comment #16 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c17
--- Comment #17 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c18
--- Comment #18 from Stefan Dirsch
The amdgpu-pro version is 19.10. which I downloaded from the same link you provided. It's not compatible with my card so I'm back using radeon which works well.
I have downloaded the SLED/SLES 15 RPM packages from https://www.amd.com/en/support/kb/release-notes/rn-rad-lin-19-10-unified In none of the packages I could find a dracut file. It's also not created by a %pre/%post RPM script. I have no idea how this file /etc/dracut.conf.d/amdgpu-5.0.13-1-default.conf is created. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c19
--- Comment #19 from James Roulston
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c20
--- Comment #20 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c21
--- Comment #21 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c22
--- Comment #22 from Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c23
--- Comment #23 from Fabian Baumanis
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c24
--- Comment #24 from Fabian Baumanis
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c25
--- Comment #25 from Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c26
--- Comment #26 from Stefan Dirsch
Strictly speaking, the postun scriptlet should check the argument $1 to see if it's an update or the actual uninstall.
Right, we would need something like this: %preun -p /bin/sh # not on update! if [ "$1" -eq 0 ]; then # dkms call may fail, so the script, which removes the dracut file, will not be executed # so make sure that it gets removed in any case rm -f /etc/dracut.conf.d/amdgpu-*.conf dkms remove -m amdgpu -v 19.10-785424 --all --rpm_safe_upgrade fi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c28
Anatoli Antonovitch
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475
http://bugzilla.opensuse.org/show_bug.cgi?id=1134475#c29
--- Comment #29 from Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com