John McCarthy wrote:
> That is the X.Org Xserver version 6.8.2. Your Xdriver indicates it was > built for XFree86 Xserver 4.3.99.902. I don't know if that is > compatible with X.Org 6.8.2 or not. If you can get a 6.8.2 version of > the X driver that would probably be better. Don't know if the 4.3.99 > would be a problem or not. This is the atrpms xdriver: ivtv_xdriver-0.10.6-3.el4.at. > Does ATrpms support CentOS packages or are you using FC4 packages? CentOS 4 is one of the redistributions of RHEL4. It is binary compatible with the el4 packages from atrpms. > At least for the PVR-150/500 cards and 0.4.1 (and 0.4.2?) you should > have the following alias lines to get the ivtv version of a few modules: > > #alias tveeprom tveeprom-ivtv > alias tuner tuner-ivtv > alias msp3400 msp3400-ivtv > > I originally ran with the tveeprom alias as well but had to disable it > to get the PVR-150 IR remote control working. Everything else is > working fine with out the ivtv tveeprom. The alias lines are only needed if using the atrpms ivtv driver packages. Since I am using a custom kernel, I have to compile from source. The atrpms packages add the '-ivtv' extension to the module names to avoid conflicting with the kernel modules of the same names. Hence the alias lines. In my case, I rename the kernel modules and avoid needing the alias lines. Interestingly, the 'workaround' I mentioned is the same thing you were doing with tveeprom. The other tuner used the cx88 driver which seemed to need the kernel tveeprom. However now with the PVR-500, ivtv seems to need it's own tveeprom in order to recognize the Samsung tuner. In any case, everything seems to be working. >> ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) >> ivtv0: unable to open firmware v4l-cx2341x-init.mpg >> ivtv0: did you put the firmware in the hotplug firmware directory? >> ivtv0: failed to read mpeg decoder initialisation file v4l-cx2341x-init.mpg > > Hmm, could this be your problem? From > http://www.ivtvdriver.org/index.php/Firmware I see the following: > > The v4l-cx2341x-dec.fw firmware and v4l-cx2341x-init.mpg (named v4l- > cx2341x-init-mpeg.bin in 0.4.1 and earlier) are needed for the PVR-350 > only. Also, v4l-cx2341x-init.mpg is not really a firmware file, but a > very small endian-flipped MPEG file needed to initialize the mpeg > decoder so that the YUV playback (not the framebuffer) works. > > I believe YUV playback is what Xv is providing so maybe having this > missing is messing up Xv playback? Check the Firmware Wiki above and > verify that you have the correctly named file in the right directory. Ah, whoops. Shoulda caught this one myself. Thanks. Unfortunately, after a reboot xine and mplayer still won't run with xv. Alas. > >> tuner: type set to 47 (LG NTSC (TAPE series)) by ivtv i2c driver #0 >> tuner: switching to v4l2 >> tuner: tv freq set to 67.25 >> tuner: tv 0x07 0x10 0x8e 0x01 >> ivtv0: Initialized WinTV PVR 350, card #0 >> ivtv: ====================== NEXT CARD ====================== >> ivtv1: Autodetected WinTV PVR 150 card (cx23416 based) >> ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 22 (level, low) -> IRQ 193 >> ivtv1: Unreasonably low latency timer, setting to 64 (was 32) >> tveeprom: Second (radio) tuner idx 101 >> tveeprom: ivtv version >> tveeprom: Hauppauge: model = 23552, rev = D487, serial# = 8921592 >> tveeprom: tuner = Samsung TCPN 2121P30A (idx = 87, type = 68) > > Ah yes, the new Samsung tuner. Note that the ATrpms 0.4.2 ivtv driver > supports this but apparently has the wrong low/mid/high frequency band > settings (at least with my and 1-2 other PVR-500 owner's Samsungs) The > symptoms are bad tuning on channels 7,19-22,55. I have a patch (from > http://www.gossamer-threads.com/lists/ivtv/users/27749) but haven't > tried to use it yet (actually I'm going to try and get ATrpms to fix > it). I don't know if the SVN head (0.5.?) fixes this or not. So far 0.4.3 is working for me with the PVR-500 once I put the ivtv tveeprom.ko module back into play. Well, thanks for looking at this John. I'm guessing at this point that I need to try to compile the xdriver from source. I tried this once without success. The only howto I've found for this is http://ivtv.writeme.ch/tiki-index.php?page=XDriverHowTo Kirk Bocek _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
