Discussion:
can't run X: UEFI Microsoft scam
(too old to reply)
David Chmelik
2024-05-12 05:10:39 UTC
Permalink
I have an Intel NUC13ANKi7 which won't run X (tried 1280x1024 and now
1920x1080). It has 'VGA compatible controller: Intel Corporation Raptor
Lake-P [Iris Xe Graphics] (rev 04)'. The main line from Xorg.log (below)
is 'vesa: Refusing to run on UEFI'. Is there any option that currently
works other than waiting for new Linux kernel Intel display drivers?

X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[ 202.033] Build Operating System: Slackware 15.0 Slackware Linux
Project
[ 202.033] Current Operating System: Linux 5.15.145 #1 SMP PREEMPT Sun
Dec 24 00:07:06 CST 2023 x86_64
[ 202.033] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-huge-5.15.145
root=UUID=ea3790d9-3fe6-4682-bb7e-6b0114e462f6 ro nomodeset hugepagesz=1G
hugepages=3
[ 202.033] Build Date: 03 April 2024 05:19:08PM
[ 202.033]
[ 202.033] Current version of pixman: 0.40.0
[ 202.033] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 202.033] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 202.033] (==) Log file: "/var/log/Xorg.0.log", Time: Sat May 11
21:27:08 2024
[ 202.034] (==) Using system config directory "/usr/share/X11/
xorg.conf.d"
[ 202.034] (==) No Layout section. Using the first Screen section.
[ 202.034] (==) No screen section available. Using defaults.
[ 202.034] (**) |-->Screen "Default Screen Section" (0)
[ 202.034] (**) | |-->Monitor "<default monitor>"
[ 202.034] (==) No monitor specified for screen "Default Screen
Section".
Using a default monitor configuration.
[ 202.034] (==) Automatically adding devices
[ 202.034] (==) Automatically enabling devices
[ 202.034] (==) Automatically adding GPU devices
[ 202.034] (==) Automatically binding GPU devices
[ 202.034] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 202.034] (WW) The directory "/usr/share/fonts/local" does not exist.
[ 202.034] Entry deleted from font path.
[ 202.034] (WW) The directory "/usr/share/fonts/CID" does not exist.
[ 202.034] Entry deleted from font path.
[ 202.034] (==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/TTF,
/usr/share/fonts/OTF,
/usr/share/fonts/Type1,
/usr/share/fonts/75dpi/:unscaled,
/usr/share/fonts/100dpi/:unscaled,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi,
/usr/share/fonts/cyrillic
[ 202.034] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 202.034] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[ 202.034] (II) Loader magic: 0x61ac80
[ 202.034] (II) Module ABI versions:
[ 202.034] X.Org ANSI C Emulation: 0.4
[ 202.034] X.Org Video Driver: 24.1
[ 202.034] X.Org XInput driver : 24.1
[ 202.034] X.Org Server Extension : 10.0
[ 202.034] (--) PCI:*(***@0:2:0) 8086:a7a0:8086:3037 rev 4, Mem @
0x6123000000/16777216, 0x4000000000/134217728, I/O @ 0x00003000/64, BIOS @
0x????????/131072
[ 202.034] (II) Open ACPI successful (/var/run/acpid.socket)
[ 202.034] (II) LoadModule: "glx"
[ 202.034] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 202.035] (II) Module glx: vendor="X.Org Foundation"
[ 202.035] compiled for 1.20.14, module version = 1.0.0
[ 202.035] ABI class: X.Org Server Extension, version 10.0
[ 202.035] (==) Matched modesetting as autoconfigured driver 0
[ 202.035] (==) Matched fbdev as autoconfigured driver 1
[ 202.035] (==) Matched vesa as autoconfigured driver 2
[ 202.035] (==) Assigned the driver to the xf86ConfigLayout
[ 202.035] (II) LoadModule: "modesetting"
[ 202.035] (II) Loading /usr/lib64/xorg/modules/drivers/
modesetting_drv.so
[ 202.035] (II) Module modesetting: vendor="X.Org Foundation"
[ 202.035] compiled for 1.20.14, module version = 1.20.14
[ 202.035] Module class: X.Org Video Driver
[ 202.035] ABI class: X.Org Video Driver, version 24.1
[ 202.035] (II) LoadModule: "fbdev"
[ 202.035] (WW) Warning, couldn't open module fbdev
[ 202.035] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 202.035] (II) LoadModule: "vesa"
[ 202.035] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 202.035] (II) Module vesa: vendor="X.Org Foundation"
[ 202.035] compiled for 1.20.10, module version = 2.5.0
[ 202.035] Module class: X.Org Video Driver
[ 202.035] ABI class: X.Org Video Driver, version 24.1
[ 202.035] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 202.035] (II) VESA: driver for VESA chipsets: vesa
[ 202.035] (++) using VT number 1

[ 202.035] (EE) open /dev/dri/card0: No such file or directory
[ 202.035] (WW) Falling back to old probe method for modesetting
[ 202.035] (EE) open /dev/dri/card0: No such file or directory
[ 202.035] vesa: Refusing to run on UEFI
[ 202.035] (EE) Screen 0 deleted because of no matching config section.
[ 202.035] (II) UnloadModule: "modesetting"
[ 202.035] (EE) Device(s) detected, but none match those in the config
file.
[ 202.035] (EE)
Fatal server error:
[ 202.035] (EE) no screens found(EE)
[ 202.035] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 202.035] (EE) Please also check the log file at "/var/log/Xorg.0.log"
for additional information.
[ 202.035] (EE)
[ 202.036] (EE) Server terminated with error (1). Closing log file.
David Chmelik
2024-05-12 09:30:12 UTC
Permalink
Post by David Chmelik
I have an Intel NUC13ANKi7 which won't run X (tried 1280x1024 and now
1920x1080). It has 'VGA compatible controller: Intel Corporation Raptor
Lake-P [Iris Xe Graphics] (rev 04)'. The main line from Xorg.log
(below) is 'vesa: Refusing to run on UEFI'. Is there any option that
currently works other than waiting for new Linux kernel Intel display
drivers?
After posting the above I learned I can use Slackware-current kernel in
Slackware-stable and the newer video mode works (would prefer the older
one) though I'm not 100% sure it's okay to run these on Slackware-stable?
Post by David Chmelik
[Xorg.log]
W. Greenhouse
2024-05-12 11:25:09 UTC
Permalink
Post by David Chmelik
Post by David Chmelik
I have an Intel NUC13ANKi7 which won't run X (tried 1280x1024 and now
1920x1080). It has 'VGA compatible controller: Intel Corporation Raptor
Lake-P [Iris Xe Graphics] (rev 04)'. The main line from Xorg.log
(below) is 'vesa: Refusing to run on UEFI'. Is there any option that
currently works other than waiting for new Linux kernel Intel display
drivers?
After posting the above I learned I can use Slackware-current kernel in
Slackware-stable and the newer video mode works (would prefer the older
one) though I'm not 100% sure it's okay to run these on Slackware-stable?
Post by David Chmelik
[Xorg.log]
It's fine
gaussianblue
2024-05-12 09:47:45 UTC
Permalink
Post by David Chmelik
I have an Intel NUC13ANKi7 which won't run X (tried 1280x1024 and now
You could already upgrade your kernel. 5 releases available are newer
than your 5.15.145 . 6.9-rc7, 6.8.9, 6.6.30, 6.1.90 and 5.15.158 are
available.

https://www.kernel.org
Marco Moock
2024-05-12 17:29:39 UTC
Permalink
Post by David Chmelik
I have an Intel NUC13ANKi7 which won't run X (tried 1280x1024 and now
1920x1080). It has 'VGA compatible controller: Intel Corporation
Raptor Lake-P [Iris Xe Graphics] (rev 04)'. The main line from
Xorg.log (below) is 'vesa: Refusing to run on UEFI'. Is there any
option that currently works other than waiting for new Linux kernel
Intel display drivers?
VESA is a standardized video mode for BIOS systems.
UEFI is normal since more than 10 years ans CSM (that give old BIOS
functionality) isn't available on most new machines anymore.
UEFI uses GOP.
Although, to use all features (even resolutions) of your graphics chip,
you need the proper driver.

This isn't Microsoft´s liability - these are standards.


Upgrade to a current kernel and test there.
--
kind regards
Marco

Send spam to ***@cartoonies.org
Sylvain Robitaille
2024-05-14 13:23:36 UTC
Permalink
I have an Intel NUC13ANKi7 which won't run X ... The main line from
Xorg.log (below) is 'vesa: Refusing to run on UEFI'.
I would be inclined to suggest that your problem is more fundamental
than it might appear. These are the lines that I would be looking more
[ 202.035] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 202.035] (EE) open /dev/dri/card0: No such file or directory
[ 202.035] (EE) open /dev/dri/card0: No such file or directory
[ 202.035] (EE) Screen 0 deleted because of no matching config section.
[ 202.035] (EE) Device(s) detected, but none match those in the config
Later messages, though, suggest that you found a way to deal with this
and move on, so if the above isn't helpful, I apologize.
--
----------------------------------------------------------------------
Sylvain Robitaille ***@therockgarden.ca
----------------------------------------------------------------------
Loading...