After a full portupgrade today, Xorg will not start-up:
[ 5903.171] (II) Loading /usr/local/lib/xorg/modules/drivers/intel_drv.so
[ 5903.171] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/intel_drv.so: /usr/local/lib/xorg/modules/drivers/intel_drv.so: Undefined symbol "fbPolySegment"
[ 5903.171] (II) UnloadModule: "intel"
[ 5903.171] (II) Unloading intel
[ 5903.171] (EE) Failed to load module "intel" (loader failed, 7)
[ 5903.171] (EE) No drivers available.
[ 5903.171] (EE)
Fatal server error:
[ 5903.171] (EE) no screens found(EE)
[ 5903.172] (EE)
The problem is about month-old, judging by this buzz out there:
Attempting to recreate the xorg.conf again with "Xorg -configure" fail with the same error:
[ 2133.610] (II) LoadModule: "modesetting"
[ 2133.610] (II) Loading /opt/lib/xorg/modules/drivers/modesetting_drv.so
[ 2133.610] (EE) Failed to load /opt/lib/xorg/modules/drivers/modesetting_drv.s
o: /opt/lib/xorg/modules/drivers/modesetting_drv.so: Undefined symbol "shadowUpd
[ 2133.610] (II) UnloadModule: "modesetting"
[ 2133.610] (II) Unloading modesetting
[ 2133.610] (EE) Failed to load module "modesetting" (loader failed, 7)
[ 2133.610] (II) LoadModule: "intel"
[ 2133.610] (II) Loading /opt/lib/xorg/modules/drivers/intel_drv.so
[ 2133.610] (EE) Failed to load /opt/lib/xorg/modules/drivers/intel_drv.so: /op
t/lib/xorg/modules/drivers/intel_drv.so: Undefined symbol "fbPolySegment"
[ 2133.610] (II) UnloadModule: "intel"
[ 2133.610] (II) Unloading intel
[ 2133.610] (EE) Failed to load module "intel" (loader failed, 7)
[ 2133.610] No devices to configure. Configuration failed.
Ok, I recovered the use of this computer by adding the following two lines to the "Module" section of /etc/X11/xorg.conf (which was in use, unmodified, for several years):
I don't think, it is reasonable to leave such a trick to a _regular_ user to figure out on their own...
Can you show full contents of xorg.conf and Xorg.0.log?
- modesetting DDX already loads "shadow" module
- intel DDX already loads "fb" module for UXA while SNA has its own fbPolySegment
(In reply to Mikhail T. from comment #0)
If you get those error with no xorg.conf file then I suspect there was a problem with your build. Did portupgrade rebuild all xf86-* ports after xorg-server?
Xorg -configure is known broken for a long time. That is an upstream issue. I have considered patching xorg-server to either disable the option or at least print a big warning stating it doesn't work and recommending no config or very minimal files in xorg.conf.d.
Created attachment 181240 [details]
Created attachment 181241 [details]
log file with the error
Here are the requested files. The "fb" and "vgahw" modules are mandatory for the "intel" driver to load without -- regardless of the config-option (UXA or SNA) it was compiled with.
> SNA has its own fbPolySegment
Yes (the sfbPolySegment). But the shared object would not load without "fb" -- because the fbPolySegment symbol will be unresolved anyway.
> Did portupgrade rebuild all xf86-* ports after xorg-server?
Not sure about the order of the upgrade, but all were upgraded. And then I manually rebuilt both xf86-video-intel (with different options) and xorg-server by hand.
Of all the binaries in xorg-server's WRKSRC, the symbol fbPolySegment is only provided by libfb.so -- it really is not that hard to confirm. So the module needs to be loaded... I guess, it was implied before, and needs to be explicit now :-/
I am surprised, you can not reproduce this problem locally...
> The "fb" and "vgahw" modules are mandatory for the "intel" driver
> to load without
Scratch the "without" part... Sorry for any confusion...
Is this still an issue?
No idea. I no longer have that computer.
Then I'm closing this for now. If the issue comes up again, please reopen this, or submit a new PR.
Yes, this is still an issue. I have the same problem with an i945GM/GMS integrated graphics card.
For me the solution with adding "fb" and "vgahw" did not help anything.
And yes, I recompiled everything from scratch several times with different options and settings.
No matter if it under 10.3, 10.4 or 11.1 , always the same error with the undefined symbol.
(In reply to gebhart from comment #10)
Have you tried the modesetting DDX instead of intel?
I use modesetting myself which works better than intel but unfortunately it suffers from tearing a lot. Until modesetting has tearfree support I don't want to recommend that as a "fix".
Personally I'm hoping to switch to sway (wayland) full time soon to get a nice tearfree desktop...
Would be nice if we could fix the intel ddx though, unless it is ready for the grave. Kind of feels like it's on life support atm.
Can you check if bug 224621 improved anything? I don't use modesetting due to subpar performance with GL clients.