[ivtv-devel] compilation problem on 2.6.21rc7
Hello, Hoping for somebody with some more experience to know the answer on how to solve below compilation problem: CC [M] /usr/src/ivtv-0.10.1/driver/ivtv-ioctl.o /usr/src/ivtv-0.10.1/driver/ivtv-ioctl.c: In function `ivtv_internal_ioctls': /usr/src/ivtv-0.10.1/driver/ivtv-ioctl.c:559: error: structure has no member named `i2c_id' /usr/src/ivtv-0.10.1/driver/ivtv-ioctl.c:560: error: structure has no member named `i2c_id' /usr/src/ivtv-0.10.1/driver/ivtv-ioctl.c:569: error: structure has no member named `i2c_id' /usr/src/ivtv-0.10.1/driver/ivtv-ioctl.c:570: error: structure has no member named `i2c_id' make[3]: *** [/usr/src/ivtv-0.10.1/driver/ivtv-ioctl.o] Error 1 As stated in subject, its on 2.6.21rc7 I need the 2.6.21 because of the attanic ethernet driver, so cannot fall back to earlier kernel (new mobo). Cheers, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [ANNOUNCEMENT]: Updated xdriver available for testing
On Monday 19 February 2007 09:25, pomidorabelisima wrote: poma wrote: Red Hat Enterprise Linux Server release 4.92 (Tikanga): snip ivtv: version 0.10.0 (tagged release) X Window System Version 7.1.1 Release Date: 12 May 2006 X Protocol Version 11, Revision 0, Release 7.1.1 Build Operating System: Linux 2.6.9-34.ELsmp i686 Red This is on kernel 2.6.9 ivtv 0.10 is for kernels = 2.6.18 ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [ivtv-users] Branched off 0.10, started on 0.11 to get ivtv in the kernel
Hans Verkuil wrote: Hi all, As you may have noticed there has been a lot of activity lately. It looks like there is a good chance that ivtv can go in the 2.6.21 kernel. If some last API changes are accepted, then there is nothing that stands in the way. So I've branched off the ivtv-0.10 series in subversion. Basically ivtv-0.10 uses the current ivtv API, while the ivtv that is maintained in the subversion trunk will be converted to the new V4L2/DVB compliant API. This means that the trunk version will be unlikely to work with MythTV, etc., in particular when it comes to the PVR350. So if you need the latest driver from subversion, then you're better off with the 0.10 branch. The trunk where ivtv-0.11.0 is being developed is the code that will hopefully go into the kernel very soon. Fingers crossed... Regards, Hans Hans, I hope all your work results in inclusion in 2.6.21! Thanks for all the work! Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [Fwd: samsung based PVR500]
Rudy Zijlstra wrote: Dear all, To add to the previous email, i just realised the card seems to be OK, as when i load an ivtv driver with no Samsung tuner support, although i cannot tune, the tuned channels (warm reboot) are fully stable. So its the tuner control that makes the troubles (image wise). Summary: I can do either of the following two: - have good image (but no tuning) - ability to tune (but unwatchable image quality) Cheers, Rudy Sigh, Its been awhile since i did a full fresh mythtv setup. Grumble. Main problem solved, ivtv bug confirmed: - image quality is now good, bad image quality was caused by scaling to 480x480 (I've never understood this low default setting in myth. Changing that to PAL full format, and i had good image. Next setting the bitrate to some sensible quality and image quality became good.) As usual, once an ivtv parameter is set, it remains set until you reboot the card (hard power off). So for ivtv the scaling problem is still to be solved. (not that i personally care too much, i never scale down. HDD space is cheap, and on bigger screens you want to have high quality recordings). Thanks, Rudy Subject: samsung based PVR500 From: Rudy Zijlstra [EMAIL PROTECTED] Date: Mon, 25 Dec 2006 17:00:48 +0100 To: Discussion list for development of the IVTV driver ivtv-devel@ivtvdriver.org To: Discussion list for development of the IVTV driver ivtv-devel@ivtvdriver.org CC: Thijs Wennekes [EMAIL PROTECTED] Cher, I am building a myth server for a friend, and his PVR500 is samsung tuner based. Some different ivtv init messages: ivtv: START INIT IVTV ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [ivtv-users] PVR-350 firmware lock-ups + tips + probs in point form
Luke McKee wrote: Hello all, I have a PVR-350 NTSC version and I'm in a PAL country. I have over-rided the standard with PAL=M, and in full debug it seems to be putting the card in PAL mode. I also use v4l2-control to do this.The MSP44xx seems to support pal audio even though it is not listed in the module options. I have some strong doubts on whether you can get this to work in a stable way. Not because of any limitation on the main chipset (cx, msp,..) but because of the tuner. NTSC is a 6MHz bandwidth. PAL is either 7 or 8MHz. This means that when you use an NTSC tuner in PAL country, you will not capture all the signal. Especially on an 8MHz PAL signal you will loose way too much information. On a 7MHz you may get lucky and capture enough of the signal to get image / sound. I suspect though, that you will most often loose out on audio. I suspect the tuner will lock on the video carrier, and the audio carrier will at least partly be outside the SAW filter of the tuner. On an 8MHz PAL this will certainly be the case. Using SVHS will work around this problem. What i do not know, is whether the only difference between NTSC / PAL version is the tuner, or whether the routing on the card is also different. Hans may know this, having gone through the code in detail on this. A different problem you can run into, is that the firmware of the card may be making some assumptions. Like that when the tuner is an NTSC, then certain combinations are unexpected and thus not supported in the firmware. This is not so much a concious not supported as well as not foreseen to be used. The latest can lead to some very dificult to debug problems. Good luck! (i suspect buying a PAL version will safe you a lot of time and effort). Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] [Fwd: samsung based PVR500]
Dear all, To add to the previous email, i just realised the card seems to be OK, as when i load an ivtv driver with no Samsung tuner support, although i cannot tune, the tuned channels (warm reboot) are fully stable. So its the tuner control that makes the troubles (image wise). Summary: I can do either of the following two: - have good image (but no tuning) - ability to tune (but unwatchable image quality) Cheers, Rudy (Sorry Hans to directly copy, i still did not see the previous email to the list reflected) ---BeginMessage--- Cher, I am building a myth server for a friend, and his PVR500 is samsung tuner based. Some different ivtv init messages: ivtv: START INIT IVTV ivtv: version 0.4.7 (tagged release) loading ivtv: Linux version: 2.6.15.6 SMP PENTIUM4 REGPARM 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 WinTV PVR 150 card (cx23416 based) ACPI: PCI Interrupt :03:08.0[A] - GSI 20 (level, low) - IRQ 50 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tveeprom 1-0050: Hauppauge model 23559, rev D596, serial# 9822524 tveeprom 1-0050: tuner model is Samsung TCPG_6121P30A (idx 96, type 4) tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom 0x74) tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 1-0050: audio processor is CX25843 (idx 37) tveeprom 1-0050: decoder processor is CX25843 (idx 30) tveeprom 1-0050: has radio, has no IR remote ivtv0: This is the first unit of a PVR500 tuner 1-0060: TEA5767 detected. tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60] tuner 1-0060: type set to 62 (Philips TEA5767HN FM Radio) tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840 1-0044: ivtv driver cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] 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: 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 tuner 1-0061: tuner type not set tuner 1-0061: tuner type not set ivtv0: Initialized WinTV PVR 500 (unit #1), card #0 ivtv: == NEXT CARD == Kernel 2.6.19:Dec 25 10:46:16 myth-master kernel: ivtv: START INIT IVTV Dec 25 10:46:16 myth-master kernel: ivtv: version 0.9.1 (tagged release) loading Dec 25 10:46:16 myth-master kernel: ivtv: Linux version: 2.6.19 SMP mod_unload PENTIUM4 REGPARM Dec 25 10:46:16 myth-master kernel: ivtv: In case of problems please include the debug info between Dec 25 10:46:16 myth-master kernel: ivtv: the START INIT IVTV and END INIT IVTV lines, along with Dec 25 10:46:16 myth-master kernel: ivtv: any module options, when mailing the ivtv-users mailinglist. Dec 25 10:46:16 myth-master kernel: ivtv0: Autodetected Hauppauge card (cx23416 based) Dec 25 10:46:16 myth-master kernel: ACPI: PCI Interrupt :03:08.0[A] - GSI 21 (level, low) - IRQ 22 Dec 25 10:46:16 myth-master kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32) Dec 25 10:46:16 myth-master kernel: ACPI: PCI Interrupt :00:1e.2[A] - GSI 17 (level, low) - IRQ 23 Dec 25 10:46:16 myth-master kernel: intel8x0_measure_ac97_clock: measured 52882 usecs Dec 25 10:46:16 myth-master kernel: intel8x0: clocking to 48000 Dec 25 10:46:16 myth-master kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: Hauppauge model 23559, rev D596, serial# 9822524 Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: tuner model is Samsung TCPG 6121P30A (idx 96, type 73) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: audio processor is
[ivtv-devel] samsung based PVR500
Cher, I am building a myth server for a friend, and his PVR500 is samsung tuner based. Some different ivtv init messages: ivtv: START INIT IVTV ivtv: version 0.4.7 (tagged release) loading ivtv: Linux version: 2.6.15.6 SMP PENTIUM4 REGPARM 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 WinTV PVR 150 card (cx23416 based) ACPI: PCI Interrupt :03:08.0[A] - GSI 20 (level, low) - IRQ 50 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tveeprom 1-0050: Hauppauge model 23559, rev D596, serial# 9822524 tveeprom 1-0050: tuner model is Samsung TCPG_6121P30A (idx 96, type 4) tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom 0x74) tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) tveeprom 1-0050: audio processor is CX25843 (idx 37) tveeprom 1-0050: decoder processor is CX25843 (idx 30) tveeprom 1-0050: has radio, has no IR remote ivtv0: This is the first unit of a PVR500 tuner 1-0060: TEA5767 detected. tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=60] tuner 1-0060: type set to 62 (Philips TEA5767HN FM Radio) tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] cx25840 1-0044: ivtv driver cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes) ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44] wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b] tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] 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: 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 tuner 1-0061: tuner type not set tuner 1-0061: tuner type not set ivtv0: Initialized WinTV PVR 500 (unit #1), card #0 ivtv: == NEXT CARD == Kernel 2.6.19:Dec 25 10:46:16 myth-master kernel: ivtv: START INIT IVTV Dec 25 10:46:16 myth-master kernel: ivtv: version 0.9.1 (tagged release) loading Dec 25 10:46:16 myth-master kernel: ivtv: Linux version: 2.6.19 SMP mod_unload PENTIUM4 REGPARM Dec 25 10:46:16 myth-master kernel: ivtv: In case of problems please include the debug info between Dec 25 10:46:16 myth-master kernel: ivtv: the START INIT IVTV and END INIT IVTV lines, along with Dec 25 10:46:16 myth-master kernel: ivtv: any module options, when mailing the ivtv-users mailinglist. Dec 25 10:46:16 myth-master kernel: ivtv0: Autodetected Hauppauge card (cx23416 based) Dec 25 10:46:16 myth-master kernel: ACPI: PCI Interrupt :03:08.0[A] - GSI 21 (level, low) - IRQ 22 Dec 25 10:46:16 myth-master kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32) Dec 25 10:46:16 myth-master kernel: ACPI: PCI Interrupt :00:1e.2[A] - GSI 17 (level, low) - IRQ 23 Dec 25 10:46:16 myth-master kernel: intel8x0_measure_ac97_clock: measured 52882 usecs Dec 25 10:46:16 myth-master kernel: intel8x0: clocking to 48000 Dec 25 10:46:16 myth-master kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: Hauppauge model 23559, rev D596, serial# 9822524 Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: tuner model is Samsung TCPG 6121P30A (idx 96, type 73) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) (eeprom 0x74) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101, type 62) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: audio processor is CX25843 (idx 37) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: decoder processor is CX25843 (idx 30) Dec 25 10:46:16 myth-master kernel: tveeprom 1-0050: has radio, has no IR remote Dec 25 10:46:16 myth-master kernel: ivtv0: Autodetected WinTV PVR 500 (unit #1) Dec 25 10:46:16 myth-master kernel: tuner 1-0043: chip found @ 0x86 (ivtv i2c driver #0) Dec 25 10:46:16 myth-master kernel: tda9887 1-0043: tda988[5/6/7] found @ 0x43 (tuner) Dec 25 10:46:16 myth-master kernel: tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0) Dec 25
Re: [ivtv-devel] oops on modprobe ivtv
D. Hugh Redelmeier wrote: | From: Rudy Zijlstra [EMAIL PROTECTED] | Mr. Myth wrote: | | D. Hugh Redelmeier wrote: | I have no advice. However, I too am seeing this problem as well on the | 2.6.17-1.2139+FC4 kernel and ivtv-kmdl-2.6.17-1.2139_FC4-0.7-115.rhfc4.at. | | I just reverted to the last 2.6.16 kernel for the time being. | | Michael | | Which version of ivtv are you using? 0.7 is intended for the 2.7.17 kernel. Huh? I don't think that there is a 2.7 kernel series yet. Perhaps there should be, but the development model changed and there is no unstable series any more. Or is that the unstable series took over the stable series' number? Typo: 2.6.17 :-[ If you (Rudy) meant 2.6.17, then you will see that Mr. Myth is using one of them (and so am I). His was for FC4 and mine was for FC5. Those are what the ATRPMS packages were built for, as I understand it. But it looks like something is wrong. Both Mr. Myth and I have problems. Someone on IRC (freenode #ivtv-dev) suggested: fuzzie well, the last calls there are to the video device registration stuff, on top of v4l stuff being tainted perhaps your v4l is wonky. but i don't really have a clue for what's really up, have you tried just compiling ivtv against FC5+updates kernel source? I have not done that but perhaps I should. I was getting a hint that IVTV doesn't build well on FC5 -- the normal kernel headers are not sufficient. So it seemed like another level of adventure. I'm hoping that an adventure is not required. I am running 0.7 against vanilla 2.6.17.4 kernel from kernel.org, and sofar no problems. Slackware-current installation. I've been using slackware since 1996 or so, and still very satisfied with that distro. Sometimes i will use Debian, but any RedHat trial has ended in frustration on my side. Cheers, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Firmware not found on SuSE 10.1 with IVTV 0.6.3
Andreas Schaefer wrote: Hi Geeks I am trying again to install IVTV on a SuSE 10.1 AMD64 box. This time IVTV started to load but failed to find the firmware. On the user mailing list there seems a lot of discussion about it but even the latest tarball did not fix the problem. This is the DMESG output: ivtv: module not supported by Novell, setting U taint flag. ivtv: START INIT IVTV ivtv: version 0.6.4 (development snapshot compiled on Sat Jul 8 15:48:05 2006) loading ivtv: Linux version: 2.6.16.13-4-default 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 Hauppauge WinTV PVR-350 card (cx23415 based) tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) tda9887 2-0043: chip found @ 0x86 (ivtv i2c driver #0) saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) saa7127 2-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) msp3400 2-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) ivtv0: unable to open firmware v4l-cx2341x-enc.fw ivtv0: did you put the firmware in the hotplug firmware directory? ivtv0 warning: failed loading encoder firmware ivtv0 warning: Error loading firmware -3! ivtv0: Error -3 initializing firmware. ivtv0: Error -12 on initialization ivtv: probe of :02:07.0 failed with error -12 ivtv: END INIT IVTV I put the firmware in '/usr/bin/hotplug/firmware' as well as the old '/usr/lib/hotplug/firmware' directory. But neither seems to work. Any help - Andy P.S.: I could not figure out the right location of the hotplug firmware directory and so I was wondering how IVTV obtains it and if it would not be possible to print the location when IVTV cannot find the firmware. It for sure would help many developers. Another location to try: /lib/firmware (slackware location). Firmware location is distro determined. I have no idea where Suse is putting it. If you can find the hotplug scripts, you should find the location. Cheers, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] oops on modprobe ivtv
Mr. Myth wrote: D. Hugh Redelmeier wrote: [Sorry if this is the wrong list. My subscribe request to -users is still pending, and I seem to remember that nobody reads -users anyway.] I am getting an oops on modprobing ivtv. Any idea why? Any suggestions of what I should do? Hardware: clone with Athlon CPU, PVR-250 card, ATI video card, lots of RAM and disk. I have no advice. However, I too am seeing this problem as well on the 2.6.17-1.2139+FC4 kernel and ivtv-kmdl-2.6.17-1.2139_FC4-0.7-115.rhfc4.at. I just reverted to the last 2.6.16 kernel for the time being. Michael Which version of ivtv are you using? 0.7 is intended for the 2.7.17 kernel. Cheers, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [NEWS] Released ivtv-0.7.0
Hans Verkuil wrote: Hi all, I've just released ivtv-0.7.0 for the 2.6.17 kernel. Available here: http://dl.ivtvdriver.org/ivtv/archive/0.7.x/ivtv-0.7.0.tar.gz It has all the features of the ivtv-0.6.3 and also these: 0.7.0 release - Added support for the DIGITAL COWBOY DCT-MTVP1 card - Updated driver to use the new ROUTING commands of the video4linux subsystem. - Removed upd64083, upd64031a and wm8739: these are now in the 2.6.17 kernel. - The ivtv driver now uses the I2C_HW_B_CX2341X board ID, instead of borrowing the bttv ID. The latter will cause lirc problems. AFAIK these are fixed in the latest lirc from their repository. Hans, on a slackware-current install with kernel 2.6.17.4 i get the following after having copied videodev2.h to /usr/include/linux: make[2]: Leaving directory `/usr/src/ivtv-0.7.0/driver' cc -I/usr/src/ivtv-0.7.0/utils/../driver -I. -D_GNU_SOURCE -O2 -Wall ivtvfbctl.c -o ivtvfbctl g++ -I/usr/src/ivtv-0.7.0/utils/../driver -I. -D_GNU_SOURCE -O2 -Wall -o ivtv-detect ivtv-detect.cpp ivtv-detect.cpp:51: error: field `cap' has incomplete type ivtv-detect.cpp: In function `card_info* find_card(const v4l2_capability*, int, int, const std::string)': ivtv-detect.cpp:65: error: invalid use of undefined type `const struct v4l2_capability' ivtv-detect.cpp:51: error: forward declaration of `const struct v4l2_capability' ivtv-detect.cpp:65: error: 'struct card_info' has no member named 'cap' ivtv-detect.cpp:69: error: 'struct card_info' has no member named 'cap' ivtv-detect.cpp: In function `int main(int, char**)': ivtv-detect.cpp:136: error: aggregate `v4l2_capability cap' has incomplete type and cannot be defined ivtv-detect.cpp:146: error: `VIDIOC_QUERYCAP' was not declared in this scope ivtv-detect.cpp:146: warning: unused variable 'VIDIOC_QUERYCAP' ivtv-detect.cpp:215: error: 'struct card_info' has no member named 'cap' ivtv-detect.cpp:219: error: 'struct card_info' has no member named 'cap' ivtv-detect.cpp:222: error: 'struct card_info' has no member named 'cap' ivtv-detect.cpp:223: error: 'struct card_info' has no member named 'cap' ivtv-detect.cpp:224: error: 'struct card_info' has no member named 'cap' make[1]: *** [ivtv-detect] Error 1 make[1]: Leaving directory `/usr/src/ivtv-0.7.0/utils' make: *** [all] Error 2 This is with gcc version: [EMAIL PROTECTED]:/usr/src/ivtv-0.7.0# gcc --version gcc (GCC) 3.4.6 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. After doing: [EMAIL PROTECTED]:/usr/include# ln -s /usr/src/linux-2.6.17.4/include/linux linux Things compiled. Cheers, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] [Fwd: X problems with 0.4.1]
Joe Votour wrote: --- Rudy Zijlstra [EMAIL PROTECTED] wrote: This time to the correct list Date: Sun, 15 Jan 2006 02:24:20 +0100 From: Rudy Zijlstra [EMAIL PROTECTED] To: ivtv-devel@lists.sourceforge.net Subject: X problems with 0.4.1 Hello, building a new Myth frontend with PVR350 TV out. I'm stuck on the following message from xorg: (--) Chipset PVR-350 found (EE) ivtvHWProvbe failed to do IVTVFB_IOCTL_GET_STATE for device (null) (EE) Screen 0 deleted because of no matching config section. (II) UnloadModule: ivtvdev (EE) Device(s) detected, but none match those in the config file. I'm very open to suggestions on how to solve this. Cheers, Rudy Needed config info: The information from dmesg: ivtv: START INIT IVTV ivtv: version 0.4.1 (tagged release) loading ivtv: Linux version: 2.6.14 preempt PENTIUM4 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 350 card (cx23415 based) ACPI: PCI Interrupt :02:09.0[A] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] saa7115 0-0021: ivtv driver saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] saa7127 0-0044: ivtv driver saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] msp34xx: init: chip=MSP3418W-A2 +nicam +simple +simpler +radio mode=simpler msp34xxg: daemon started ivtv0: i2c attach to card #0 ok [client=MSP3418W-A2, addr=40] tveeprom 0-0050: Hauppauge model 48134, rev J347, serial# 7014191 tveeprom 0-0050: tuner model is LG TP18PSB01D (idx 47, type 28) tveeprom 0-0050: TV standards PAL(B/G) (eeprom 0x04) tveeprom 0-0050: audio processor is MSP4418 (idx 25) tveeprom 0-0050: decoder processor is SAA7115 (idx 19) tveeprom 0-0050: has radio, has IR remote ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02040011 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-mpeg.bin firmware (155648 bytes) tuner 0-0061: type set to 28 (LG PAL_BG+FM (TPI8PSB01D)) ivtv0: Initialized WinTV PVR 350, card #0 ivtv: END INIT IVTV ivtv0-osd: Framebuffer module loaded (attached to ivtv card id 0) ivtv0-osd warning: Framebuffer is at decoder-relative address 0x0051 and has 1704960 bytes. 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 0xf951, mapped to 0xd1b9, size 1620k ivtv0-osd: mode is 720x576x32, linelength=2880 ivtv0-osd: fb1: cx23415 TV out frame buffer device = See xorg.conf entry below which points to /dev/fb1 ivtv0: Allocate DMA decoder OSD stream: 16 x 65536 buffers (1024KB total) ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel Is your PCI bus ID (the line BusID) correct for your PVR-350? You also have the correct framebuffer (/dev/fbx) device, right? Both of these will keep XFree86 from working. Additionally, we need to see the Monitor section to make sure that everything points to the correct places. -- Joe lspci: 02:09.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) xorg.conf: Section Device Identifier Hauppage PVR350 Driver ivtvdev Option ivtvdev /dev/fb1 BusID PCI:2:9:0 EndSection Section Monitor Identifier PAL TV HorizSync 30-68 VertRefresh 50-120 DisplaySize 240 180 Mode 720x576 DotClock 42.6 HTimings 720 760 832 944 VTimings 576 577 580 602 Flags-HSync -VSync EndMode EndSection Section Screen Identifier TV Device Hauppage PVR350 Monitor PAL TV DefaultDepth24
Re: [ivtv-devel] [Fwd: X problems with 0.4.1]
Got it working by removing the console frame buffer. Still do not understand it though One problem remaining: - DVB-S MPEG2 recordings play only partly: i get video OK, but no audio. - same when i do live-TV from one of the SAT tuners. Cheers, Rudy Rudy Zijlstra wrote: Joe Votour wrote: --- Rudy Zijlstra [EMAIL PROTECTED] wrote: This time to the correct list Date: Sun, 15 Jan 2006 02:24:20 +0100 From: Rudy Zijlstra [EMAIL PROTECTED] To: ivtv-devel@lists.sourceforge.net Subject: X problems with 0.4.1 Hello, building a new Myth frontend with PVR350 TV out. I'm stuck on the following message from xorg: (--) Chipset PVR-350 found (EE) ivtvHWProvbe failed to do IVTVFB_IOCTL_GET_STATE for device (null) (EE) Screen 0 deleted because of no matching config section. (II) UnloadModule: ivtvdev (EE) Device(s) detected, but none match those in the config file. I'm very open to suggestions on how to solve this. Cheers, Rudy Needed config info: The information from dmesg: ivtv: START INIT IVTV ivtv: version 0.4.1 (tagged release) loading ivtv: Linux version: 2.6.14 preempt PENTIUM4 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 350 card (cx23415 based) ACPI: PCI Interrupt :02:09.0[A] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] saa7115 0-0021: ivtv driver saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] saa7127 0-0044: ivtv driver saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] msp34xx: init: chip=MSP3418W-A2 +nicam +simple +simpler +radio mode=simpler msp34xxg: daemon started ivtv0: i2c attach to card #0 ok [client=MSP3418W-A2, addr=40] tveeprom 0-0050: Hauppauge model 48134, rev J347, serial# 7014191 tveeprom 0-0050: tuner model is LG TP18PSB01D (idx 47, type 28) tveeprom 0-0050: TV standards PAL(B/G) (eeprom 0x04) tveeprom 0-0050: audio processor is MSP4418 (idx 25) tveeprom 0-0050: decoder processor is SAA7115 (idx 19) tveeprom 0-0050: has radio, has IR remote ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02040011 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-mpeg.bin firmware (155648 bytes) tuner 0-0061: type set to 28 (LG PAL_BG+FM (TPI8PSB01D)) ivtv0: Initialized WinTV PVR 350, card #0 ivtv: END INIT IVTV ivtv0-osd: Framebuffer module loaded (attached to ivtv card id 0) ivtv0-osd warning: Framebuffer is at decoder-relative address 0x0051 and has 1704960 bytes. 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 0xf951, mapped to 0xd1b9, size 1620k ivtv0-osd: mode is 720x576x32, linelength=2880 ivtv0-osd: fb1: cx23415 TV out frame buffer device = See xorg.conf entry below which points to /dev/fb1 ivtv0: Allocate DMA decoder OSD stream: 16 x 65536 buffers (1024KB total) ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel Is your PCI bus ID (the line BusID) correct for your PVR-350? You also have the correct framebuffer (/dev/fbx) device, right? Both of these will keep XFree86 from working. Additionally, we need to see the Monitor section to make sure that everything points to the correct places. -- Joe lspci: 02:09.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) xorg.conf: Section Device Identifier Hauppage PVR350 Driver ivtvdev Option ivtvdev /dev/fb1 BusID PCI:2:9:0 EndSection Section Monitor Identifier PAL TV HorizSync 30-68 VertRefresh 50-120
Re: [ivtv-devel] ivtv, mythtv, and reboot
espnleo linux wrote: Hello, I have a PVR250, installed mythtv, everything was fine. Then I made the mistake of rebooting my computer, and ivtv seems to hang. No video in myth. when I try to use mplayer to watch an mpg file recorded straight from /dev/video0, it produces an empty file. The ivtv portion of the system logs can be found below. Any suggestions. Thanks in advance Leo You seem to be the happy owner of a PVR250 that needs a cold boot in order to behave nicely. Try a cold boot (and without power for at least 20 seconds). ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] Will ivtv be merged in mainline anytime soon ?
Nicolas Mailhot wrote: Hi, I'm sorry if this is a FAQ, but I searched the Wiki and couldn't answer this question. Right now ivtv is developed separately from the mainline kernel. Are there any plans (and ETAs) for merging it in mainline ? My past experience with out-of-tree drivers have been nothing short of disastrous. It seems a cool idea at first (isolating changes) but it always ends up in train wrecks with either the out-of-tree project fading from relevance (openswan) or years of painful merging (alsa). This was true in 2.4 and is even more true in 2.6 with its fast change rate (some of which like latency work directly relevant to HTPC use). And in the meanwhile if there is a single problem the out-of-tree developers accuse mainline of changing things behind their feet, and mainline developers accuse out-of-tree of not staying in sync with mainline changes (sync which would have been automatic with a marged driver). And the end-user who cares little about which fault it is is left with a broken system. So before I invest in hardware that requires ivtv to work, I'd like to know if a merge is been worked on or if the ivtv team decided not to bother with merging, and offload code sync problems on users. If a merge is planned with clear milestones and people working on it I'm ready to put up with out-of-tree problems for some time. If not I'll just choose hardware with a merged/being-merged driver. I value my time too much to put up with the hassles out-of-tree drivers cause. Regards, See http://www.gossamer-threads.com/lists/ivtv/devel/23179 and http://www.gossamer-threads.com/lists/ivtv/devel/25060 You could of course assist in helping. We value your valuable time... Cheers, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] PVR500 ivtv 0.4.0 module loading issue
Michael Norman wrote: I am trying to install a PVR500 card into a new AMD64 machine running Gentoo (2.6.13-gentoo-r4) and using version 0.4.0 of ivtv. The modules (tveeprom, tuner, etc.) fail to load automatically. I have tried modprobe'ing the relevant modules manually prior to modprobe'ing ivtv to no avail. Any ideas? Just modprobe'ing ivtv results in the following: # lsmod Module Size Used by nvidia 4384136 12 # modprobe ivtv # lsmod Module Size Used by ivtv 208212 0 i2c_algo_bit 10568 1 ivtv i2c_core 21312 1 i2c_algo_bit videodev 11520 1 ivtv nvidia 4384136 12 Check you kernel config to see whether you have automatic module loading enabled. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] No sound on pvr-350
Louie Ilievski wrote: On Saturday 22 October 2005 07:29 pm, Brent Kilgore wrote: Here is something new/different in the logs. Get the same error statement no matter what driver version I use now. Everything else in the ivtv block appears identical. I will scan through it again see if there are any other differences. Why is it no longer autodetecting the audio mode? How do I set it manually if this is no longer going to work? Thanks Have you made sure to rename/delete the kernel versions of msp3400.ko, tda9887.ko and tuner.ko? Maybe somewhere in the process of upgrading you got the kernel versions again. Just a thought. Also, have you done a cold boot? Possibly the card needs a full reset. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] xorg problem
Dear, I had a working ivtv-fb system on a 350. I upgraded this to the latest ivtvdev_drv and now have a non-working setup... Error message i get is: No matching device section in Xorg.log. This by ivtvdrv... Any idea what is wrong? Any suggestion what to improve? Thanks, Rudy ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
