Oli Comber <[EMAIL PROTECTED]> writes: > Apologies for leaving it so long before following this up - I followed your
No need to apologize, it's your problem, not mine. > advice below, M�ns, but unfortunately I couldn't spot anything particularly > wierd in the X or Kernel logs. > > However, I've just been reading the Framebuffer Howto at Ibiblio, > which states in several places that there can be a conflict between > the Vesa framebuffer device and Permedia cards. OK, so you're using VESA framebuffer? > As I'm running the Redhat 7.3 Distribution kernel (not for much longer, > though, soon as I have the time... ;) ) I imagine I've got VesaFB support > compiled in, and FB modules for other cards lying around. Boot with "vga=normal video=vesafb:off", and see if it helps. > Could this be the problem? For completeness, I would be compiling in > PM3FB and setting the 'usefbdev' option in X, but will this solve > the problem here? It's OK to use the pm3fb console even without usefbdev in X config. > If this is the problem, how does bootstrapping it with 'X -configure' get > around it? It could be that the vesa or fbdev driver does something when probing that makes the pm3 driver not crash. Move /usr/X11R6/lib/modules/drivers/vesa_drv.o and fbdev.o to some other place and see if X -configure also locks things up. Then we know it's one of those drivers that "fixed" the problem. -- M�ns Rullg�rd [EMAIL PROTECTED] _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
