Stian Jordet (liste@xxxxxxxxx): > fre, 2003-01-10 kl. 03:45 skrev Wan Tat Chee: > > On 10 Jan 2003, Stian Jordet wrote: > > > Have any of you guys with a SAA7134 gotten tvtime to work? > > > http://tvtime.sf.net > > > > I don't have a FV3K (saa7134), but my experience with TVTime on FV2K > > (saa7130) up to 0.9.5 was that it hung my system hard (need hardware > > reset). It usually dies faster in framebuffer mode than in X11. > > YMMV. (Sorry I couldn't be more precise, it's been a while since I > > tried to use it). > Sounds more or less like my experience. Damn, the SAA7134 doesn't work > too well :( What do you think the problem might be? I'm still unclear on when things crash and why. The first bug report we got (bug 633039) was just about the tuner not letting us set its mode, but I thought we had that fixed. Now it seems that there is a difference between kernel versions, and that kernel panics are happening? I don't know how to approach this. The driver webpage (http://bytesex.org/saa7134/) doesn't note anything, but it does say you need the V4L2 patches. Is there something odd about its V4L1 support? Are there known problems? Also, I've heard that xawtv in XVideo mode also causes kernel panics with this driver. Does this information help? I'd love to know what I can do to provide more debugging information about these crashes. If just tvtime crashes, can you get a stack trace or anything out of it? If it's the kernel crashing, I guess logs should be posted on the web somewhere? Would that help? If there's anything else I can do to help debug this that you can think of, let me know. So that I can track this better, I'd appreciate it if one of you could post a bugreport with some output to the tvtime bugs page: http://tvtime.sourceforge.net/ There's also a thread on the tvtime mailing list about this. Thanks, -Billy -- Billy Biggs vektor@xxxxxxxxxxxx
