Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: dspence on February 22, 2018, 12:50:41 PM
-
Hi all,
I'm having trouble getting Tiny Core 8 to work on a new machine that has an Intel Atom E3930 CPU, with integrated HD Graphics 500. lspci identifies the graphics as "Intel Corporation Device 5a85 (rev 0b)".
I want to run Xvesa on it, but it reports "Interrupt pointer (seg d0 off 20) doesn't point at ROM" four times, before reporting "Fatal server error: no screens found", followed by a segmentation fault.
I have also tried Xorg. I installed that with libva-intel-driver.tcz, xf86-video-intel.tcz, and also firmware-i915.tcz, and from /var/log/messages and /var/log/Xorg.0.log, it looked like it was working, but I only had a black screen.
Xvesa is really the one I want to have working, though.
Has anyone managed to get Tiny Core 8 to work with graphics on this chip? Any help would be appreciated.
Thanks.
-
You have a third option, framebuffer and Xfbdev. Please see the FAQ for samples of the vga= bootcode.
-
Thank you, curaga! Xfbdev works! It even seems fast on this hardware!
-
Just an update: I got Xorg to work and I've decided to continue with that, for reasons of performance and compatibility with other, older Atom CPUs with integrated graphics.
Thank you again!
-
Hi dspence
If it could help someone else with hardware similar to yours, maybe you could post some hints on what they need to do.
-
Hi Rich,
There was really no issue with Xorg on this hardware. There was a syntax error before the call to 'waitforX', caused by the automatic removal of three conditional calls to Xvesa with different screen resolutions.
I think that Xvesa won't run because this machine has UEFI with no Compatibility Support Module.
I did have an issue with Xorg on some older hardware, with Intel Atom N2600, Z530, and Z510 that looked like this in Xorg.0.log:
...
[ 39.219] (EE) Backtrace:
[ 39.219] (EE) 0: /usr/local/lib/xorg/Xorg (xorg_backtrace+0x43) [0x8141cef]
[ 39.219] (EE) 1: /usr/local/lib/xorg/Xorg (0x8048000+0x11ce65) [0x8164e65]
[ 39.219] (EE) 2: linux-gate.so.1 (__kernel_rt_sigreturn+0x0) [0xb772db40]
[ 39.219] (EE) 3: /usr/local/lib/dri/kms_swrast_dri.so (0xb6400000+0x788c5d) [0xb6b88c5d]
[ 39.219] (EE) 4: /usr/local/lib/dri/kms_swrast_dri.so (0xb6400000+0x7899b7) [0xb6b899b7]
[ 39.219] (EE) 5: /usr/local/lib/dri/kms_swrast_dri.so (0xb6400000+0x78d128) [0xb6b8d128]
[ 39.219] (EE) 6: /usr/local/lib/libgbm.so.1 (0xb7010000+0x2607) [0xb7012607]
[ 39.219] (EE) 7: /usr/local/lib/libgbm.so.1 (0xb7010000+0x26f0) [0xb70126f0]
[ 39.219] (EE) 8: /usr/local/lib/libgbm.so.1 (0xb7010000+0x3506) [0xb7013506]
[ 39.219] (EE) 9: /usr/local/lib/libgbm.so.1 (gbm_create_device+0x8c) [0xb701247c]
[ 39.219] (EE) 10: /usr/local/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x7f) [0xb703174e]
[ 39.219] (EE) 11: /usr/local/lib/xorg/modules/drivers/modesetting_drv.so (0xb7047000+0x9cbb) [0xb7050cbb]
[ 39.219] (EE) 12: /usr/local/lib/xorg/Xorg (InitOutput+0xd1f) [0x80e90fb]
[ 39.219] (EE) 13: /usr/local/lib/xorg/Xorg (0x8048000+0x1ff88) [0x8067f88]
[ 39.219] (EE) 14: /lib/libc.so.6 (__libc_start_main+0x157) [0xb72e423f]
[ 39.220] (EE) 15: /usr/local/lib/xorg/Xorg (0x8048000+0x20791) [0x8068791]
[ 39.220] (EE)
[ 39.220] (EE) Illegal instruction at address 0xb65313bb
[ 39.220] (EE)
Fatal server error:
[ 39.220] (EE) Caught signal 4 (Illegal instruction). Server aborting
...
This was solved by removing libva-intel-driver.tcz from onboot.lst. The Illegal Instruction seems to be coming from file /usr/local/lib/dri/kms_swrast_dri.so in the Xorg-7.7-3d.tcz extension.
-
as per the Xorg-7.7-3d info file:
*** minimum cpu pentium-m ***
-
Those Atoms are above pentium-m, so maybe another compiler/build process bug.
-
This could all be outdated info, but AFAICT the Xorg Intel driver does not appear to support the 500 series graphics chip used in many Atom based computers.
https://www.x.org/wiki/IntelGraphicsDriver/ (https://www.x.org/wiki/IntelGraphicsDriver/)
This apparently is the list of currently supported Intel graphics chips
https://www.x.org/wiki/IntelLaptopChips/ (https://www.x.org/wiki/IntelLaptopChips/)
On the positive side Intel has released a driver "Intel Embedded Graphic Driver" for linux which supports these graphics chipsets.... but i'm still looking for that.
-
Okay, there are still issues on the machine with the Intel Atom E3930 CPU with integrated HD Graphics 500. Overall it seems to work fine, but when I connected using x11vnc, opened a terminal (aterm) and scrolled, the image was corrupted.
After trying a bunch of different things (various arguments to x11vnc, a different VNC server, an older version of aterm) I then tried grabber.tcz to get a screen grab of what was displayed on the screen (as opposed to what I saw with VNC) and the same thing happened with grabber.
I have attached a couple of files to this message.
1. File camera.jpg is what I see on the screen.
2. File grabber.png is what is grabbed with the grabber program. This is the same as what appears when connected using x11vnc and x0vncserver.
Using the exact same software, this corruption does not happen when using older hardware with Atom N2600 or Z530.
So yeah, maybe the Xorg Intel driver doesn't fully support this chip yet. :-/
-
What happens with the xorg-server modesetting driver (i.e. don't load the intel driver)?
-
IIRC the same was seen in vmware, and there the user decided to use another terminal instead of aterm.
-
Hi Juanito,
So I removed xf86-video-intel.tcz from onboot.lst, and rebooted.
I ended up at "failed in waitforX".
The Xorg.0.log reads as follows:
[ 25.537]
X.Org X Server 1.19.5
Release Date: 2017-10-12
[ 25.537] X Protocol Version 11, Revision 0
[ 25.537] Build Operating System: Linux 4.8.17-tinycore i486
[ 25.537] Current Operating System: Linux test64.nitrex.com 4.8.17-tinycore #2017 SMP Sun Mar 5 15:49:22 UTC 2017 i686
[ 25.537] Kernel command line: BOOT_IMAGE=(hd0,gpt1)/tce/boot/vmlinuz syslog quiet waitusb=5 tce=sda1 nodhcp lang=en_US.utf8
[ 25.537] Build Date: 15 October 2017 11:14:52AM
[ 25.537]
[ 25.537] Current version of pixman: 0.34.0
[ 25.537] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 25.537] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 25.537] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 14 15:33:29 2018
[ 25.537] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
[ 25.537] (==) No Layout section. Using the first Screen section.
[ 25.537] (==) No screen section available. Using defaults.
[ 25.537] (**) |-->Screen "Default Screen Section" (0)
[ 25.537] (**) | |-->Monitor "<default monitor>"
[ 25.539] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 25.539] (==) Automatically adding devices
[ 25.539] (==) Automatically enabling devices
[ 25.539] (==) Automatically adding GPU devices
[ 25.539] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 25.539] (WW) The directory "/usr/local/lib/X11/fonts/OTF/" does not exist.
[ 25.539] Entry deleted from font path.
[ 25.539] (WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
[ 25.539] Entry deleted from font path.
[ 25.539] (==) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/
[ 25.539] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[ 25.539] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 25.539] (II) Loader magic: 0x81b7a80
[ 25.539] (II) Module ABI versions:
[ 25.539] X.Org ANSI C Emulation: 0.4
[ 25.539] X.Org Video Driver: 23.0
[ 25.539] X.Org XInput driver : 24.1
[ 25.539] X.Org Server Extension : 10.0
[ 25.666] (--) PCI:*(0:0:2:0) 8086:5a85:8086:2212 rev 11, Mem @ 0x90000000/16777216, 0x80000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[ 25.666] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 25.666] (II) LoadModule: "glx"
[ 25.667] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 25.686] (II) Module glx: vendor="X.Org Foundation"
[ 25.686] compiled for 1.19.5, module version = 1.0.0
[ 25.686] ABI class: X.Org Server Extension, version 10.0
[ 25.686] (==) Matched intel as autoconfigured driver 0
[ 25.686] (==) Matched modesetting as autoconfigured driver 1
[ 25.686] (==) Matched fbdev as autoconfigured driver 2
[ 25.686] (==) Matched vesa as autoconfigured driver 3
[ 25.686] (==) Assigned the driver to the xf86ConfigLayout
[ 25.686] (II) LoadModule: "intel"
[ 25.686] (WW) Warning, couldn't open module intel
[ 25.687] (II) UnloadModule: "intel"
[ 25.687] (II) Unloading intel
[ 25.687] (EE) Failed to load module "intel" (module does not exist, 0)
[ 25.687] (II) LoadModule: "modesetting"
[ 25.687] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 25.689] (II) Module modesetting: vendor="X.Org Foundation"
[ 25.689] compiled for 1.19.5, module version = 1.19.5
[ 25.689] Module class: X.Org Video Driver
[ 25.689] ABI class: X.Org Video Driver, version 23.0
[ 25.689] (II) LoadModule: "fbdev"
[ 25.690] (WW) Warning, couldn't open module fbdev
[ 25.690] (II) UnloadModule: "fbdev"
[ 25.690] (II) Unloading fbdev
[ 25.690] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 25.690] (II) LoadModule: "vesa"
[ 25.690] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 25.690] (II) Module vesa: vendor="X.Org Foundation"
[ 25.690] compiled for 1.19.1, module version = 2.3.4
[ 25.690] Module class: X.Org Video Driver
[ 25.690] ABI class: X.Org Video Driver, version 23.0
[ 25.690] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 25.690] (II) VESA: driver for VESA chipsets: vesa
[ 25.690] (--) using VT number 2
[ 25.694] (EE) open /dev/dri/card0: No such file or directory
[ 25.694] (WW) Falling back to old probe method for modesetting
[ 25.694] (EE) open /dev/dri/card0: No such file or directory
[ 25.694] (EE) Screen 0 deleted because of no matching config section.
[ 25.694] (II) UnloadModule: "modesetting"
[ 25.694] (II) Loading sub module "vbe"
[ 25.694] (II) LoadModule: "vbe"
[ 25.694] (II) Loading /usr/local/lib/xorg/modules/libvbe.so
[ 25.696] (II) Module vbe: vendor="X.Org Foundation"
[ 25.696] compiled for 1.19.5, module version = 1.1.0
[ 25.696] ABI class: X.Org Video Driver, version 23.0
[ 25.696] (II) Loading sub module "int10"
[ 25.696] (II) LoadModule: "int10"
[ 25.696] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[ 25.700] (II) Module int10: vendor="X.Org Foundation"
[ 25.700] compiled for 1.19.5, module version = 1.0.0
[ 25.700] ABI class: X.Org Video Driver, version 23.0
[ 25.700] (II) VESA(0): initializing int10
[ 25.701] (EE) VESA(0): V_BIOS address 0xd00 out of range
[ 25.701] (II) UnloadModule: "vesa"
[ 25.701] (II) UnloadSubModule: "int10"
[ 25.701] (II) Unloading int10
[ 25.701] (II) UnloadSubModule: "vbe"
[ 25.701] (II) Unloading vbe
[ 25.701] (EE) Screen(s) found, but none have a usable configuration.
[ 25.701] (EE)
Fatal server error:
[ 25.701] (EE) no screens found(EE)
[ 25.701] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 25.701] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 25.701] (EE)
[ 25.707] (EE) Server terminated with error (1). Closing log file.
[EDIT]: Added code tags. Rich
-
Hi curaga,
I will try another terminal and post the results. Thanks for the suggestion.
Edit:
So I tried lxterminal.tcz. It does not show the same bad behaviour as aterm, but I can't use it for other reasons.
The gnome-terminal.tcz extension also doesn't display the bad behaviour as aterm. It has other bad points (and btw it is missing dependency libffi5.tcz, but even after providing that it won't launch from the icon on wbar. I had to launch it using sudo, from aterm.)
I will look for other terminals to try.
-
Hi dspence
I will look for other terminals to try.
Maybe rxvt?
-
was graphics-KERNEL loaded?
-
The gnome-terminal.tcz extension also doesn't display the bad behaviour as aterm. It has other bad points (and btw it is missing dependency libffi5.tcz, but even after providing that it won't launch from the icon on wbar. I had to launch it using sudo, from aterm.)
gnome-terminal and vte-gtk3 recompiled and posted - thanks for reporting this
-
[juanito] my apologies, I modified this post rather than quoting it and can't get it back :(
-
Juanito, thanks! No, graphics-KERNEL was not loaded! I have added it to onboot.lst, and it works, and there is no visual corruption now with aterm!
From Xorg.0.log:
...
[ 25.614] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 25.739] (--) PCI:*(0:0:2:0) 8086:5a85:8086:2212 rev 11, Mem @ 0x90000000/16777216, 0x80000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[ 25.739] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 25.740] (II) LoadModule: "glx"
[ 25.741] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 25.760] (II) Module glx: vendor="X.Org Foundation"
[ 25.760] compiled for 1.19.5, module version = 1.0.0
[ 25.760] ABI class: X.Org Server Extension, version 10.0
[ 25.761] (==) Matched intel as autoconfigured driver 0
[ 25.761] (==) Matched intel as autoconfigured driver 1
[ 25.761] (==) Matched modesetting as autoconfigured driver 2
[ 25.761] (==) Matched fbdev as autoconfigured driver 3
[ 25.761] (==) Matched vesa as autoconfigured driver 4
[ 25.761] (==) Assigned the driver to the xf86ConfigLayout
[ 25.761] (II) LoadModule: "intel"
[ 25.761] (WW) Warning, couldn't open module intel
[ 25.761] (II) UnloadModule: "intel"
[ 25.761] (II) Unloading intel
[ 25.761] (EE) Failed to load module "intel" (module does not exist, 0)
[ 25.761] (II) LoadModule: "modesetting"
[ 25.761] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 25.764] (II) Module modesetting: vendor="X.Org Foundation"
[ 25.764] compiled for 1.19.5, module version = 1.19.5
[ 25.764] Module class: X.Org Video Driver
[ 25.764] ABI class: X.Org Video Driver, version 23.0
[ 25.764] (II) LoadModule: "fbdev"
[ 25.764] (WW) Warning, couldn't open module fbdev
[ 25.764] (II) UnloadModule: "fbdev"
[ 25.764] (II) Unloading fbdev
[ 25.764] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 25.764] (II) LoadModule: "vesa"
[ 25.764] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[ 25.765] (II) Module vesa: vendor="X.Org Foundation"
[ 25.765] compiled for 1.19.1, module version = 2.3.4
[ 25.765] Module class: X.Org Video Driver
[ 25.765] ABI class: X.Org Video Driver, version 23.0
[ 25.765] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 25.765] (II) VESA: driver for VESA chipsets: vesa
[ 25.765] (--) using VT number 2
[ 25.799] (II) modeset(0): using drv /dev/dri/card0
[ 25.799] (WW) Falling back to old probe method for vesa
[ 25.799] (II) modeset(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 25.799] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[ 25.799] (==) modeset(0): RGB weight 888
[ 25.799] (==) modeset(0): Default visual is TrueColor
[ 25.799] (II) Loading sub module "glamoregl"
[ 25.799] (II) LoadModule: "glamoregl"
[ 25.800] (II) Loading /usr/local/lib/xorg/modules/libglamoregl.so
[ 25.842] (II) Module glamoregl: vendor="X.Org Foundation"
[ 25.842] compiled for 1.19.5, module version = 1.0.0
[ 25.842] ABI class: X.Org ANSI C Emulation, version 0.4
[ 25.842] (II) glamor: OpenGL accelerated X.org driver based.
[ 25.843] couldn't get display device
[ 25.843] (EE) modeset(0): glamor initialization failed
[ 25.843] (II) modeset(0): ShadowFB: preferred YES, enabled YES
[ 25.843] (II) modeset(0): Double-buffered shadow updates: off
[ 25.844] (II) modeset(0): Output eDP-1 has no monitor section
[ 25.844] (II) modeset(0): Output DP-1 has no monitor section
[ 25.845] (II) modeset(0): Output HDMI-1 has no monitor section
[ 25.845] (II) modeset(0): Output DP-2 has no monitor section
[ 26.057] (II) modeset(0): Output HDMI-2 has no monitor section
[ 26.059] (II) modeset(0): EDID for output eDP-1
[ 26.059] (II) modeset(0): Printing probed modes for output eDP-1
[ 26.059] (II) modeset(0): Modeline "640x480"x60.0 25.18 640 656 752 800 480 492 494 525 -hsync -vsync (31.5 kHz P)
[ 26.059] (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[ 26.059] (II) modeset(0): Modeline "512x384"x120.0 32.50 512 524 592 672 384 385 388 403 doublescan -hsync -vsync (48.4 kHz d)
[ 26.059] (II) modeset(0): Modeline "400x300"x120.6 20.00 400 420 484 528 300 300 302 314 doublescan +hsync +vsync (37.9 kHz d)
[ 26.059] (II) modeset(0): Modeline "400x300"x112.7 18.00 400 412 448 512 300 300 301 312 doublescan +hsync +vsync (35.2 kHz d)
[ 26.059] (II) modeset(0): Modeline "320x240"x120.1 12.59 320 328 376 400 240 245 246 262 doublescan -hsync -vsync (31.5 kHz d)
[ 26.059] (II) modeset(0): EDID for output DP-1
[ 26.060] (II) modeset(0): EDID for output HDMI-1
[ 26.060] (II) modeset(0): EDID for output DP-2
[ 26.274] (II) modeset(0): EDID for output HDMI-2
[ 26.274] (II) modeset(0): Output eDP-1 connected
[ 26.274] (II) modeset(0): Output DP-1 disconnected
[ 26.274] (II) modeset(0): Output HDMI-1 disconnected
[ 26.274] (II) modeset(0): Output DP-2 disconnected
[ 26.274] (II) modeset(0): Output HDMI-2 disconnected
[ 26.274] (II) modeset(0): Using exact sizes for initial modes
[ 26.274] (II) modeset(0): Output eDP-1 using initial mode 640x480 +0+0
[ 26.274] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[ 26.274] (++) modeset(0): DPI set to (96, 96)
[ 26.274] (II) Loading sub module "fb"
[ 26.274] (II) LoadModule: "fb"
[ 26.274] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[ 26.283] (II) Module fb: vendor="X.Org Foundation"
[ 26.283] compiled for 1.19.5, module version = 1.0.0
[ 26.283] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.283] (II) Loading sub module "shadow"
[ 26.283] (II) LoadModule: "shadow"
[ 26.284] (II) Loading /usr/local/lib/xorg/modules/libshadow.so
[ 26.285] (II) Module shadow: vendor="X.Org Foundation"
[ 26.285] compiled for 1.19.5, module version = 1.1.0
[ 26.285] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.285] (II) UnloadModule: "vesa"
[ 26.285] (II) Unloading vesa
[ 26.285] (==) Depth 24 pixmap format is 32 bpp
[ 26.289] (==) modeset(0): Backing store enabled
[ 26.289] (==) modeset(0): Silken mouse enabled
[ 26.289] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 26.290] (==) modeset(0): DPMS enabled
[ 26.290] (--) RandR disabled
[ 26.290] (II) AIGLX: Screen 0 is not DRI2 capable
[ 26.290] (EE) AIGLX: reverting to software rendering
[ 26.290] (EE) AIGLX error: dlopen of /usr/local/lib/dri/swrast_dri.so failed (/usr/local/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[ 26.290] (EE) GLX: could not load software renderer
[ 26.290] (II) GLX: no usable GL providers found for screen 0
[ 26.291] (II) modeset(0): Damage tracking initialized
[ 26.291] (II) modeset(0): Setting screen physical size to 169 x 126
...
The performance seems good on this chip.
I tried the same on the older Atoms that I have. Performance is not good on those, so I think I'll use xf86-video-intel on those, and the modesetting driver on this one.
[EDIT] Added code tags. Rich
-
Hi dspence
Instead of using tt tags please use code tags. This will still preserve spacing as it too uses a monotype font in addition to
adding scroll bars for longer printouts.
-
Rich: Sorry! I'll try to remember to use code tags in future.
I tried rxvt, and it had the same problem as aterm. I went back all the way to the Tiny Core 4 extension repository and got xterm.tcz, and it was mostly okay, so there's a chance I would have used that one.
pq5190362: Thanks for the info! It looks like the modesetting driver is easier than that to get running, though. Juanito's solution of not loading xf86-video-intel, but loading graphics-KERNEL, worked for me, without needing configuration files.
-
It looks like the modesetting driver is easier than that to get running, though. Juanito's solution of not loading xf86-video-intel, but loading graphics-KERNEL, worked for me, without needing configuration files.
There is no "not loading xf86-video-intel BUT loading graphics-KERNEL".
The reason xf86-video-intel did not work very likely is due to you not having installed graphics-KERNEL.
So, since you have installed graphics-KERNEL now, you might also want to re-install xf86-video-intel and compare it with xf86-video-modesetting.
And, yes, not installing xf86-video-intel results in xf86-video-modesetting automatically loading since it is built into xorg-server. The configuration file allows you to have xf86-video-intel installed but forcing xf86-video-modesetting to load instead of xf86-video-intel (i.e. using xf86-video-modesetting without uninstalling xf86-video-intel).
-
pq5190362,
No, graphics-KERNEL is a dependency of xf86-video-intel. It was there, it was just not loaded anymore after removing xf86-video-intel from onboot.lst. I added it on its own, and now the modesetting driver works.
-
Then maybe graphics-KERNEL should be made a dependency of Xorg-7.7-3d or even xorg-server, since xf86-video-modesetting is built into xorg-server.
-
It is a relatively big file, and many Xorg users do not need to load it. Generally optional dependencies are listed in info files.
-
Xorg-7.7 info file modified accordingly