[SOLVED] Intel NUC13ANKi7 forces UEFI so can't startx
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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?
Code:
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@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.
Raptor lake was released more than a year after the kernel 5.15, it probably isn't supported properly. Try updating i915 module.
Couldn't find basic information on it on intel.com... do you think building latest 5.15.n kernel with Slackware's source code kernel build scripts would work or I should switch to 6.n for these?
I think in your other SOLVED thread you came to the conclusion that the newer drivers of Slackware-current (live) worked but the monitor didn't. Did you try another monitor? It could be helpful to see the Xorg.0.log file from slackware-current live.
I think in your other SOLVED thread you came to the conclusion that the newer drivers of Slackware-current (live) worked but the monitor didn't. Did you try another monitor? It could be helpful to see the Xorg.0.log file from slackware-current live.
I shouldn't have marked that solved, and it may have been Slackware-stable-live, but I don't know why I said the drivers work when the monitor didn't... I stated in the original post of this thread that I tried a different resolution--different monitor (obviously). Which kernel should I build then?
I don't know whether you're still using my slackscan/slackup but you can easily configure it to borrow the latest kernels from slackware-current.
edit the scan file in your slackscan profile directory to look something like this:
Code:
# /etc/slackscan/local/scan
#
# List of locations where 'slackscan' can recursively find
# slackware packages.
#
# Each line may contain the path of a local directory, or
# the URL of a remote CHECKSUMS.md5 file.
#
# Local hotfixes for issues unresolved upstream:
/local/slackware/packages64/15.0/hotfix
# Customised packages:
/local/slackware/packages64/15.0/custom
# slackware current kernel files (see also filter list):
https://slackware.uk/slackware/slackware64-current/slackware64/CHECKSUMS.md5
# slackware64-15.0 patches:
/local/slackware/mirror/slackware64-15.0/patches/packages
/local/slackware/mirror/slackware64-15.0/slackware64
# Local directory of additional packages:
/local/slackware/packages64/15.0/misc
And then edit your filter file to look like this:
Code:
# /etc/slackup/local/filter
# Format: basic-regex
#
# This file is the 'filter' file for the 'slackup' utility.
# Package files not matching one of the following patterns will
# be excluded from install and upgrade actions.
#
# Patterns passed on the command line will be appended to those
# in this file when processing the filters at run-time.
#
# Patterns in the blacklist file are processed after these
# filters are applied.
#
# Slackware-current kernel files:
/slackware64-current/slackware64/a/kernel-generic
/slackware64-current/slackware64/a/kernel-modules
/slackware64-current/slackware64/a/kernel-firmware
# Slackware-15.0:
/slackware64-15.0/patches/packages/
/slackware64-15.0/slackware64/
# Include local packages dir:
/local/slackware/packages64/15.0/
(obviously these are tailored to my system, but you get the idea)
CAUTION: Don't forget the filter entries or you'll end up running CURRENT!
This way it will automatically prefer the kernel/modules/firmware from current but get all the other packages from my usual locations.
Try the kernels from -current. No need to build [...]
OpenGL won't work without other components of the graphics stack, so don't run sddm. Try xdm and fvwm.
Thanks! Those work but I thought you shouldn't use Slackware-current packages on Slackware-stable... kernels are an exception? I don't use KDE anymore anyway (Just some KDE programs).
I shouldn't have marked that solved, and it may have been Slackware-stable-live, but I don't know why I said the drivers work when the monitor didn't... I stated in the original post of this thread that I tried a different resolution--different monitor (obviously). Which kernel should I build then?
Those Live ISOs you got linked to in the other thread are booting Slackware-current according to their URL. Your posts in that other thread there shows that Slackware-current supports your NUC just fine. However you attach a 20-year old LCD monitor to this brand new machine, of which you state (in that same thread) that your RasPi device was not able to draw anything on that monitor.
Safe to say that the problem is that old monitor. Either find a newer one, or look for ways to force a refresh rate and/or resolution which is supported by the monitor because apparently X.Org is not able to find one on its own. Look at xrandr for instance.
To finish, you may want to change the title of this topic. Your "UEFI Microsoft scam" is just insulting for no good reason and has nothing to do with your actual problem (trying to get an el-cheapo stone age monitor to work with present-day computer hardware).
It does no good to your own standing because it shows a lack of understanding. I assume you were thinking about SecureBoot when you wrote it.
The EFI specification was created by Intel, not Microsoft. It was superseded by the UEFI specification which is an open standard, maintained by a consortium of companies, not by Microsoft. It has an open source reference implementation, TianoCore EDKII, which is for instance used by QEMU to offer a UEFI boot environment to its virtual guests.
Yeah, the kernels are different as they don't rely on glibc. That said, I wouldn't advise installing kernel-headers from current as they are supposed to be tied to the glibc version.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Intel NUC13ANKi7 forces UEFI so can't startx
