X does not start anymore after today's update
Hi, when I started my Tumbleweed this morning it still started lightdm fine. I did some maintenance tasks including a zypper dup. (The other things were just copying data in my home from another disk but this really shouldn't break X.) After the next reboot X/lightdm did not start anymore. I read /var/log/Xorg.0.log carefully multiple times now but do not find any error there. It does a lot of things and late includes all the different input drivers. After the last and 0.5 seconds later it starts to tell me that it removed devices again, undloads libinput and finally says (II) Server terminated successfully (0). Closing log file. So I'm a bit lost. The logs looks like a graceful X shutdown but for sure did not do that myself. From a quick look I see only a few packages which might be relevant and have been updated: xorg-x11-Xvnc kernel-default dmesg shows [ 20.012692] [drm] Unknown EDID CEA parser results [ 20.026952] [drm] Unknown EDID CEA parser results I cannot tell if I had those before. And because I was in the middle of setting up this new system I cannot/do not want to use snapper to go back completely to an intermediate state. Graphics device is Model: "ATI Cezanne" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1638 "Cezanne" Driver: "amdgpu" Driver Modules: "amdgpu" Any ideas or other people having similar issues? Thanks, Wolfgang
On 20.11.2021 17:51, Wolfgang Rosenauer wrote:
Hi,
when I started my Tumbleweed this morning it still started lightdm fine.
I did some maintenance tasks including a zypper dup. (The other things were just copying data in my home from another disk but this really shouldn't break X.)
After the next reboot X/lightdm did not start anymore.
I read /var/log/Xorg.0.log carefully multiple times now but do not find any error there. It does a lot of things and late includes all the different input drivers. After the last and 0.5 seconds later it starts to tell me that it removed devices again, undloads libinput and finally says
(II) Server terminated successfully (0). Closing log file.
So I'm a bit lost. The logs looks like a graceful X shutdown but for sure did not do that myself.
From a quick look I see only a few packages which might be relevant and have been updated: xorg-x11-Xvnc kernel-default
dmesg shows [ 20.012692] [drm] Unknown EDID CEA parser results [ 20.026952] [drm] Unknown EDID CEA parser results
I cannot tell if I had those before.
And because I was in the middle of setting up this new system I cannot/do not want to use snapper to go back completely to an intermediate state.
Graphics device is Model: "ATI Cezanne" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1638 "Cezanne" Driver: "amdgpu" Driver Modules: "amdgpu"
Any ideas or other people having similar issues?
Full output of "journalctl -b" and full Xorg.log may give some hints.
В письме от суббота, 20 ноября 2021 г. 17:51:15 MSK пользователь Wolfgang Rosenauer писал:
I did some maintenance tasks including a zypper dup. (The other things were just copying data in my home from another disk but this really shouldn't break X.)
After the next reboot X/lightdm did not start anymore.
Graphics device is Model: "ATI Cezanne" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1638 "Cezanne" Driver: "amdgpu" Driver Modules: "amdgpu"
Any ideas or other people having similar issues?
I recently ran into a similar problem. After removing the xf86-video-ati package (see [1]), the X Server is now started without any problem. 1. https://bugzilla.opensuse.org/show_bug.cgi?id=1160807#c3
Am 20.11.21 um 17:19 schrieb Andrey Karepin:
В письме от суббота, 20 ноября 2021 г. 17:51:15 MSK пользователь Wolfgang Rosenauer писал:
I did some maintenance tasks including a zypper dup. (The other things were just copying data in my home from another disk but this really shouldn't break X.)
After the next reboot X/lightdm did not start anymore.
Graphics device is Model: "ATI Cezanne" Vendor: pci 0x1002 "ATI Technologies Inc" Device: pci 0x1638 "Cezanne" Driver: "amdgpu" Driver Modules: "amdgpu"
Any ideas or other people having similar issues?
I recently ran into a similar problem. After removing the xf86-video-ati package (see [1]), the X Server is now started without any problem.
that didn't help unfortunately. Wolfgang
Am 20.11.21 um 16:24 schrieb Andrei Borzenkov:
Full output of "journalctl -b" and full Xorg.log may give some hints.
Xorg.log I didn't find anything useful. Checking journalctl -b ... and finally it surely was my stupidity :-( I added some users manually when migrating from my old to the new system and finally lightdm's var folder where owned by another user. Sorry for the noise. Wolfgang
El sáb, 20 nov 2021 a las 14:06, Wolfgang Rosenauer
(
Am 20.11.21 um 16:24 schrieb Andrei Borzenkov:
Full output of "journalctl -b" and full Xorg.log may give some hints.
Xorg.log I didn't find anything useful. Checking journalctl -b ...
and finally it surely was my stupidity :-(
I added some users manually when migrating from my old to the new system and finally lightdm's var folder where owned by another user.
Sorry for the noise.
Today I experienced a black screen at the end of the Tumbleweed
update, bay later appeared the Plasma screen.
In dmesg I find (with Radeon RX-580):
[ 0.839352] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
[ 0.839354] vesafb: scrolling: redraw
[ 0.839355] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[ 0.839368] vesafb: framebuffer at 0xd0000000, mapped to
0x(____ptrval____), using 8128k, total 8128k
[ 0.839456] Console: switching to colour frame buffer device 240x67
[ 0.858557] fb0: VESA VGA frame buffer device
[ 3.494774] [drm] amdgpu kernel modesetting enabled.
[ 3.494858] amdgpu: CRAT table not found
[ 3.494861] amdgpu: Virtual CRAT table created for CPU
[ 3.494875] amdgpu: Topology: Add CPU node
[ 3.498234] fb0: switching to amdgpu from VESA VGA
[ 3.498343] Console: switching to colour dummy device 80x25
[ 3.498363] amdgpu 0000:01:00.0: vgaarb: deactivate vga console
[ 3.498480] [drm] initializing kernel modesetting (POLARIS10
0x1002:0x67DF 0x1DA2:0xE366 0xE7).
[ 3.498486] amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ)
feature not supported
[ 3.498496] [drm] register mmio base: 0xF7FC0000
[ 3.498498] [drm] register mmio size: 262144
[ 3.498500] [drm] PCIE atomic ops is not supported
[ 3.498505] [drm] add ip block number 0
participants (4)
-
Andrei Borzenkov -
Andrey Karepin -
Juan Erbes -
Wolfgang Rosenauer