LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Closed Thread
 
Search this Thread
Old 07-29-2006, 11:43 PM   #286
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 66

True that glxgears will give diff scores.

It's not a real benchmark for video in linux.

I think it's time I find one that works...
 
Old 07-30-2006, 12:16 AM   #287
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
I concurr. I noticed that if for example my desktop resolution is let's say : 1024 x 768 and I run glxgears I get about 5000 FPS (with the 8.26 drivers) ; then if I change to 1200x900 (my normal resolution I use) it would drop to the 4200 FPS I shown you before. Which goes to show it's a relative bench at most. Now that ATI threw a curve ball with this release it's wierd.

Now I saw on that link I gave a while back that Tom's hardware uses the benchmark tool in Unreal Tournament 2004. They also say they had to do a bunch of trix to get it to work. I wish they explained what and how to be honest. Would be a nice thing if there were an industry standard of some type for gnu/linux like there is in the windows world.

I also believe that even using fglrx is not a good judge; as in the windows world you have 3rd party app's that catch some driver tweaks for anti-aliasing, open-gl that the vendors use sometimes to up their performance data. Hence, allowing us consumers to compare manufacturer's and driver versions. After all an educated consumer is the best customer right?
 
Old 07-30-2006, 10:32 AM   #288
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 66
Been searching: No joy. What is out there is so HORRIBLY out of date, it won't even compile.

And UT is used as a benchmark...Unfortunately, I don't have it. So...

And yes, if you change res, the benchmarks change. Think about it: you have 800x600x16 color. thats alot few pixels to push than 768x1024x32. So the lower resolution would be faster than the higher.
 
Old 07-31-2006, 06:26 PM   #289
Samoth
Member
 
Registered: Apr 2005
Distribution: Exherbo
Posts: 474
Blog Entries: 1

Rep: Reputation: 32
Quote:
Originally Posted by cwwilson721
Heres your actual chip:
Code:
01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15)
Use that. Run 'xorgconfig' and choose the chip. Not sure if DRI will work with it.
Actually, that is what I use because I wasn't able to get the chip supported. But I have onboard Graphics too, which is in the ouput of my "lspci" command.
 
Old 08-01-2006, 07:42 PM   #290
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 66
That was the only thing that was in your 'lspci'

Reread it.

It's the only thing that says "vga" or even "video". If you have it disabled, how can we see it?
 
Old 08-02-2006, 08:24 PM   #291
Samoth
Member
 
Registered: Apr 2005
Distribution: Exherbo
Posts: 474
Blog Entries: 1

Rep: Reputation: 32
yeah, sorry, i turned it off in the BIOS. Dont worry about it....I don't care now that i have my Nvidia card.....
 
Old 08-03-2006, 10:00 PM   #292
Chikne
Member
 
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140

Rep: Reputation: 15
hi guys,

I have tried all the things described on this thread and I only get around 770 fps when running glxgears.
I tried to recompile kernel with different bits out of it, i am using 2.6.17, but nothing would improve the fps.
I have a geforce2 mmx 440, and used the drivers on the nvidia website.

Now for the good stuff, well I tried to patch my kernel to the latest and ended up messing it all up so I am now downloading the full tree.

My question really is, is this the maximum you could get out of such an old card or am I doing something not right?

thanks for the info it's all good stuff!!!
 
Old 08-03-2006, 10:10 PM   #293
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 66
My GeForceMX 440: 5900~6600 fps, using the steps here.
2.6.16.22 kernel, -current
 
Old 08-03-2006, 11:15 PM   #294
Chikne
Member
 
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140

Rep: Reputation: 15
Quote:
Originally Posted by cwwilson721
My GeForceMX 440: 5900~6600 fps, using the steps here.
2.6.16.22 kernel, -current
Just installed the new kernel 2.6.17.7 and I get the same... what version of xorg do you use? I am running xorg6.7, do you know if there are any issues with it?
 
Old 08-03-2006, 11:16 PM   #295
Chikne
Member
 
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140

Rep: Reputation: 15
Quote:
Originally Posted by cwwilson721
My GeForceMX 440: 5900~6600 fps, using the steps here.
2.6.16.22 kernel, -current
Just installed the new kernel 2.6.17.7 and I get the same... what version of xorg do you use? I am running xorg6.7, do you know if there are any issues with it?

Oh and would you mind to explain to me what you mean by current? thanks
 
Old 08-04-2006, 02:10 AM   #296
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 66
-current is the 'testing' version of Slackware.

As for your video, can you post the results of
Code:
glxinfo | grep direct
And your /etc/X11/xorg.conf ?

Something is going on...
 
Old 08-04-2006, 11:41 PM   #297
Chikne
Member
 
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140

Rep: Reputation: 15
Quote:
Originally Posted by cwwilson721
-current is the 'testing' version of Slackware.

As for your video, can you post the results of
Code:
glxinfo | grep direct
And your /etc/X11/xorg.conf ?

Something is going on...
hi,

damien@darkstar:~$ glxinfo | grep direct
direct rendering: Yes

ok this is my xorg conf created by xorgsetup:

ction "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
Load "glx"
#Load "record"
#Load "extmod"
#Load "dbe"
#Load "dri"
#Load "xtrap"
#Load "freetype"
#Load "type1"
#Load "freetype"
#Load "speedo"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/mouse"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NV11 [GeForce2 MX/MX 400]"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

and this is the one made by xorgconfig and modified a bit later, I've tried several configurations and nothing works better than this.... even with dri at the end of the file!

# File generated by xf86config.

#
# Copyright (c) 2004, by the X.Org
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of X.Org shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# X.Org.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
Load "dri"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for X.Org
# Option "XkbRules" "__XKBDEFRULES__"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "fr"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"
Option "ZAxisMapping" "4 5"

# Mouse-speed setting for PS/2 mouse.

#Option "Resolution" "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "dell"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 48.5

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "geforce2"
# VendorName "Unknown"
# BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "nvidia"
Option "NvAGP" "1"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 32768

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

#Section "Device"
# Identifier "geforce2"
# Driver "nvidia"
# unsupported card
# VideoRam 32768
# Insert Clocks lines here if appropriate
#EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "geforce2"
Monitor "dell"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

#Section "DRI"
#Mode 0666
#EndSection

Oh and sorry about the long post
 
Old 08-05-2006, 12:40 AM   #298
cwwilson721
Senior Member
 
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Blog Entries: 1

Original Poster
Rep: Reputation: 66
DRI is working, by the
Code:
damien@darkstar:~$ glxinfo | grep direct
direct rendering: Yes
How ever, you do have a few small issues, like glx and dri being loaded twice, and a few other things.

Yours looks like you ran 'xorgconfig', then 'xorgsetup', then the nvidia.

What may help you:
  • Backup your current /etc/X11/xorg.conf (rename it, whatever you wish), then delete it (You can always restore from the backup)
  • Run 'xorgsetup'
  • Run the nvidia installer again
Then, look thru the xorg.conf file, and see if it is a bit 'cleaner' and shorter.

Look at this file (My xorg.conf for my nvidia machine), and see how it compares.

Maybe this will help...
 
Old 08-05-2006, 02:27 AM   #299
Old_Fogie
Senior Member
 
Registered: Mar 2006
Distribution: SLACKWARE 4TW! =D
Posts: 1,515

Rep: Reputation: 62
question for you nvidia guys please D

I'm going to load up a friend of mine's pc with slackware 10.2.

His computer has an nvidia geforce card in it, but it is a "PCI" expansion slot type of card.

Question 1: Can "DRI" be achieved on "PCI" video cards?

I'm going to use the 2.6.13 testing kernel on this pc, as I don't see any need to go special yet at this time on it.

Question 2: Is the slack testing kernel to be used with the script on the front of the page too? Just wondering, I wasn't sure if that was for above 2.6.16 or not the way I read that.

Thank you in advnance.
 
Old 08-05-2006, 10:43 AM   #300
Chikne
Member
 
Registered: Jul 2006
Distribution: Slackware 11
Posts: 140

Rep: Reputation: 15
Quote:
Originally Posted by cwwilson721
DRI is working, by the
Code:
damien@darkstar:~$ glxinfo | grep direct
direct rendering: Yes
How ever, you do have a few small issues, like glx and dri being loaded twice, and a few other things.

Yours looks like you ran 'xorgconfig', then 'xorgsetup', then the nvidia.

What may help you:
  • Backup your current /etc/X11/xorg.conf (rename it, whatever you wish), then delete it (You can always restore from the backup)
  • Run 'xorgsetup'
  • Run the nvidia installer again
Then, look thru the xorg.conf file, and see if it is a bit 'cleaner' and shorter.

Look at this file (My xorg.conf for my nvidia machine), and see how it compares.

Maybe this will help...
Well well, did that but it doesn't help at all... oh I made a mistake it's not a geforce 440mx it's a geforce2 mx 32mb...

what would you think of upgrading xorg??

thanks

Last edited by Chikne; 08-05-2006 at 12:02 PM.
 
  


Closed Thread

Tags
3d, acceleration, ati, enabling, fglrx, glx, intel, nvidia, s3, savage, slackware, via, video, x11, xorg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
enabling hardware acceleration PennyroyalFrog Linux - Newbie 5 02-26-2010 12:21 PM
xorg-x11 7.0 and exa acceleration jtshaw Linux - Software 0 12-19-2005 08:42 AM
3d acceleration and X11 bspus Linux - Newbie 3 09-06-2005 07:05 AM
Problem Enabling 3D Hardware acceleration. mir_sheely Linux - Hardware 0 06-14-2004 01:37 PM
Audigy Sound card and enabling 3D acceleration for GeoForce3 ti 500 heavyarmor4ever Linux - Newbie 1 01-03-2003 10:27 PM


All times are GMT -5. The time now is 03:26 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration