Comment # 28 on bug 1188954 from Felix Miata

Created attachment 863603 [details]
first and second and third Xorg.0.logs from a fresh boot (fail=1, fail=2,
success=3)

Yet another host suffering this without having i915 included in the initrd.
There are three things to distinguish this one from previous comments. First:
this one locks up at the black screen, no response to keyboard. Remote login
enables xdm to be restarted, after which operation is normal. Second, KDM3 is
the DM. Third, when X attempts start automatically for the second time, it uses
/dev/dri/card1 instead of /dev/dri/card0. The manual xdm start also uses
/dev/dri/card1. This /dev/dri/card1 usage on #2+ starts is not unique. I've
seen it with other problem hosts not already mentioned here.
# inxi -SG
System:
  Host: gx280 Kernel: 6.0.12-1-default arch: i686 bits: 32 Desktop: KDE
    v: 3.5.10 Distro: openSUSE Tumbleweed 20221219
Graphics:
  Device-1: Intel 82915G/GV/910GL Integrated Graphics driver: i915 v: kernel
  Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: intel
    unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915
    resolution: 1680x1050~60Hz
  API: OpenGL v: 2.1 Mesa 22.2.4 renderer: i915 (: 915G)
# dmesg | grep ailed
[   62.345100] platform regulatory.0: Direct firmware load for regulatory.db
failed with error -2
[   62.345122] cfg80211: failed to load regulatory.db
[   80.820683] simple-framebuffer simple-framebuffer.0:
[drm:drm_atomic_helper_check_planes] [CRTC:34:crtc-0] atomic driver check
failed
[   80.820690] simple-framebuffer simple-framebuffer.0:
[drm:drm_atomic_check_only] atomic driver check for 963f11c1 failed: -22
[  145.537805] i915 0000:00:02.0: [drm:i915_gem_execbuffer2_ioctl [i915]] copy
1 exec entries failed
[  201.786429] i915 0000:00:02.0: [drm:i915_gem_execbuffer2_ioctl [i915]] copy
1 exec entries failed
[ 2583.712955] i915 0000:00:02.0: [drm:i915_gem_execbuffer2_ioctl [i915]] copy
1 exec entries failed