I am new to flight gear and have tried the software on the following pc's:Box no. 1:Pentium 4 1.6ghz w/256meg ram and nvidia riva tnt2 model 64 display adapter running windows xp. The simulator frame rate seems too slow for the system it is running on. How can it be sped up? Is there a tweek for the video card? Also, the keyboard will only allow the rudder to turn in one direction and the throttle seems stuck at idle.Box no. 2:Pentium III 500mhz w/196meg ram and sis6326 video card running red hat linux 9.0.This is worse than the xp box. It runs like a slide show. Would like to know if anyone uses the sis video adapter and how they got it to work. Also, has anyone used a geforce card? Would a geforce card make much of a difference on this system?

>The simulator frame rate seems too slow for the system it is>running on.What do you mean by "slow"?>How can it be sped up? Is there a tweek for the>video card? Also, the keyboard will only allow the rudder to>turn in one direction and the throttle seems stuck at idle.What aircraft are you using?There are many aircrafts in FlightGear, but most of them are incompleted due to lack of data to complete them or lack of time on the authors' part.>This is worse than the xp box. It runs like a slide show.It sounds like direct rendering is not enabled on your system. Type the following command to see whether you have direct rendering or not:glxinfo | grep rendering

For the windows xp box, I am using the dc3 aircraft that came with the package. By a slow frame rate, I can see the frames per second. For input/output, I chose generic. I am assuming this is the interface. By turning num lock off, the throttle now works, but the aircraft becomes wild, unable to control and it crashes.I will try the suggested line on the linux box and post later.

>For the windows xp box, I am using the dc3 aircraft that came>with the package. By a slow frame rate, I can see the frames>per second. Are you using 0.9.6?>For input/output, I chose generic. I am assuming>this is the interface. By turning num lock off, the throttle>now works, but the aircraft becomes wild, unable to control>and it crashes.Try using the mouse for control, and the PageUp/PageDown key for throttle.

I typed in glxinfo | grep rendering and received a no, so I am assuming that the stock driver does only 2d mode. I would like your comment on this link: http://www.winischhofer.at/linuxsisvga.shtmlThis site provides 3d drivers for the sis video cards. I am not sure if these work with red hat linux 9.0. Would there be any compatability issues?

>I typed in glxinfo | grep rendering and received a no, so I>am assuming that the stock driver does only 2d mode.Not necessary. Sometimes, direct rendering doesn't work because X wasn't configure properly. Othertimes, it is because the particular support for the graphic card wasn't compiled into the kernel. Or as I found out today, xlibmesa-dri and xlibmesa wasn't installed.>I would like your comment on this link:>http://www.winischhofer.at/linuxsisvga.shtml>>This site provides 3d drivers for the sis video cards. I am>not sure if these work with red hat linux 9.0. Would there be>any compatability issues?Unfortunately, my knowledge regarding hardwares and Linux drivers is very limited. The only suggestion I have is do some googling. In particular, see if it is XF86Config or your kernel configuration that is causing your problems. If it is proven that they are not the causes, then you can try the drivers.You should also check out any error or warning messages that you may have in your XFree86.0.log by typing:cat /var/log/XFree86.0.log

I tried xconfig in a terminal window and in the Gnome run box. I can not get it to run. I heard that the make xconfig is tricky to use. How does one run this utility? Also, I have the xfree86.0.log file. If I posted it, can the problem be located in the file?

>I tried xconfig in a terminal window and in the Gnome run>box. I can not get it to run. I heard that the make xconfig is>tricky to use. How does one run this utility? Also, I have the>xfree86.0.log file. If I posted it, can the problem be located>in the file?Yes, the xfree86.0.log file can be very helpfull here.If XFree finds errors during start, they will be marked wit (EE) in the log file.So to find the errors just look at the lines that start with (EE) they will tell you what went wrong. There are also other Markers, here's a Description of all Markers:(--) probed(**) from config file(==) default setting(++) from command line(!!) notice(II) informational(WW) warning(EE) error(NI) not implemented(??) unknown.The interesting ones to find errors are (EE), (WW), (NI) and (??).

Ok, I checked out the log file and here are two interesting ones:(WW) PCI-PCI bridge at 0:7:3 has unexpected header: 0x0(II) Host-to-PCI bridge:(EE) SIS(0): [dri] DRIScreenInit failed. Disabling DRI.All the other lines had the other prefixes. Do they point to where the 3d problem is?

>(WW) PCI-PCI bridge at 0:7:3 has unexpected header: 0x0(II)>Host-to-PCI bridge:Ok, you can ignore this one. This is just a warning message.>>(EE) SIS(0): [dri] DRIScreenInit failed. Disabling DRI.>>All the other lines had the other prefixes. Do they point to>where the 3d problem is?>The problem can be seen at above message.DRI can't be initalized. It gets disabled and without DRI you won't have 3d accerlation Take a look at this site:http://dri.sourceforge.net/cgi-bin/moin.cg...ategoryHardwareCheck if you linux kernel was compiled with the kernel module sis-4.4.0 activated. In Kernel config menu from kernel 2.4.x choose:character devices -> Direct Rendering Manager (XFree86 DRI support) -> SiS (NEW)This module must be activated, so that it can be used with DRI.You also need AGP support turned on for your mainbaord chipset.After that, check if everthing is set correctly in /etc/X11/XF86Configor /etc/X11/xorg.conf.Especially the DRI and Video driver part.There is also a manpage for the sis video driver:man sisYou should also read this site:http://dri.sourceforge.net/cgi-bin/moin.cg...TroubleshootingEspecially this is interesting:Do dmesg | grep drm to find if drm modul is loaded in your kernel.and this:" If the DRM is probing correctly, take a look at your XFree86 log. It's usually located at /var/log/XFree86.0.log. First, make sure the dri module is getting loaded. Running grep dri /var/log/XFree86.0.log | grep LoadModule will show it being loaded. If not, add Load "dri" to the Modules section of XF86Config. Load "glx" is also necessary. If you are having troubles with your changes to XF86Config not having any effect, make sure the XF86Config you are editing matches the one being used according to grep config file /var/log/XFree86.0.log"

>Check if you linux kernel was compiled with the kernel module>sis-4.4.0 activated. >>In Kernel config menu from kernel 2.4.x choose:>character devices -> Direct Rendering Manager (XFree86 DRI>support) -> SiS (NEW)>>This module must be activated, so that it can be used with>DRI.If he didn't compile the kernel himself, chances are that he forgot to load the modules.Sirus, run the command "modconf" as root. Press the down arrow on your keyboard until you see "kernel/drivers/char/drm". Highlight it and press enter. You should then see something similar to this:http://www.ellak.gr/pub/OpenGuides/Debian/...05/modconf2.pngFind any entry that says "sis" and see if there is a "+" sign beside it. If not, highlight that entry, press Enter and follow the steps to load the module.

Thank you for the replies. I printed out everything and will post back my results asap.

I was not able to run the command modconf. Linux returned 'command not found'. Also, xconfig returned 'command not found'. I tried make xconfig and it returned 'make xconfig no rule to make target xconfig. stop.' Can I get these commands to run? I am pasting part of the xfree86.0.log to provide additional info.(==) SIS(0): Write-combining range (0xe7000000,0x400000)drmOpenDevice: minor is 0drmOpenDevice: node name is /dev/dri/card0drmOpenDevice: open result is -1, (No such device)drmOpenDevice: open result is -1, (No such device)drmOpenDevice: Open faileddrmOpenDevice: minor is 0drmOpenDevice: node name is /dev/dri/card0drmOpenDevice: open result is -1, (No such device)drmOpenDevice: open result is -1, (No such device)drmOpenDevice: Open failed[drm] failed to load kernel module "sis"(II) SIS(0): [drm] drmOpen failed(EE) SIS(0): [dri] DRIScreenInit failed. Disabling DRI.(II) SIS(0): Frame Buffer From (0,0) To (1024,1343)(II) SIS(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles Solid Horizontal and Vertical Lines Offscreen Pixmaps Setting up tile and stipple cache: 16 128x128 slots 4 256x256 slots(==) SIS(0): Backing store disabled(==) SIS(0): Silken mouse enabled(**) Option "dpms"(**) SIS(0): DPMS enabled(II) SIS(0): Using SiS5597/5598/6326/530/620 HW Xv(II) SIS(0): Direct rendering disabled(==) RandR enabled(II) Setting vga for screen 0.

>I was not able to run the command modconf. Linux returned>'command not found'. Also, xconfig returned 'command not>found'. I tried make xconfig and it returned 'make xconfig no>rule to make target xconfig. stop.' Can I get these commands>to run?These commands are only available for root (administrator).So login as root and try again.Don't forget to logout as root, after you are finished with this.> I am pasting part of the xfree86.0.log to provide>additional info.>>(==) SIS(0): Write-combining range (0xe7000000,0x400000)>drmOpenDevice: minor is 0>drmOpenDevice: node name is /dev/dri/card0>drmOpenDevice: open result is -1, (No such device)>drmOpenDevice: open result is -1, (No such device)>drmOpenDevice: Open failed>drmOpenDevice: minor is 0>drmOpenDevice: node name is /dev/dri/card0>drmOpenDevice: open result is -1, (No such device)>drmOpenDevice: open result is -1, (No such device)>drmOpenDevice: Open failed>[drm] failed to load kernel module "sis"You need to load the sis module with modprobe.If this does not work you have to recompile the Kernel with sis support.The Kernel modules are stored in /lib/modules/(enter_kernel_version)/check if you have a sis module there.

>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. So, he will still need to use modconf if he wants the modules loaded automatically everytime his computer starts.