Skip to main content
Topic: Back with more Xorg (Read 828 times) previous topic - next topic - Topic derived from The code or CLI to re...
0 Members and 2 Guests are viewing this topic.

Back with more Xorg

Having issues with xorg, thinking it has something to do with systemd… Linux headers… or graphics drivers… file should be attached but I am far too tired to keep wrenching at this right now.

For some context: xorg was working fine until I tried to install splashtop-streamer via yay… not sure how that managed to break things yet.

Code: [Select]

[  1348.159]
X.Org X Server 1.21.1.8
X Protocol Version 11, Revision 0
[  1348.160] Current Operating System: Linux slicks-laptop 6.1.51-1-lts #1 SMP PREEMPT_DYNAMIC Sun, 03 Sep 2023 14:39:10 +0000 x86_64
[  1348.161] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=734e4c33-d0fd-4c4d-8099-ee879b3e4d7a rw loglevel=3 quiet
[  1348.162] 
[  1348.163] Current version of pixman: 0.42.2
[  1348.164] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1348.164] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1348.167] (==) Log file: "/home/slick_57/.local/share/xorg/Xorg.0.log", Time: Tue Sep 12 23:11:03 2023
[  1348.168] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1348.168] (==) No Layout section.  Using the first Screen section.
[  1348.168] (==) No screen section available. Using defaults.
[  1348.168] (**) |-->Screen "Default Screen Section" (0)
[  1348.168] (**) |   |-->Monitor "<default monitor>"
[  1348.168] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  1348.168] (==) Automatically adding devices
[  1348.168] (==) Automatically enabling devices
[  1348.168] (==) Automatically adding GPU devices
[  1348.168] (==) Automatically binding GPU devices
[  1348.168] (==) Max clients allowed: 256, resource mask: 0x1fffff
[  1348.168] (WW) The directory "/usr/share/fonts/misc" does not exist.
[  1348.168] Entry deleted from font path.
[  1348.168] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[  1348.168] Entry deleted from font path.
[  1348.168] (Run 'mkfontdir' on "/usr/share/fonts/TTF").
[  1348.168] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[  1348.168] Entry deleted from font path.
[  1348.168] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[  1348.168] Entry deleted from font path.
[  1348.168] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[  1348.168] Entry deleted from font path.
[  1348.168] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[  1348.168] Entry deleted from font path.
[  1348.168] (==) FontPath set to:

[  1348.168] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1348.168] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[  1348.168] (II) Module ABI versions:
[  1348.168] X.Org ANSI C Emulation: 0.4
[  1348.168] X.Org Video Driver: 25.2
[  1348.168] X.Org XInput driver : 24.4
[  1348.168] X.Org Server Extension : 10.0
[  1348.169] (++) using VT number 2

[  1348.170] (EE) systemd-logind: failed to get session: PID 14045 does not belong to any known session
[  1348.171] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1348.171] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[  1348.174] (--) PCI:*(0@0:2:0) 8086:1916:17aa:222c rev 7, Mem @ 0xf0000000/16777216, 0xe0000000/268435456, I/O @ 0x0000e000/64, BIOS @ 0x????????/131072
[  1348.174] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[  1348.174] (II) LoadModule: "glx"
[  1348.174] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1348.175] (II) Module glx: vendor="X.Org Foundation"
[  1348.175] compiled for 1.21.1.8, module version = 1.0.0
[  1348.175] ABI class: X.Org Server Extension, version 10.0
[  1348.175] (==) Matched intel as autoconfigured driver 0
[  1348.175] (==) Matched modesetting as autoconfigured driver 1
[  1348.175] (==) Matched fbdev as autoconfigured driver 2
[  1348.175] (==) Matched vesa as autoconfigured driver 3
[  1348.175] (==) Assigned the driver to the xf86ConfigLayout
[  1348.175] (II) LoadModule: "intel"
[  1348.175] (WW) Warning, couldn't open module intel
[  1348.175] (EE) Failed to load module "intel" (module does not exist, 0)
[  1348.175] (II) LoadModule: "modesetting"
[  1348.175] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1348.176] (II) Module modesetting: vendor="X.Org Foundation"
[  1348.176] compiled for 1.21.1.8, module version = 1.21.1
[  1348.176] Module class: X.Org Video Driver
[  1348.176] ABI class: X.Org Video Driver, version 25.2
[  1348.176] (II) LoadModule: "fbdev"
[  1348.176] (WW) Warning, couldn't open module fbdev
[  1348.176] (EE) Failed to load module "fbdev" (module does not exist, 0)
[  1348.176] (II) LoadModule: "vesa"
[  1348.176] (WW) Warning, couldn't open module vesa
[  1348.176] (EE) Failed to load module "vesa" (module does not exist, 0)
[  1348.176] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1348.177] (EE) open /dev/dri/card0: Permission denied
[  1348.177] (WW) Falling back to old probe method for modesetting
[  1348.177] (EE) open /dev/dri/card0: Permission denied
[  1348.177] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[  1348.177] (EE) Screen 0 deleted because of no matching config section.
[  1348.177] (II) UnloadModule: "modesetting"
[  1348.177] (EE) Device(s) detected, but none match those in the config file.
[  1348.177] (EE)
Fatal server error:
[  1348.177] (EE) no screens found(EE)
[  1348.177] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
[  1348.177] (EE) Please also check the log file at "/home/slick_57/.local/share/xorg/Xorg.0.log" for additional information.
[  1348.177] (EE)
[  1348.220] (EE) Server terminated with error (1). Closing log file.


 

Re: Back with more Xorg

Reply #1
For some context: xorg was working fine until I tried to install splashtop-streamer via yay… not sure how that managed to break things yet.

At least you can now use your hardware remotely.

Why else did you build and install the package?
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: Back with more Xorg

Reply #2
For some context: xorg was working fine until I tried to install splashtop-streamer via yay… not sure how that managed to break things yet.

At least you can now use your hardware remotely.

Why else did you build and install the package?


I cannot use the hardware remotely

I attempted to build and install - but the installer kept erroring out on some packages

If I would have seen all the systemd dependencies, I would have just not touched the repo

Re: Back with more Xorg

Reply #3
You could try looking in /var/log/pacman.log for a record of package changes when splashtop-streamer was installed, and revert them back to how it was before. If it did some other freestyle config outside of this, then you would probably have to deduce it from reading the PKGBUILD and package source and documentation..

Re: Back with more Xorg

Reply #4
You could try looking in /var/log/pacman.log for a record of package changes when splashtop-streamer was installed, and revert them back to how it was before. If it did some other freestyle config outside of this, then you would probably have to deduce it from reading the PKGBUILD and package source and documentation..

Thanks for the pointer, I probably wont get to checking this out until this weekend

Hoping that it is Case#1 vs Case#2, as the second way sounds like a much larger headache.

Thanks!


Re: Back with more Xorg

Reply #6
I have attached logs too from the day I borked everything, and it shows some of the Pac-Man -R’s I tried to run as well…

If anything is noticable please let me know; I don’t know exactly what to look for but I don’t know much else of what to try.

Re: Back with more Xorg

Reply #7
You could try looking in /var/log/pacman.log for a record of package changes when splashtop-streamer was installed, and revert them back to how it was before. If it did some other freestyle config outside of this, then you would probably have to deduce it from reading the PKGBUILD and package source and documentation..


Does yay not produce its own logs or are they linked to pacman logs…? I thought that yay basically pulled repos from aur and that was it…? Apologies for my ignorance I just thought I had understood this already I guess…

Re: Back with more Xorg

Reply #8
So…. Odd change in behavior… and I’m not sure why… x will now start but I am getting no response once I get into my desktop… dwm and dwm-blocks seem to load but nothing else is responding…