abduct
Apprentice
Joined: 19 Mar 2015
Posts: 215
|
 Posted: Mon Aug 13, 2018 11:54 pm Post subject: New MESA error while updating |
 |
|
This is the first time I've seen this error from Mesa since it usually compiles fine.
The error is simple enough to understand and resolve, but my confusion comes from which entry to remove from my make.conf.
The error is "Problem encountered: Only one i915 provider can be built" which made me look at my make.conf:
| Code: | VIDEO_CARDS="intel i915 i965"
|
I am not sure which entries to remove since Mesa has never complained before.
Xorg loads the following drivers:
| Code: |
[ 49.670] (==) Matched intel as autoconfigured driver 0
[ 49.670] (==) Matched intel as autoconfigured driver 1
[ 49.670] (==) Matched modesetting as autoconfigured driver 2
[ 49.670] (==) Matched fbdev as autoconfigured driver 3
[ 49.670] (==) Matched vesa as autoconfigured driver 4
[ 49.670] (==) Assigned the driver to the xf86ConfigLayout
[ 49.670] (II) LoadModule: "intel"
[ 49.671] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 49.757] (II) Module intel: vendor="X.Org Foundation"
[ 49.757] compiled for 1.19.5, module version = 2.99.917
[ 49.757] Module class: X.Org Video Driver
[ 49.757] ABI class: X.Org Video Driver, version 23.0
[ 49.757] (II) LoadModule: "modesetting"
[ 49.758] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 49.767] (II) Module modesetting: vendor="X.Org Foundation"
[ 49.768] compiled for 1.19.5, module version = 1.19.5
[ 49.768] Module class: X.Org Video Driver
[ 49.768] ABI class: X.Org Video Driver, version 23.0
[ 49.768] (II) LoadModule: "fbdev"
[ 49.769] (WW) Warning, couldn't open module fbdev
[ 49.769] (II) UnloadModule: "fbdev"
[ 49.769] (II) Unloading fbdev
[ 49.769] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 49.769] (II) LoadModule: "vesa"
[ 49.770] (WW) Warning, couldn't open module vesa
[ 49.770] (II) UnloadModule: "vesa"
[ 49.770] (II) Unloading vesa
[ 49.770] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 49.770] (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
[ 49.772] (II) intel: Driver for Intel(R) HD Graphics
[ 49.772] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 49.772] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 49.772] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 49.772] (--) using VT number 7
[ 49.788] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20180308
[ 49.802] (WW) Falling back to old probe method for modesetting
[ 49.805] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000
[ 49.805] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx; using a maximum of 2 threads
[ 49.805] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
|
So from this I gather I can remove the i965 entry, but I am not sure about the intel entry...
If I recall I added the i965 entry some time ago when doing research on getting hardware acceleration support to work on my laptop top. I am not sure if this entry actually fixed the hardware acceleration or not, but it is currently in a working state.
Anyone have any input?
Thanks |
|
Kernel & Hardware
