Hello Holly,
Saturday, January 22, 2005, 12:16:47 PM, you wrote:
HB> Anyway, what does fglrxinfo say now (you might want to restart the X HB> server, or even reboot to get accurate info as to what OGL renderer is HB> actually being used)?
Rebooted ad this is what I get...
bash-2.05b$ fglrxinfo Xlib: extension "XFree86-DRI" missing on display ":0.0". display: :0.0 screen: 0 OpenGL vendor string: Mesa project: www.mesa3d.org OpenGL renderer string: Mesa GLX Indirect OpenGL version string: 1.2 (1.5 Mesa 6.1)
Getting nowhere are we!
OK, this sucks. The ATI drivers are admittedly a (big) pain to install properly, but 1) this is excessive, and 2) this is gentoo, where the drivers are as easy to install as they are ever going to get (given a properly configured kernel). I know this for a fact, because I have installed and used the ATI binary drivers under Mandrake, Debian, SuSE, Slackware and Gentoo, from versions 3.2.8 to 3.14.6, so I'm really familiar with the intricacies of the ATI binary driver's general PITA-ness.
Given that fglrx is loaded (it did load after the reboot, right?), this should not be happening.
There could be several reasons that it is:
1) drivers not properly compiled (you have booted to the same kernel version that /usr/src/linux is linked to, yes?)
2) kernel misconfigured so driver does not work (main issue is that DRM must be off)
3) X.org misconfiguration (I'll look at your attachment again)
4) driver fault. If you are using the new 8.8.25 drivers, this is quite possible-- a *lot* of people are having trouble getting it installed, under a wide range of distributions; pretty much all of the major ones, though gentoo seems to be having the highest success rate so far.
5) application conflict with any one of the above.
I've been following the initial reports on the new ATI binary drivers fairly closely to determine what I should best do (due to a number of factors I don't have gentoo re-installed yet, and these drivers are not backported to SuSE 9.1, which is what I'm using atm)... I do seem to recall some issue with the xv extension (you have to set something in xorg.conf to get it to work), and also conflicts between the driver and x.org 6.8 itself (you can't use the driver DRI and the x.org composite extension together), but one or both of us would have to research that to see what the issues and fixes are specifically.
I would suggest checking out the many threads on the Rage3D Linux drivers forums: http://www.rage3d.com/board/forumdisplay.php?f=88 , as it's getting really hard for an 'outsider' like me to keep track of exactly what your config is atm, whereas you are in a much better position to see the "big picture" (exactly what your errors are, what you have done, how everything is configured).
You might also check out the TVTime site at http://tvtime.sourceforge.net/ and/or the Xawtv website at http://linux.bytesex.org/xawtv/ .
I also noticed this: you might want to downgrade Xawtv, if you are using version 4.x:
Q: what is new in xawtv 4.x
There are alot of internal changes which are required for the new features. Due to that several stuff broke. Some just isn't fixed yet and will be available again in the future. Some features are gone forever through.
New features and major changes:
* MPEG2 software decoding.
* Support for DVB cards, including budget cards.
* Reworked configuration framework.Dropped features:
* Overlay without Xvideo extention.
* Switching display resolution.If the fglrx driver has problems with the Xvideo extension (it does; I often can't get it to work), and the current version of xawtv isn't going to run without it, then maybe the version that does allow you to run without that extension would work where this one does not.
There's also a bloomin' lot of kernel patches available on the site, which suggests that you might need some patching to get this to work.
Sorry not to be more help-- it's not that I'm out of ideas, but that at this point, I'd almost have to be sitting in front of the PC to track this down, given that there are 4 vectors of error (kernel, fglrx driver, X.org, or application). So at this point I'd suggest you start eliminating the vectors methodically: first by checking available sources to see if anyone else has this problem (on rage3D and the TVtime site), then confirming that your kernel is properly configured (on the rage3d forums there is a very good ati driver install how-to, and check the TVtime and xawtv sites to see if there is any specific kernel configuration that those applications need), then making sure that the fglrx rivers you're using actually support the features you need for this to work (rage3d forums again) and/or if there is some conflict between the drivers and the specific features of X.org that may be preventing things from working, and lastly checking the applications' websites to see if the issue is in the faq or is otherwise known/solved.
Holly
-- [email protected] mailing list
