When runing tvtime ... as root or a user, with or without a .tvtime directory, I get the following error: tvtime: Running tvtime 0.9.8.5. config: Reading configuration from /etc/tvtime/tvtime.xml config: Reading configuration from /root/.tvtime/tvtime.xml xvoutput: Received X error event: BadAlloc (insufficient resources for operation) deinterlace: GreedyH disabled: required CPU accelleration features unavailable. deinterlace: Greedy disabled: required CPU accelleration features unavailable. deinterlace: Greedy2Frame disabled: required CPU accelleration features unavailable. deinterlace: TwoFrame disabled: required CPU accelleration features unavailable.deinterlace: VideoBob disabled: required CPU accelleration features unavailable.deinterlace: VideoWeave disabled: required CPU accelleration features unavailable. deinterlace: TomsMoComp disabled: required CPU accelleration features unavailable. deinterlace: Vertical disabled: required CPU accelleration features unavailable.xvoutput: Received X error event: BadAlloc (insufficient resources for operation) warning: failed to load external entity "/root/.tvtime/stationlist.xml" station: No station file found, creating a new one. [1]+ Done tvtime ----- TVTIME is version media-tv/tvtime-0.9.8.5 +lirc GCC compiled with sys-devel/gcc-3.2.3-r2 -static +nls -bootstrap +java -build Architecture is K6-2, running X x11-base/xfree-4.3.0-r3 -3dfx -sse +mmx +3dnow +xml2 +truetype +nls -cjk -doc -ipv6 -debug -static
Sorry I did not know there was a gentoo bug tracker for my application that I should watch. What video card do you have and what driver are you using with XFree86?
Please try version 0.9.10-r1 and report back with your findings.
Sorry I took so long to get back to this. As for not knowing about the Gentoo bug tracker, Gentoo likes to handle all the bugs as a first line fo defense so that the authors don't get slammed directly with things that might be Gentoo-related. tvtime actually worked at first, but then suddenly decided to crash all the time. I'm using a Matrox G400 (at the time) and have added a Matrox Millenium as well. Tvtime does not appear to work on the second head. It took me quite awhile to get xawtv working correctly across heads. version 0.9.10-r1 works without crashes, although does not display on the seconds head. As far as I'm concerned, if it doesn't segfault anymore, this bug can be closed.
Do you mean to say that you have a G400 as one head and a Matrox Millennium as the second head? There has been some work to get XVIDEO working on the Millennium II cards, see this URL: http://www.penguintown.net/~gorlik/millennium.html However, it mentions problems with dual head setups. If you have a G400-dual head card, tvtime definitely won't work on the second head, since hardware overlays are not accellerated there. I assume that when you say you got xawtv working across both heads, you were using its 'overlay' mode? If so, this is something tvtime will never support, since you would be unable to have any OSD or other UI. Please let me know more about your situation though as I am quite curious.
Created attachment 17950 [details] debug (-v 2) from xawtv.
As for the MTRR support, its turned on in my kernel. I always keep it turned on. Are you sure X isn't using it? I think you are right about it not using the hardware scaler on the G400 - it would be neat if it could, but wouldn't make any sense from what I know of how it works. It doesn't quite go edge-to-edge on the millenium's screen when its full screen. I just never paid it much attension. The v4l overlay does work, and it does scale fine on the G400 (even in the weird video mode I use - which is designed for a NeXT fixed-frequency monitor, with a similar FB console mode since it doesn't sync to text mode - I use the millenium/PCI as the default video in the BIOS so I can see the BIOS and grub's boot menu, and when the FB console is initialzed the screen switches to the big monitor on the G400 using matroxfb and the vesafb on the millenium .. using matroxfb on the small one is too difficult to keep the resolutions seperate). I think the xawtv output is attached
(==) MGA(0): Write-combining range (0xe0000000,0x800000) (WW) MGA(0): Failed to set up write-combining range (0xe0000000,0x2000000) So, that's failing on one of the heads, the other seems to be succeeding. I don't know what effect this would have. Regardless, I guess I just don't understand how things are working or why they aren't. By your X logs, the "v4l" module has set up to use a YUY2 overlay for scaling, so if that exists on both heads, then the XVIDEO driver should be able to handle it on both heads. If tvtime only appears on one head but xawtv using that goes on both, I have to assume this is some bug in the X server, and maybe we should report it there. But I honestly don't know enough about X server internals to understand this. Thanks for all the debugging information anyway, it has been a learning experience for me.
As far as this bug is concerned, I (and Billy) think we're done. :-)
