Re: [ivtv-devel] Noob question about ivtv driver version
Just wanted to follow up on this thread to let everyone know what became of this issue. First, I gave up on the 500 and returned it in exchange for another 250. So now, I have dual 250s. I installed one of the 250s and went through the motions of trying to validate the feed on /dev/video0 using the methods described in Jarods guide (http://wilsonet.com/mythtv/fcmyth.php). I was never able to get this to work (I have the 0.4.0 driver). I was able to do this quite successfully when I was on the old 0.2.x driver. Rather than continue to struggle with this validation step, I decided to just fire up mythtvsetup and configure this capture card, and, voila, it worked! Then, I added the second 250, configured it, and it worked too. I was never able to get a satisfactory test by running mplayer on a sampling of either /dev/video0 or /dev/video1. I suspect that the 500 I ended up returning would have worked as well, but I never got past the diagnostics to find out whether it would have worked in myth. I should have done this, but it's too late now (sigh). I think the ultimate problem is that with the upgrade from 0.2.x to 0.4.0, the diagnostics procedure I was trying to use is now obsolete. If anyone can elaborate on the proper methodology to test a capture card with the ivtv 0.4.0 driver, it might help those who are still trying to solve this issue. A search of this database seems to suggest I was not the only one fighting this issue. Maybe if we are all nice to Jarod (or send him gobs of money), he will update his How-to :) LarryOn 10/19/05, Timothy McFadden [EMAIL PROTECTED] wrote: On 10/18/05, Larry K [EMAIL PROTECTED] wrote:5) Installed the mkinitrd changes and recreated my boot image.Can anyone explain why this is necessary for the PVR-500?Based on Jarod's site, it appears this change is necessary for the PVR-350 since it has on-board TV-out and piping X over that requires some modules be made available in the boot image?Hi Larry.I don't think this was neccessary because you are using a PVR-500. You are right in that it's only for PVR-350 users who are usingTV-OUT.The purpose is to get IVTV loaded soon enough that you cansee the machine boot up ( rhgb, log in, etc ).It's not arequirement.In fact, I don't use it anymore.It's just nice to have. ( I'll probably wind up putting it back in to mine ).It's been a while, but do you need the following lines in modprobe.conf?install tveeprom /sbin/modprobe tveeprominstall ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe ivtv-fb install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2cI'm not using ivtv_4.0 yet so I don't know if this was changed.-Tim___ ivtv-devel mailing listivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
That step was specific to using a PVR-350 with TV Out ( under the heading Running X on the PVR-350's TV-Out ). -Tim On 10/10/05, Larry K [EMAIL PROTECTED] wrote: Tim, I don't see that anywhere in Jarod's guide. Appreciate further info. On 10/10/05, Timothy McFadden [EMAIL PROTECTED] wrote: Also check to see if you used Jarod's mkinit-rd patch to include the ivtv drivers. You need to re-make the initial ramdisk with the new drivers installed. -Tim ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel -- Want to try Gmail? Send me an email requesting an invite. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
Tim, I don't see that anywhere in Jarod's guide. Appreciate further info.On 10/10/05, Timothy McFadden [EMAIL PROTECTED] wrote:Also check to see if you used Jarod's mkinit-rd patch to include the ivtv drivers.You need to re-make the initial ramdisk with the newdrivers installed.-Tim___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? Many thanks from a frustrated PVR-500 owner. snip ivtv: START INIT IVTV ivtv: version 0.3.8 (tagged release) loading ivtv: Linux version: 2.6.12-1.1378_FC3 686 REGPARM 4KSTACKS gcc-3.4 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv: Autodetected WinTV PVR 150 card (iTVC16 based) ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 3 PCI: setting IRQ 3 as level-triggered ACPI: PCI Interrupt :02:08.0[A] - Link [LNK3] - GSI 3 (level, low) - IRQ 3 ivtv: Unreasonably low latency timer, setting to 64 (was 32) tveeprom: Hauppauge: model = 23552, rev = D592, serial# = 8221024 tveeprom: tuner = Philips FQ1236A MK4 (idx = 92, type = 57) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50] ivtv: This is the first unit of a PVR500 tuner: chip found at addr 0xc0 i2c-bus ivtv i2c driver #0 TEA5767 detected. ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=60] tuner: type set to 62 (Philips TEA5767HN FM Radio) by autodetect type set to 62 (Philips TEA5767HN FM Radio) tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840: loading /lib/modules/HcwMakoA.ROM ivtv: i2c attach to card #0 ok [client=cx25840[50], addr=44] ivtv: i2c attach to card #0 ok [client=wm8775[50], addr=1b] tda9885/6/7: chip found @ 0x86 ivtv: i2c attach to card #0 ok [client=tda9887, addr=43] ivtv: Detected a TEA5767 radio tuner. Enabling radio support. ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: Encoder revision: 0x02040024 ivtv warning: Encoder Firmware can be buggy, use version 0x02040011 ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv: Create encoder radio stream tuner: type set to 57 (Philips FQ1236A MK4) by ivtv i2c driver #0 ivtv: Initialized WinTV PVR 500 (unit #1), card #0 ivtv: == NEXT CARD == ivtv: Autodetected WinTV PVR 150 card (iTVC16 based) ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt :02:09.0[A] - Link [LNK4] - GSI 5 (level, low) - IRQ 5 ivtv: Unreasonably low latency timer, setting to 64 (was 32) tveeprom: Hauppauge: model = 23552, rev = D592, serial# = 8221024 tveeprom: tuner = Philips FQ1236A MK4 (idx = 92, type = 57) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv: i2c attach to card #1 ok [client=tveeprom[50], addr=50] tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #1 ivtv: i2c attach to card #1 ok [client=(tuner unset), addr=61] cx25840: loading /lib/modules/HcwMakoA.ROM ivtv: i2c attach to card #1 ok [client=cx25840[50], addr=44] ivtv: i2c attach to card #1 ok [client=wm8775[50], addr=1b] tda9885/6/7: chip found @ 0x86 ivtv: i2c attach to card #1 ok [client=tda9887, addr=43] ivtv: This is the second unit of a PVR500 ivtv: Correcting tveeprom data: no radio present on second unit ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: Encoder revision: 0x02040024 ivtv warning: Encoder Firmware can be buggy, use version 0x02040011 ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) tuner: type set to 57 (Philips FQ1236A MK4) by ivtv i2c driver #1 ivtv: Initialized WinTV PVR 500 (unit #2), card #1 ivtv: END INIT IVTV lirc_dev: IR
Re: [ivtv-devel] Noob question about ivtv driver version
One additional thing I fergot to mention. If I take out the 3 alias commands from modprobe.conf: alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv The unknown module messages go away in the dmesg output. Then, the modprobe info looks the same as above. Any advice appreciated. On 10/9/05, Philip Rowlands [EMAIL PROTECTED] wrote: On Sun, 9 Oct 2005, Larry K wrote:Is something wrong here? Does 0.2.0 in this context mean that I'm notloading the 0.3.8 driver?Yes; see the very recent archives for the Cannot install new 0.4.0 ivtvdrivers thread.Cheers,Phil___ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On Monday 10 October 2005 22:13, Larry K wrote: I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? Many thanks from a frustrated PVR-500 owner. bttv: disagrees about version of symbol tveeprom_hauppauge_analog bttv: Unknown symbol tveeprom_hauppauge_analog cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog cx88xx: Unknown symbol tveeprom_hauppauge_analog Well, I do know what is wrong, but I don't know why you are bitten by it. The tveeprom_hauppauge_analog() function in tveeprom.c has an extra client argument in the upcoming 2.6.14 kernel. However, it looks like your kernel has that extra argument already. Can you check tveeprom.c from your kernel tree (it should be in drivers/media/video) and report if the function looks like this: void tveeprom_hauppauge_analog(struct i2c_client *c, struct tveeprom *tvee, unsigned char *eeprom_data) or this: void tveeprom_hauppauge_analog(struct tveeprom *tvee, unsigned char *eeprom_data) Note the extra i2c_client pointer in the first. One option is not to use the ivtv tveeprom but the one from the kernel. This should work. Alternatively you can edit tveeprom.c in ivtv to add the 'struct i2c_client *c' argument. Hans ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? well, we do recommend that you use the ivtv versions. But you have some problems below. Many thanks from a frustrated PVR-500 owner. snip bttv: disagrees about version of symbol tveeprom_hauppauge_analog bttv: Unknown symbol tveeprom_hauppauge_analog cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog Why is cx88xx loading? You have another capture card in there somewhere? And if you do, this is a conflict where the kernel cx88xx module will not use the ivtv tveeprom. So you'll have to use the kernel version of tveeprom. Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv These aliases are from the atrpms version of the modules. if you look in /lib/modules/2.6.12-1.1378_FC3/ivtv, you'll probably see that there is a tveeprom-ivtv.ko in there instead of the normal tveeprom.ko. [EMAIL PROTECTED] ~]# modinfo tveeprom filename: /lib/modules/2.6.12-1.1378_FC3/kernel/drivers/media/ video/tveeprom.ko As a result, this means nothing. Yes, this is the modinfo for tveeprom, but you're actually loading tveeprom-ivtv. So, this really boils down to a couple of things: 1. You're loading cx88xx for some reason or another and it doesn't like the ivtv version of tveeprom. If you need cx88xx for something, then you'll need the kernel version of tveeprom to get it working. 2. The naming scheme of atrpms' ivtv modules is confusing you and/or your kernel. Just saw your newest email. You can use the kernel versions of tveeprom and tuner, but you must use the ivtv version of msp3400. Keith C ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On 10/10/05, Keith C [EMAIL PROTECTED] wrote: On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading.To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly.I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output.Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used.I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version.But I put everything back to the way it was at the start, and below is the modinfo output.I am concerned that perhaps I am not loading the correct version of these modules?well, we do recommend that you use the ivtv versions.But you havesome problems below. Many thanks from a frustrated PVR-500 owner. snip bttv: disagrees about version of symbol tveeprom_hauppauge_analog bttv: Unknown symbol tveeprom_hauppauge_analog cx88xx: disagrees about version of symbol tveeprom_hauppauge_analog Why is cx88xx loading?You have another capture card in theresomewhere?And if you do, this is a conflict where the kernel cx88xxmodule will not use the ivtv tveeprom.So you'll have to use the kernel version of tveeprom. I don't have anything installed except the PVR-500MCE. I have no idea why cx88xx is loading. The machine has the pvr-500 and an nvidia video card. That's it. Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtvThese aliases are from the atrpms version of the modules.if you look in/lib/modules/2.6.12-1.1378_FC3/ivtv, you'll probably seethat there is a tveeprom-ivtv.ko in there instead of the normaltveeprom.ko. [EMAIL PROTECTED] ~]# modinfo tveeprom filename: /lib/modules/2.6.12- 1.1378_FC3/kernel/drivers/media/ video/tveeprom.koAs a result, this means nothing.Yes, this is the modinfo fortveeprom, but you're actually loading tveeprom-ivtv.So, this really boils down to a couple of things: 1.You're loading cx88xx for some reason or another and it doesn'tlike the ivtv version of tveeprom.If you need cx88xx for something,then you'll need the kernel version of tveeprom to get it working.2.The naming scheme of atrpms' ivtv modules is confusing you and/or your kernel.Just saw your newest email.You can use the kernel versions oftveeprom and tuner, but you must use the ivtv version of msp3400. I'm not sure whether or not I need to include the alias stuff in modprobe. If I do, I get the errors. If I don't, the errors go away, but I'm not sure if I am loading the right modules Keith C___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I don't have the tveeprom.c anywhere on my system ( I searched for it like so: find / -name tveeprom.c). I suspect I am using the kernel version of tveeprom now. However, I still have the original issue that is the source of my angst: I get good audio and video on /video1, but nothing but static (no sound) on /video0. Axel Thimm, Jarod Wilson, et. al., maintains the atrpm stuff at http://atrpms.net/ I can try to contact them. Do you know those guys?On 10/10/05, Hans Verkuil [EMAIL PROTECTED] wrote: On Monday 10 October 2005 22:50, Larry K wrote: Hans, I'm not working from source. I pulled the compiled kernel from atrpms like so: apt-get install kernel=2.6.12-1.1378_FC3 Do you have any other ideas as to how I can pursue this?In that case just use the kernel tveeprom (or edit ivtv tveeprom.c as per myprevious email). Can someone else check just which tveeprom.c is included inthat kernel?Hans___ivtv-devel mailing listivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
Keith C wrote: On Oct 10, 2005, at 3:13 PM, Larry K wrote: I now have the right version of the ivtv driver loading. To do this I had to upgrade to kernel 2.6-12-1.1378 in order to get atrpms to install the driver properly. I was using 2.6-10.x and there appears to be no prepackaged ivtv 0.3.x driver for this kernel. Now, having gotten the ivtv driver corrected, I seem to have introduced another problem with a number of unknown symbols, as shown below in dmesg output. Can anyone shed any light on this? I also read that the ivtv version of tuner, tveeprom, and msp3400 must be used. I played around with renaming the kernel version of the drivers, in an attempt to force the system to laod the ivtv version. But I put everything back to the way it was at the start, and below is the modinfo output. I am concerned that perhaps I am not loading the correct version of these modules? well, we do recommend that you use the ivtv versions. But you have some problems below. Personally, I only recommend ivtv versions of tveeprom and tuner if the kernel ones already contain the right definitions. Go with the kernel ones if you can. msp3400 is a different story. -- Tyler Trafford ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I can certainly install the card on my win2k machine as a test. What I'm doing now to test the card is to cat from /dev/video0 and /dev/video1, like so: # /usr/bin/ivtvctl -u 0x3000 -d /dev/video0 # /usr/bin/ivtvctl -p 6 -d /dev/video0 # /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video0 # cat /dev/video0 /tmp/test_capture0.mpg (ctrl-c to stop capture) # mplayer -vo xv /tmp/test_capture0.mpg # /usr/bin/ivtvctl -u 0x3000 -d /dev/video1 # /usr/bin/ivtvctl -p 6 -d /dev/video1 # /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video1 # cat /dev/video1 /tmp/test_capture1.mpg (ctrl-c to stop capture) # mplayer -vo xv /tmp/test_capture1.mpg Under this scenario, only /dev/video1 produces a playable file. /dev/video0 produces lots of static, and no audio.On 10/10/05, Hans Verkuil [EMAIL PROTECTED] wrote:On Monday 10 October 2005 23:08, Larry K wrote: I don't have the tveeprom.c anywhere on my system ( I searched for it like so: find / -name tveeprom.c). I suspect I am using the kernel version of tveeprom now. However, I still have the original issue that is the source of my angst: I get good audio and video on /video1, but nothing but static (no sound) on /video0.Can you test under Windows? It sounds like a hardware problem to me. I doassume that you tuned both tuners to the same channel? I also assume that you have no other TV cards in your system and are not mixing up /dev/videoXdevices :-)Hans___ivtv-devel mailing list ivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
This problem has come up on the list several times before. lirc_i2c sometimes pulls in the cx88xx module for some reason (doesn't happen to me any more, but did until fairly recently) and that conflicts with the ivtv version of tveeprom. For me, editing tveeprom.c did NOT fix the problem, I still got the same error. The solution is to use the tveeprom.ko that came with your kernel. I definately had this problem with 2.6.12-*_FC3. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
Why is cx88xx loading? You have another capture card in there somewhere? And if you do, this is a conflict where the kernel cx88xx module will not use the ivtv tveeprom. So you'll have to use the kernel version of tveeprom. I don't have anything installed except the PVR-500MCE. I have no idea why cx88xx is loading. The machine has the pvr-500 and an nvidia video card. That's it. Then you should probably look into why bttv/cx88xx is loading. Thats not a good thing. Look through dmesg for more bttv and cx88xx and see what else is going on there. Here is my modprobe.conf: snip #ivtv PVR500 alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias tuner tuner-ivtv alias msp3400 msp3400-ivtv I'm not sure whether or not I need to include the alias stuff in modprobe. If I do, I get the errors. If I don't, the errors go away, but I'm not sure if I am loading the right modules Let me clarify this a little. If you use the kmdls from atrpms, and don't rename anything at all, and you want to use the ivtv versions of everything, then you MUST have the alias lines in modprobe.conf. Because thats what the ivtv modules are named in atrpms. Its a failsafe device added by Axel to ensure that linux newbies don't get the wrong modules loaded. But, the kernel version of bttv and cx88xx are not compatible with the ivtv version of tveeprom. So you'll get those unknown symbol errors when those modules are loaded. But if you really don't need those modules, no harm done. A lot of people can use the kernel versions of tuner and tveeprom. I don't think you're going to be one of them, because your kernel is too old to have the sync stuff that Hans has been committing to the v4l repository. So you'll need the ivtv versions, and you'll have those unknown symbols errors. If you want to try the kernel version of tveeprom and/or tuner, only remove those alias lines. Leave the msp3400 line there to force it to use the ivtv version. I just saw Adam's response that its lirc_i2c that is trying to load bttv and cx88xx. You could try blacklisting those modules from loading, but that might cause lirc_i2c to fail as well. Keith C ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
I don't have anything installed except the PVR-500MCE. I have no idea why cx88xx is loading. The machine has the pvr-500 and an nvidia video card. That's it. Then you should probably look into why bttv/cx88xx is loading. Thats not a good thing. Look through dmesg for more bttv and cx88xx and see what else is going on there. lirc is pulling in cx88xx, and doesn't seem to work without it on 2.6.12*FC3 kernels for me with a pvr350. Using the kernel tveeprom allows this to happen without issue. bttv used to get pulled in for me at some point too, but it doesn't cause any problems. Let me clarify this a little. If you use the kmdls from atrpms, and don't rename anything at all, and you want to use the ivtv versions of everything, then you MUST have the alias lines in modprobe.conf. Because thats what the ivtv modules are named in atrpms. Its a failsafe device added by Axel to ensure that linux newbies don't get the wrong modules loaded. I'm pretty sure that's only true for the 0.2 versions NOT the 0.3.8 / now 0.4 versions (the default) from atrpms, thus him getting the errors. But, the kernel version of bttv and cx88xx are not compatible with the ivtv version of tveeprom. So you'll get those unknown symbol errors when those modules are loaded. But if you really don't need those modules, no harm done. It will cause lirc not to work on 0.3.* / 2.6.12*FC3 with a pvr350 at least for me. A lot of people can use the kernel versions of tuner and tveeprom. I don't think you're going to be one of them, because your kernel is too old to have the sync stuff that Hans has been committing to the v4l repository. So you'll need the ivtv versions, and you'll have those unknown symbols errors. This is not correct for tveeprom I think. It should work anyways. If you want to try the kernel version of tveeprom and/or tuner, only remove those alias lines. Leave the msp3400 line there to force it to use the ivtv version. Again, I don't think that's correct since he's using 0.4 not 0.2. I just saw Adam's response that its lirc_i2c that is trying to load bttv and cx88xx. You could try blacklisting those modules from loading, but that might cause lirc_i2c to fail as well. He's better off using the kernel tveeprom which should work fine. Keith C ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On 10/10/05, Larry K [EMAIL PROTECTED] wrote: Actually, I'm using 0.3.8. Not 0.4.x. Ok. Well, I looked back at the thread and there were so many messages that I'm a bit confused. Do locate tveeprom.ko, then move any it finds to tveeprom.ko.HIDE. Repeat for tuner and tda9887. Then reboot. Since the modules you want to use have been renamed to tveeprom-ivtv.ko etc, this is safe. Also, don't use any ivtvctl commands at all either on bootup or when capturing. What frequency map have you been selecting with ptune-ui? Make sure you're using the right one. What now happens with /dev/video0 and /dev/video1? ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Noob question about ivtv driver version
On Sun, 9 Oct 2005, Larry K wrote: Is something wrong here? Does 0.2.0 in this context mean that I'm not loading the 0.3.8 driver? Yes; see the very recent archives for the Cannot install new 0.4.0 ivtv drivers thread. Cheers, Phil ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
