On Sun, 2 Jun 2002, Carl Hultquist wrote: > Hi all, > > I've been having a couple of issues with this card: I've finally managed > to get it working fine as far as viewing TV in xawtv/motv goes, but have > the following issues: > > 1) Every now and then running xawtv/motv will cause a system hang. This > doesn't happen at all often, but does happen. On FlyVideo2000 I haven't seen this happen (yet) > 2) Running xawtv with the -noxv switch seems to consistently hang my > machine. Hmm. What is your hardware/software config? > 3) Occasionally flipping channels results in the sound being messed up: by > flipping back and forth I can often rectify this. In fullscreen mode, > flipping channels sometimes results in a black-screen with the correct > sound: again, flipping back and forth fixes this. I occasionally see the video black screen problem also. Somehow the video sync is lost and the driver stops sending video data? (I'm speculating here) As for sound being messed up, do you mean sound / channel mismatch? I suspect that the I/O access to the card doesn't always work properly, and the registers don't get programmed to the correct values once in a while. (This is beyond my expertise). > 4) Sometimes, switching to fullscreen doesn't do anything: my vidmode > changes (to the fullscreen mode I've specified in my conf file), but no > video is displayed: just a black screen. Flipping back and forth between > channels or from fullscreen to non-fullscreen back to fullscreen doesn't > fix this either. I don't often get this issue. I think (3) and (4) are related. > 5) Capturing of video seems impossible: I seem to be able to capture audio > fine, but trying to capture video never works. I get the same errors as > reported by Dave Antliff who has exactly the same card as me (same > make/model, same chipset, same tuner-type). > I've tried on 2.4.19-pre10 running on RH 7.3, ASUS A7S333 motherboard, ATI Rage Pro 4MB (old!), FlyVideo2000, latest saa7134 snapshot (June 4), mp1e 1.9.1 with v4l2 patch (enable O_RDWR), and I get a hard kernel lock due to a NULL pointer dereference (same thing as reported by Dave). I think saa7134 is horribly broken wrt. mp1e support. Don't know where the problem is... (Gerd?) Has anyone gotten mp1e to work with a v4l2 based driver/card other than saa7134? It'd be interesting to compare notes. > Items 3 and 5 have definitely been reported on this mailing list by > Dave who, as mentioned above, has the same card. => this seems like > something driver related (since it's not sporadic, i.e. not happening to > one poor soul). Both Dave and I are happy to help out anyone in the > know-how to try things and report back results: please can someone help... T.C. ---- Wan Tat Chee (Lecturer) School of Computer Science, Univ. Science Malaysia, 11800 Minden, Penang, Malaysia. Ofc Ph: +604 657-7888 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
