Re: Bug#77511: [ketil@ii.uib.no: Bug#77511: relationships between packages for 3d support]

[Ketil Malde <ketil@ii.uib.no>]

"Marcelo E. Magallon" <mmagallo@debian.org> writes:

>  This is correct, it goes like this:

Looks like I'd got it right then.  I really recommend the DRI user
guide at sourceforge
        http://dri.sourceforge.net/DRIuserguide.html
it gives, I think, a nice overview.

>  * 3dfx DRM kernel module

Apparently, it doesn't work with DRM compiled into a monolithic
kernel?  When I change the default setting to 16bpp, I get another
signal 11.  I'm probably going to file another bug report, but I want
to play around a bit.  It seems like it's DRM that's the problem:

----8<---- X OUTPUT ----8<----

  (--) Chipset 3dfx Banshee found
    [...]
  (**) TDFX(0): Depth 16, (--) framebuffer bpp 16
    [...]
  (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 DDC supported
  (WW) TDFX(0): Failed to set up write-combining range (0xe2000000,0x2000000)
  (II) TDFX(0): Textures Memory 10.99 MB
  (0): [drm] created "tdfx" driver at busid "PCI:1:0:0"
  (0): [drm] added 4096 byte SAREA at 0xc9170000
  (0): [drm] mapped SAREA 0xc9170000 to 0x40017000
  (0): [drm] framebuffer handle = 0xe2000000
  (0): [drm] added 1 reserved context for kernel
  (EE) TDFX(0): TDFXDRIScreenInit failed (DRM version = 0.0.1, expected 1.0.x).  Disabling DRI.
  (0): [drm] failed to remove DRM signal handler

  Fatal server error:
  Caught signal 11.  Server aborting

----8<---- END ----8<----

I've reconfigured the kernel to use a module, but haven't gotten
around to compile/install/testing it yet.  Get back to you on this. 

Still using a Banshee and a 2.4 test kernel.

-kzm
-- 
If I haven't seen further, it is by standing in the footprints of giants