Jason Thorpe <thorpej@nas.nasa.gov> writes:

> Someone suggested to me that this was a side-effect of the change of
> where the i386 kernel is located (it's now at address 0xc0000000
> instead of 0xf0000000).

Is this something I can easily change back in order to test, or have
other things changed that make it impossible?

> Where there any other errors, like failure to open /dev/mem?

Nope.  Other servers, though, like XF86_Mono, complain about being
unable to open /dev/vga or /dev/xf86.  XF86_SVGA just gives the error
message I quoted, and screws up the display so that I have to reboot
blind in order to get anything displayed on the monitor again...  :-)

> Is your XF86_SVGA binary setuid-0?

Nope.

> Are you using the Xwrapper thingie?

Whether I run XF86_SVGA directly as root, or through Xwrapper as a
non-privileged user makes no difference.

> (--) SVGA: PCI: NeoMagic NM2200 rev 32, Memory @ 0xfd000000, 0xfe800000

You don't have a conflict between the kernel address and any of those,
then.  It's interesting, in light of your suggestion, to notice that
it's complaining about the one of the two addresses listed that's
closer to the new kernel load address.

-tih
-- 
Popularity is the hallmark of mediocrity.  --Niles Crane, "Frasier"