Bug 2743

Created attachment 2122 [details]
xorg logfile from failed startup

Created attachment 2123 [details]
xorg config file from failed startup - xinerama, nv, glint, tdfx

interesting.  you should be able to work around this by saying Load "fbdevhw" in
the Module section of xorg.conf, for now.  but that still shouldn't happen.

I tried the "fbdevhw" suggestion.  No go.  glint_drv still won't load.  Of
course, the unresovled symbol error did go away, so it suggests to me there's
something deeper going on here.  I still get the Invalid mem allocation errors.

Latest update... Just upgraded to Slack 10.1 with Dropline Gnome 10.1.  X server
is now Xorg 6.8.2.  With fbdevhw enabled, I no longer get the unresolved symbol
error.  Now, however, the X server crashes with a Sig 11 error:

---------- tail end of Xorg.0.log ------------
(==) GLINT(1): Write-combining range (0xde800000,0x800000)
(II) GLINT(1): I2C device "DDC:ddc2" registered at address 0xA0.

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional
information.

(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) Screen 2 shares mem & io resources

Further data point:  Starting X with just the glint driver configured still
throws a sig 11 error.

please test with one of the upcoming release candidates, or with the 6.8.99.14
snapshot (as soon as it exists), as those will be able to give more information
on the segfault.

starting with the 6.8.99.14 snapshot, on linux systems, the X server can print
its own backtrace when it crashes.  please confirm that these bugs are still
valid with 6.8.99.14 or later, and if they are please attach a the server log
from the crash.

Closing as INVALID now. Re-test with Xorg 7.1 and reopen if the problem persists.