re:voodoo 5 DRM

[smarm]

Edit:
Move from hardware:

I cannot, for the life of me, get DRM to work with my voodoo5. Bus mastering is not enabled on my agp, which I think has something to do with it.

From the DRI users guide:

/snip

setpci -s 01:00.0 4.w

A hexadecimal value will be printed. Convert the least significant digit to binary. For example, if you see 3, that's 0011 in binary (bit two is 0). If you see 7, that's 0111 in binary (bit two is 1). In the first example, bus mastering is disabled. It's enabled in the second example.

The following shell script will enabled bus mastering for your graphics card and host bridge. Run it as root.

#!/bin/bash
dev=01:00.0 # change as appropriate
echo Enabling bus mastering on device $dev
setpci -s $dev 4.w=$(printf %x $((0x$(setpci -s $dev 4.w)|4)))
dev=00:00.0
echo Enabling bus mastering on host bridge $dev
setpci -s $dev 4.w=$(printf %x $((0x$(setpci -s $dev 4.w)|4)))

You can check if this worked by running the first setpci command again.

Code: Select all

 
 setpci -s 01:00.0 4.w 
 

returns 0003, which according to the above information, says that bus mastering is not enabled. Using the the enclosed shell script, does nothing.

Relevant information is as follows:

XFree86.0.log

Code: Select all

 
 
 (II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee, 
 (WW) TDFX: No matching Device section for instance (BusID PCI:1:0:1) found 
 (II) TDFX(0): Softbooting the board (through the int10 interface). 
 (II) TDFX(0): Primary V_BIOS segment is: 0xc000 
 (II) TDFX(0): Softbooting the board succeeded. 
 (II) TDFX(0): TDFXFindChips: found 2 chip(s) 
 (**) TDFX(0): Depth 16, (--) framebuffer bpp 16 
 (==) TDFX(0): RGB weight 565 
 (==) TDFX(0): Default visual is TrueColor 
 (--) TDFX(0): Chipset: "3dfx Voodoo5" 
 (--) TDFX(0): Linear framebuffer at 0xB8000000 
 (--) TDFX(0): MMIO registers at addr 0xC8000000 
 (--) TDFX(0): PIO registers at addr 0x6C00 
 (II) TDFX(0): DRAMINIT1 read 0x40202031, programming 0x40202031 (not Banshee) 
 (II) TDFX(0): TDFXInitChips: numchips = 1 
 (II) TDFX(0): TDFXInitChips: cfgbits = 0x00000005, initbits = 0x00000301 
 (II) TDFX(0): TDFXInitChips: mem0base = 0xc8000000, mem1base = 0xb8000008 
 (II) TDFX(0): TDFXInitChips: mem0size = 0x02000000, mem1size = 0x08000000 
 (II) TDFX(0): TDFXInitChips: mem0bits = 0x00000005, mem1bits = 0x00000000 
 (II) TDFX(0): TDFXInitChips: cfgbits = 0x00000005 
 (II) TDFX(0): TDFXInitChips: MMIOAddr[0] = 0xc8000000 
 (II) TDFX(0): TDFXInitChips: LinearAddr[0] = 0xb8000008 
 (**) TDFX(0): VideoRAM: 65536 kByte Mapping 131072 kByte 
 (==) TDFX(0): Using gamma correction (1.0, 1.0, 1.0) 
 (II) TDFX(0): Monitor0: Using hsync range of 30.00-70.00 kHz 
 (II) TDFX(0): Monitor0: Using vrefresh range of 50.00-160.00 Hz 
 (II) TDFX(0): Clock range: 12.00 to 350.00 MHz 
 
 <snip> 
 
 (==) TDFX(0): DPI set to (75, 75) 
 (**) TDFX(0): ShowCache Disabled 
 (**) TDFX(0): video key default 0x1e 
 (II) TDFX(0): initializing int10 
 (II) TDFX(0): Primary V_BIOS segment is: 0xc000 
 (II) TDFX(0): VESA BIOS detected 
 (II) TDFX(0): VESA VBE Version 3.0 
 (II) TDFX(0): VESA VBE Total Mem: 16384 kB 
 (II) TDFX(0): VESA VBE OEM: 3dfx Interactive, Inc. 
 (II) TDFX(0): VESA VBE OEM Software Rev: 1.0 
 (II) TDFX(0): VESA VBE OEM Vendor: 3dfx Interactive, Inc. 
 (II) TDFX(0): VESA VBE OEM Product: Voodoo5 5500 
 (II) TDFX(0): VESA VBE OEM Product Rev: Version 1.00 
 (II) TDFX(0): VESA VBE DDC supported 
 (II) TDFX(0): VESA VBE DDC Level 2 
 (II) TDFX(0): VESA VBE DDC transfer in appr. 8 sec. 
 (II) TDFX(0): VESA VBE DDC read successfully 
 (II) TDFX(0): Manufacturer: KDS Model: 1745 Serial#: 18019734 
 (II) TDFX(0): Year: 2001 Week: 18 
 (II) TDFX(0): EDID Version: 1.3 
 (II) TDFX(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V 
 (II) TDFX(0): Sync: Separate Composite 
 (II) TDFX(0): Max H-Image Size [cm]: horiz.: 31 vert.: 23 
 (II) TDFX(0): Gamma: 2.50 
 (II) TDFX(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display 
 (II) TDFX(0): redX: 0.625 redY: 0.342 greenX: 0.280 greenY: 0.595 
 (II) TDFX(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298 
 (II) TDFX(0): Supported VESA Video Modes: 
 (II) TDFX(0): 720x400@70Hz 
 (II) TDFX(0): 720x400@88Hz 
 (II) TDFX(0): 640x480@60Hz 
 (II) TDFX(0): 640x480@67Hz 
 (II) TDFX(0): 640x480@72Hz 
 (II) TDFX(0): 640x480@75Hz 
 (II) TDFX(0): 800x600@56Hz 
 (II) TDFX(0): 800x600@60Hz 
 (II) TDFX(0): 800x600@72Hz 
 (II) TDFX(0): 800x600@75Hz 
 (II) TDFX(0): 832x624@75Hz 
 (II) TDFX(0): 1024x768@87Hz (interlaced) 
 (II) TDFX(0): 1024x768@60Hz 
 (II) TDFX(0): 1024x768@70Hz 
 (II) TDFX(0): 1024x768@75Hz 
 (II) TDFX(0): Manufacturer's mask: 0 
 (II) TDFX(0): Supported Future Video Modes: 
 (II) TDFX(0): #0: hsize: 1024 vsize 768 refresh: 85 vid: 22881 
 (II) TDFX(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853 
 (II) TDFX(0): #2: hsize: 640 vsize 480 refresh: 85 vid: 22833 
 (II) TDFX(0): #3: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 
 (II) TDFX(0): Monitor name: Visual Sensat 
 (II) TDFX(0): Monitor name: ions VS-7i 
 (II) TDFX(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 70 kHz, PixClock max 110 MHz 
 (II) TDFX(0): Serial No: AAB18019734 
 (==) TDFX(0): Write-combining range (0xb8000000,0x8000000) 
 (II) TDFX(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x6900 
 (II) TDFX(0): Changing back offset from 0x03cff000 to 0x03cfe000 
 (II) TDFX(0): Textures Memory 58.58 MB 
 (II) TDFX(0): Cursor Offset: [0x00000000,0x00001000) 
 (II) TDFX(0): Fifo Offset: [0x00001000, 0x00041000) 
 (II) TDFX(0): Front Buffer Offset: [0x00041000, 0x0026A000) 
 (II) TDFX(0): Texture Offset: [0x0026A000, 0x03CFE000) 
 (II) TDFX(0): BackOffset: [0x03CFE000, 0x03E7E000) 
 (II) TDFX(0): DepthOffset: [0x03E7F000, 0x03FFF000) 
 (II) TDFX(0): Minimum 338, Maximum 3327 lines of offscreen memory available 
 (II) TDFX(0): [dri] VideoRAM = 65536, VirtualXres = 1024, VirtualYres= 768, 
 (II) TDFX(0): [drm] drmOpen failed 
 (EE) TDFX(0): [dri] DRIScreenInit failed, disabling DRI. 
 (II) TDFX(0): Using XFree86 Acceleration Architecture (XAA) 
 (==) TDFX(0): Backing store disabled 
 (==) TDFX(0): Silken mouse enabled 
 (**) TDFX(0): DPMS enabled 
 (==) TDFX(0): Direct rendering disabled 
 

XF86Config

Code: Select all

 
 Section "ServerLayout" 
 Identifier "XFree86 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/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 "extmod" 
 Load "dri" 
 Load "dbe" 
 Load "record" 
 Load "xtrap" 
 Load "glx" 
 Load "speedo" 
 Load "type1" 
 EndSection 
 
 Section "InputDevice" 
 Identifier "Keyboard0" 
 Driver "keyboard" 
 Option "XkbModel" "pc104" 
 Option "XkbLayout" "us" 
 EndSection 
 
 Section "InputDevice" 
 Identifier "Mouse0" 
 Driver "mouse" 
 Option "Protocol" "auto" 
 Option "Device" "/dev/mouse" 
 Option "ZAxisMapping" "4 5" 
 EndSection 
 
 Section "Monitor" 
 #DisplaySize 310 230 # mm 
 Identifier "Monitor0" 
 VendorName "KDS" 
 ModelName "ions VS-7i" 
 Option "DPMS" 
 HorizSync 30-70 
 VertRefresh 50-160 
 
 # ModeLine "1152x864/78Hz" 110 1152 1240 1324 1552 864 864 876 908 
 EndSection 
 
 Section "Device" 
 ### Available Driver options are:- 
 ### Values: <i>: integer, <f>: float, <bool>: "True"/"False", 
 ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" 
 ### [arg]: arg optional 
 #Option "NoAccel" # [<bool>] 
 #Option "SWcursor" # [<bool>] 
 #Option "Dac6Bit" # [<bool>] 
 #Option "Dac8Bit" # [<bool>] 
 #Option "DMAForXv" # [<bool>] 
 #Option "ForcePCIMode" # [<bool>] 
 #Option "CCEPIOMode" # [<bool>] 
 #Option "CCENoSecurity" # [<bool>] 
 #Option "CCEusecTimeout" # <i> 
 #Option "AGPMode" # <i> 
 #Option "AGPSize" # <i> 
 #Option "RingSize" # <i> 
 #Option "BufferSize" # <i> 
 #Option "Display" # <str> 
 #Option "PanelWidth" # <i> 
 #Option "PanelHeight" # <i> 
 #Option "ProgramFPRegs" # [<bool>] 
 #Option "UseFBDev" # [<bool>] 
 #Option "VideoKey" # <i> 
 #Option "ShowCache" # [<bool>] 
 
 Identifier "Card0" 
 # Driver "ati" 
 # Driver "vesa" 
 Driver "tdfx" 
 VideoRam 65536 
 VendorName "Generic" 
 BoardName "Voodoo 5 5500" 
 BusID "PCI:1:0:0" 
 
 EndSection 
 
 Section "Screen" 
 Identifier "Screen0" 
 Device "Card0" 
 Monitor "Monitor0" 
 DefaultDepth 16 
 
 SubSection "Display" 
 Depth 1 
 Modes "1152x864/78Hz" "1024x768" "800x600" "640x480" 
 Virtual 0 0 
 EndSubSection 
 SubSection "Display" 
 Depth 4 
 Modes "1152x864/78Hz" "1024x768" "800x600" "640x480" 
 Virtual 0 0 
 EndSubSection 
 SubSection "Display" 
 Depth 8 
 Modes "1152x864/78Hz" "1024x768" "800x600" "640x480" 
 Virtual 0 0 
 EndSubSection 
 SubSection "Display" 
 Depth 15 
 Modes "1152x864/78Hz" "1024x768" "800x600" "640x480" 
 Virtual 0 0 
 EndSubSection 
 SubSection "Display" 
 Depth 16 
 Modes "1152x864/78Hz" "1024x768" "800x600" "640x480" 
 Virtual 0 0 
 EndSubSection 
 
 SubSection "Display" 
 Depth 24 
 Modes "1280x1024/70Hz" "1152x864" "1024x768" "800x600" "640x480" 
 
 # Modes "1152x864/78Hz" "1024x768" "800x600" "640x480" 
 
 Virtual 0 0 
 EndSubSection 
 
 SubSection "Display" 
 Depth 32 
 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" "320x240" 
 Virtual 0 0 
 EndSubSection 
 
 
 EndSection 
 
 Section "dri" 
 Mode 0666 
 EndSection 
 
 Section "ServerFlags" 
 
 EndSection 
 

glxinfo

Code: Select all

 
 name of display: :0.0 
 display: :0 screen: 0 
 direct rendering: No 
 server glx vendor string: SGI 
 server glx version string: 1.2 
 server glx extensions: 
 GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context 
 client glx vendor string: SGI 
 client glx version string: 1.2 
 client glx extensions: 
 GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context 
 GLX extensions: 
 GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context 
 OpenGL vendor string: Mesa project: www.mesa3d.org 
 OpenGL renderer string: Mesa GLX Indirect 
 OpenGL version string: 1.3 Mesa 4.0.4 
 OpenGL extensions: 
 GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp, 
 GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
 GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3, 
 GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color, 
 GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add, 
 GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, 
 GL_EXT_texture_lod_bias 
 glu version: 1.3 
 glu extensions: 
 GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess 
 
 visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav 
 id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat 
 ---------------------------------------------------------------------- 
 0x23 16 tc 1 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 0 0 None 
 0x24 16 tc 1 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 None 
 0x25 16 tc 1 16 0 r y . 5 6 5 8 0 16 8 16 16 16 16 0 0 None 
 0x26 16 tc 1 16 0 r . . 5 6 5 8 0 16 8 16 16 16 16 0 0 None 
 0x27 16 dc 1 16 0 r y . 5 6 5 0 0 16 0 0 0 0 0 0 0 None 
 0x28 16 dc 1 16 0 r y . 5 6 5 0 0 16 8 16 16 16 0 0 0 None 
 0x29 16 dc 1 16 0 r y . 5 6 5 8 0 16 8 16 16 16 16 0 0 None 
 0x2a 16 dc 1 16 0 r . . 5 6 5 8 0 16 8 16 16 16 16 0 0 None 
 

ldd /usr/X11R6/bin/glxinfo

Code: Select all

 
 libGLU.so.1 => /usr/lib/libGLU.so.1 (0x4002a000) 
 libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x400a2000) 
 libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4010c000) 
 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4011a000) 
 libpthread.so.0 => /lib/libpthread.so.0 (0x401f7000) 
 libm.so.6 => /lib/libm.so.6 (0x40248000) 
 libc.so.6 => /lib/libc.so.6 (0x4026a000) 
 libstdc++.so.5 => /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libstdc++.so.5 (0x40398000) 
 libgcc_s.so.1 => /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.2/libgcc_s.so.1 (0x40451000) 
 libdl.so.2 => /lib/libdl.so.2 (0x4045a000) 
 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000) 
 

slocate tdfx

Code: Select all

 
 /usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm/tdfx_drv.c 
 /usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm/tdfx.h 
 /usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm-4.0/tdfx_drv.c 
 /usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm-4.0/tdfx_context.c 
 /usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm-4.0/tdfx_drv.h 
 /usr/src/linux-2.4.22-gentoo-r5/drivers/video/tdfxfb.c 
 /usr/X11R6/lib/modules/dri/tdfx_dri.so 
 /usr/X11R6/lib/modules/drivers/tdfx_drv.o 
 

Also I've browsed the forums and found several posts, but damned if I can find any obvious docs on why i should do what they suggest.

http://forums.gentoo.org/viewtopic.p ... voodoo5

What is glut? Why do I need it? What is mesa-glu? Why do I need it, according to the documents on the mesa web site say that all the mesa code I need for this video card are built into XFree86. I have the correct version of glide (Why do I need...?):

Searching...
[ Results for search key : glide ]
[ Applications found : 1 ]

* media-libs/glide-v3
Latest version available: 3.10-r3
Latest version installed: 3.10-r3
Size of downloaded files: 3,566 kB
Homepage: http://glide.sourceforge.net/
Description: Hardware support for the voodoo3, voodoo4 and voodoo5
License: 3DFX

My kernel is compiled correctly (according to the hardware acceleration HOW-TO). I hope someone can see / suggest something I've missed.

Peter

[synapscape]

Peter,

Glide is needed for all Voodoo-based cards. It is part of the 3D-rendering-pipeline:

Client -> OpenGL / GLX -> Glide as HAL (DRI) -> hardware

See the DRI-Website for more information about Glide and DRI.

IIRC there might be problems with glide and xfree, which could be solved by reemerging xfree AFTER glide: xfree -> glide -> xfree again. Umm, i just want to point that out, because it is already mentioned in the post you referenced to and which i just read.

Mesa and mesa-glu are not needed. I have glut installed on my system, but i cannot tell you if it was/is necessary. Sorry, but it's too late for me (2:30 in the night) to figure that out...

Make sure you have just "3dfx" in your use flags (no "voodoo3"). You should also emerge "xfree-drm", but i guess you already did that.

As a note, i have a voodoo3500 in my system, not a voodoo5. Too bad that the ViVo features are useless under linux...

HTH and good luck!

[smarm]

IIRC there might be problems with glide and xfree, which could be solved by reemerging xfree AFTER glide: xfree -> glide -> xfree again. Umm, i just want to point that out, because it is already mentioned in the post you referenced to and which i just read.

Well it didn't make a great deal of sense to me to emerge xfree twice, especially when I haven't changed anything in between compiles. But you're saying there might be problems? Of what nature? Can you refrence a web site? A post?

Thanks for the tip. I'll try it out.

Peter

[smarm]

No, I'm still not Directly Rendering. Though my konqueror does seem to hard lock my system now. Wierd that. Anyway, anyone else?

glxinfo -

Code: Select all

name of display: :0.0
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
OpenGL extensions:
    GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
    GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
    GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
    GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
    GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x23 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x24 16 tc  1 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 None
0x25 16 tc  1 16  0 r  y  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
0x26 16 tc  1 16  0 r  .  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
0x27 16 dc  1 16  0 r  y  .  5  6  5  0  0 16  0  0  0  0  0  0 0 None
0x28 16 dc  1 16  0 r  y  .  5  6  5  0  0 16  8 16 16 16  0  0 0 None
0x29 16 dc  1 16  0 r  y  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None
0x2a 16 dc  1 16  0 r  .  .  5  6  5  8  0 16  8 16 16 16 16  0 0 None

XFree86.0.log

Code: Select all

<snip>

grep EE /var/log/XFree86.0.log
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) TDFX(0): [dri] DRIScreenInit failed, disabling DRI.

Peter

[synapscape]

Problems with Xfree and Glide:

I cannot remember correctly where i read about this, you may find more info in these forums when searching for glide. I guess it had something to do with linking against the correct libraries/header files ( ? ). Anyway, the correct way to emerge glide and xfree should be:

try unemerging everything

then emerge everything in this order

xfree {with no voodoo3 or 3dfx in the USE varable}
glide {with voodoo3 and 3dfx in the use varable}
xfree {leave the 3dfx and voodoo3 for this one}
glut {leave 3dfx and voodoo3 for this and leave the libgilde3.la file alone}

This was posted by whytewolf here

Another thing came to my mind:
1) XF86Config should be case-insensitive, but who knows?!
-> Change Section "dri" to Section "DRI"

Make sure the "files" under /dev/dri have the proper permissions (crw rw rw).

2) Did you compile the tdfx-driver as a module? You have to manually load it then. Sometimes it helps to have agpgart included in the kernel than having it as a module.

Good Luck!

EDIT and PS: YAY, i am an apprentice now! hip-hop-hooray

[smarm]

Another thing came to my mind:
1) XF86Config should be case-insensitive, but who knows?!
-> Change Section "dri" to Section "DRI"

The module and the section identifier must be the same, case wise, from what I've read. I'm trying it though, no harm no foul if its correct.

Make sure the "files" under /dev/dri have the proper permissions (crw rw rw).

According to the DRI website the xfree-drm doesn't use those files anymore. But I did check and it is 777, so no problems there.

2) Did you compile the tdfx-driver as a module? You have to manually load it then. Sometimes it helps to have agpgart included in the kernel than having it as a module.

I didn't see any tdfx module in the kernel? Agpart is already hard compiled in and it is active at boot time.

Code: Select all

dmesg | grep agp
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: Detected SiS 735 chipset
agpgart: AGP aperture is 128M @ 0xd0000000

This line of inquery has produced some results (I hope), your talk of modules led me to insmod, thence to modprobe and /etc/modules.conf. Grepping modules.conf for "tdfx" produces no results and there is no mention in /etc/modules.d/ of "tdfx" either. There is however a mention of svgalib, some sort of video driver (something) I assume. So it seems my modules configurations knows nothing about my DRM module. Which is:

Code: Select all

/usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm/tdfx_drv.c
/usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm/tdfx.h
/usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm-4.0/tdfx_drv.c
/usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm-4.0/tdfx_context.c
/usr/src/linux-2.4.22-gentoo-r5/drivers/char/drm-4.0/tdfx_drv.h
/usr/src/linux-2.4.22-gentoo-r5/drivers/video/tdfxfb.c
[b]/usr/X11R6/lib/modules/dri/tdfx_dri.so[/b]
/usr/X11R6/lib/modules/drivers/tdfx_drv.o
/usr/X11R6/man/man4/tdfx.4.gz

It is the "tdfx_dri.so" correct?

Modprobe also led me to depmod and its respective "conf" file:

Code: Select all

more /lib/modules/2.4.22-gentoo-r5/modules.dep

/lib/modules/2.4.22-gentoo-r5/kernel/drivers/net/dummy.o:

/lib/modules/2.4.22-gentoo-r5/kernel/drivers/net/e100/e100.o:

/lib/modules/2.4.22-gentoo-r5/kernel/drivers/net/sis900.o:      /lib/modules/2.4.22-gentoo-r5/kernel/lib/crc32.o

/lib/modules/2.4.22-gentoo-r5/kernel/lib/crc32.o:

/lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/alg/ipsec_aes.o: /lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/ipsec.o

/lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/alg/ipsec_serpent.o:     /lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/ipse
c.o

/lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/alg/ipsec_twofish.o:     /lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/ipse
c.o

/lib/modules/2.4.22-gentoo-r5/kernel/net/ipsec/ipsec.o:

/lib/modules/2.4.22-gentoo-r5/misc/svgalib_helper.o:

Again no mention of my "tdfx" driver, but I didnt compile any into the kernel, so this may be a blind lead. Of course that could be mistake.

Trying to insert the module with modprobe returns:

Code: Select all

modprobe -vn /usr/X11R6/lib/modules/dri/tdfx_dri.so

modprobe: Can't locate module /usr/X11R6/lib/modules/dri/tdfx_dri.so

Which I find extremely odd. It seems the driver specified is not the correct module, but I can find no others that work. Trying to insert the ".o" file returns a similar error.

Code: Select all

modprobe -vn /usr/X11R6/lib/modules/drivers/tdfx_drv.o

modprobe: Can't locate module /usr/X11R6/lib/modules/drivers/tdfx_drv.o

Hopefully that will shed some light on the problem.

Peter

[synapscape]

3d-gfx-drivers come with two modules: one for the kernel and one for XFree.

Code: Select all

/lib/modules/2.4.22-ck2/kernel/drivers/char/drm/tdfx.o
/usr/X11R6/lib/modules/dri/tdfx_dri.so
/usr/X11R6/lib/modules/drivers/tdfx_drv.o

The first one is the kernel driver, the "direct rendering manager" for the voodoo-card. The second one is the user-space ( ?, i may be wrong but i think it's userspace) counterpart of the kernel-driver. The last one is the 2D-makeitshowscreen-driver for Xfree.

It seems to me that you forgot to emerge "xfree-drm"?! Please emerge this package to have the latest drivers for your voodoo5. It will install the appropriate modules, at least the dri/drm parts. With this package, there is no need to compile support for tdfx into your kernel. You also have to edit /etc/modules.autoload.d/kernel-2.4 to contain a line with "tdfx" in it (and nothing else!). With that, the module will be autoloaded on system-startup.

You can see which modules are loaded with "lsmod". Check if you got a module called tdfx loaded. if not, try "modprobe tdfx" and if it fails, emerge "xfree-drm" and "modprobe tdfx" again when it's finished. Shouldn't take that long to compile.

Good Luck!

[smarm]

I installed xfree-drm before posting, so no worries there. Your suggestion about manually inserting the module at boot time has yielded some results.

[code]

grep EE /var/log/XFree86.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(EE) Failed to load module "DRI" (module does not exist, 0)

grep WW /var/log/XFree86.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(WW) Warning, couldn't open module DRI
(WW) TDFX: No matching Device section for instance (BusID PCI:1:0:1) found

[/code]

So now XFree can't find the DRI module rather than just failing to start. Some other useful informaiton:

lsmod

[code]
lsmod
Module Size Used by Not tainted
sis900 13612 1
crc32 2896 0 [sis900]
tdfx 36912 0 (unused)


[/code]

The module is there but unused?!

glxinfo

[code]
glxinfo
name of display: :0.0
Xlib: extension "XFree86-DRI" missing on display ":0.0". <- here
display: :0 screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
GLX extensions:
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4
OpenGL extensions:
GL_ARB_imaging, GL_ARB_multitexture, GL_ARB_texture_border_clamp,
GL_ARB_texture_cube_map, GL_ARB_texture_env_add,
GL_ARB_texture_env_combine, GL_ARB_texture_env_dot3,
GL_ARB_transpose_matrix, GL_EXT_abgr, GL_EXT_blend_color,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_lod_bias
glu version: 1.3
glu extensions:
GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav
id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat
----------------------------------------------------------------------
0x23 24 tc 1 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x24 24 tc 1 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x25 24 tc 1 24 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x26 24 tc 1 24 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x27 24 dc 1 24 0 r y . 8 8 8 0 0 16 0 0 0 0 0 0 0 None
0x28 24 dc 1 24 0 r y . 8 8 8 0 0 16 8 16 16 16 0 0 0 None
0x29 24 dc 1 24 0 r y . 8 8 8 8 0 16 8 16 16 16 16 0 0 None
0x2a 24 dc 1 24 0 r . . 8 8 8 8 0 16 8 16 16 16 16 0 0 None

[/code]

Now there's an interesting bit, at least its trying to start the DRM, but can't find the module. So the next step appears to be to locate module and load it at boot, yes?

[quote]
3d-gfx-drivers come with two modules: one for the kernel and one for XFree.


Code:



/lib/modules/2.4.22-ck2/kernel/drivers/char/drm/tdfx.o
/usr/X11R6/lib/modules/dri/tdfx_dri.so
/usr/X11R6/lib/modules/drivers/tdfx_drv.o



The first one is the kernel driver, the "direct rendering manager" for the voodoo-card.The second one is the user-space ( ?, i may be wrong but i think it's userspace) counterpart of the kernel-driver. The last one is the 2D-makeitshowscreen-driver for Xfree.

[/quote]

So if I locate and use both sets of drivers then I should have DRM, correct?

An aside. Shouldn't XFree be doing all of this for me? Why must I manually load my video driver at boot, isn't there some facility for detecting and inserting the correct driver at load time? An Xfree -configure does correctly auto detect the driver to use, so why wasn't I using it the first time? And now that I have xfree-drm installed correctly (I would assume) why doesn't Xfree insert the superior driver? Its all very confusing. It seems that something as basic as video drivers for (admitedly) older hardware should be included in Xfree, rendering video being its primary function after alll. I just don't understand why this is such a hastle.

Peter

[synapscape]

ok....

Step by step:

1) Make sure that:
- agpgart is compiled into the kernel (not as a module)
- there is NO XFree86 DRI enabled in your kernel. Nada. Not even as a module. This is ALL provided by package "xfree-drm"

2) you have already emerged "xfree-drm", but if you compile a new kernel or recompile the current, you'll have to reemerge that package! Add a line containing "tdfx" to the config-file /etc/modules.autoload.d/kernel-2.4. This autoloads the module tdfx (the dri module) on system startup.

3) You XF86Config should look like this:

Code: Select all

Section "Module"
    Load        "dbe"   # Double buffer extension

    SubSection  "extmod"
#      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the Type1 and FreeType font modules
    Load        "extmod"
#    Load        "type1"
    Load  "freetype"
    Load        "speedo"
    Load        "bitmap"
#    Load       "pex5"

#    Load       "xie"
    Load        "dri"
    Load        "record"
    Load        "xtrap"

# This loads the GLX module
    Load       "glx"
EndSection

Section "DRI"
        Mode 0666
EndSection

Section "Device"
    Identifier  "Voodoo3500TV"
    VendorName  "3DFX"
    BoardName     "Voodoo3500"
    Driver     "tdfx"
    BusID      "PCI:1:0:0"
    VideoRam    16384
EndSection

Section "Screen"
    Identifier  "Standard"
    Device      "Voodoo3500TV"
    Monitor     "Sony200ES"
    DefaultDepth 16

    Subsection "Display"
        Depth       8
        Modes       "1024x768" "800x600" "640x480" "320x200"
        ViewPort    0 0
                Virtual 0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1024x768" "800x600" "640x480" "320x200"
        ViewPort    0 0
                Virtual 0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1024x768" "800x600" "640x480" "320x200"
        ViewPort    0 0
                Virtual 0 0
    EndSubsection
EndSection

I snipped some lines to include only the necessary. Although the voodoo5 is able to do high resolutions in 24Bit+, set DefaultDepth to 16 AND choose a resolution of 1024x768. The driver has to be able to cope with that. Later you can try and "stress" things with higher/odd resolutions. For now keep it simple!

To answer your questions: It shouldn't be that hard to enable 3D with a voodoo. Mine worked like a breeze. Basically, there are just these three points to follow and voila! You have to autoload the kernel-module tdfx because this is part of the kernel, not X.

Something is borked in your system.... But keep trying!

Good Luck!

[smarm]

Agpart is definetly part of the kernel:

Code: Select all

dmesg | grep agp
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: Detected SiS 735 chipset
agpgart: AGP aperture is 128M @ 0xd0000000

DRI is definetley disabled in the kernel, made double sure of that myself. X-free drm is compiled fresh for this video card and kernel (did it twice with VIDEO_CARDS="3dfx"). modules.autoload is configured correctly:

Code: Select all

more /etc/modules.autoload.d/kernel-2.4
# /etc/modules.autoload.d/kernel-2.4:  kernel modules to load when system boots.
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/modules.autoload.d/kernel-2.4,v 1.1 2003/03/09 09:06:23 azarah Exp $
#
# Note that this file is for 2.4 kernels.  If you need different modules
# for a 2.5 kernel, you can create /etc/modules.autoload.d/kernel-2.5
#
# Add the names of modules that you'd like to load when the system
# starts into this file, one per line.  Comments begin with # and
# are ignored.  Read man modules.autoload for additional details.

# For example:
# 3c59x

tdfx

My XF86Config is nearly identical to yours:

Code: Select all

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

       Identifier  "Card0"
#       Driver      "ati"
#       Driver      "vesa"
        Driver      "tdfx"
        VideoRam    65536
        VendorName  "Generic"
        BoardName   "Voodoo5 5500"
        BusID       "PCI:1:0:0"

EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultDepth 16

        SubSection "Display"
                Depth     16

                Modes       "1024x768" "800x600" "640x480"

#               Modes       "1152x864/78Hz" "1024x768" "800x600" "640x480"
                ViewPort    0 0
                Virtual 0 0
        EndSubSection

        SubSection "Display"
                Depth     24
                Modes       "1280x1024/70Hz" "1152x864" "1024x768" "800x600" "640x480"

#               Modes       "1152x864/78Hz" "1024x768" "800x600" "640x480"

                Virtual 0 0
        EndSubSection

EndSection

Section "DRI"
    Mode 0666
 EndSection

Section "ServerFlags"

EndSection

Edit:

No DRM:

Code: Select all

glxinfo | grep render
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

Though grepping my /var/log/XFree86.0.log does show that the DRM is not being disabled anymore:

Code: Select all

grep EE /var/log/XFree86.0.log
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
peter@slut mnt $ grep WW /var/log/XFree86.0.log
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(WW) TDFX: No matching Device section for instance (BusID PCI:1:0:1) found

I find that last line troubling, why would it search on PCI:1:0:1? I specifically configured my video card at PCI:1:0:0, yet it continues to probe at 101 no matter what I do. Strange, maybe that could be my problem?

Also you said there were high resolutions at 32bit color? I have yet to get XFree working with 32bit color, it says the driver can't support any resolution at that depth?!

Seem we've run out of options. The next step I suppose is to post debugging information? Or did I truly find a bug in Xfree, or the tdfx driver? Either way, I need to know how to diagnose the problem with more depth than merely the XFree86.log.

Peter

[smarm]

Some more information:

XFree86.0.log:

Code: Select all

(--) PCI:*(1:0:0) 3Dfx Interactive, Inc. Voodoo 4 / Voodoo 5 rev 1, Mem @ 0xc8000000/26, 0xb8000000/27, I/O @ 0x6c00/8, BIOS
 @ 0xcfef0000/16
(--) PCI: (1:0:1) 3Dfx Interactive, Inc. Voodoo 4 / Voodoo 5 rev 1, I/O @ 0xfffffe00/8

<snip>

(II) TDFX(0): [dri] VideoRAM = 65536, VirtualXres = 1024, VirtualYres= 768,
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 5, (OK)
drmGetBusid returned ''
(II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"

<snip>

II) TDFX(0): [drm] installed DRM signal handler
(II) TDFX(0): [DRI] installation complete
(==) TDFX(0): Direct rendering enabled <---------------!

So what exactly is going on? The log and glxinfo disagree on whether its really directly rendering. Also it seems to detect another voodoo5 at 101?! Wierd stuff.

Peter

[synapscape]

The "mysterious" entry "PCI:1:0:1" reflects that you got 2 vsa100 chips on your voodoo5. I don't remember correctly how 3DFX handled that two chips on the card as AGP can only talk to one chip. Yes, if you got a gfx board with two identical chips on it you'll have to do some tricks to get both chips working. IIRC one chip is master and the other one is slave.

Anyway, AGP is treated as PCI until software activates and uses AGP features. The meaning of those numbers is: PCI:Bus:Device:Function. AGP is seen as the second "bus" (although AGP is an interface, not a bus) with PCI being the first. The device-part identifies a device on the pci-bus; with AGP, this is always 0, as there can be only one device. Every device on a pci-bus gets a number assigned to it. Please note that this has nothing to do with IRQs. The function-part is there to distinguish multiple devices on one card, i.e. the two vsa100 chips or, say, a NIC with 4 ports on it. I have seen some weird ASUS SCSI-adapter which also got sound onboard, this is an ideal example where you have two devices ( = functions) on one card.

Having explained that: Only one vsa100 chip is used under linux. So don't worry about the warnings about the second chip. Unfortunatly a voodoo5 isn't running at full power under linux, and i don't think that this is ever going to change. 3DFX collapsed to early to have fully working drivers for the v5. It behaves like a voodoo4 under linux, which only has one vsa100.

But it's still weird that there's no direct rendering...

Well:
a) do you have just "3dfx" in your use flags? I mean no "voodoo3"?
b) try "opengl-update xfree", just to make sure...

Otherwise, i am at the end of my wisdom. Sorry

Good luck!

[smarm]

a) do you have just "3dfx" in your use flags? I mean no "voodoo3"?
b) try "opengl-update xfree", just to make sure...

Definetly no voodoo3 flag set in use, the only flag I have in fact is 3dfx. Opengl-update doesn't do anything as far as I can see. I acutally have a bit less performance under glxgears (200 - 150fps down from 300 - 200).

I followed the instructions on this topic:

http://forums.gentoo.org/viewtopic.php?t=2647

I seem to have broken my glxinfo as well:

Code: Select all

glxinfo
glxinfo: relocation error: /usr/lib/libGLU.so.1: undefined symbol: __gxx_personality_v0

which glxinfo
/usr/X11R6/bin/glxinfo

The mesa-glu was masked, so no surprise that it broke something, but using the glxgears metric I should be able to tell if DRI is enabled or not, so its not. Of course the log says different, but still no performance increases:

Code: Select all

(II) TDFX(0): [dri] VideoRAM = 65536, VirtualXres = 1024, VirtualYres= 768,
(II) TDFX(0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
(II) TDFX(0): [drm] added 8192 byte SAREA at 0xd0880000
(II) TDFX(0): [drm] mapped SAREA 0xd0880000 to 0x40026000
(II) TDFX(0): [drm] framebuffer handle = 0xb8000000
(II) TDFX(0): [drm] added 1 reserved context for kernel
(II) TDFX(0): [drm] Registers = 0xc8000000
(II) TDFX(0): visual configs initialized
(II) TDFX(0): Using XFree86 Acceleration Architecture (XAA)
(==) TDFX(0): Backing store disabled
(==) TDFX(0): Silken mouse enabled
(**) TDFX(0): DPMS enabled
(II) TDFX(0): X context handle = 0x00000001
(II) TDFX(0): [drm] installed DRM signal handler
(II) TDFX(0): [DRI] installation complete
(==) TDFX(0): Direct rendering enabled <-----------

A thought occured to me while I was browsing http://www.voodoofiles.com/, in their forums they speak of three versions of the bios on the card itself. The 1.06, or stock bios, the 1.16 or last revision bios, and the 1.18 or hacked bios. I have the 1.06, the stock bios. I haven't used this video card in some time, is it possible that the TDFX driver was designed around this last bios update? I could flash my card with the 1.16, but I see no reason to unless I know for certain that the outdated bios is the problem.

As it stands i'm out of ideas.

Peter

[synapscape]

Oh well.....

I don't think that the BIOS version really does matter and i agree with you that updating the cards BIOS should be the last thing to try.

As i said before something must be really broken on your system. It seems that the kernel module is ok. At least the reports from the Xfree-log suggest that. I think the problem lies somewhere between X free, glide and glut.

You'll hate me for this , but: I'd unmerge everything (Xfree, glide, glut, any mesa-stuff) and start over fresh. Your broken glxinfo also suggests rebuilding all.

You asked me why one has to build Xfree twice with glide. See this lfs-hint for some info.

Anyway, you really did emerge xfree, glide, xfree with the appropriate use-flags i mentioned above? The trick seems to be that Xfree is build without specific card support first, then glide is emerged with correct use-flags, then xfree again with the same use-flags. And don't emerge anything mesa-related! xfree, glide and glut is all you need!

This is all very odd...

[POLAX]

As i said before something must be really broken on your system. It seems that the kernel module is ok. At least the reports from the Xfree-log suggest that.

I'd have to disagree here. I'm getting the same problem and I haven't done anything unusual on my gentoo build.