xorg Digest, Vol 204, Issue 15
zarniwhoop at ntlworld.com
Fri Jul 29 01:11:20 UTC 2022
On Thu, Jul 28, 2022 at 06:35:16PM +0200, Ahsan wrote:
> Hi Ken,
> Thanks for your input. Please see my comments inline below.
> > Message: 3
> > Date: Wed, 27 Jul 2022 21:49:30 +0100
> > From: Ken Moffat <zarniwhoop at ntlworld.com>
> > To: xorg at lists.x.org
> > Subject: Re: Xserver Error loading intel_drv.so undefined
> > symbol:I810InitMC
> > Message-ID: <YuGk2inKZGc/w484 at llamedos.localdomain>
> > Content-Type: text/plain; charset=utf-8
> > On Wed, Jul 27, 2022 at 08:47:58PM +0200, Ahsan wrote:
> > > Hello,
> > >
> > Hi Ahsan,
> > I doubt I can help directly, but a few comments (so, I'm snipping a
> > lot of your details)
> > TLDR: Do you really need the intel driver ?
> No, there is no hard requirement for this, unfortunately, this error stops
> loading the intel driver module properly hence a target machine ends up with
> incorrect resolution. The idea is to avoid this error so that loading of
> intel module (for Intel HD 630) works fine.
A quick google suggests HD630 is a Kaby Lake, so fairly recent. At
one time I think there was a linux kernel config option to enable
newer intel video chipsets, but I can't find any details and I
expect that option is long gone.
Looking at gentoo, Skylake and later need video firmware
(i915/skl_dmc_ver1_27.bin on my Skylake) but I guess if that was
missing you would not get any video output from X.
When you say "incorrect resolution", what results and what should it
be ? I seem to recall that in some odd cases peopel have had to
override the EDID to get proper resolution, but I've never needed
that and don't know where to look.
> In a previous version of BR, the combination of intel drivers and xorg
> works fine, however, in a new BR release, the combination is broken and
> I end up with the error above. So far, I've found that the intel video
> driver version is same for both xorg 1.20.xx and 1.21.2 (or 21.1.2).
> I'm trying to pinpoint what's been changed in 21.1.x that causes i810InitMC
> error but so far I've had no luck.
> I tried --enable-kms-only(the other flag is already enabled) but no luck.
> Could you please point me to the repo link. The last version on xorg's
> website (https://xorg.freedesktop.org/releases/individual/driver/)
> seems to be 2.99.917. Perhaps, I'm looking at an old link?
I don't have a link. Someone took a snapshot, presumably on
20210222 or for a commit from that date, then tarred it up.
Unfortunately, not everyone in BLFS thinks it is important to put
those sort of details in a snapshot.
the last commit was on 20210115 so I guess that soemone noticed that
was an important commit 'sna: Always validate userptr upon creation'
and cloned it.
Given what Felix said about i810, I find it odd that anything in the
recent video stack references it. Oh, I see it is in
Using the following autogen options:
./autogen.sh --prefix=/usr \
reports at the end:
xf86-video-intel 2.99.917 will be compiled with:
Xorg Video ABI version: 25.2 (xorg-server-21.1.3)
pixman version: pixman-1-0.40.0
Acceleration backends: none *sna uxa
Additional debugging support? none
Support for Kernel Mode Setting? yes
Support for legacy User Mode Setting (for i810)? no
Support for Direct Rendering Infrastructure: *DRI2 DRI3 Present
Support for Xv motion compensation (XvMC and libXvMC): yes
Support for display hotplug notifications (udev): yes
Build additional tools and utilities? xf86-video-intel-backlight-helper intel-virtual-output
Running make appears to NOT build anything in i810.
Does your build compile anything in src/legacy/i810 ? If it does,
try to disable that. If it doesn't, maybe something else in the
X stack has been compiled against an older version.
Looking at the configure script, the following mention i810:
--enable-xaa Enable legacy X Acceleration Architecture (XAA) for
i810 chipsets [default=auto]
--enable-dga Enable legacy Direct Graphics Access (DGA) for i810
So I think it only gets enabled if you force one of those (but
it tests for xaa.h and dgaproc.h, perhaps you have one of those).
It should be possible to disable both of those (or --enable-???=no
in some cases). But I cannot see my build even looking for either
It is very easy to get ridiculously confused about the tenses of
time travel, but most things can be resolved by a sufficiently
large ego. -- The Last Continent
More information about the xorg