[opensuse-factory] Flickering screen (and worse)
I've been having trouble with an intermittently flickering screen on my laptop for the past few weeks. About half the time, it's minor, just flickering for a few seconds, but it can get worse, lasting for a minute or two and blanking large (nearly all) of the screen. The worst incidents will end with the following in the log: Jul 24 15:44:50 homelap7 kernel: i915 0000:00:02.0: [drm] HPD interrupt storm detected on connector eDP-1: switching from hotplug detection to polling After this, the flickering stops. Searching, I noticed issues like this associated with the i915 driver over the past few years, so I though I'd ask if there might be a cause in recent Tumbleweed releases. Otherwise, I guess I'm off to the local computer repair shop. Here's some hopefully-relevant information about the graphics card:
hwinfo --gfxcard 24: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp._LgIsmf7zU8 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620 (Whiskey Lake)" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x3ea0 "UHD Graphics 620 (Whiskey Lake)" SubVendor: pci 0x1558 "CLEVO/KAPOK Computer" SubDevice: pci 0x1323 Driver: "i915" Driver Modules: "i915" Memory Range: 0x6022000000-0x6022ffffff (rw,non-prefetchable) Memory Range: 0x4000000000-0x400fffffff (ro,non-prefetchable) I/O Ports: 0x4000-0x403f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 131 (15907724 events) Module Alias: "pci:v00008086d00003EA0sv00001558sd00001323bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown
Primary display adapter: #24 Thanks! David Walker
On 7/25/20 1:15 PM, David Walker wrote:
Jul 24 15:44:50 homelap7 kernel: i915 0000:00:02.0: [drm] HPD interrupt storm detected on connector eDP-1: switching from hotplug detection to polling
There is a lot of discussion about this over the past two years. The freedesktop bug was: [drm] HPD interrupt storm detected on connector HDMI-A-1 : switching from hot... https://bugs.freedesktop.org/show_bug.cgi?id=106675 This was supposed resolved in the 4.18 kernel release. However, a search with "interrupt storm switching from hotplug to polling" discloses pages of questions for just about every distribution. A regression is a possibility, other than that, I am no where near familiar enough with hardware to know what would trigger the message, or even if flaky hardware is capable of triggering the problem. -- David C. Rankin, J.D.,P.E.
David C. Rankin composed on 2020-07-25 22:38 (UTC-0500):
David Walker wrote:
Jul 24 15:44:50 homelap7 kernel: i915 0000:00:02.0: [drm] HPD interrupt storm detected on connector eDP-1: switching from hotplug detection to polling ... Whiskey Lake ...
There is a lot of discussion about this over the past two years. The freedesktop bug was:
[drm] HPD interrupt storm detected on connector HDMI-A-1 : switching from hot... https://bugs.freedesktop.org/show_bug.cgi?id=106675
This was supposed resolved in the 4.18 kernel release.
That bug was closed months before Whiskey Lake was available to the public, while originally filed against a decade older IGP. Does switching from Intel DDX to modesetting DDX or vice versa change anything? inxi -Gxx https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-gra... -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 25/07/2020 20.15, David Walker wrote:
I've been having trouble with an intermittently flickering screen on my laptop for the past few weeks. About half the time, it's minor, just flickering for a few seconds, but it can get worse, lasting for a minute or two and blanking large (nearly all) of the screen. The worst incidents will end with the following in the log:
Jul 24 15:44:50 homelap7 kernel: i915 0000:00:02.0: [drm] HPD interrupt storm detected on connector eDP-1: switching from hotplug detection to polling
After this, the flickering stops.
Now that you mention it, I have observed some flickering in my laptop after coming back from suspend to ram. I thought it was hardware related, but after reading your post I will observe the log the next time it happens. But on Leap 15.1 -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On Sat, 2020-07-25 at 11:15 -0700, David Walker wrote:
I've been having trouble with an intermittently flickering screen on my laptop for the past few weeks. About half the time, it's minor, just flickering for a few seconds, but it can get worse, lasting for a minute or two and blanking large (nearly all) of the screen. The worst incidents will end with the following in the log:
Jul 24 15:44:50 homelap7 kernel: i915 0000:00:02.0: [drm] HPD interrupt storm detected on connector eDP-1: switching from hotplug detection to polling
After this, the flickering stops.
This is just a guess, but have you tried adding "i915.enable_psr=0" to the kernel parameters at boot (hit 'e' when the bootloader shows up, add the above snippet right after '...splash=silent quiet' on the same line)? There have been issues with the i915 graphics flickering that have been helped with this, perhaps at the cost of somewhat higher power usage [see e.g. < https://wiki.archlinux.org/index.php/Dell_XPS_13_(7390)>]. Cheers, -- Atri Bhattacharya Sun 26 Jul 14:10:40 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks, everyone! I've summarized responses below. David On 7/26/20 5:17 AM, Atri Bhattacharya wrote:
On Sat, 2020-07-25 at 11:15 -0700, David Walker wrote:
This is just a guess, but have you tried adding "i915.enable_psr=0" to the kernel parameters at boot (hit 'e' when the bootloader shows up, add the above snippet right after '...splash=silent quiet' on the same line)? There have been issues with the i915 graphics flickering that have been helped with this, perhaps at the cost of somewhat higher power usage [see e.g. < https://wiki.archlinux.org/index.php/Dell_XPS_13_(7390)>].
Cheers, This seems the easiest suggestion, so I've started with it. The flickering doesn't happen every day, so it may take a while before I know if it works.
On 7/26/20 3:58 AM, Carlos E. R. wrote:
Now that you mention it, I have observed some flickering in my laptop after coming back from suspend to ram. I thought it was hardware related, but after reading your post I will observe the log the next time it happens.
But on Leap 15.1
Thanks. Note, though, that the log entry doesn't always appear, only when the flickering is severe (/e.g./, lasting a minute or more, or blacking-out large portions of the screen. On 7/25/20 9:30 PM, Felix Miata wrote:
Does switching from Intel DDX to modesetting DDX or vice versa change anything?
inxi -Gxx
https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-gra...
Here's the output from "inxi -Gxx": Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: <xdpyinfo missing> OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.3 compat-v: 3.0 direct render: Yes I'll try switching to the Intel DDX after resolving Atri's suggestion. I currently have xorg-x11-driver-video installed and the following xf86-video-* packages: xf86-video-fbdev xf86-video-vesa Am I right that I can switch to the Intel DDX by just installing xf86-video-intel? I notice there's also xf86-video-intel-32bit; is there a reason it should be installed, too? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
David Walker composed on 2020-07-26 10:37 (UTC-0700):
Here's the output from "inxi -Gxx":
Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: <xdpyinfo missing>
Most installations include this. Did you start with a minimal installation and keep recommends disabled? It's a small and useful utility for X diagnosis.
OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.3 compat-v: 3.0 direct render: Yes
I'll try switching to the Intel DDX after resolving Atri's suggestion. I currently have xorg-x11-driver-video installed and the following xf86-video-* packages:
xf86-video-fbdev xf86-video-vesa
Those are crude, useful mainly as fallbacks for diagnosis and repai.
Am I right that I can switch to the Intel DDX by just installing xf86-video-intel?
That's how it has always worked for me. /etc/X11/xorg_pci_ids/modesetting_ids supposedly exists to be able to override it, but it has only ever been a 2 byte placeholder for me.
I notice there's also xf86-video-intel-32bit; is there a reason it should be installed, too?
I didn't know it existed. I suppose Wine users might benefit from it. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks, Felix. Comments below. David On 7/26/20 12:02 PM, Felix Miata wrote:
David Walker composed on 2020-07-26 10:37 (UTC-0700):
Here's the output from "inxi -Gxx":
Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: <xdpyinfo missing> Most installations include this. Did you start with a minimal installation and keep recommends disabled? It's a small and useful utility for X diagnosis.
As far as I know, I did a normal Tumbleweed installation. I've now installed xdpyinfo: Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.Org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.3 compat-v: 3.0 direct render: Yes
I notice there's also xf86-video-intel-32bit; is there a reason it should be installed, too? I didn't know it existed. I suppose Wine users might benefit from it.
I thought the same thing. It seems to be the only one with a "-32bit" version, though. Strange.
I got some flickering with "i915.enable_psr=0", so I've removed it and have installed xf86-video-intel and xf86-video-intel-32bit, which pulled in libvdpau_va_gl1, libvulkan_intel, libxcb-util1-32bit, libXv1-32bit, libXvMC1, and libXvMC1-32bit. I haven't seen any flickering since installing these, but it has been very long. Also...
Am I right that I can switch to the Intel DDX by just installing xf86-video-intel? That's how it has always worked for me. /etc/X11/xorg_pci_ids/modesetting_ids supposedly exists to be able to override it, but it has only ever been a 2 byte placeholder for me.
If I'm reading the following from "inxi -Gxx" right, though, it doesn't look like I am using the Intel DDX after installing it. Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.Org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.3 compat-v: 3.0 direct render: Yes Am I misreading this, or is there something more I need to do to use the Intel DDX? David
I am still having flickering woes, and I'm increasingly convinced that simply installing xf86-video-intel and xf86-video-intel-32bit isn't sufficient to actually switch to the intel DDX, instead of modesetting. (See below.) Can anyone shed some light on how to switch from modesetting to intel? I have the feeling that the wiki's documentation may be out of date (or things aren't working as they should). David On 7/27/20 10:20 AM, David Walker wrote:
I got some flickering with "i915.enable_psr=0", so I've removed it and have installed xf86-video-intel and xf86-video-intel-32bit, which pulled in libvdpau_va_gl1, libvulkan_intel, libxcb-util1-32bit, libXv1-32bit, libXvMC1, and libXvMC1-32bit. I haven't seen any flickering since installing these, but it has been very long. Also...
Am I right that I can switch to the Intel DDX by just installing xf86-video-intel? That's how it has always worked for me. /etc/X11/xorg_pci_ids/modesetting_ids supposedly exists to be able to override it, but it has only ever been a 2 byte placeholder for me. If I'm reading the following from "inxi -Gxx" right, though, it doesn't look like I am using the Intel DDX after installing it.
Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.Org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa alternate: intel resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.3 compat-v: 3.0 direct render: Yes
Am I misreading this, or is there something more I need to do to use the Intel DDX?
David
David Walker wrote:
I am still having flickering woes, and I'm increasingly convinced that simply installing xf86-video-intel and xf86-video-intel-32bit isn't sufficient to actually switch to the intel DDX, instead of modesetting. (See below.) Can anyone shed some light on how to switch from modesetting to intel? I have the feeling that the wiki's documentation may be out of date (or things aren't working as they should).
For me it does work that way, at least for the normal Xorg. There, intel has higher priority than modesetting, and just by having xf86-video-intel installed it uses it (32bit isn't needed in my case). /var/log/Xorg.0.log confirms that intel is used (see excerpt below). This is with a HD530 (Skylake) GPU. But you seem to use Wayland? No idea how that works, and which logs are created there... ------------------ [ 27.107] (==) Matched intel as autoconfigured driver 0 [ 27.107] (==) Matched modesetting as autoconfigured driver 1 [ 27.107] (==) Matched fbdev as autoconfigured driver 2 [ 27.107] (==) Matched vesa as autoconfigured driver 3 .... [ 27.125] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: ..... [ 27.154] (II) UnloadModule: "modesetting" [ 27.154] (II) Unloading modesetting [ 27.154] (II) UnloadModule: "fbdev" [ 27.154] (II) Unloading fbdev [ 27.154] (II) UnloadSubModule: "fbdevhw" [ 27.154] (II) Unloading fbdevhw [ 27.154] (II) UnloadModule: "vesa" [ 27.154] (II) Unloading vesa ----------------------------------- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
David Walker composed on 2020-07-27 10:20 (UTC-0700):
If I'm reading the following from "inxi -Gxx" right, though, it doesn't look like I am using the Intel DDX after installing it.
Graphics: Device-1: ... driver: modesetting unloaded: fbdev,vesa alternate: intel ...
Am I misreading this, or is there something more I need to do to use the Intel DDX?
You did run inxi to generate this after a full X restart, right? If so, then there may be a configuration file specifying use of the modesetting driver, or /etc/X11/xorg_pci_ids/modesetting_ids is more than 2 bytes and specifying an override. Does /etc/X11/xorg.conf.d/50-device.conf exist and contain uncommented lines, including one that specifies modesetting as device? If not, is there some other file specifying modesetting? If not, maybe you should susepaste /var/log/Xorg.0.log for us to examine. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks, Felix! Yours and Peter's comments gave me a new path for investigation. I logged into Gnome using X11, rather than Wayland, and now I'm using the intel driver: > inxi -Gxx Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.4 compat-v: 3.0 direct render: Yes So it seems that Wayland doesn't use the intel DDX if it's installed, but X11 does. I'll run like this for a while to see how it goes. If it goes OK, I'll switch back to the modesetting DDX but stay with X11 to see if its the DDX or Wayland. Specific comments below. David On 7/31/20 6:53 AM, Felix Miata wrote:
You did run inxi to generate this after a full X restart, right?
Yes. I checked again just before switching from Wayland to X11, and it showed the same thing.
If so, then there may be a configuration file specifying use of the modesetting driver, or /etc/X11/xorg_pci_ids/modesetting_ids is more than 2 bytes and specifying an override. Does /etc/X11/xorg.conf.d/50-device.conf exist and contain uncommented lines, including one that specifies modesetting as device? If not, is there some other file specifying modesetting? If not, maybe you should susepaste /var/log/Xorg.0.log for us to examine.
None of these three files exist on my system. I have to admit it'd be nice to know where Xorg.0.log is; I'm running the 20200729 Tumbleweed snapshot and have always been staying pretty current.
* David Walker
On 7/31/20 6:53 AM, Felix Miata wrote:
You did run inxi to generate this after a full X restart, right?
Yes. I checked again just before switching from Wayland to X11, and it showed the same thing.
If so, then there may be a configuration file specifying use of the modesetting driver, or /etc/X11/xorg_pci_ids/modesetting_ids is more than 2 bytes and specifying an override. Does /etc/X11/xorg.conf.d/50-device.conf exist and contain uncommented lines, including one that specifies modesetting as device? If not, is there some other file specifying modesetting? If not, maybe you should susepaste /var/log/Xorg.0.log for us to examine.
None of these three files exist on my system. I have to admit it'd be nice to know where Xorg.0.log is; I'm running the 20200729 Tumbleweed snapshot and have always been staying pretty current.
you may find it below /var/log/ -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
David Walker composed on 2020-07-31 11:42 (UTC-0700):
Felix Miata composed on 2020-07-31 09:53 (UTC-0400):
...maybe you should susepaste /var/log/Xorg.0.log for us to examine.
...I have to admit it'd be nice to know where Xorg.0.log is...
In some environments, maybe only some distros, it's ~/.local/share/xorg/Xorg.0.log which is sometimes copied to /var/log/Xorg.0.log. Historically, and in every openSUSE environment I've used, it's always been /var/log/Xorg.0.log. Note too that in some situations X will run in an additional session, such as using startx from a vtty while a display manager is running. In those situations the 0 will be replaced by a 1, or if a third session, a 2. Previous sessions' logs are saved by the same name except with .old appended. With Wayland sessions, I have no idea if there automatically exists any such log as a discrete file, but IIRC, in Fedora at least, equivalent information shows up in the journal if the session is Gnome, and maybe for other DEs/WMs too. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Thanks, Felix and Patrick. The Xorg logs are in ~/.local/share/xorg, not /var/log (or its subdirectories). It is also available in the journal with a type of "/usr/lib/gdm/gdm-x-session" when using X11. When using Wayland, it's is not in the journal. And things get more confusing... I switched back to Wayland from X11 to generate a Xorg.0.log to help debug why the intel DDX was not selected, and Wayland came up with the intel DDX selected: > inxi -Gxx Graphics: Device-1: Intel UHD Graphics 620 vendor: CLEVO/KAPOK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo bus ID: 1-7:3 chip ID: 04f2:b649 Display: wayland server: X.Org 1.20.8 compositor: gnome-shell driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 20.1.4 compat-v: 3.0 direct render: Yes (In case it's not clear, I "switch" between X11 and Wayland by selecting one or the other in GDM when I log in.) My guess is that the log is no longer of use, since it shows a successful selection of intel, but the Xorg.0.log is in https://paste.opensuse.org/60046995, if it does have value. Since i'm now up on Wayland with the intel DDX, I'll stay there to see what happens. I'll then try X11 with the intel DDX if that seems warranted. Is this occupying too much bandwidth on the list? I can move this to bugzilla, if so. It's probably two or three issues: 1) the screen flickering, 2) non-selection of the intel DDX, and maybe 3) documentation of where the logs are kept. Let me know your preference. Thanks for all the time you're spending on this. David On 7/31/20 2:06 PM, Felix Miata wrote:
David Walker composed on 2020-07-31 11:42 (UTC-0700):
Felix Miata composed on 2020-07-31 09:53 (UTC-0400): ...maybe you should susepaste /var/log/Xorg.0.log for us to examine. ...I have to admit it'd be nice to know where Xorg.0.log is... In some environments, maybe only some distros, it's ~/.local/share/xorg/Xorg.0.log which is sometimes copied to /var/log/Xorg.0.log. Historically, and in every openSUSE environment I've used, it's always been /var/log/Xorg.0.log. Note too that in some situations X will run in an additional session, such as using startx from a vtty while a display manager is running. In those situations the 0 will be replaced by a 1, or if a third session, a 2. Previous sessions' logs are saved by the same name except with .old appended.
With Wayland sessions, I have no idea if there automatically exists any such log as a discrete file, but IIRC, in Fedora at least, equivalent information shows up in the journal if the session is Gnome, and maybe for other DEs/WMs too.
Hi David, There is a dedicated mailing list "opensuse-support" for support topics like this specifically. Let's draw a line under this thread; this ML is dedicated to topics related to openSUSE development. Cheers, -- Atri Bhattacharya Sat 1 Aug 00:48:28 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Atri Bhattacharya -
Carlos E. R. -
David C. Rankin -
David Walker -
Felix Miata -
Patrick Shanahan -
Peter Suetterlin