The 0.4.3 update allows users of the Hauppauge PVR500 with the Samsung TCPN 2121P30A tuner to use it properly. A working ebuild for the 0.4.3 version is exactly the same as the current 0.4.2 version except for the changed version number. This works on my tested system of an Athlon 1000 w/ Gentoo 2005.1. I apologise for not including the actual ebuild code here.
Created attachment 80370 [details] ivtv-0.4.3 updated ebuild Here is the 'updated' ebuild.
*** Bug 127205 has been marked as a duplicate of this bug. ***
This should stay listed as a request for ivtv-0.4.3, not 0.6.0! ivtv versions now have different versions for different kernels. ivtv-0.4.x is still needed for 2.6.15 series kernels while ivtv-0.6.0 is needed for 2.6.16 series kernels required Kernel version ivtv version ================================== 2.6.15-x 0.4.x 2.6.16-x 0.6.x 2.6.17-x 0.7.x 2.6.18-x hopefully built into kernel. So there is a need for both new ebuilds.
Relax everyone.... I'm more then aware of the releases. I actually write code for ivtv. ivtv 0.4.3 did not work on my hardware so it was never added to Portage and it won't be since it doesn't work so I can't test it. Entirely besides the fact that I asked for testers many times over and no one answered. So... no ivtv-0.4.3 ivtv-0.6.0 will be in the tree when I reboot my box to 2.6.16 which probably won't happen until Friday.
Doug, I've been running this version for about a week now, it seems quite solid on my system. I'm not sure where you asked for testers, but odds are I wasn't there or I would have spoken up. Got a pointer to what you want for testing?
More than happy to help test... running on AMD64 X2 (so awkward with some hardware)... Rob.
As another data point, I've been running ivtv 0.4.3 on gentoo-sources 2.6.15-r5 for some time now. Hardware config is an Athlon 64 3700+ with a PVR-500 (late model with the Samsung tuners), running an AMD64 build for everything. Other than the weak-signal issues that others have reported with this card and some channels (the worst is channel 45, which is a real pisser because that's SciFi), ivtv 0.4.3 has been running like a champ. (I suppose I can get my BSG fix from BitTorrent until the tuner situation is sorted...good thing the season just ended. Maybe it'll be fixed in time for season 3. :-) )
Minor correction to the last: the kernel version I'm running is gentoo-sources 2.6.15-r1.
*** Bug 127948 has been marked as a duplicate of this bug. ***
(In reply to comment #5) > ivtv 0.4.3 did not work on my hardware so it was never added to Portage and it > won't be since it doesn't work so I can't test it. Entirely besides the fact > that I asked for testers many times over and no one answered. So... no > ivtv-0.4.3 I just came across this bug today and wanted to note that I've been running the 0.4.3 code since the 24th of February and it actually fixed a lot of issues for me. I can now see channels above 54, channel 19 is tunable now, and the channels in the 7-10 range show up clearly. I did, however, modify the existing 0.4.2 build as I didn't know that the 0.4.3 build was posted here for testing.
*** Bug 128272 has been marked as a duplicate of this bug. ***
(In reply to comment #12) > *** Bug 128272 has been marked as a duplicate of this bug. *** ok only for the records. it was 0.4.4 and it works well with hardened profile on x86. i only renamed the 0.4.2 ebuild to 0.4.4 in /usr/local/portage...
I can vouge for the renaming of the 0.4.2 ebuild to 0.4.4 working fine on kernel 2.6.15-r1. I have a PVR250MCE & PVR350.
(In reply to comment #14) > I can vouge for the renaming of the 0.4.2 ebuild to 0.4.4 working fine on > kernel 2.6.15-r1. > > I have a PVR250MCE & PVR350. > Did the same with 0.6.0 - Changed ebuild name, changed version in ebuild header to 0.6.0 and changed the download url to 0.6.0. All worked as intended except for the compilation error :( Turns out that the /usr/include/linux/videodev2.h file is too old for 0.6.0 and needs to be replaced with /usr/src/linux-2.6.16-x/include/linux/videodev2.h. Compiles successfully and works well.
(In reply to comment #15) > (In reply to comment #14) > > I can vouge for the renaming of the 0.4.2 ebuild to 0.4.4 working fine on > > kernel 2.6.15-r1. After a reboot 0.4.4 could not find the firmware anymore. Hotplug & coldplug were setup and all firmware files were in the right place. No I've the bug 120816... And then downgraded to 0.4.0-r3 and the same firmware could be loaded. Maybe there is a failure between hotplug and the 0.4.4 version.
Could someone post their ebuild for 0.6.0? With my modified version based off the 0.4.2 ebuild, i get WARNING: //lib/modules/2.6.16-gentoo-r1/extra/ivtv.ko needs unknown symbol tveeprom_read WARNING: //lib/modules/2.6.16-gentoo-r1/extra/ivtv.ko needs unknown symbol tveeprom_hauppauge_analog WARNING: //lib/modules/2.6.16-gentoo-r1/ivtv/ivtv.ko needs unknown symbol tveeprom_read WARNING: //lib/modules/2.6.16-gentoo-r1/ivtv/ivtv.ko needs unknown symbol tveeprom_hauppauge_analog Now, I'm unsure where to go since the firmware files are installed and named correctly.
Too slow big winking smiley ;-), 0.4.4 is released. As soon as i can reload the driver I'll report back.
I tested a port for 0.4.4 on my pvr150-mce and it has worked very well (kernel 2.6.15-gentoo-r8).
Perhaps a version bump in stable to 0.60 is in order, as 2.6.16 went stable this weekend? When I tried to update the kernel from gentoo-sources and update the modules, I got a "tuner type not set" in my logs, and the sync watching livetv from my pvr-150 was atrocious.
4/25: 0.6.1 released stable for kernel 2.6.16 users, and 0.4.4 for earlier kernels. Thanks!
Here's the reason I haven't bumped 0.4.3 or 0.4.4 in Portage. I haven't had time to trouble shoot or even worry about my MythTV system lately. Shortly however I will. ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.4 (tagged release) loading ivtv: Linux version: 2.6.15-gentoo gcc-4.1 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected WinTV PVR 150 card (cx23416 based) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tveeprom 3-0050: Hauppauge model 25012, rev B158, serial# 7751146 tveeprom 3-0050: tuner model is Philips FM1236 MK3 (idx 58, type 43) tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 3-0050: audio processor is CX25843 (idx 37) tveeprom 3-0050: decoder processor is CX25843 (idx 30) tveeprom 3-0050: has radio, has no IR remote tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 3-0044: loaded v4l-cx25840.fw firmware (14264 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] tda9887 3-0043: chip found @ 0x86 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0 warning: Encoder mailbox not found ivtv0 warning: Decoder mailbox not found ivtv0: Error locating firmware. ivtv0: Error -12 on initialization ivtv: probe of 0000:00:06.0 failed with error -12 ivtv0: Autodetected WinTV PVR 150 card (cx23416 based) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner 3-0060: TEA5767 detected. tuner 3-0060: chip found @ 0xc0 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60] tuner 3-0060: type set to 62 (Philips TEA5767HN FM Radio) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 3-0044: loaded v4l-cx25840.fw firmware (14264 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] tveeprom 3-0050: Hauppauge model 23552, rev E587, serial# 8381873 tveeprom 3-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 4) tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 3-0050: audio processor is CX25843 (idx 37) tveeprom 3-0050: decoder processor is CX25843 (idx 30) tveeprom 3-0050: has radio, has no IR remote ivtv0: This is the first unit of a PVR500 ivtv0: Detected a TEA5767 radio tuner. Enabling radio support. ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0 warning: Encoder mailbox not found ivtv0 warning: Decoder mailbox not found ivtv0: Error locating firmware. ivtv0: Error -12 on initialization ivtv: probe of 0000:01:08.0 failed with error -12 ivtv0: Autodetected WinTV PVR 150 card (cx23416 based) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 3-0044: loaded v4l-cx25840.fw firmware (14264 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] tveeprom 3-0050: Hauppauge model 23552, rev E587, serial# 8381873 tveeprom 3-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 4) tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 3-0050: audio processor is CX25843 (idx 37) tveeprom 3-0050: decoder processor is CX25843 (idx 30) tveeprom 3-0050: has radio, has no IR remote ivtv0: This is the second unit of a PVR500 ivtv0: Correcting tveeprom data: no radio present on second unit ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0 warning: Encoder mailbox not found ivtv0 warning: Decoder mailbox not found ivtv0: Error locating firmware. ivtv0: Error -12 on initialization ivtv: probe of 0000:01:09.0 failed with error -12 ivtv: ==================== END INIT IVTV ====================
Cardoe, what's the md5sum on your firmware?
I'm running 2.6.16-gentoo-r4 on amd64, and used this ebuild to install ivtv-0.6.1. It compiled and loads fine, but doesn't work right. If I unload and relaod the modules manually, I can usually watch it with 'mplayer /dev/video0'. MythTV (0.19_p9163-r1) won't display LiveTV though, and the backend crashes whenever it tries to record something. I've gotten the frontend to spit out an error similar to this: "[mpeg @ 0xb7700360]Parser not found for Codec Id: 94210 !" Has anyone else had this problem?
Jesse: 305dba74bbe5905447add8883f3ecb68 v4l-cx2341x-dec.fw d85cb08382395390dc95ac6ebc2205f9 v4l-cx2341x-enc.fw 0661f8b2693fe3123e6234557353eacc v4l-cx2341x-init.mpg 3a4803384f749d644ee1f1ca9dcb12fa v4l-cx25840.fw
(In reply to comment #21) > 4/25: 0.6.1 released stable for kernel 2.6.16 users, and 0.4.4 for earlier > kernels. Thanks! > Does anybody have a proper ebuild for either of these? I tried to bump the 0.4.3 to 0.4.4 just like I did from 0.4.2 to 0.4.3 and I'm now getting errors like these: tuner 0-000a: i2c i/o error: rc == -121 (should be 2) tuner 1-000a: i2c i/o error: rc == -121 (should be 2) I'm also getting this: ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.4.4 (tagged release) loading ivtv: Linux version: 2.6.15-gentoo-r1 PENTIUMIII gcc-3.3 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected WinTV PVR 150 card (cx23416 based) ACPI: PCI Interrupt Link [LNKM] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [LNKM] -> GSI 5 (level, low) -> IRQ 5 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tveeprom 0-0050: Hauppauge model 23552, rev D487, serial# 8757517 tveeprom 0-0050: tuner model is Samsung TCPN 2121P30A (idx 87, type 4) tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 0-0050: audio processor is CX25843 (idx 37) tveeprom 0-0050: decoder processor is CX25843 (idx 30) tveeprom 0-0050: has radio, has no IR remote ivtv0: This is the first unit of a PVR500 tuner 0-0060: TEA5767 detected. tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60] tuner 0-0060: type set to 62 (Philips TEA5767HN FM Radio) tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 0-0044: loaded v4l-cx25840.fw firmware (14264 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] ivtv0: Detected a TEA5767 radio tuner. Enabling radio support. ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv0: Create encoder radio stream tuner 0-0061: type set to 68 (Philips TUV1236D ATSC/NTSC dual in) tuner 0-000a: i2c i/o error: rc == -121 (should be 2) tuner 0-000a: i2c i/o error: rc == -121 (should be 2) tuner 0-000a: i2c i/o error: rc == -121 (should be 2) tuner 0-000a: i2c i/o error: rc == -121 (should be 2) ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
I adhoc'ed an ebuild for ivtv 0.6.3 using the ivtv-0.4.2.ebuild. Just changed the download location, and digested it. Every thing compiled fine, firmware got loaded, and is currently running. lspci: 00:07.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) (PVR-150 LP)
Renaming the 0.4.2 ebuild to 0.4.5 works flawless for me. I am using gcc-3.3.6, glibc-2.3.5-r3, 2.6.13-gentoo-r3 i686 (P4) with pvr350 card. lspci: 01:04.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
Can something like this be added to the ebuilds? for ivtv-0.4.x: kernel_is lt 2 6 16 || die "ivtv-0.4.x requires a kernel version 2.6.15 or older, for kernel 2.6.16 you need ivtv-0.6.x" for ivtv-0.6.x kernel_is gt 2 6 15 || die "for kernels older than 2.6.16 you need ivtv-0.4.x" this can prevent a lot of questions. ps, please check exact syntax, there I am not 100% sure I am using kernel_is correctly.
I found what was causing MythTV to misbehave with the 0.6 drivers. The new drivers supposedly rename tuner numbering to the V4L standard (the first tuner being Tuner 1), whereas older releases had Tuner 0 as the first one. The device names (/dev/v4l) stay the same, but MythTV needs to be told about the change. mythtv-setup must be run, and the capture card deleted and recreated. Anything less (like simply changing the tuner assignment) might allow LiveTV to work, but recording will not. Once the 0.6 driver is brought into the tree, this info should be added to the ebuild.
Uhm, what's the status here? ivtv ebuilds in portage are kinda useless w/ current stable kernel...
jakub, the status is still the same it's been. I can't get a single version of ivtv since 0.4.2 to work for me. Hans (upstream maintainer) is perplexed and as a result I can't test. What I can't test, I can't commit. Reason I don't just commit it is cause there's all sorts of funky combos of udev+kernel+hotplug+ivtv that don't and do work.. 1 person sends me an e-mail saying "This ebuild works for me..." which is just a rename of 0.4.2 to 0.6.2 (I can do that myself folks.. ) then 2 days later that person is on the mailing list commenting how nothing works for them anymore.
(In reply to comment #32) > jakub, > > 1 person sends me an e-mail saying "This ebuild works for me..." which is just > a rename of 0.4.2 to 0.6.2 (I can do that myself folks.. ) then 2 days later > that person is on the mailing list commenting how nothing works for them > anymore. > That is because the tuner numbering changed in 0.6.x but i do have 0.4.4 working without problems.0.6.2 is a bit more difficult. It needed a firmware reload before it would start working for me (symptons only snow even after using ivtv-tune to set frequenty): mythtv ~ # ivtvctl -H ioctl IVTV_IOC_RELOAD_FW ok mythtv ~ # dmesg | grep ivtv ivtv output: ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.6.2 (tagged release) loading ivtv: Linux version: 2.6.16-gentoo-r3 K7 gcc-3.4 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected Hauppauge WinTV PVR-350 card (cx23415 based) tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) tda9887 0-0043: chip found @ 0x86 (ivtv i2c driver #0) saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) msp3400 0-0040: MSP4418G-B3 found @ 0x80 (ivtv i2c driver #0) ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 ivtv0: Decoder revision: 0x02020023 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv0: Create encoder radio stream ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv0: Create decoder VOUT stream ivtv0: Allocate DMA decoder YUV stream: 20 x 51840 buffers (1024KB total) ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) ivtv0: Initialized Hauppauge WinTV PVR-350, card #0 ivtv: ==================== END INIT IVTV ==================== ivtv0-osd: Framebuffer module loaded (attached to ivtv card id 0) ivtv0-osd: screen coords: [0 0] -> [720 576] ivtv0-osd: original global alpha = 208 ivtv0-osd: current OSD state = 39 ivtv0-osd: new global alpha = 208 (1 255 0) ivtv0-osd: framebuffer at 0xf1510000, mapped to 0xd1f90000, size 1665k ivtv0-osd: mode is 720x576x32, linelength=2880 ivtv0-osd: fb1: cx23415 TV out frame buffer device ivtv0: Allocate DMA decoder OSD stream: 16 x 65536 buffers (1024KB total) Let me know if you need more info. Greets Sander
Well now there's masked versions of 0.4.5 and 0.6.2. Matt, if you feel like tinkering with either one you use and mask sure it's good to go... you can unmask it.
Hi Doug, how may I help? I have 0.6.x working for me since I installed kernel 2.6.16. I had 0.4.x working before on 2.6.15 I even felt brave and used a higher version firmware than the recommended one on ivtvdriver.org. Actually, I used the version recommended by Hauppauge. My card is a Hauppauge PVR-150 (so I cannot test de decoder part). My system is on x86 stable (updating daily), with no importat instable package. Is there any tests you would like me to perform? Beside normal viewing using mplayer and mythtv activity (which work without problems) I have no ideea of other tests. Thanks, Dan.
The masked ivtv-0.4.5.ebuild has worked well for me for the last few days (gentoo-sources-2.6.15-gentoo-r8). I will try to unmask it shortly
Hi, After googling for a while, I found out why my ivtv didn't work anymore on my 2.6.16 kernel.... (ivtv-0.6.x) It would indeed be good to add a warning in the ebuilds. Besides, it still don't work for me. I have sound but no video (black image). I'll continue googling...
Btw, here how I use my PVR-250. Perhaps it can give you ideas: ---------- PlayChannel.sh ----------- #!/bin/bash STANDARD=$1 CHANNEL=$2 if [ "$STANDARD" == "secam" ] || [ "$STANDARD" == "SECAM" ] ; then TABLE="secam-france" STANDARD="SECAM" ivtvctl --set-standard=0x7F0000 else TABLE="pal-europe" STANDARD="PAL" ivtvctl --set-standard=0xFF fi ivtvctl --set-input=4 ivtvctl --set-format=width=720,height=576 ivtvctl --set-codec-params=framerate=1 ivtvctl --set-codec-params=stream_type=10 /usr/bin/ptune.pl --freqtable $TABLE --channel $CHANNEL # Change and reset (sometime problems) ivtvctl --set-io=input=7,output=1 ivtvctl --set-io=input=7,output=2 sleep 1 mplayer -ao arts -vo xv /dev/video0 ---------- PlayChannel.sh ----------- Use: PlayChannel pal 49
AHAHAAAAAAAAA! YIPPEEEEEEE! The input numbering seems to have changed. < ivtvctl --set-input=4 > ivtvctl --set-input=0 Now I have a the picture again. I should have tested with ptune-ui.pl first...
I unmasked =media-tv/ivtv-0.4.5. Now if only I had time to upgrade to 2.6.16...
0.4.5 bump works fine for me and my PVR-350 + gentoo-sources-2.6.15-r1 + mythtv 0.18.1-r2 on x86. Thanks.
ivtv-0.6.x does not seem to work with vdr-pvrinput. I read that the devices are now 0-indexed instead of 1-indexed, and the problem is VERY probably linked (I just installed vdr, so I never had it running...) > Jun 3 14:00:06 gentoo vdr: [29145] no DVB device found > Jun 3 14:00:06 gentoo vdr: [29145] initializing plugin: pvrinput (0.1.1): use Hauppauge PVR as input device > Jun 3 14:00:06 gentoo vdr: [29145] ERROR: invalid primary device number: 1 > Jun 3 14:00:06 gentoo vdr: [29145] ERROR: no primary device found - using first device! > Jun 3 14:00:06 gentoo vdr: [29145] ERROR: invalid primary device number: 1 > Jun 3 14:00:06 gentoo vdr: [29145] deleting plugin: pvrinput > Jun 3 14:00:06 gentoo vdr: [29145] exiting A warning should be added to avoid vdr users to google like crazy.
It has to be noted that the newer pvr500/150 with samsung TCPG_6221P30A (pal) tuner do not work out of the box with 0.6.2. In 0.6.2 they are using the in kernel modules instead of their own copies and this one did not make it into 2.6.16/17 but should be in 2.6.18. 3 files need to be updated in mainline, tuner.h, tuner-types.c and tveeprom.c. The changes are small and would also be needed for 0.7.x. Would you be willing to take a patch for gentoo-sources so people in PAL countries with this tuner can have a working ivtv in kernels 2.6.16 and 2.6.17? As noted in the original bug report it does work on >=0.4.3
Sander, I don't have any control over gentoo-sources. But why don't you attach the required patch and we'll CC the maintainers of gentoo-sources... it can't hurt to ask.
Created attachment 88630 [details, diff] samsung pal tuner patch Ok, the patch does 2 things. 1: Rename the samsung ntsc tuner chip as it was incorrect 2: Add the samsung pal tuner chip. Small changes but it will prevent people getting problems with the 0.6/0.7 releases.
I'm planning to update my system to 2.6.16-gentoo-r9 kernel and I'll have to switch to ivtv-0.6.x. My system have a PVR-250 board with Philips FI1236 MK2 tuner. I understand that ivtv-0.6.2 have some issue with boards which have Samsung tuner ... now my question ... it suppose to work with my capture board or ... I dave to experiment and see if it does ?
(In reply to comment #46) > I'm planning to update my system to 2.6.16-gentoo-r9 kernel and I'll have to > switch to ivtv-0.6.x. > My system have a PVR-250 board with Philips FI1236 MK2 tuner. That should be fine. It is the PVR150/500 that have the new samsung tuners.
I think you answered your own question... You said you had a Phillips tuner and then pointed out that Samsung tuners have an issue. So then you wouldn't be affected by that issue. But then again I have a Phillips tuner on one of my cards and it still doesn't work. But that's just one of the many fun issues with 2.6.16 & 0.6.x
new package.mask entry for ivtv-0.6.2 # it doesn't work for many people but others want it # by doesn't work I mean one of the following: # - does not compile # - can't find tuner (tuners are renumbered in this version.. remember that) # - can't change channels # - can't see all the channels # - can't hear sound # Gentoo users wanting 0.6.x have caused lots of noise on multiple mailing lists # and IRC. They have insulted upstream developers and users alike because they want # there latest version and they want it NOW!!!!111oneoneoneeleven Knock it off.. # it's not endearing. Use kernel 2.6.15 & ivtv 0.4.5.
(In reply to comment #47) > (In reply to comment #46) > > I'm planning to update my system to 2.6.16-gentoo-r9 kernel and I'll have to > > switch to ivtv-0.6.x. > > My system have a PVR-250 board with Philips FI1236 MK2 tuner. > > That should be fine. It is the PVR150/500 that have the new samsung tuners. > I just updated to 2.6.16-gentoo-r9 and ivtv-0.6.2 and everything work as expected ... I use mythtv so I had to change the tuner setup ... and after that worked. Thank you for the great support, Jake
(In reply to comment #49) > new package.mask entry for ivtv-0.6.2 > > # it doesn't work for many people but others want it > # by doesn't work I mean one of the following: > # - does not compile > # - can't find tuner (tuners are renumbered in this version.. remember that) > # - can't change channels > # - can't see all the channels > # - can't hear sound > # Gentoo users wanting 0.6.x have caused lots of noise on multiple mailing > lists > # and IRC. They have insulted upstream developers and users alike because they > want > # there latest version and they want it NOW!!!!111oneoneoneeleven Knock it > off.. > # it's not endearing. Use kernel 2.6.15 & ivtv 0.4.5. > Added a note on the wiki, hopefully this will help :) The recommended kernel and driver version are # kernel <=2.6.15 # ivtv version 0.4.x Do not use ivtv 0.6.x with kernel versions other then 2.6.16. Also it changes a lot of things and will break your mythtv box or whatever script you have been using. So dont use it unless you know how toi fix it!!! Now on with the guide.
Well 0.6.3 finally works for me... closing this bug.
