View previous topic :: View next topic |
Author |
Message |
chemical chris Tux's lil' helper

Joined: 17 Aug 2004 Posts: 80 Location: l33ds (uk)
|
Posted: Sun Nov 14, 2004 8:08 pm Post subject: Seting X to 16bpp depth to enable GLX on a Voodo3 |
|
|
after a lot of hard work and serching i am just a few steps away form getting glx and therefore quake3 running on my system, i have looked throu the xorg logs and found a reason why GLX isnt loading:
Code: |
(EE) TDFX(0): [dri] tdfx DRI not supported in 32 bpp mode, disabling DRI.
(II) TDFX(0): [dri] To use DRI, invoke the server using 16 bpp
(-depth 15 or -depth 16).
|
at this stage unfortunitally i draw a blank as to how to boot x using the -depth 16 command, as my system boots Xdm which loads GDM which boots Enlightenment i dont know what file runs the 'startx' command (im asssuming 'startx -depth 16' is the command i need to run)
if anyone can point me in the rite direction id be very happy. |
|
Back to top |
|
 |
eelke Guru


Joined: 17 May 2004 Posts: 406 Location: Earth, Netherlands, Friesland
|
Posted: Sun Nov 14, 2004 8:25 pm Post subject: |
|
|
You can change the bit depth of X permenantly in your XF86config look for DefaultDepth in the Screen Section. Or if you just want to change it temporary you can also go to the console do:
Code: | /etc/init.d/xdm stop |
and then manually start X with the startx command. I think in your case the right command would be
Code: | startx -- -depth 16 |
The -- tells the startx script that the options following should be passed to X. |
|
Back to top |
|
 |
chemical chris Tux's lil' helper

Joined: 17 Aug 2004 Posts: 80 Location: l33ds (uk)
|
Posted: Sun Nov 14, 2004 8:38 pm Post subject: |
|
|
but will that run automatically everyime i boot? |
|
Back to top |
|
 |
eelke Guru


Joined: 17 May 2004 Posts: 406 Location: Earth, Netherlands, Friesland
|
Posted: Sun Nov 14, 2004 9:01 pm Post subject: |
|
|
When you change the DefaultDepth in XF86config X will use that bit depth at each following boot /start. |
|
Back to top |
|
 |
chemical chris Tux's lil' helper

Joined: 17 Aug 2004 Posts: 80 Location: l33ds (uk)
|
Posted: Sun Nov 14, 2004 9:03 pm Post subject: |
|
|
ok, it worked, glxgears returns a segmentation fault. on restart it swiches off again.
i think i should point out im using xorg on the 2.6.8 kernel (all relovent drivers have been loaded into the kernel)
--getting logs to show y'all--...
oh.. thats NOT good
Code: |
bash-2.05b$ glxinfo
name of display: :0.0
Segmentation fault
....
bash-2.05b$ glxgears
Segmentation fault
....
(then from the logs)
(II) TDFX(0): [DRI] installation complete
(==) TDFX(0): Direct rendering enabled
(==) RandR enabled
....
bash-2.05b$ cat Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Failed to load module "speedo" (module does not exist, 0)
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension MIT-SCREEN-SAVER
|
i dontnhave the first clue what is wrong at the moment, can anyone help? |
|
Back to top |
|
 |
chemical chris Tux's lil' helper

Joined: 17 Aug 2004 Posts: 80 Location: l33ds (uk)
|
Posted: Sun Nov 14, 2004 10:06 pm Post subject: |
|
|
bump: corrected errors in xorg.conf
now glxgears runs at 400fps!!! but games still dont work..
over to the logs:
Code: |
(II) TDFX(0): [drm] created "tdfx" driver at busid "pci:0000:00:0c.0"
(II) TDFX(0): [drm] drmAddMap failed
(EE) TDFX(0): [dri] DRIScreenInit failed, disabling DRI.
(II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Dashed Lines
Offscreen Pixmaps
Driver provided NonTEGlyphRenderer replacement
Setting up tile and stipple cache:
32 128x128 slots
10 256x256 slots
|
heres some stuff from the dmesg that a mailing list said may help
Code: |
tdfxfb: Can't reserve smem
tdfxfb: probe of 0000:00:0c.0 failed with error -6
...
[drm] Initialized tdfx 1.0.0 20010216 on minor 0: 3Dfx Interactive, Inc. Voodoo 3
...
|
dose anyone know whats going on? |
|
Back to top |
|
 |
chemical chris Tux's lil' helper

Joined: 17 Aug 2004 Posts: 80 Location: l33ds (uk)
|
Posted: Sun Nov 14, 2004 10:44 pm Post subject: |
|
|
okay... i have tried all of the fixes deatailed in the other two threds concerning opengl... even though there for NVIDA i figured they MAY work, no joy
i havent used the kernel headers thing because i dont have a clue what that involves
in other news: glxinfo now dose this:
Code: |
bash-2.05b$ glxinfo | grep rendering
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x26
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2a
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2e
libGL warning: 3D driver claims to not support visual 0x31
libGL warning: 3D driver claims to not support visual 0x32
libGL warning: 3D driver claims to not support visual 0x35
libGL warning: 3D driver claims to not support visual 0x36
libGL warning: 3D driver claims to not support visual 0x39
libGL warning: 3D driver claims to not support visual 0x3a
libGL warning: 3D driver claims to not support visual 0x3d
libGL warning: 3D driver claims to not support visual 0x3e
libGL warning: 3D driver claims to not support visual 0x41
libGL warning: 3D driver claims to not support visual 0x42
direct rendering: No
|
im begining to loose hope that this system will ever run anything more then 2d games. |
|
Back to top |
|
 |
synapscape Apprentice


Joined: 07 Apr 2003 Posts: 234 Location: Germany
|
Posted: Mon Nov 15, 2004 3:56 pm Post subject: |
|
|
You might try searching for "voodoo dri" on these forums, help may be on the way
Your problem surely lies with glide, which is a real bitch. See this post.
bye,
markus _________________ mad season forever |
|
Back to top |
|
 |
|