Hey, I have been following most of the Nvidia thread and I have a few of my own probs with my card to ask. Here is my setup. I have a Viper 550 AGP for my PII 400 w/ 256MB of RAM running KDE2 installed on SuSE 7.1 Personal Edition. This is a fresh install (I checked on 3d acceleration when I installed my card...I suppose this was to install the mesa drivers)...I did the Yast 2 Control Update...which installed the latest Nvidia drivers (I think...any suggestions on how to verify this?) I can run Lokigames no prob...looks great. When I try to run any GL screensaver it crashes (klock comes up) with a signal 11 (SIGSEGV) Blender runs slow as dirt and I get a 'Default configuration 'mesa3.1' in init file' when I run it from the command line. Any suggestions? Brian D.
Brian Dunaway wrote:
Hey,
I have been following most of the Nvidia thread and I have a few of my own probs with my card to ask.
Here is my setup. I have a Viper 550 AGP for my PII 400 w/ 256MB of RAM running KDE2 installed on SuSE 7.1 Personal Edition. This is a fresh install (I checked on 3d acceleration when I installed my card...I suppose this was to install the mesa drivers)...I did the Yast 2 Control Update...which installed the latest Nvidia drivers (I think...any suggestions on how to verify this?)
I can run Lokigames no prob...looks great.
When I try to run any GL screensaver it crashes (klock comes up) with a signal 11 (SIGSEGV)
Blender runs slow as dirt and I get a 'Default configuration 'mesa3.1' in init file' when I run it from the command line.
Any suggestions?
Brian D.
Look in /etc/X11/XF86CONFIG for the line Driver "nvidia" = hardware 3d acceleration or Driver "nv" = no hardware 3d acceleration If you have the later you will need mesasoft for software 3d -- Mark Hounschell dmarkh@cfl.rr.com
When I try to run any GL screensaver it crashes (klock comes up) with a signal 11 (SIGSEGV)
Blender runs slow as dirt and I get a 'Default configuration 'mesa3.1' in init file' when I run it from the command line.
Any suggestions?
Brian D.
The latest drivers need to be 'activated' for 3D. The file tells you to install them in a particular order and then run the "switch2nvidia.glx"(sp?) file to activate the 3D. I did what it said and mine works fine on a very similar system to your own (V550, AMD450). Without the switch-file being run I got about 50fps in 'gears', afterwards I got over 400. (Just type "gears" in the console and that should run it - it prints the FPS in the console window so you can see if your 3D accel is working) The full info about how to install and activate the drivers is on the NVidia site.
I tried, reinstalling the 1.0x drivers again, since people said they were faster. I get lots of oddities with them. Interestingly moving windows in KDE is nearly as smooth as Windoze, however, there is a delay between changing workspaces in "WindowMaker" which is really irritating. I didnt notice any speed increase at all. Back to 0.976 again. dids
The latest drivers need to be 'activated' for 3D. The file tells you to install them in a particular order and then run the "switch2nvidia.glx"(sp?) file to activate the 3D.
I have tried it two ways both on fresh installs. I installed 7.2 personal edition straight out of the box and downloaded the drivers from Nvidia following their intructions. I get OpenGL support in my games no problem...but my GL screensavers and Blender both look for Mesa drivers. I also tried getting the software update from the Yast Control Center before I installed the Nvidia drivers from Nvidia....I get the same bugginess before and after I install the Nvidia drivers from Nvidia's site.
I did what it said and mine works fine on a very similar system to your own (V550, AMD450). Without the switch-file being run I got about 50fps in 'gears', afterwards I got over 400. (Just type "gears" in the console and that should run it - it prints the FPS in the console window so you can see if your 3D accel is working)
I ran gears and I get a little more than 600 FPS. Brian D.
* Brian Dunaway (brian@fusionwerks.com) [010602 02:40]: ->> The latest drivers need to be 'activated' for 3D. The file tells you to ->> install them in a particular order and then run the ->> "switch2nvidia.glx"(sp?) file to activate the 3D. -> ->I have tried it two ways both on fresh installs. I installed 7.2 personal ->edition straight out of the box and downloaded the drivers from Nvidia ->following their intructions. I get OpenGL support in my games no ->problem...but my GL screensavers and Blender both look for Mesa drivers. I ->also tried getting the software update from the Yast Control Center before I ->installed the Nvidia drivers from Nvidia....I get the same bugginess before ->and after I install the Nvidia drivers from Nvidia's site. -> ->> I did what it said and mine works fine on a very similar system to your own ->> (V550, AMD450). Without the switch-file being run I got about 50fps in ->> 'gears', afterwards I got over 400. (Just type "gears" in the console and ->> that should run it - it prints the FPS in the console window so you can see ->> if your 3D accel is working) -> ->I ran gears and I get a little more than 600 FPS. Ok..it wouldn't look for the Mesa drivers if you installed nVidia's GLX and run the modified 'switch2nv_glx' script I've posted twice. It really does work. I just ran the pipes GL screen saver in KDE2 in order to check.. :) Here ya go... -- Ben Rosenberg mailto:ben@whack.org ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
Ok, now it's my turn :-) I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script. I added "glx" to the Loaded Modules in XF86Config, and then restarted X. I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251 Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler. Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection I have tried to set the Driver to "nvidia" from "nv", but when I do that, X will not start at all. I don't really run 3D stuff on this machine, but it would be nice to have the card working, somewhat. If I am missing something obvious, please let me know. I've been monitoring the NVIDIA thread for a few weeks, now, but haven't seen anything that seems applicable. Thanks, Ron Cordell On Saturday 02 June 2001 05:46, you wrote:
* Brian Dunaway (brian@fusionwerks.com) [010602 02:40]: ->> The latest drivers need to be 'activated' for 3D. The file tells you to ->> install them in a particular order and then run the ->> "switch2nvidia.glx"(sp?) file to activate the 3D. -> ->I have tried it two ways both on fresh installs. I installed 7.2 personal ->edition straight out of the box and downloaded the drivers from Nvidia ->following their intructions. I get OpenGL support in my games no ->problem...but my GL screensavers and Blender both look for Mesa drivers. I ->also tried getting the software update from the Yast Control Center before I ->installed the Nvidia drivers from Nvidia....I get the same bugginess before ->and after I install the Nvidia drivers from Nvidia's site. -> ->> I did what it said and mine works fine on a very similar system to your own ->> (V550, AMD450). Without the switch-file being run I got about 50fps in ->> 'gears', afterwards I got over 400. (Just type "gears" in the console and ->> that should run it - it prints the FPS in the console window so you can see ->> if your 3D accel is working) -> ->I ran gears and I get a little more than 600 FPS.
Ok..it wouldn't look for the Mesa drivers if you installed nVidia's GLX and run the modified 'switch2nv_glx' script I've posted twice. It really does work. I just ran the pipes GL screen saver in KDE2 in order to check.. :)
Here ya go...
This may or may not help. Modules: Load "dbe" #double buffer extension Load "glx" #you did that #Load "dri" #useless under nvidia #Load "GLcore #loads implicitly, no need to delcare Load "extmod" #think this lets and driver extensions load? Then, another thing; the mesa drivers. It's ok (and even desireable) to leave the mesa lib in, but the driver conflicts - therefore: "rpm -e mesasoft". And also, in the user account: login when in gui to the console using "sux" (the x give SU user privileges to the X-server of the user) and then root password. Now give command "switch2nvidia_glx" (that's after switching the Driver from nv to nvidia) > also you can change "Identifier" for Device[0] to "NV AGP" and add Videoram "32768" or whatever size the vid-ram is in Kb's. Also, some have stated that the rpm's don't load/install the kernel modules correctly. Might also try to use tarballs. Cheers, Curtis On Monday 04 June 2001 09:23 am, Ron Cordell wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
I have tried to set the Driver to "nvidia" from "nv", but when I do that, X will not start at all.
I don't really run 3D stuff on this machine, but it would be nice to have the card working, somewhat.
If I am missing something obvious, please let me know. I've been monitoring the NVIDIA thread for a few weeks, now, but haven't seen anything that seems applicable.
Thanks,
Ron Cordell
On Saturday 02 June 2001 05:46, you wrote:
* Brian Dunaway (brian@fusionwerks.com) [010602 02:40]: ->> The latest drivers need to be 'activated' for 3D. The file tells you to ->> install them in a particular order and then run the ->> "switch2nvidia.glx"(sp?) file to activate the 3D. -> ->I have tried it two ways both on fresh installs. I installed 7.2 personal ->edition straight out of the box and downloaded the drivers from Nvidia ->following their intructions. I get OpenGL support in my games no ->problem...but my GL screensavers and Blender both look for Mesa drivers. I ->also tried getting the software update from the Yast Control Center before I ->installed the Nvidia drivers from Nvidia....I get the same bugginess before ->and after I install the Nvidia drivers from Nvidia's site. -> ->> I did what it said and mine works fine on a very similar system to your own ->> (V550, AMD450). Without the switch-file being run I got about 50fps in ->> 'gears', afterwards I got over 400. (Just type "gears" in the console and ->> that should run it - it prints the FPS in the console window so you can see ->> if your 3D accel is working) -> ->I ran gears and I get a little more than 600 FPS.
Ok..it wouldn't look for the Mesa drivers if you installed nVidia's GLX and run the modified 'switch2nv_glx' script I've posted twice. It really does work. I just ran the pipes GL screen saver in KDE2 in order to check.. :)
Here ya go...
I snuck some time from work to play with this a little more. Booting to the command line instead of the graphical prompt allowed me to see quite a bit more information about what errors were for the display when attempting to start X. Turns out that the nvidia driver did not like my 1600x1200 display resolution. I ran SAX2 from the command line, and lo and behold, there is a cool NVidia screen coming up on my X Server! Wow! I set for 1024x768 and that worked. I then set up 1280x1024 and that is what I am using now. I don't know why 1600x1200 doesn't work - oh well. I suppose that will give my eyes a rest. :-) Still, a 21" monitor does will at that resolution, and 1280x1024 looks HUGE ;-) So I ran gears, and at the default window size that comes up I get 1008 FPS. At full screen I get something like 264 FPS. The only thing that I changed in my XF86Config file was the setting for videoram and the driver from "nv" to "nvidia". I wonder if it was the videoram setting that made the difference. -ronc On Tuesday 05 June 2001 11:19, you wrote:
This may or may not help. Modules:
Load "dbe" #double buffer extension Load "glx" #you did that #Load "dri" #useless under nvidia #Load "GLcore #loads implicitly, no need to delcare Load "extmod" #think this lets and driver extensions load?
Then, another thing; the mesa drivers. It's ok (and even desireable) to leave the mesa lib in, but the driver conflicts - therefore: "rpm -e mesasoft".
And also, in the user account: login when in gui to the console using "sux" (the x give SU user privileges to the X-server of the user) and then root password. Now give command "switch2nvidia_glx" (that's after switching the Driver from nv to nvidia) > also you can change "Identifier" for Device[0] to "NV AGP" and add Videoram "32768" or whatever size the vid-ram is in Kb's.
Also, some have stated that the rpm's don't load/install the kernel modules correctly. Might also try to use tarballs.
Cheers, Curtis
On Monday 04 June 2001 09:23 am, Ron Cordell wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
I have tried to set the Driver to "nvidia" from "nv", but when I do that, X will not start at all.
I don't really run 3D stuff on this machine, but it would be nice to have the card working, somewhat.
If I am missing something obvious, please let me know. I've been monitoring the NVIDIA thread for a few weeks, now, but haven't seen anything that seems applicable.
Thanks,
Ron Cordell
On Saturday 02 June 2001 05:46, you wrote:
* Brian Dunaway (brian@fusionwerks.com) [010602 02:40]: ->> The latest drivers need to be 'activated' for 3D. The file tells you to ->> install them in a particular order and then run the ->> "switch2nvidia.glx"(sp?) file to activate the 3D. -> ->I have tried it two ways both on fresh installs. I installed 7.2 personal ->edition straight out of the box and downloaded the drivers from Nvidia ->following their intructions. I get OpenGL support in my games no ->problem...but my GL screensavers and Blender both look for Mesa drivers. I ->also tried getting the software update from the Yast Control Center before I ->installed the Nvidia drivers from Nvidia....I get the same bugginess before ->and after I install the Nvidia drivers from Nvidia's site. -> ->> I did what it said and mine works fine on a very similar system to your own ->> (V550, AMD450). Without the switch-file being run I got about 50fps in ->> 'gears', afterwards I got over 400. (Just type "gears" in the console and ->> that should run it - it prints the FPS in the console window so you can see ->> if your 3D accel is working) -> ->I ran gears and I get a little more than 600 FPS.
Ok..it wouldn't look for the Mesa drivers if you installed nVidia's GLX and run the modified 'switch2nv_glx' script I've posted twice. It really does work. I just ran the pipes GL screen saver in KDE2 in order to check.. :)
Here ya go...
If this resolution worked with the other driver (nv), you'll want to use this option: Option "IgnoreEDID" "boolean" Disable probing of EDID (Extended Display Identification Data) from your monitor. Requested modes are compared against values gotten from your monitor EDIDs (if any) during mode validation. Some monitors are known to lie about their own capabilities. Ignoring the values that the monitor gives may help get a certain mode validated. On the other hand, this may be dangerous if you don't know what you are doing. Default: Use EDIDs. hth,
From Ron Cordell to Curtis Rey and suse-linux-e@suse.com about Re: [SLE]...:
I snuck some time from work to play with this a little more. Booting to the command line instead of the graphical prompt allowed me to see quite a bit more information about what errors were for the display when attempting to start X. Turns out that the nvidia driver did not like my 1600x1200 display resolution. I ran SAX2 from the command line, and lo and behold, there is a cool NVidia screen coming up on my X Server! Wow!
I set for 1024x768 and that worked. I then set up 1280x1024 and that is what I am using now. I don't know why 1600x1200 doesn't work - oh well. I suppose that will give my eyes a rest. :-) Still, a 21" monitor does will at that resolution, and 1280x1024 looks HUGE ;-)
So I ran gears, and at the default window size that comes up I get 1008 FPS. At full screen I get something like 264 FPS.
The only thing that I changed in my XF86Config file was the setting for videoram and the driver from "nv" to "nvidia". I wonder if it was the videoram setting that made the difference.
-ronc
On Tuesday 05 June 2001 11:19, you wrote:
This may or may not help. Modules:
Load "dbe" #double buffer extension Load "glx" #you did that #Load "dri" #useless under nvidia #Load "GLcore #loads implicitly, no need to delcare Load "extmod" #think this lets and driver extensions load?
Then, another thing; the mesa drivers. It's ok (and even desireable) to leave the mesa lib in, but the driver conflicts - therefore: "rpm -e mesasoft".
And also, in the user account: login when in gui to the console using "sux" (the x give SU user privileges to the X-server of the user) and then root password. Now give command "switch2nvidia_glx" (that's after switching the Driver from nv to nvidia) > also you can change "Identifier" for Device[0] to "NV AGP" and add Videoram "32768" or whatever size the vid-ram is in Kb's.
Also, some have stated that the rpm's don't load/install the kernel modules correctly. Might also try to use tarballs.
Cheers, Curtis
On Monday 04 June 2001 09:23 am, Ron Cordell wrote:
Ok, now it's my turn :-)
I downloaded the latest NVIDIA drivers for SuSE and installed them. I then ran the switch2nv_glx shell script.
I added "glx" to the Loaded Modules in XF86Config, and then restarted X.
I noticed that the xconsole indicated the following: Jun 4 10:12:31 linux kernel: NVRM: loading NVIDIA kernel module version 1.0-1251
Now when I attempt to run gears, I get the following error message: Xlib: extension "NV-GLX" missing on display ":0.0". Segmentation fault
If I try to enable and run an OpenGL screensaver, I get the KDE Krash handler.
Here is the portion of my XF86Config file for the TNT2 Ultra card: Section "Device" BoardName "Riva TNT2 Ultra" Driver "nv" Identifier "Device[0]" Screen 0 VendorName "Nvidia" EndSection
I have tried to set the Driver to "nvidia" from "nv", but when I do that, X will not start at all.
I don't really run 3D stuff on this machine, but it would be nice to have the card working, somewhat.
If I am missing something obvious, please let me know. I've been monitoring the NVIDIA thread for a few weeks, now, but haven't seen anything that seems applicable.
Thanks,
Ron Cordell
On Saturday 02 June 2001 05:46, you wrote:
* Brian Dunaway (brian@fusionwerks.com) [010602 02:40]: ->> The latest drivers need to be 'activated' for 3D. The file tells you to ->> install them in a particular order and then run the ->> "switch2nvidia.glx"(sp?) file to activate the 3D. -> ->I have tried it two ways both on fresh installs. I installed 7.2 personal ->edition straight out of the box and downloaded the drivers from Nvidia ->following their intructions. I get OpenGL support in my games no ->problem...but my GL screensavers and Blender both look for Mesa drivers. I ->also tried getting the software update from the Yast Control Center before I ->installed the Nvidia drivers from Nvidia....I get the same bugginess before ->and after I install the Nvidia drivers from Nvidia's site. -> ->> I did what it said and mine works fine on a very similar system to your own ->> (V550, AMD450). Without the switch-file being run I got about 50fps in ->> 'gears', afterwards I got over 400. (Just type "gears" in the console and ->> that should run it - it prints the FPS in the console window so you can see ->> if your 3D accel is working) -> ->I ran gears and I get a little more than 600 FPS.
Ok..it wouldn't look for the Mesa drivers if you installed nVidia's GLX and run the modified 'switch2nv_glx' script I've posted twice. It really does work. I just ran the pipes GL screen saver in KDE2 in order to check.. :)
Here ya go...
-- dieter
dieter wrote:
If this resolution worked with the other driver (nv), you'll want to use this option:
Option "IgnoreEDID" "boolean" Disable probing of EDID (Extended Display Identification Data) from your monitor. Requested modes are compared against values gotten from your monitor EDIDs (if any) during mode validation. Some monitors are known to lie about their own capabilities. Ignoring the values that the monitor gives may help get a certain mode validated. On the other hand, this may be dangerous if you don't know what you are doing. Default: Use EDIDs.
I wonder if the correct value to turn EDID off is "true" or "on". Or either one. I noticed that some other options were set "off". Paul
From Paul Abrahams to SuSE listserve about Re: [SLE] More Nvidia Fun:
I wonder if the correct value to turn EDID off is "true" or "on". Or either one. I noticed that some other options were set "off".
You can choose between "1", "on", "true" and "yes" the opposites are "0", "off", "false" and "no" as you probably already guessed :)
Paul
-- dieter
I assume that this Option would be in the Monitor section? -ronc On Tuesday 05 June 2001 13:05, you wrote:
From Paul Abrahams to SuSE listserve about Re: [SLE] More Nvidia Fun:
I wonder if the correct value to turn EDID off is "true" or "on". Or either one. I noticed that some other options were set "off".
You can choose between "1", "on", "true" and "yes" the opposites are "0", "off", "false" and "no" as you probably already guessed :)
Paul
It turns out that I did not need to do this. I edited the monitor parameters for Vsync and Hsync to match the monitor manual specs - the Hsync was set to 100KHz and it was actually 95Khz. Once I did this, I was able to set for 1600x1200. Thanks to all for helping me get the NVidia drivers up and running. -ronc On Tuesday 05 June 2001 13:05, you wrote:
From Paul Abrahams to SuSE listserve about Re: [SLE] More Nvidia Fun:
I wonder if the correct value to turn EDID off is "true" or "on". Or either one. I noticed that some other options were set "off".
You can choose between "1", "on", "true" and "yes" the opposites are "0", "off", "false" and "no" as you probably already guessed :)
Paul
* Ron Cordell
I snuck some time from work to play with this a little more. Booting to the command line instead of the graphical prompt allowed me to see quite a bit more information about what errors were for the display when attempting to start X. Turns out that the nvidia driver did not like my 1600x1200 display resolution. I ran SAX2 from the command line, and lo and behold, there is a cool NVidia screen coming up on my X Server! Wow!
a TNT2 should be able to do 1600x1200 accelerated. However, the question is how much memory does your TNT2 board have ? If it's 8M you cannot do 1600x1200 accelerated. (and yes, 1600x1200 is excellent on a 21" monitor, and doable on a 17 i forgot exalty how the math goes, but there used to be an entry about this on the dri project over on sourceforge. And there is ;) .. http://dri.sourceforge.net/faq/faq_display.phtml?id=21 or even better check http://dri.sourceforge.net/res/rescalc.phtml Running at 1600 x 1200 you will need at least this much video memory: 16 bpp: 11520000 bytes = 10.986328125 megabytes 32 bpp: 23040000 bytes = 21.97265625 megabytes If your cards video memory falls within 1-2 megabytes of the given value it will be a very tight fit. In that case you should try lowering your screen resolution or running at a lower color depth. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Global Technical Support Fax +31-10.280.1511 Jason Geosystems BV (When calling please note: we are in GMT+1) gdenhollander@jasongeo.com POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON.......#1 in Reservoir Characterization The Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Since X doesn't support true 32 bit, the 24 bit will run as 32 bit with a framebuffer. I you run at 16 bit it will give the normal fps with gears. I'm tinkering around to see if I get more performance at the 24-->fb/32bit level. I'll post if any I have any sucess. Cheers. Curtis On Saturday 02 June 2001 04:38 am, Brian Dunaway wrote:
The latest drivers need to be 'activated' for 3D. The file tells you to install them in a particular order and then run the "switch2nvidia.glx"(sp?) file to activate the 3D.
I have tried it two ways both on fresh installs. I installed 7.2 personal edition straight out of the box and downloaded the drivers from Nvidia following their intructions. I get OpenGL support in my games no problem...but my GL screensavers and Blender both look for Mesa drivers. I also tried getting the software update from the Yast Control Center before I installed the Nvidia drivers from Nvidia....I get the same bugginess before and after I install the Nvidia drivers from Nvidia's site.
I did what it said and mine works fine on a very similar system to your own (V550, AMD450). Without the switch-file being run I got about 50fps in 'gears', afterwards I got over 400. (Just type "gears" in the console and that should run it - it prints the FPS in the console window so you can see if your 3D accel is working)
I ran gears and I get a little more than 600 FPS.
Brian D.
Curtis Rey wrote:
Since X doesn't support true 32 bit, the 24 bit will run as 32 bit with a framebuffer. I you run at 16 bit it will give the normal fps with gears. I'm tinkering around to see if I get more performance at the 24-->fb/32bit level. I'll post if any I have any sucess.
There is no such thing as "true 32 bit". Colors are represented as an RGB tripplet where each color can take up to 256 values, giving you 2^24 combinations. When a server runs at 32 bit depth, it still uses 24 bits, but uses 4 bytes to store the value. In 24 bit depth it will use only three bytes by a packing 4 pixels in 12 bytes. This trick involves packing an unpacking the values. 24 bit depth incurres in lower performance but saves memory, 32 bit is faster but wastes memory. -- Rafael
participants (11)
-
Ben Rosenberg -
Brian Dunaway -
Curtis Rey -
dids -
dieter -
Gerhard den Hollander -
Mark Hounschell -
Paul Abrahams -
Rafael Herrera -
Riever -
Ron Cordell