Re: F24 : X won't start on SKL xeon : how to force FB ?
On 12/10/2016 11:24 AM, sean darcy wrote:
The intel driver doesn't detect P530 graphics on skylake xeon
E3-1245 :
[ 97799.240] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35,
Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 97799.240] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 97799.240] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 97799.240] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics:
5200, 6200, P6300
[ 97799.385] (EE) No devices detected.
Can I force X to start with another device ? VGA ? Frame buffer ?
sean
So I tried using the VESA driver:
Section "Device"
Identifier "Intel P530"
Driver "vesa"
EndSection
But that didn't work because the P530 was bound to the i915 kernel driver:
[119500.984] (II) VESA: driver for VESA chipsets: vesa
[119500.984] xf86EnableIOPorts: failed to set IOPL for I/O (Operation
not permitted)
[119500.984] vesa: Ignoring device with a bound kernel driver
[119500.984] (WW) Falling back to old probe method for vesa
[119500.984] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card
support
[119500.984] (EE) Screen 0 deleted because of no matching config section.
[119500.984] (II) UnloadModule: "vesa"
[119500.984] (EE) Device(s) detected, but none match those in the config
file.
Removed vesa conf, and tried X again. This time X defaulted to the
framebufer driver. But now it failed because of glamor !
[119689.245] (II) Loading sub module "fb"
[119689.245] (II) LoadModule: "fb"
[119689.245] (II) Loading /usr/lib64/xorg/modules/libfb.so
[119689.246] (II) Module fb: vendor="X.Org Foundation"
[119689.246] compiled for 1.18.4, module version = 1.0.0
[119689.246] ABI class: X.Org ANSI C Emulation, version 0.4
..................
[119689.247] (==) Depth 24 pixmap format is 32 bpp
[119689.248] (WW) glamor0: Failed to get GLSL version
[119689.248] (EE) modeset(0): Failed to initialize glamor at
ScreenInit() time.
[119689.248] (EE)
Fatal server error:
Any help appreciated.