The latest are not in the saa7134 listing directory. Use http://bytesex.org/snapshot. The most recent is dated jan 10. I haven't had time to look at it yet though. T.C. ---- Wan Tat Chee (Lecturer) School of Computer Science, Univ. Science Malaysia, 11800 Minden, Penang, Malaysia. Ofc Ph: +604 653-3888 x 3617 Internet: tcwan@xxxxxxxxx Web: http://nrg.cs.usm.my/~tcwan GPG Key : http://nrg.cs.usm.my/~tcwan/tcw_gpg.asc F'print : FB0F CED7 85A5 ECF9 DEF0 50E8 A550 A0D2 8638 B1EB On 13 Jan 2003, Stian Jordet wrote: > I did not get the time to test much today, I'm sorry. To be honest I'm > not that sure what to test either, but here's a short summary of what's > happening. > > I'm using kernel 2.4.20 with latest v4l2 patch, dated december 18, and > saa7134 0.2.2. The capture board is a Terratec Cinergy 600. My computer > is a Asus CUV266-DLS Dual P3 1ghz, integrated scsi, Radeon 9700 Pro, > using ATI's binary drivers (might have something to do with it?), scsi > harddrivers, dvd, etc. > > XAWTV: > ====== > Actually, my first try to start xawtv tonight gave me this error, and a > picture like when using overlay, even though it was colour this time, > but displaced from the xawtv frame, and some striped and noise in the > picture: > > ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 > [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode > .seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits=""; > sequence=0;memory=unknown): IO-error > > This was with xawtv set to "grabdisplay". With overlay, I get a black > and white picture, which is displaced from the xawtv frame. Other than > this first time, xawtv in grabdisplay mode works perfect, as it always > have. > > Zapping: > ======== > In "Capture mode" I get the same as with tvtime, every second frame is > green. (Probably it is not every second, but maybe ten green, and ten > frames with good picture). > > In overlay mode I get the same as with xawtv. > > Tvtime: > ======= > Excactly the same behaviour as Zapping in Capture mode, green frames > half of the time. Besides, sometimes it segfaults at startup, but with > the latest v4l2 patches, it doesn't seem to freeze my computer anymore.. > > Mplayer: > ======== > When running mplayer as a user, I got this message first: > > ioctl mcapture failed: Ugyldig fildeskriptor > > "Ugyldig fildeskriptor" should be something like invalid filedescriptor > (perhaps..) And this fills up my screen, and I have to kill it with > ctrl+c. > > Second try I got this message: > > ioctl set tuner failed: Ugyldig argument > > "Ugyldig argument" should be invalid argument. And mplayer exits. > > BUT, when running mplayer as root, I get the same errors as a normal > user, but sometimes it starts, and it's like tvtime and zapping in > capture mode, half the frames are green. I really don't get it. > > VCR: > ==== > Works perfectly (well, I don't get sound, but I don't think that's a > problem with the driver). > > > I really don't think this helps anyone, but it seems that everyone with > the saa7134 driver seems to have more or less the same problems. Btw. I > get the same results with kernel 2.5.56, except that xv doesn't seem to > work, but I blame that on the ATI drivers, and haven't investigated any > further yet. > > If someone would join me on that, I would donate half the money to buy a > Terratec 600 if someone would try fix these issues... > > Oh well, time for some sleep. I do understand that this most likely just > makes everyone more confused, but please get back to me with what I > shall do if anyone has any ideas. > > Best regards, > Stian Jordet > > s�n, 2003-01-12 kl. 03:44 skrev Billy Biggs: > > Stian Jordet (liste@xxxxxxxxx): > > > > > > 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 have already talked to you about this, both on mail and irc. I > > > really don't think it's a problem with tvtime, but with the saa7134 > > > driver. I'll try to do some more debugging tomorrow and file a > > > bugreport with more info. > > > > Sorry, I remember now. :) I think the only way to get this fixed > > will have to be more specific investigation by someone with a card, or > > if you have any suggestions for what I can do... And yeah, there should > > be a tvtime bug about this. :) > > > > > But what DO happen (with SAA7134 0.2.2 (latest) and kernel 2.4.20 with > > > latest v4l2 patch) is that xawtv works perfect in grabdisplay mode, > > > but overlay gives black and white picture, which is a bit to the left > > > of the xawtv frame. Several users have reported this. > > > > Yeah, and this is confusing to me. Why would xawtv work in > > grabdisplay mode, and tvtime would fail? What was interesting was this > > user who says that xawtv using the XVideo/v4l module causes the crash. > > This makes me wonder if something is conflicting there between XVideo > > being used and tvtime at the same time. > > > > > Tomorrow I will try some v4l1 applications, and tell you about it. But > > > as I remember, tvtime sometimes freezes my pc when I launch tvtime, > > > some times it starts, but gives green pictures every second frame (or > > > something). This is quite similar with mplayer. So I'm quite sure it > > > is the saa7134 driver. > > > > I'm sure too but I want to help get this fixed soon, since the bug > > reports are annoying. :) > > > > > But I'll get back to you. > > > > Thanks, > > Billy > > > > >
