On Fri, Feb 15, 2002 at 12:01:20PM +0100, Werner Heuser wrote: Hi WebBoys,
...
trying to run it on a Gericom Webboy Laptop with this "troublemaking" SIS 630 Chipset. I have several difficulties but will pose them under different
I don't own a WebBoy but http://www.webit.com/tw/linuxsis630.shtml may be a good source of information about the graphic chipset.
Thomas Winischhofer under the above mentioned url even provides drivers for the troublesome sis630. You will have to recompile your kernel in order to use the new sisfb (framebuffer driver for sis630), patch your kernel, to get the permissions for drm right and then just copy the x-driver to the appropriate dir. Have a look at the XF86Config he provides. And *disable* APIC, provided you have compiled that into the kernel! If you forget that you won't be able to change back from X to console. The system will freeze. Additionally you may not use vesa-framebuffer support when compiling your new kernel (console-drivers) if you use sisfb. If you have any problems Thomas is pretty sure to be able to reply in German ;-) THomas Winischhofer has done a great work! His driver made it into the ac-kernel, and probably will be part of some future regular kernel-release.
You wrote about `fbset' showing the usage of framebuffer. This shows only the framebuffer works in text (console) mode. You may have a look into /var/log/XFree86.0.log or the appropriate XF86Config file to get information about the "fbdev" device with X-Windows.
If you rather would like to use sax2 to configure your X-system then try SaX2 -m 0=fbdev which worked for me. Then you still just have the (unaccelerated) framebuffer, but it works at least. Do that with your system as is, that is before you experiment with Thomas Winischhofer's sisfb. You can use is X-driver (sis_drv.o) independently from sisfb. So you don't have to compile sisfb into your kernel, you don't even need a new kernel, just copy the file to the X-drivers-directory. On trhe other hand you will lack 3d acceleration then. To get things straight: I had a lot of trouble, installing the drivers (APIC was enabled, vesa-framebuffer was enabled at first), drm-patch didn't work etc. pp. You only need sisfb for a graphical console, it's not necessarily needed for X. Have a look at the website Werner mentioned. Now I have two kernels: one containig sisfb, the other one vesa-fb, two XF86Configs, so that I can change from one XF86Config to the other. I still have one problem with the x-driver: I have a black edge of about 8mm at the bottom of the screen. ANy ideas? Timing problem? And /usr/bin/gears runs at about 140 fps under vesa-framebuffer whereas it produces something like 105 fps with Thomas' drivers. Tschüss aus Berlin Henning -- The box said "Requires Windows 95 or better." I can't understand why it won't work on my Linux computer. The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first.