X.org 6.8.x includes the new "voodoo" driver for Voodoo 1 & 2 cards. The driver is, however, not being built during a normal emerge of xorg-x11. The 3DFX use flag is related to the tdfx driver, I think. If this is not the case, you get a chance to slap me. I will try to re-emerge xorg with the flag but it'll take a while (old PC). Reproducible: Always Steps to Reproduce: 1.emerge xorg-x11 2. 3. Actual Results: X.org builds nicely but without the "voodoo" OR the "glide" driver for that matter. Expected Results: Built the voodoo driver as well Gentoo Base System version 1.4.16 Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r9 i586) ================================================================= System uname: 2.6.11-gentoo-r9 i586 AMD-K6(tm) 3D processor Python: dev-lang/python-2.3.5 [2.3.5 (#1, Jun 1 2005, 15:33:16)] distcc 2.16 i586-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=k6-2 -O2 -pipe -fomit-frame-pointer" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k6-2 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/ http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://192.168.1.2/gentoo-portage" USE="x86 16bit 16bittmp 3dnow 3dnowext S3TC X aac acpi alsa apache2 apm arts artworkextra avi bash-completion berkdb bitmap-fonts cdparanoia crypt cups dga emboss encode foomaticdb fortran gdbm gif gimp gimpprint gphoto2 gpm gtk2 icq imap imlib ipv6 jabber joystick jpeg jpeg2k kde kdeenablefinal kdexdeltas libg++ libwww logitech-mouse mad mailbox maildir matroska mbox mikmod mmap mmx mng motif mp3 mpeg mplayer msn ncurses nls offensive ogg opengl openssl oss pam pdflib perl png python qt quicktime readline rtc samba scanner sdl spell ssl tcpd theora truetype truetype-fonts type1-fonts unicode userlocales utf8 xine xml2 xmms xscreensaver xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
I don
I don´t have such card, but $ euse -i 3dfx ftp xorg-x11 # ************************************************************ [- ] 3dfx - Adds support for 3dfx video cards to XFree86. See: voodoo3 $ euse -i voodoo3 global use flags (searching: voodoo3) ************************************************************ [- ] voodoo3 - Adds support for 3Dfx's Voodoo3 video chipset, else defaults to Voodoo4/5 support if not in USE. seems pretty self-explanatory.
So it seems..but it also seems I was right this one time. Enabling the 3dfx USE flag does not make the ebuild compile the voodoo driver (again, I'm NOT talking about the tdfx driver here). Firing up X.org with a Device section defined using the voodoo driver produces something like: (EE) Failed to load "voodoo" (module does not exist, 0)
reassign, voodoo(4) isn't an external driver.
Created attachment 68868 [details, diff] xorg-x11-6.8.2-r5.ebuild.patch Try this ebuild patch.
Please reopen when you respond.
Tested! Works wonderfully! Card detected and configured with "X -configure". Too bad the driver only supports 2D but it's still better than nothing and I think - something the windows driver couldn't do :)
Awesome. This patch should work against any of the future xorg-x11 versions. xorg-x11 6* are in "maintenance mode", that is, no new features, only some bugfixes. This is to avoid introducing new bugs on something will soon be replaced. I don't plan on making many more changes to 6.8.2 so you're safe putting a revision of your choice (probably want -r6 due to fixes that exist in it) in your overlay with this patch applied.
