José Romildo Malaquias wrote: > I have read your Linux SiS page, grabbed some drivers, and tested them > with the SiS 305 card. I have followed the instructions in your page: > > 1. Compiled and installed a linux 2.4.18 kernel with the sisfb driver > sisfb_src_100202.tar.gz. I have tried some configurations: > > a) VESA framebuffer driver enabled and disabled
Never enable the VESA framebuffer when using the sis framebuffer. These two have the same purpose. > b) compiled the vesafb driver into the kernel (instead of > as a module) What is it with you people that you all stick to this VESA thing?! :) As said: Disable the VESA framebuffer (don't even compile into the kernel nor as a module). > c) added the kernel parameters video=sisfb:mode:none,mem:12288 or > video=sisfb:1024x768x16:none,mem:12288 The second statement is wrong: if you don't want to use a graphical console, use video=sisfb:mode:none,mem:12288 > 2. Installed the SiS X driver sis_drv.o_260202.tar.gz. > > 3. Set up the X config file with a depth of 16 or 24 and specified > the option MaxXFBMem to 12288 in the Device section. > > 4. Tried to run the tuxracer program. The screen became black (or almost) > with a dark pointer in it. Some clicks were heard on the speakers, > and the system froze. > > Attached is the output of the xdpyinfo program. > > Any clues? Well, not yet. Please send me (not the list) the X log, your XF86Config-4 and the output of glxinfo. The relevant part of syslog would be interesting, too (the lines starting with "sisfb:" and a few of the following) It is known that some older distributions of X 4.1 (such as early Redhat's) had problems with DRI. I use Debian's 4.1.0.1 and it works here. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
