On Thu, 20 Jun 2024, Michael Hennebry wrote:
On Thu, 20 Jun 2024, Roger Heflin wrote:
You would need to find the log file that starts up Xorg after you login it.
There are a number of things that can be set wrong and/or missing that
will cause Xorg to attempt to start and fail and exit like this.
F39 puts the log file here on my machine.
/var/log/Xorg.0.log
No go on F40.
I expect I need some incantation involving journalctl .
I looked yet again and this time I did find such a file.
'Tis different from the one under ~/.local
Here is the tail end.
[ 592.348] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c8
[ 592.352] (--) PCI:*(0@0:2:0) 8086:29d2:103c:281e rev 2, Mem @ 0xf0100000/524288, 0xe0000000/268435456, 0xf0000000/1048576, I/O @ 0x00001240/8, BIOS @ 0x????????/131072
[ 592.353] (II) LoadModule: "glx"
[ 592.353] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 592.355] (II) Module glx: vendor="X.Org Foundation"
[ 592.355] compiled for 1.20.14, module version = 1.0.0
[ 592.355] ABI class: X.Org Server Extension, version 10.0
[ 592.355] (==) Matched intel as autoconfigured driver 0
[ 592.355] (==) Matched modesetting as autoconfigured driver 1
[ 592.355] (==) Matched fbdev as autoconfigured driver 2
[ 592.355] (==) Matched vesa as autoconfigured driver 3
[ 592.355] (==) Assigned the driver to the xf86ConfigLayout
[ 592.355] (II) LoadModule: "intel"
[ 592.355] (WW) Warning, couldn't open module intel
[ 592.355] (EE) Failed to load module "intel" (module does not exist, 0)
[ 592.355] (II) LoadModule: "modesetting"
[ 592.356] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 592.356] (II) Module modesetting: vendor="X.Org Foundation"
[ 592.356] compiled for 1.20.14, module version = 1.20.14
[ 592.356] Module class: X.Org Video Driver
[ 592.356] ABI class: X.Org Video Driver, version 24.1
[ 592.356] (II) LoadModule: "fbdev"
[ 592.356] (WW) Warning, couldn't open module fbdev
[ 592.356] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 592.356] (II) LoadModule: "vesa"
[ 592.356] (WW) Warning, couldn't open module vesa
[ 592.356] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 592.356] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 592.356] (EE) open /dev/dri/card0: No such file or directory
[ 592.356] (WW) Falling back to old probe method for modesetting
[ 592.356] (EE) open /dev/dri/card0: No such file or directory
[ 592.357] (EE) Screen 0 deleted because of no matching config section.
[ 592.357] (II) UnloadModule: "modesetting"
[ 592.357] (EE) Device(s) detected, but none match those in the config file.
[ 592.357] (EE)
Fatal server error:
[ 592.357] (EE) no screens found(EE)
[ 592.357] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 592.357] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 592.357] (EE)
[ 592.359] (EE) Server terminated with error (1). Closing log file.
I note that Xorg could not find intel, fbdev or vesa,
all of which strike me as s trange.
--
Michael hennebry@xxxxxxxxxxxxxxxxxxxxxx
"SCSI is NOT magic. There are *fundamental technical
reasons* why it is necessary to sacrifice a young
goat to your SCSI chain now and then." -- John Woods
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
