Created attachment 138378 [details]
X log - possibly from rhgb?

Created attachment 138379 [details]
X log

Trying to restart X fails...

This patch fixes the problem:

--- a/src/neo_driver.c
+++ b/src/neo_driver.c
@@ -118,6 +118,9 @@ #define _XF86DGA_SERVER_
 #include <X11/extensions/xf86dgastr.h>
 #endif

+/* For abs() */
+#include <stdlib.h>
+
 /* Mandatory functions */
 static const OptionInfoRec *   NEOAvailableOptions(int chipid, int busid);
 static void     NEOIdentify(int flags);

This patch is in the upstream bug report but has not been acted on in 2 months.
 Perhaps you would consider applying.  It's trivial and is clearly the right
thing to do.

Hmm, well that fixed the problem back in FC6T2, but appears to have no effect on
what I'm seeing now.

Now with Fedora 7, xorg-x11-server 1.3.0.0-9.fc7 and neomagic 1.1.1 I get no
display at all and the following error:

(EE) NEOMAGIC(0): Only 640x480,
     800x600,
 and 1024x768 panels are currently supported
(II) UnloadModule: "neomagic"
(II) UnloadModule: "vgahw"
(II) Unloading /usr/lib/xorg/modules//libvgahw.so
(EE) Screen(s) found, but none have a usable configuration.

Have we completely lost support for external displays?

Applying my patch above makes no difference now.

Can we get updated version of /var/log/Xorg.0.log and /etc/X11/xorg.conf (if any
exists) as separate uncompressed attachments to this bug, please?

Created attachment 160252 [details]
X log

# Xorg configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen	    0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver	    "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver	    "neomagic"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device	   "Videocard0"
	DefaultDepth	 24
	SubSection "Display"
		Viewport   0 0
		Depth	  24
	EndSubSection
EndSection

Could you try to run Xorg without any /etc/X11/xorg.conf whatsoever, please?
What does the magical auto-detection give us?

Reporter, could you please reply to the previous question? If you won't reply in
one month, this bug will be closed as INSUFFICIENT_DATA. Thank you.

Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
information.

Closing as INSUFFICIENT_DATA.