>>You need to load the sis module with modprobe.>The command modprobe, as I understands it, allows you to load>the modules manaully. It doesn't load the modules on>startup... not on my computer at least. On a typical Linux Distribution (like Slackware Linux) all themodprobe commands are put into a script that get's startet at boot time.Here on my Slackware box this script is called /etc/rc.modules >So, he will still>need to use modconf if he wants the modules loaded>automatically everytime his computer starts.modconf is a Suse or Redhat specific thing, normally you use modprobe inside of a script to load a module at boot time.

>On a typical Linux Distribution (like Slackware Linux) all>the>modprobe commands are put into a script that get's startet at>boot time.>>Here on my Slackware box this script is called>/etc/rc.modulesOdd. That didn't work on my Debian.>>So, he will still>>need to use modconf if he wants the modules loaded>>automatically everytime his computer starts.>>modconf is a Suse or Redhat specific thing, normally you use>modprobe inside of a script to load a module at boot time.I have modconf on my Debian machine, and it edits the file /etc/modules.

I will look for those script files. I did try those commands as root. I went into a terminal window and typed su -Then my password for root. I tried all lower case and a capital for the first letter of the command. Is this the administrator?

Yes, root is the administrator and you write root only lower case, there is no capital letter in the name root.If root can't find these commands too (that would be very unusual),then you should look into /sbin/ and /usr/sbin/ this is the placewere those files usually are.I need to correct my last posting.This script rc.modules is in /etc/rc.d/rc.modules and only available on Slackware Linux Distributions.Other Linux Distributions use other files for this.See Hardraade's posting for the Debian Linux Distribution.

Ok, I just checked the directories from your last post and the commands are not listed. Can the files be manually installed from the distribution cd set? Or would automatic update do it? I also tried the commands from root.

It's a wonder that you don't have modprobe on your Linux system installed. This is a necessary standard tool.What distribution are you using?Maybe it is in another directory.So try the following:1. login as root2. open a terminal or console3. enter the following into the terminal/console and press enter:cd / && find -name modprobe(this could take a while, so wait a little)4. When this does not work, use the following command:locate modprobeTo your question, yes, you can install this file from the distribution cd set, you only need to find the correct package file that has this tool. When you have found it, just install the package.

Good news finally. After typeing in cd / && find -name modprobe it listed the following:./proc/sys/kernel/modprobe./ect/log.d/scripts/services/modprobe./sbin/modprobeWith the above information, is it possible to install the modules?My distribution is Fedora core 1. I believe it is the same as Red Hat Linux 9.0.

Yes, with this one when logged in as root:./sbin/modprobe

Ok, are these the modules I need to load? The path is: /lib/modules/2.4.22-1.2115.nptl/build/drivers/video/sis300vtbl.h310btbl.hinit301.cinit301.hinit.cinitdef.hinit.hmakefileoem300.hoem310.hosdef.hsis_accel.csis_accel.hsis.hsis_main.csis_main.hvgatypes.hvstruct.hDo I need to run make first and then modprobe using the above path? Just guessing, I believe the needed file is the sis_accel.

These are all source code files, normally they don't should be in /lib/modules/....This is just not the place for driver source code.Did you copy those files into this directory?If yes then it is wrong.Kernel compilation is allways made in /usr/src/linuxHowever if this is the way things work in fedora then i think yes, you'll need to use make in this directory.This should compile all drivers in this directoy so that you'll have *.o files.One of those *.o files is the right one for your card.I don't know which one.Just read on dri.sf.net or in the manpages->man sis

The dri.sf.net site lists these as 2d files. The sis_accel is a 2d accelleration driver as I read it. I am learning as I go, so if these are 2d driver files, and my system is currently using a sis driver for basic 2d stuff, then I need a 3d file? When this module is correctly probed, then when Flightgear is run, the sis card will use that module?

I just got the official word that there is no dri support for the sis6326 card at this time. Can you recommend a card replacement for a 500mhz pc. It has the first international mainboard va503+.

>I just got the official word that there is no dri support for>the sis6326 card at this time. Can you recommend a card>replacement for a 500mhz pc. It has the first international>mainboard va503+.What kind of video card do you want?If it should be a card that has open source 3d drivers thenyour best bet is an ATI Radeon 9200. (newer ATI cards only offer bad closed source drivers)If you are happy with closed source drivers, then you should get a videocard from NVidia.A nvidia Geforce 4 Ti videocard should be fine for flightgear and is inexpensive today.