Michel D�nzer wrote:
>>I'm currently using an old XFree86 3.x installation with frame buffer on
>>this machine. Could the fact that the kernel is compiled with frame
>>buffer support have anything to do with this?
>>
>
> Some people would say yes, but I doubt it. :)
>
> Provided you use aty128fb and not just vesafb, you can try Option
> "UseFBDev".
OK. Here is what I tried:
- re-compiled the kernel without any framebuffer support. I still
get a black screen as before (so you were right :-)
- re-compiled the kernel with aty128fb. This time the screen
went black upon booting.
- re-compiled kernel with vesafb (the original configuration).
I tried "UseFBDev" in this configuration, but doing startx
prints a bunch of unresolved externals. E.g. "Symbol xf86int10Addr
from module /usr/local/X11R6/lib/modules/drivers/r128_drv.o is
unresolved!"
Perhaps one noteworthy thing: when I say "screen went black", I
literally mean that. As if the screen is turned off. You can clearly
tell that it is not just a cls(). Funny that aty128fb and the native
xfree86 drivers have the same effect (turning the screen 'off').
I'm clueless. :-(
Arno
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
