[SOLVED] intel driver fails to set drm interface version

nullptr-deref · 2024-07-24 11:48:26

Hi.

I'm struggling with the following issue for a couple of days now and had no success yet.

Preamble

A couple of years ago I've installed LightDM on my machine (MacBook Pro early 2011), made a couple of tweaks and it somehow have been working for a year or so up until I've decided to switch to xinit startup for the sake of experiment.

I've sticked with it for a year or so and then decided to switch back to LightDM and here where my journey begins.

Problem

After installing lightdm package, removing xinit package, enabling LightDM in systemd and rebooting my display greeted me with the black screen and blinking cursor in the top left corner without any ability to switch to VT1..6 (Ctrl-Alt-F? did not seem to work properly). I've been struggling with it for about a week and, having no success, switched back to xinit where my screen seemed to work somehow properly.

After half-a-year break I've returned to this issue with somewhat deeper knowledge of the system and discovered that it's Xorg and it's related stuff seems to cause problems.

Xorg.1.log
Xorg.0.log

uname -a output:

Linux anonymous 6.9.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 18 Jul 2024 18:06:13 +0000 x86_64 GNU/Linux

lspci | grep -F 'VGA' output:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

As far as I understand, there's some issues with permissions and due to them intel driver cannot access /sys/class/card0 (perhaps a mistake).

I've tried wiping /etc/X11/xorg.conf, /etc/X11/xorg.conf.d/20-intel.conf (my laptop uses Intel HD Graphics), somehow tweaking those config files, juggling with drivers (right now I have mesa-amber, libva-mesa-driver, xf86-video-intel, vulkan-intel packages installed), disabling simpledrm_platform_driver_init via initcall_blacklist kernel argument and read almost every thread mentioning quote "*failed to set drm interface version*" (there are not that many of them, surprisingly).

Don't have any clues by now how to make LightDM work properly. Any help is appreciated.

P.S. Perhaps journalctl output would be useful but I'm not posting it right now because I have no idea what should be filtered out in order to reduce it's size and not to make it useless at the same time.

Last edited by nullptr-deref (2024-07-28 22:02:43)

Lone_Wolf · 2024-07-24 13:13:35

Hard to tell atm , need more info .

as root, run journacltctl -b -1 | curl -F 'file=@-' 0x0.st to get the journal from the previous boot.
If that's not a lightdm failed boot, increase the number to get earlier boots .
The command will upload the journal to public hosting and output a link when finished .
Post that link .

Also post the contents of your /etc/mkinitcpio.conf file and the output of ls -lR /etc/X11/xorg.conf.d/ .

nullptr-deref · 2024-07-24 15:39:36

Thanks for the quick response.

journalctl -b -1 output
Contents of /etc/mkinitcpio.conf

ls -lR /etc/X11/xorg.conf.d/ output:

/etc/X11/xorg.conf.d/:
total 8
-rw-r--r-- 1 root root 393 Dec  5  2023 00-keyboard.conf
-rw-r--r-- 1 root root 129 Oct  1  2022 30-touchpad.conf

Also I think that it'd be useful to post contents of /etc/default/grub since I've also modified it in order to resolve the issue. -> /etc/default/grub

Seems like lightdm's trying to load itself several times for some reason.

Lone_Wolf · 2024-07-25 10:33:07

Unpatched return thunk in use. This should not happen!

there's an issue between your kernel and the broadcom-wl driver , https://bbs.archlinux.org/viewtopic.php?id=296729.

Have you recently tried using the b43 module from the kernel ?

Jul 24 18:24:22 anonymous x-daemon[601]: X.Org X Server 1.21.1.13
Jul 24 18:24:22 anonymous x-daemon[601]: X Protocol Version 11, Revision 0
Jul 24 18:24:22 anonymous x-daemon[601]: Current Operating System: Linux anonymous 6.9.10-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 18 Jul 2024 18:06:13 +0000 x86_64
Jul 24 18:24:22 anonymous x-daemon[601]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=74434249-988c-4df6-b45e-034dcef8bd3e rw loglevel=3 quiet acpi_backlight=native initcall_blacklist=simpledrm_platform_driver_init i915.modeset=1
Jul 24 18:24:22 anonymous x-daemon[601]:  
Jul 24 18:24:22 anonymous x-daemon[601]: Current version of pixman: 0.43.4
Jul 24 18:24:22 anonymous x-daemon[601]:         Before reporting problems, check http://wiki.x.org
Jul 24 18:24:22 anonymous x-daemon[601]:         to make sure that you have the latest version.
Jul 24 18:24:22 anonymous x-daemon[601]: Markers: (--) probed, (**) from config file, (==) default setting,
Jul 24 18:24:22 anonymous x-daemon[601]:         (++) from command line, (!!) notice, (II) informational,
Jul 24 18:24:22 anonymous x-daemon[601]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Jul 24 18:24:22 anonymous x-daemon[601]: (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 18:24:22 2024
Jul 24 18:24:22 anonymous kernel: 8021q: 802.1Q VLAN Support v1.8
Jul 24 18:24:22 anonymous x-daemon[601]: (==) Using config directory: "/etc/X11/xorg.conf.d"
Jul 24 18:24:22 anonymous x-daemon[601]: (==) Using system config directory "/usr/share/X11/xorg.conf.d"

Jul 24 18:24:23 anonymous x-daemon[601]: (EE) client bug: Invalid path /dev/input/event5
Jul 24 18:24:23 anonymous x-daemon[601]: [dix] couldn't enable device 11
Jul 24 18:24:23 anonymous dhcpcd[586]: wlan0: soliciting a DHCP lease
Jul 24 18:24:24 anonymous systemd[1]: Started X on vt7.
Jul 24 18:24:24 anonymous systemd[1]: Started Direct X login for user militarycoder.
Jul 24 18:24:24 anonymous systemd[1]: Reached target Graphical Interface.


Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Parsing config file: /home/militarycoder/.config/polybar/config.ini
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Listening for IPC messages (PID: 828)
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'archlogo' of type 'custom/script'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'xworkspaces' of type 'internal/xworkspaces'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'memory' of type 'internal/memory'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'cpu' of type 'internal/cpu'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'temperature' of type 'internal/temperature'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'wlan' of type 'internal/network'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  module/wlan: Discovered wireless interface wlan0
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'backlight' of type 'internal/backlight'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'alsa' of type 'internal/alsa'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'xkeyboard' of type 'internal/xkeyboard'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'battery' of type 'internal/battery'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loading module 'date' of type 'internal/date'
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loaded 11 modules
Jul 24 18:24:25 anonymous bash[828]: polybar|notice:  Loaded font "FiraCode Nerd Font:size=10" (name=FiraCode Nerd Font, offset=0, file=/usr/share/fonts/TTF/FiraCodeNerdFont-Regular.ttf)
Jul 24 18:24:25 anonymous bash[828]: polybar|warn:  tray: bar/berry.tray-position is deprecated, use the dedicated tray module to display the system tray


Jul 24 18:24:25 anonymous systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 24 18:24:25 anonymous systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 24 18:24:26 anonymous systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Jul 24 18:24:26 anonymous systemd[1]: Starting Light Display Manager...
Jul 24 18:24:26 anonymous systemd[1]: Started Light Display Manager.
Jul 24 18:24:25 anonymous systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 24 18:24:25 anonymous systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jul 24 18:24:26 anonymous systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Jul 24 18:24:26 anonymous systemd[1]: Starting Light Display Manager...
Jul 24 18:24:26 anonymous systemd[1]: Started Light Display Manager.

What is x-daemon and where does it come from ?

Are you tring to start 2 graphical sessions :
one with an autologin as user militarycoder , posibly including polybar
another session with LightDM
?

Head_on_a_Stick · 2024-07-25 13:45:36

@OP: have you installed a greeter?

https://wiki.archlinux.org/title/LightDM#Greeter

I don't recommend LightDM at all though, it runs X under the root user, which is really bad. Using just startx/xinit runs X under your normal user, which is _much_ better.

seth · 2024-07-25 18:33:39

If it's not just lacking a greeter:

Jul 24 18:24:28 anonymous systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Jul 24 18:24:28 anonymous systemd[1]: lightdm.service: Failed with result 'exit-code'.

Post the lightdm log, it's in /var/log and because of the symptoms (despite the i9125 module apparently being in the initramfs) try https://wiki.archlinux.org/title/LightD … TTY_output

But I agree w/ HoaS, on a de-facto single-user system, DMs are kinda pointless.
You could instead boot straight into your (locked) GUI session.

nullptr-deref · 2024-07-25 22:38:08

Lone_Wolf wrote:

Have you recently tried using the b43 module from the kernel ?

No, I've been tweaking this for some time quite a while ago and for some reason (which I cannot remember right now) stuck with broadcom-wl.

Right now I've replaced it with b43-firmware from AUR and it works perfectly fine.

Jul 26 00:32:30 anonymous kernel: b43-phy0: Broadcom 4331 WLAN found (core revision 29)
Jul 26 00:32:30 anonymous kernel: b43-phy0: Found PHY: Analog 9, Type 7 (HT), Revision 1
Jul 26 00:32:30 anonymous kernel: b43-phy0: Found Radio: Manuf 0x17F, ID 0x2059, Revision 0, Version 1
Jul 26 00:32:30 anonymous kernel: b43-phy0 warning: 5 GHz band is unsupported on this PHY
Jul 26 00:32:30 anonymous systemd-modules-load[282]: Inserted module 'b43'
Jul 26 00:32:31 anonymous kernel: b43-phy0: Loading firmware version 784.2 (2012-08-15 21:35:19)
Jul 26 00:32:33 anonymous kernel: b43-phy0: Loading firmware version 784.2 (2012-08-15 21:35:19)

Lone_Wolf wrote:

What is x-daemon and where does it come from ?

To my greatest shame I cannot tell what that x-daemon is, what spawns it and how this log gets into journal.
I thought that these logs are coming from LightDM X child process but now it's obvious that they are not because they
appear much earlier than LightDM actual boot up.

Lone_Wolf wrote:

Are you tring to start 2 graphical sessions :
one with an autologin as user militarycoder , posibly including polybar
another session with LightDM
?

Absolutely not. All I'm trying to do is to just make display manager work somehow appropriately. To be more precise, I actually want it to do 2 things:

load login screen after startup;
load desktop after login is complete.

That's what it's behavior looked like back in the day and that's what I'm trying to achieve, at least.

Interesting thing is that sometimes right before black screen with blinking cursor appearance my standard desktop appears for a split second.
Aforementioned logs explain this phenomenon but I still cannot figure out where are they coming from.

This may be related with autologin attempt you've mentioned earlier but as far as I remember I didn't mess up with autologin stuff.
According to https://wiki.archlinux.org/title/Xinit# … X_at_login there should be some setup code in ~/.bash_profile but my ~/.bash_profile looks like that:

#
# ~/.bash_profile
#

[[ -f ~/.bashrc ]] && . ~/.bashrc

Seems like something is setting up X server before LightDM and I cannot figure out what actually does it.

systemctl list-unit-files | grep -F 'enabled' reports the following:

acpid.service                                                             enabled         disabled
dhcpcd.service                                                            enabled         disabled
getty@.service                                                            enabled         enabled
iwd.service                                                               enabled         disabled
lightdm.service                                                           enabled         disabled
lm_sensors.service                                                        enabled         disabled
mbpfan.service                                                            enabled         disabled
systemd-boot-update.service                                               disabled        enabled
systemd-confext.service                                                   disabled        enabled
systemd-fsck-root.service                                                 enabled-runtime disabled
systemd-homed-activate.service                                            disabled        enabled
systemd-homed.service                                                     disabled        enabled
systemd-network-generator.service                                         disabled        enabled
systemd-networkd-wait-online.service                                      disabled        enabled
systemd-networkd.service                                                  disabled        enabled
systemd-pstore.service                                                    disabled        enabled
systemd-remount-fs.service                                                enabled-runtime disabled
systemd-resolved.service                                                  disabled        enabled
systemd-sysext.service                                                    disabled        enabled
systemd-timesyncd.service                                                 enabled         enabled
wluma.service                                                             enabled         disabled
systemd-journald-audit.socket                                             disabled        enabled
systemd-mountfsd.socket                                                   disabled        enabled
systemd-nsresourced.socket                                                disabled        enabled
systemd-userdbd.socket                                                    disabled        enabled
machines.target                                                           disabled        enabled
reboot.target                                                             disabled        enabled
remote-cryptsetup.target                                                  disabled        enabled
remote-fs.target                                                          enabled         enabled

Apart from lightdm.service I'm not noticing anything that could autostart X before LightDM.

Any clues which configuration file I've messed up?

nullptr-deref · 2024-07-25 22:41:17

Head_on_a_Stick wrote:

@OP: have you installed a greeter?

Yes, I have lightdm-gtk-greeter installed and properly configured via /etc/lightdm/lightdm.conf.

nullptr-deref · 2024-07-25 22:50:49

seth wrote:

try https://wiki.archlinux.org/title/LightD … TTY_output

Done. No luck yet.

lightdm log

nullptr-deref · 2024-07-25 23:08:56

Now I see what actually starts up X server.
I found out that I'm using xlogin-git and have xlogin@username.service enabled which have been launching X server.

I disabled xlogin@username.service and display manager starts up smoothly again.
Well, relatively smoothly tbh because it cannot get past login screen but It gets to the greeter now, at least.

However, this all seems a bit off-topic according to thread title. Should I change it to somewhat appropriate and mark as resolved or shall we continue to resolving intel driver issues?

seth · 2024-07-26 05:51:26

Yes, please create a new thread and there please post a complete system journal after attempting to login w/ lightdm

nullptr-deref · 2024-07-27 08:49:18

Ok, will create a new thread after performing a bit of investigation myself.

nullptr-deref wrote:

After half-a-year break I've returned to this issue with somewhat deeper knowledge of the system and discovered that it's Xorg and it's related stuff seems to cause problems.
Xorg.1.log
Xorg.0.log

Back to the thread topic, any guesses what exactly causes such an error listed in Xorg.1.log?

Was driver under screen :1 not able to access DRI because another screen (:0 in this particular case) have obtained access to the DRI earlier?

I looked through this article but it does not cover multi-screen DRI access if this feature is present at all.

Last edited by nullptr-deref (2024-07-27 08:58:20)

seth · 2024-07-27 11:58:15

This is a concurrent access issue, though should™ not be a problem when running two X11 servers on different VTs
I suspect lightdm and that xlogin service try to concurrently run X11 servers on the same VT - maybe it's also some race condition?
Can you start lightdm, switch to another VT and "startx" there (provided you've a meningful xinitrc)?

Sidebar, you probably want to remove xf86-video-vesa and xf86-video-fbdev

nullptr-deref · 2024-07-28 20:50:10

seth wrote:

Can you start lightdm, switch to another VT and "startx" there (provided you've a meningful xinitrc)?

Yes, I'm writing this post having X server launched under VT2 and lightdm on VT7 simultaneously. Perhaps you're right about your suspicions.

nullptr-deref · 2024-07-28 22:02:03

Replying to this post: the WM wasn't properly loading upon login success because I've configured greeter to load nonexistent WM. I've modified greeter's preference to launch previously installed berry WM, tweaked & updated .xprofile and now it's running smoothly again. No need for the separate thread.

As long as both problems are gone, I'm marking this thread as solved. Perhaps you have some commentaries on https://bbs.archlinux.org/viewtopic.php … 5#p2186535 and https://bbs.archlinux.org/viewtopic.php … 0#p2186810 - I'll gladly read them: deeper knowledge of the system is never excessive.

Arch Linux

#1 2024-07-24 11:48:26