There's also the vesa driver for XFree86 4.1.0 (might be in 4.0.3 also, I don't remember. Haven't used anything but 4.1.0 since it went stable). The trick described below uses 3.3.6. The advantage to the 4.1.0 vesa driver is that you don't have to have vesafb compiled into the kernel, which can be used to hack around some stability issues, also, using 4.1.0 gives a better upgrade path, if you snag a better-supported card (or when specs for the KyroII finally become available)
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 27, 2001 7:45 PM To: [EMAIL PROTECTED] Subject: Re: [Newbie]configuring VESA driver Hi Malcolm, If you want to use a graphic board which is not supported by XFree86, it is possible to configure a Vesa Framebuffer. Then XFree86 uses the Framebuffer instead of the graphic board driver. To activate the framebuffer perhaps you have to recompile the kernel. By using "make menuconfig" in /usr/src/linux you find the point "console drivers", where you have to enable the Framebuffer support. Then finish compiling the kernel and add it to your bootmanager. When you can see the penguin on boot process the activating of framebuffer was successful. Now you can use XF86_FBDev to connect the X-Windows System to the Framebuffer. You can read more about the Framebuffer at the official framebuffer side (sorry I don't know the URL currently but you will find it by searching via www.google.com) I hope it could help With kind regards sascha _______________________________________________ Newbie mailing list [EMAIL PROTECTED] *** To unsubscribe , or change message options, see: http://XFree86.Org/mailman/listinfo/newbie _______________________________________________ Newbie mailing list [EMAIL PROTECTED] *** To unsubscribe , or change message options, see: http://XFree86.Org/mailman/listinfo/newbie
