No, no problem removing it. vbe and ddc are used in communicating with newer monitors to determine what modes they support. They can be used to help us auto configure your system, but are not required to run. Especially if you already have a working XF86Config file. IIRC, the lockup you mention is fixed in CVS.
-- Kevin "Marcello M.Pavan" wrote: > > > Kevin > > I tried your next-to-latest driver (the lastest one 4.1.99 was not compatible > with my 4.1.0 server, or so it claimed) and it STILL did not work. > Running XFree86 -probeonly locked up the computer as before, yielding > no output at all in /var/log/XFree86.0.log. > > However, following a suggestion someone sent me, I removed the library > libvbe.o and now it works ! > > now why is that ? is libvbe.o an optional library ? I am > skeptical, expecting some kind of performance decrease in exchange. (of > course, working at all is a huge performance increase from before ! ;-) > > Interestingly, when trying the 4.1.99 driver, XF did get past the stage of > loading libvde , only to die afterwards when it tried to load the s3virge > driver. odd. > > anyhow, am I courting disaster by removing the libvbe library ? is there > something else I should do ?? > > regards, > Marcello > > > > > There have been some recent fixes for MX, you can grab a test driver > > from my page below. Add it to your modules directory then try: > > > > sync > > X -probeonly > > > > let us know what happens and send a copy of /var/log/XFree86.0.log. _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
