First I tried to use 'framebuffer' and 'bootsplash' with the tdfxfb driver. Framebuffer works fine, but didn't get a /proc/splash so 'bootsplash' fails. Kernelparameter was: video=tdfxfb:1280x768@76 (this make tdfxfb to be fb0). All VT's are in expected video modes. If I switch to vesa with kernelparameter: video=vesa:ywrap,mtrr vga=0x31a (this makes vesa to be /dev/fb0 and tdfx to be /dev/fb1), the framebuffer _works_ until fb1 is initialized for just a second and ends up in a mangled and distorted console (all VT's), but boot normaly into X11 and /proc/splash is present. I think, this can be solved by disabling the tdfx-driver (not tried yet, because running a really slow machine) in the kernel and use only vesa, but vesa didn't support refreshrates greater than 60HZ, so I recommend to fix tdfxfb. Thank you.
Forgotten the used kernelsources: gentoo-sources 2.4.20-rc5
this still a problem with latest gentoo sources ?
Instructions on www.bootsplash.org (the origin of the bootsplash patches) look like most testing was only conducted with the VESA fb driver. As you have found, having 2 different fb drivers trying to access the hardware (in your case tdfx-fb and vesafb) is likely to cause problems. Please test this with only the VESA fb driver (ie: don't build the tdfxfb driver either as a module or in the kernel). If it works with just VESA then I suggest that you contact the author of the tdfxfb driver. Also have a search on forums.gentoo.org, there are reports there from people who have successfully achieved better refresh rates from the vesafb.
tad is not an active developer.
Any updates on the problem? Is this still an issue with the latest 2.6 kernels?
Closing, since the has been no comment from the bug reporter for almost a year..