Menu
▾
▴
ivtv-devel — Developers' list for the ivtv iTVC15 driver Project
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(245) |
Mar
(714) |
Apr
(690) |
May
(946) |
Jun
(454) |
Jul
(398) |
Aug
(339) |
Sep
(328) |
Oct
(609) |
Nov
(742) |
Dec
(843) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(1136) |
Feb
(558) |
Mar
(830) |
Apr
(656) |
May
(785) |
Jun
(1148) |
Jul
(729) |
Aug
(547) |
Sep
(1048) |
Oct
(1240) |
Nov
(762) |
Dec
(615) |
| 2005 |
Jan
(784) |
Feb
(836) |
Mar
(1002) |
Apr
(966) |
May
(980) |
Jun
(896) |
Jul
(780) |
Aug
(927) |
Sep
(878) |
Oct
|
Nov
|
Dec
|
|
From: Michel V. <Mi...@ve...> - 2005-09-25 19:48:04
|
Hans,
I have been using version *ivtv: Encoder revision: 0x02050032 *since
version 0.3.4 and up with out any problems on my PVR150 and PVR350.
Regards,
Michel.
Hans Verkuil wrote:
>The driver contains the following check:
>
> if (data[0] > 0x02040011)
> IVTV_DEBUG_WARN("Encoder Firmware can be buggy, use version
>0x02040011.\n");
>
>Is this still valid? I get the impression that this is no longer an issue. Are
>there actually buggy firmware versions?
>
> Hans
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by:
>Tame your development challenges with Apache's Geronimo App Server.
>Download it for free - -and be entered to win a 42" plasma tv or your very
>own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
>_______________________________________________
>ivtv-devel mailing list
>ivt...@li...
>https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>
>
|
|
From: Michel V. <Mi...@ve...> - 2005-09-25 19:47:49
|
Hans, Sorry for the late answer. I was a short weekend away. Just now (sun 25th september 20:40) I updated to subversion 2710 and the problem, audio kicking in late, seems to be gone. I will do some extra testing. Answers to your question see below. Regards, Michel. Hans Verkuil wrote: >On Saturday 24 September 2005 08:47, Michel Verbraak wrote: > > >>Hans, >> >>Spoke to soon. The sound kicking in late is still there on the same >>channels as before. >>Probably on my firt test the sound was found fast. >> >>Is there any tool to test the incoming signal strength for the set channel? >> >>Wat I will try this weekend, when I have time, to go back to the >>recomended firware versions to see if this fixes it. I'm still using the >>newer ones. >> >> > >Questions: > >1) It happens only with your PVR150, right? > > Yes Only for my PVR150 (non MCE) >2) Which channels give the problem? And more specific: from which country? > > I'm in the Netherlands. Casema Soest and SBS6 (frequency 639,25), Net5 (681,25) and Ned3 (189,25) were the channels I had problems with. >I'm pretty sure it's related to the cx25840 autodetect settings and not to any >firmware versions. Doesn't do any harm to try, though, if only to rule out >that approach. > > Hans > > >------------------------------------------------------- >SF.Net email is sponsored by: >Tame your development challenges with Apache's Geronimo App Server. >Download it for free - -and be entered to win a 42" plasma tv or your very >own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php >_______________________________________________ >ivtv-devel mailing list >ivt...@li... >https://lists.sourceforge.net/lists/listinfo/ivtv-devel > > -8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<- ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.3.9 (development svn snapshot revision 2710) loading ivtv: Linux version: 2.6.12-1.1456_FC4smp SMP 686 REGPARM 4KSTACKS gcc-4.0 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 0000:02:0c.0[A] -> GSI 20 (level, low) -> IRQ 193 tveeprom: ivtv version tveeprom: Hauppauge: model = 26059, rev = C155, serial# = 7583011 tveeprom: tuner = Philips FQ1216ME MK3 (idx = 55, type = 38) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50] tuner (ivtv): 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, addr=44] ivtv: i2c attach to card #0 ok [client=wm8775, addr=1b] tda9885/6/7: (ivtv) chip found @ 0x86 ivtv: i2c attach to card #0 ok [client=tda9887, addr=43] ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: Encoder revision: 0x02050032 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: 161 x 12960 buffers (2048KB total) ivtv: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c driver #0 ivtv: Initialized WinTV PVR 150, card #0 ivtv: ====================== NEXT CARD ====================== ivtv: Autodetected WinTV PVR 350 card (iTVC15 based) ACPI: PCI Interrupt 0000:02:0d.0[A] -> GSI 21 (level, low) -> IRQ 201 tveeprom: ivtv version tveeprom: Hauppauge: model = 48134, rev = I121, serial# = 6182877 tveeprom: tuner = Philips FM1216 (idx = 21, type = 5) tveeprom: tuner fmt = PAL(B/G) (eeprom = 0x04, v4l2 = 0x00000007) tveeprom: audio processor = MSP4418 (type = 19) tveeprom: decoder processor = SAA7115 (type = 13) ivtv: i2c attach to card #1 ok [client=tveeprom[50], addr=50] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #1 ivtv: i2c attach to card #1 ok [client=(tuner unset), addr=61] ivtv: i2c attach to card #1 ok [client=saa7115[50], addr=21] saa7127 2-0044: saa7127 found @ 0x88 (ivtv i2c driver #1) ivtv: i2c attach to card #1 ok [client=saa7127, addr=44] msp34xx: ivtv version msp34xx: init: chip=MSP3418W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode msp34xx: $Id$ compiled on: Sep 25 2005 20:34:43 ivtv: i2c attach to card #1 ok [client=MSP3418W-A2, addr=40] ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: loading /lib/modules/ivtv-fw-dec.bin ivtv: Encoder revision: 0x02050032 ivtv warning: Encoder Firmware can be buggy, use version 0x02040011!!!! ivtv: Decoder revision: 0x02020023 ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv: Create encoder radio stream ivtv: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv: Create decoder VOUT stream ivtv: Allocate DMA decoder YUV stream: 20 x 51840 buffers (1024KB total) tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles)) by ivtv i2c driver #1 ivtv: Initialized WinTV PVR 350, card #1 ivtv: ==================== END INIT IVTV ==================== |
|
From: Tyler T. <tat...@co...> - 2005-09-25 19:41:05
|
Hans Verkuil wrote:
> The driver contains the following check:
>
> if (data[0] > 0x02040011)
> IVTV_DEBUG_WARN("Encoder Firmware can be buggy, use version
> 0x02040011.\n");
>
> Is this still valid? I get the impression that this is no longer an issue. Are
> there actually buggy firmware versions?
According to Chris, people should use either that version or 0x02050032.
--
Tyler Trafford
|
|
From: Lorrin N. <lhn...@ne...> - 2005-09-25 19:07:19
|
I'm only seeing snow from my PVR-250. My best guess is that the problem is that even though tveeprom detects the correct tuner type the tuner module doesn't clue in. Are their options I should be telling modprobe to pass to the tuner module? Thanks! -Lorrin Sep 25 11:39:30 tomato kernel: ivtv: ==================== START INIT IVTV ==================== Sep 25 11:39:30 tomato kernel: ivtv: version 0.3.8 (tagged release) loading Sep 25 11:39:30 tomato kernel: ivtv: Linux version: 2.6.8 SMP preempt PENTIUM4 gcc-3.3 Sep 25 11:39:30 tomato kernel: ivtv: In case of problems please include the debug info Sep 25 11:39:30 tomato kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when Sep 25 11:39:30 tomato kernel: ivtv: mailing the ivtv-devel mailinglist. Sep 25 11:39:30 tomato kernel: ivtv: Autodetected WinTV PVR 250 card (iTVC16 based) Sep 25 11:39:30 tomato kernel: ACPI: PCI interrupt 0000:02:0b.0[A] -> GSI 23 (level, low) -> IRQ 23 Sep 25 11:39:30 tomato kernel: msp34xx: init: chip=MSP3445G-B8 +nicam +simple +radio Sep 25 11:39:30 tomato kernel: ivtv: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40] Sep 25 11:39:30 tomato kernel: msp3410: daemon started Sep 25 11:39:30 tomato kernel: tuner: chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 Sep 25 11:39:30 tomato kernel: ivtv: i2c attach to card #0 ok [client=(tuner unset), addr=61] Sep 25 11:39:30 tomato kernel: tveeprom: Ignoring new-style parameters in presence of obsolete ones Sep 25 11:39:30 tomato kernel: tveeprom: Hauppauge: model = 32062, rev = C199, serial# = 8115526 Sep 25 11:39:30 tomato kernel: tveeprom: tuner = TCL 2002N 5H (idx = 99, type = 50) Sep 25 11:39:30 tomato kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) Sep 25 11:39:30 tomato kernel: tveeprom: audio processor = MSP3445 (type = c) Sep 25 11:39:30 tomato kernel: tveeprom: decoder processor = SAA7115 (type = 13) Sep 25 11:39:30 tomato kernel: ivtv: i2c attach to card #0 ok [client=tveeprom[50], addr=50] Sep 25 11:39:30 tomato kernel: saa7115: Ignoring new-style parameters in presence of obsolete ones Sep 25 11:39:30 tomato kernel: ivtv: i2c attach to card #0 ok [client=saa7115[50], addr=21] Sep 25 11:39:30 tomato kernel: ivtv: requesting ivtv-fw-enc.bin from hotplug Sep 25 11:39:30 tomato kernel: ivtv: Encoder revision: 0x02040011 Sep 25 11:39:30 tomato kernel: ivtv: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) Sep 25 11:39:30 tomato kernel: ivtv: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) Sep 25 11:39:30 tomato kernel: ivtv: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) Sep 25 11:39:30 tomato kernel: ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) Sep 25 11:39:30 tomato kernel: tuner: tuner type not set Sep 25 11:39:30 tomato kernel: ivtv: Initialized WinTV PVR 250, card #0 Sep 25 11:39:30 tomato kernel: ivtv: ==================== END INIT IVTV ==================== |
|
From: John H. <joh...@bt...> - 2005-09-25 19:07:06
|
Maybe. I'm actually still working on the initialization but may give up soon and just submit the code I have that plays the smallest mpeg file I have that initializes the video. However I am trying to to work out what actually changes when video is decoded. If I get past this I have some changes I want to make to reduce the work done each frame which should save cpu and possibly help with this problem. John > -----Original Message----- > From: ivt...@li... [mailto:ivtv-devel- > ad...@li...] On Behalf Of Lucas Meijer > Sent: 25 September 2005 18:27 > To: ivt...@li... > Subject: Re: [ivtv-devel] Please check: list of remaining driver problems > > Hans Verkuil wrote: > > Well, it looks like the major sound problems have been resolved. This > means > > that it is time to evaluate what still has to be done before 0.3.9 can > be > > released. Below is a list of known problems and what their status is. > Please > > check this and notify me if I've missed one. > > Hey Hans, > > I'm assuming xv issues are not for the .3 branch, but in case I'm > mistaking: there are still some a/v issues with xv playback on the > pvr350. a/v gets out of sync, but only a very little bit. it gets > noticable after +- 20 minutes of watching. a quick 5 second rewind fixes > the problem for the next 20 minutes. > > Bye, Lucas > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. > Download it for free - -and be entered to win a 42" plasma tv or your very > own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > ivtv-devel mailing list > ivt...@li... > https://lists.sourceforge.net/lists/listinfo/ivtv-devel |
|
From: <nh...@es...> - 2005-09-25 18:51:44
|
I will look into that tomorrow afternoon, and report back when i find somet= hing of interest. Best regards Niels Hans Verkuil <hve...@xs...> wrote: > On Sunday 25 September 2005 19:49, nh...@es... wrote: > > Hi Hans. > > > > Thankyou for your quick response. > > However, i thought you might like to know that after > upgrading to the SVN > > version i picked up this morning, the picture quality > became notably worse, > > a lot of blur was introduced by this change. So i changed > back to 2696,( > > using type 68 ) and all was fine again. >=20 > Can you do me a big favor and test with versions 2700, 2702 > and 2703? Let me=20 > know where the quality changes. Must be somewhere around > these versions. >=20 > Hans >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App > Server.=20 > Download it for free - -and be entered to win a 42" plasma > tv or your very > own Sony(tm)PSP. Click here to play: > http://sourceforge.net/geronimo.php > _______________________________________________ > ivtv-devel mailing list > ivt...@li... > https://lists.sourceforge.net/lists/listinfo/ivtv-devel |
|
From: Hans V. <hve...@xs...> - 2005-09-25 18:25:59
|
The driver contains the following check:
if (data[0] > 0x02040011)
IVTV_DEBUG_WARN("Encoder Firmware can be buggy, use version
0x02040011.\n");
Is this still valid? I get the impression that this is no longer an issue. Are
there actually buggy firmware versions?
Hans
|
|
From: Adam F. <agf...@gm...> - 2005-09-25 18:02:42
|
On 9/25/05, Claude M. Schrader <iv...@cl...> wrote: > hmm - no luck with that, unfortunately. I took that section right out of > the fedora howto - I assume that was based on an older ivtv rev? Yeah, that's for the 0.1 and 0.2 series. Did your dmesg change after you removed those and rebooted? The tveeprom etc weren't being loaded, I assumed those lines were why... |
|
From: Hans V. <hve...@xs...> - 2005-09-25 18:01:24
|
On Sunday 25 September 2005 19:24, Bill Graef wrote: > Currenty running with the svn revision 2710. What is seen is a static > picture on /dev/video0, while on > /dev/video1 the picture is clear. Sound works on both. I'm waiting for input from Andrew Saunders, who has the same tuner (and he has sound problems). With a bit of luck the problems are related. Meanwhile, can you do a quick check? Load the tuner and tda9887 modules with module option debug=1. Select the same channel for both tuners and verify that the first has static and the second is fine. Please post the tuner and tda9887 debug output. Hans |
|
From: Hans V. <hve...@xs...> - 2005-09-25 17:56:20
|
On Sunday 25 September 2005 19:49, nh...@es... wrote: > Hi Hans. > > Thankyou for your quick response. > However, i thought you might like to know that after upgrading to the SVN > version i picked up this morning, the picture quality became notably worse, > a lot of blur was introduced by this change. So i changed back to 2696,( > using type 68 ) and all was fine again. Can you do me a big favor and test with versions 2700, 2702 and 2703? Let me know where the quality changes. Must be somewhere around these versions. Hans |
|
From: <nh...@es...> - 2005-09-25 17:50:05
|
Hi Hans. Thankyou for your quick response. However, i thought you might like to know that after upgrading to the SVN v= ersion i picked up this morning,=20 the picture quality became notably worse, a lot of blur was introduced by t= his change.=20 So i changed back to 2696,( using type 68 ) and all was fine again. Best regards Niels Hoffmann > > Detection of the (LG) tuner type, has also changed from > svn 2694 where type > > 68 was used ? >=20 > That's correct, I reverted that change, it wasn't needed > after all. >=20 > Hans >=20 >=20 |
|
From: Jan O. <op...@ra...> - 2005-09-25 17:32:42
|
Hans Verkuil wrote: >On Sunday 25 September 2005 18:50, Jan Ophey wrote: > >>Hi again! >>Today I found some time to do some debugging and decided update fro= m a >>2.6.11 to a 2.6.12 kernel (2.6.12-gentoo-r10) an whohooo... all my >>problems are gone. >>I still build it with "genkernel --menuconfig all" (genkernel is a >>gentoo-tool for building kernels & approperiate (spelling right?!?) >>initramfs) using the default settings with only changing my cpu-typ= e + >>disabling all drivers except the drivers for hardware i use [ sound= card, >>onboard ethernet, usb, prism54 wireless, sw-raid and v4l2 without a= ny >>specific card activated]. >>rebootet and installed 0.3.8 for fun, not expecting it to work... b= ut as >>you read before: everything worked. Maybe I'm just to dumb for this= , but I >>then did a diff on my old kernel .config and I cannot see any chang= es... >>And i rebuild my old kernel twice with this settings... 2.6.11-gent= oo-r6 >>did not work... 2.6.12-gentoo-r10 works. I'm at the end of my knowl= edge... >> >>but for driver development: I guess you can forget about this. sorr= y for >>stealing your time. > > >So, if you go back to 2.6.11 the problem reappears? If so, can you s= till do >the tests I asked in an earlier mail with 2.6.11? It still could be = a driver >bug that gets activated in certain situations or memory layout. Havi= ng a >reproducable case helps a lot trying to track down the cause. > >=09=09Hans > If I boot my old kernel I can reproduce the problems. I will do the tests tomorrow during work. Jan --=20 Realit=E4t ist da, wo der Pizzamann herkommt... |
|
From: Lucas M. <lu...@ma...> - 2005-09-25 17:25:06
|
Hans Verkuil wrote: > Well, it looks like the major sound problems have been resolved. This means > that it is time to evaluate what still has to be done before 0.3.9 can be > released. Below is a list of known problems and what their status is. Please > check this and notify me if I've missed one. Hey Hans, I'm assuming xv issues are not for the .3 branch, but in case I'm mistaking: there are still some a/v issues with xv playback on the pvr350. a/v gets out of sync, but only a very little bit. it gets noticable after +- 20 minutes of watching. a quick 5 second rewind fixes the problem for the next 20 minutes. Bye, Lucas |
|
From: Bill G. <jav...@gm...> - 2005-09-25 17:24:18
|
Currenty running with the svn revision 2710. What is seen is a static
picture on /dev/video0, while on
/dev/video1 the picture is clear. Sound works on both.
Here are the details of my system based on data requests from previous post=
s:
[4358292.528000] ivtv: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D START INIT IVTV =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
[4358292.528000] ivtv: version 0.3.9 (development svn snapshot
revision 2710) loading
[4358292.528000] ivtv: Linux version: 2.6.12-9-386 386 gcc-3.4
[4358292.528000] ivtv: In case of problems please include the debug info
[4358292.528000] ivtv: between the START INIT IVTV and END INIT IVTV lines =
when
[4358292.528000] ivtv: mailing the ivtv-devel mailinglist.
[4358292.534000] ivtv: Autodetected WinTV PVR 150 card (iTVC16 based)
[4358292.534000] ACPI: PCI Interrupt 0000:06:08.0[A] -> GSI 16 (level,
low) -> IRQ 16
[4358292.633000] tveeprom: Second (radio) tuner idx 101
[4358292.633000] tveeprom: ivtv version
[4358292.633000] tveeprom: Hauppauge: model =3D 23552, rev =3D D592,
serial# =3D 2995686
[4358292.633000] tveeprom: tuner =3D Philips FQ1236A MK4 (idx =3D 92, type =
=3D 57)
[4358292.633000] tveeprom: tuner fmt =3D NTSC(M) (eeprom =3D 0x08, v4l2 =3D
0x00001000)
[4358292.633000] tveeprom: audio processor =3D CX25843 (type =3D 25)
[4358292.633000] tveeprom: decoder processor =3D CX25843 (type =3D 1e)
[4358292.633000] ivtv: i2c attach to card #0 ok [client=3Dtveeprom[50], add=
r=3D50]
[4358292.635000] ivtv: This is the first unit of a PVR500
[4358292.642000] tuner (ivtv): chip found at addr 0xc0 i2c-bus ivtv
i2c driver #0
[4358292.644000] TEA5767 detected.
[4358292.644000] ivtv: i2c attach to card #0 ok [client=3D(tuner unset), ad=
dr=3D60]
[4358292.645000] tuner: type set to 62 (Philips TEA5767HN FM Radio) by
autodetect
[4358292.645000] type set to 62 (Philips TEA5767HN FM Radio)
[4358292.646000] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv
i2c driver #0
[4358292.646000] ivtv: i2c attach to card #0 ok [client=3D(tuner unset), ad=
dr=3D61]
[4358292.709000] cx25840: loading /lib/modules/HcwMakoA.ROM
[4358294.300000] ivtv: i2c attach to card #0 ok [client=3Dcx25840, addr=3D4=
4]
[4358294.322000] ivtv: i2c attach to card #0 ok [client=3Dwm8775, addr=3D1b=
]
[4358294.333000] tda9885/6/7: (ivtv) chip found @ 0x86
[4358294.333000] ivtv: i2c attach to card #0 ok [client=3Dtda9887, addr=3D4=
3]
[4358294.337000] ivtv: Detected a TEA5767 radio tuner. Enabling radio suppo=
rt.
[4358294.947000] ivtv: loading /lib/modules/ivtv-fw-enc.bin
[4358295.160000] ivtv: Encoder revision: 0x02050032
[4358295.160000] ivtv warning: Encoder Firmware can be buggy, use
version 0x02040011!!!!
[4358295.161000] ivtv: Allocate DMA encoder MPEG stream: 128 x 32768
buffers (4096KB total)
[4358295.163000] ivtv: Allocate DMA encoder YUV stream: 194 x 10800
buffers (2048KB total)
[4358295.165000] ivtv: Allocate DMA encoder VBI stream: 120 x 17472
buffers (2048KB total)
[4358295.168000] ivtv: Allocate DMA encoder PCM audio stream: 455 x
4608 buffers (2048KB total)
[4358295.171000] ivtv: Create encoder radio stream
[4358295.172000] tuner: type set to 57 (Philips FQ1236A MK4) by ivtv
i2c driver #0
[4358295.620000] ivtv: Initialized WinTV PVR 500 (unit #1), card #0
[4358295.620000] ivtv: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D NEXT CARD =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
[4358295.620000] ivtv: Autodetected WinTV PVR 150 card (iTVC16 based)
[4358295.620000] ACPI: PCI Interrupt 0000:06:09.0[A] -> GSI 18 (level,
low) -> IRQ 18
[4358295.688000] tveeprom: Second (radio) tuner idx 101
[4358295.688000] tveeprom: ivtv version
[4358295.688000] tveeprom: Hauppauge: model =3D 23552, rev =3D D592,
serial# =3D 2995686
[4358295.688000] tveeprom: tuner =3D Philips FQ1236A MK4 (idx =3D 92, type =
=3D 57)
[4358295.688000] tveeprom: tuner fmt =3D NTSC(M) (eeprom =3D 0x08, v4l2 =3D
0x00001000)
[4358295.688000] tveeprom: audio processor =3D CX25843 (type =3D 25)
[4358295.688000] tveeprom: decoder processor =3D CX25843 (type =3D 1e)
[4358295.688000] ivtv: i2c attach to card #1 ok [client=3Dtveeprom[50], add=
r=3D50]
[4358295.709000] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv
i2c driver #1
[4358295.709000] ivtv: i2c attach to card #1 ok [client=3D(tuner unset), ad=
dr=3D61]
[4358295.777000] cx25840: loading /lib/modules/HcwMakoA.ROM
[4358297.322000] ivtv: i2c attach to card #1 ok [client=3Dcx25840, addr=3D4=
4]
[4358297.339000] ivtv: i2c attach to card #1 ok [client=3Dwm8775, addr=3D1b=
]
[4358297.345000] tda9885/6/7: (ivtv) chip found @ 0x86
[4358297.345000] ivtv: i2c attach to card #1 ok [client=3Dtda9887, addr=3D4=
3]
[4358297.354000] ivtv: This is the second unit of a PVR500
[4358297.354000] ivtv: Correcting tveeprom data: no radio present on second=
unit
[4358297.973000] ivtv: loading /lib/modules/ivtv-fw-enc.bin
[4358298.186000] ivtv: Encoder revision: 0x02050032
[4358298.186000] ivtv warning: Encoder Firmware can be buggy, use
version 0x02040011!!!!
[4358298.187000] ivtv: Allocate DMA encoder MPEG stream: 128 x 32768
buffers (4096KB total)
[4358298.224000] ivtv: Allocate DMA encoder YUV stream: 194 x 10800
buffers (2048KB total)
[4358298.226000] ivtv: Allocate DMA encoder VBI stream: 120 x 17472
buffers (2048KB total)
[4358298.245000] ivtv: Allocate DMA encoder PCM audio stream: 455 x
4608 buffers (2048KB total)
[4358298.245000] tuner: type set to 57 (Philips FQ1236A MK4) by ivtv
i2c driver #1
[4358298.642000] ivtv: Initialized WinTV PVR 500 (unit #2), card #1
[4358298.642000] ivtv: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D END INIT IVTV =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
ivtvctl --audio-status --video-status
ioctl IVTV_IOC_AUDIO_DEC_STATUS ok
ioctl IVTV_IOC_VIDEO_DEC_STATUS ok
/etc/modutils/ivtv (location on ubuntu)
alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-81-1 ivtv
Output from lspci -v:
0000:06:08.0 Multimedia video controller: Internext
Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev01)
Subsystem: Hauppauge computer works Inc.:Unknown device e807
Flags: bus master, medium devsel, latency 64,IRQ 16
Memory at e4000000 (32-bit, prefetchable)[size=3D64M]
Capabilities: [44] Power Management version 2
0000:06:09.0 Multimedia video controller: Internext
Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev01)
Subsystem: Hauppauge computer works Inc.:Unknown device e817
Flags: bus master, medium devsel, latency 64,IRQ 18
Memory at e8000000 (32-bit, prefetchable)[size=3D64M]
Capabilities: [44] Power Management version 2
i2cdetect -l
i2c-1 unknown ivtv i2c driver #1 Algorithm unavailable
i2c-0 unknown ivtv i2c driver #0 Algorithm unavailable
i2cdetect -a 0
WARNING! This program can confuse your I2C bus, cause
data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX UU UU XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: UU UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
i2cdetect -a 1
WARNING! This program can confuse your I2C bus, cause
data loss and worse!
I will probe file /dev/i2c-1.
I will probe address range 0x00-0x7f.
Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX UU XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX UU UU XX XX XX XX XX XX XX XX XX XX XX
50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
Hope someone can determine the cause, I have this
problem with ivtv builds 0.3.7k thru latest.
Thanks, Bill
|
|
From: Hans V. <hve...@xs...> - 2005-09-25 16:59:46
|
On Sunday 25 September 2005 18:50, Jan Ophey wrote: > Jan Ophey wrote: > >Hans Verkuil wrote: > >>Well, it looks like the major sound problems have been resolved. This > >> means that it is time to evaluate what still has to be done before 0.3.9 > >> can be released. Below is a list of known problems and what their status > >> is. > > Please > > >>check this and notify me if I've missed one. > >> > >>[...] > >>7) Problems with the hue, brightness and contrast controls (saa7115). > > > >Strange > > > >>values seem to be filled in, possibly also the cause of a messed up > >> video. Waiting for the answer of the questions I asked Jan Ophey. > >>[...] > > > >Hi Hans, hi all! > >Sorry for the delay, but there are several reasons why i was not able to > >debug the driver in the last few days. > > Hi again! > Today I found some time to do some debugging and decided update from a > 2.6.11 to a 2.6.12 kernel (2.6.12-gentoo-r10) an whohooo... all my > problems are gone. > I still build it with "genkernel --menuconfig all" (genkernel is a > gentoo-tool for building kernels & approperiate (spelling right?!?) > initramfs) using the default settings with only changing my cpu-type + > disabling all drivers except the drivers for hardware i use [ soundcard, > onboard ethernet, usb, prism54 wireless, sw-raid and v4l2 without any > specific card activated]. > rebootet and installed 0.3.8 for fun, not expecting it to work... but as > you read before: everything worked. Maybe I'm just to dumb for this, but I > then did a diff on my old kernel .config and I cannot see any changes... > And i rebuild my old kernel twice with this settings... 2.6.11-gentoo-r6 > did not work... 2.6.12-gentoo-r10 works. I'm at the end of my knowledge... > > but for driver development: I guess you can forget about this. sorry for > stealing your time. So, if you go back to 2.6.11 the problem reappears? If so, can you still do the tests I asked in an earlier mail with 2.6.11? It still could be a driver bug that gets activated in certain situations or memory layout. Having a reproducable case helps a lot trying to track down the cause. Hans |
|
From: Jan O. <op...@ra...> - 2005-09-25 16:50:24
|
Jan Ophey wrote: >Hans Verkuil wrote: > >>Well, it looks like the major sound problems have been resolved. Th= is means >>that it is time to evaluate what still has to be done before 0.3.9 = can be >>released. Below is a list of known problems and what their status i= s. Please >>check this and notify me if I've missed one. >> >>[...] >>7) Problems with the hue, brightness and contrast controls (saa7115= ). > >Strange > >>values seem to be filled in, possibly also the cause of a messed up= video. >>Waiting for the answer of the questions I asked Jan Ophey. >>[...] > > >Hi Hans, hi all! >Sorry for the delay, but there are several reasons why i was not abl= e to >debug the driver in the last few days. > Hi again! Today I found some time to do some debugging and decided update from = a 2.6.11 to a 2.6.12 kernel (2.6.12-gentoo-r10) an whohooo... all my problems are gone. I still build it with "genkernel --menuconfig all" (genkernel is a gentoo-tool for building kernels & approperiate (spelling right?!?) initramfs) using the default settings with only changing my cpu-type = + disabling all drivers except the drivers for hardware i use [ soundca= rd, onboard ethernet, usb, prism54 wireless, sw-raid and v4l2 without any specific card activated]. rebootet and installed 0.3.8 for fun, not expecting it to work... but= as you read before: everything worked. Maybe I'm just to dumb for this, = but I then did a diff on my old kernel .config and I cannot see any changes= ... And i rebuild my old kernel twice with this settings... 2.6.11-gentoo= -r6 did not work... 2.6.12-gentoo-r10 works. I'm at the end of my knowled= ge... but for driver development: I guess you can forget about this. sorry = for stealing your time. Jan --=20 Realit=E4t ist da, wo der Pizzamann herkommt... |
|
From: P.O. S. <tr...@ne...> - 2005-09-25 16:41:01
|
Hi. I'm trying to get the tv-out working on a PVR-350 card, but it seems like the ivtv module doesn't recognize its tv-out capabilities. The ivtv-module loads just fine: ivtv: Linux version: 2.6.12.4 SMP preempt PENTIUM4 gcc-3.3 ivtv: Initialized WinTV PVR 350, card #0 ivtv: ==================== END INIT IVTV ==================== Then, when I try to to a "modprobe ivtv-fb" I get the following error: root@mythtv /etc/X11 $ modprobe ivtv-fb FATAL: Error inserting ivtv_fb (/lib/modules/2.6.12.4/extra/ivtv-fb.ko): Operation not permitted Which generates this line in dmesg: ivtv-osd: Specified card (id 0) is either not present or does not support TV out Versions: IVTV: 0.3.8 (tried 0.3.9 with same error) Ivtvdev_drv.o: 0.10.6 -Per Olav |
|
From: Sigurd N. <sig...@on...> - 2005-09-25 16:28:30
|
Andrew wrote: > a while ago i posted here, reporting silence with ivtv-radio > > well, I just upgraded from 0.3.6z to 0.3.9 and the radio now works! > > I don't know if it would work for me with a version _between_ the above two, having lef the (human vs. bugs) battlefield a few weeks ago, and not trying anything beyond 0.3.6z until now, but thanks to all those who've been fighting! :-) > > > (I'm on a VIA motherboard with a PVR-350 > Linux ****** 2.6.12-1.1398_FC4smp #1 SMP Fri Jul 15 01:30:13 EDT 2005 i686 i686 i386 GNU/Linux ) > > Andrew > Is there any frontend to use this feature? Sigurd |
|
From: Andrew <no...@fl...> - 2005-09-25 15:36:58
|
a while ago i posted here, reporting silence with ivtv-radio well, I just upgraded from 0.3.6z to 0.3.9 and the radio now works! I don't know if it would work for me with a version _between_ the above two, having lef the (human vs. bugs) battlefield a few weeks ago, and not trying anything beyond 0.3.6z until now, but thanks to all those who've been fighting! :-) (I'm on a VIA motherboard with a PVR-350 Linux ****** 2.6.12-1.1398_FC4smp #1 SMP Fri Jul 15 01:30:13 EDT 2005 i686 i686 i386 GNU/Linux ) Andrew |
|
From: Sigurd N. <sig...@on...> - 2005-09-25 14:48:39
|
Sigurd Nes wrote: > something has happened to the video produced with svn rev later than > 2693. When jumping forward (or backward) in mythtv - the initial video - > for one second - is very distorted. > Other than that - perfect... > > Regards > > Sigurd > Sorry about that - turned out to be a bug in mythtv: http://www.gossamer-threads.com/lists/mythtv/commits/151292 Regards Sigurd |
|
From: Hans V. <hve...@xs...> - 2005-09-25 14:13:33
|
On Sunday 25 September 2005 16:04, nh...@es... wrote: > s this a known problem on the 150MCE ? > When i use the ivtv-radio utility, i am able to tune to the channels on my > cableconnection, but there is a distinct crackling sound coming from the > tuner. I have heard similar reports, but it is something that I cannot test myself since all I have is the aerial antenna, which has a lousy quality. I want to split the cable radio and extend it to my computer, but that's not yet in place. > Detection of the (LG) tuner type, has also changed from svn 2694 where type > 68 was used ? That's correct, I reverted that change, it wasn't needed after all. Hans |
|
From: <nh...@es...> - 2005-09-25 14:05:05
|
s this a known problem on the 150MCE ? When i use the ivtv-radio utility, i am able to tune to the channels on my = cableconnection, but there is a distinct crackling sound coming from the tuner. Detection of the (LG) tuner type, has also changed from svn 2694 where type= 68 was used ? Best regards Niels Hoffmann ivtv: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D START IN= IT IVTV =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ivtv: version 0.3.9 (development svn snapshot revision 2710) loading ivtv: Linux version: 2.6.11-1.1369_FC4 686 REGPARM 4KSTACKS gcc-4.0 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 0000:02:09.0[A] -> Link [LNKC] -> GSI 11 (level, low) -= > IRQ 11 tveeprom: ivtv version tveeprom: Hauppauge: model =3D 26559, rev =3D C260, serial# =3D 7863203 tveeprom: tuner =3D LG S001D MK3 (idx =3D 60, type =3D 38) tveeprom: tuner fmt =3D PAL(B/G) PAL(I) SECAM(L/L=B4) PAL(D/K) (eeprom =3D = 0x74, v4l2 =3D 0x00400e17) tveeprom: audio processor =3D CX25843 (type =3D 25) tveeprom: decoder processor =3D CX25843 (type =3D 1e) ivtv: i2c attach to card #0 ok [client=3Dtveeprom[50], addr=3D50] tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 ivtv: i2c attach to card #0 ok [client=3D(tuner unset), addr=3D61] cx25840: loading /lib/modules/HcwMakoA.ROM ivtv: i2c attach to card #0 ok [client=3Dcx25840, addr=3D44] ivtv: i2c attach to card #0 ok [client=3Dwm8775, addr=3D1b] tda9885/6/7: (ivtv) chip found @ 0x86 ivtv: i2c attach to card #0 ok [client=3Dtda9887, addr=3D43] ivtv: loading /lib/modules/ivtv-fw-enc.bin ivtv: Encoder revision: 0x02050032 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: 161 x 12960 buffers (2048KB total) ivtv: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB tot= al) ivtv: Create encoder radio stream tuner: type set to 38 (Philips PAL/SECAM multi (FM1216ME MK3)) by ivtv i2c = driver #0 ivtv: Initialized WinTV PVR 150, card #0 ivtv: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D END INI= T IVTV =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |
|
From: Hans V. <hve...@xs...> - 2005-09-25 12:07:55
|
On Sunday 25 September 2005 11:46, Robin Gilks wrote: > Sep 25 18:53:52 media ivtv: ==================== START INIT IVTV > ==================== > Sep 25 18:53:52 media ivtv: version 0.3.9 (development svn snapshot > revision ) loading > Sep 25 18:53:52 media ivtv: Linux version: 2.6.12-gentoo-r9 preempt > VIAC3-2 gcc-3.3 > Sep 25 18:53:52 media ivtv: In case of problems please include the debug > info Sep 25 18:53:52 media ivtv: between the START INIT IVTV and END INIT > IVTV lines when > Sep 25 18:53:52 media ivtv: mailing the ivtv-devel mailinglist. > Sep 25 18:53:52 media ivtv: Autodetected WinTV PVR 150 card (iTVC16 based) > Sep 25 18:53:52 media ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKB] > -> GSI 10 (level, low) -> IRQ 10 > Sep 25 18:53:52 media ivtv: Unreasonably low latency timer, setting to 64 > (was 32) > Sep 25 18:53:52 media tveeprom: The eeprom says no radio is present, but > the tuner type 60 > Sep 25 18:53:52 media tveeprom: indicates otherwise. I will assume that > radio is present. ^^^^^^^^^^^^^^^^^^^^^^^^ > Sep 25 18:53:52 media tveeprom: ivtv version > Sep 25 18:53:52 media tveeprom: Hauppauge: model = 26559, rev = C260, > serial# = 8212656 > Sep 25 18:53:52 media tveeprom: tuner = LG S001D MK3 (idx = 60, type = 38) > Sep 25 18:53:52 media tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') > PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) > Sep 25 18:53:52 media tveeprom: audio processor = CX25843 (type = 25) > Sep 25 18:53:52 media tveeprom: decoder processor = CX25843 (type = 1e) I think they didn't hook up the radio. Note that the eeprom says no radio is present but that the tuner type indicated otherwise. I don't have that message: tveeprom: ivtv version tveeprom: Hauppauge: model = 26559, rev = C260, serial# = 7626249 tveeprom: tuner = LG S001D MK3 (idx = 60, type = 38) tveeprom: tuner fmt = PAL(B/G) PAL(I) SECAM(L/L') PAL(D/K) (eeprom = 0x74, v4l2 = 0x00400e17) tveeprom: audio processor = CX25843 (type = 25) tveeprom: decoder processor = CX25843 (type = 1e) I think I should believe what the eeprom says: it looks like they simply didn't hook up the radio part. Unless you can demonstrate that radio is working under Windows, then I have to assume that your model strangely enough does not have a radio. The tveeprom is leading for Hauppauge, so I'm inclined to believe that. Hans |
|
From: Robin G. <g8...@gi...> - 2005-09-25 11:31:37
|
> You don't have another non-ivtv TV card in your PC, have you? You can > check > with ivtv-detect: both /dev/radio0 and /dev/video24 should belong to the > PVR150 you are testing. Nope - just a barefoot SP13000 Epia, 512M RAM & a diskless nfs link back to the server. Running with 2.6.12-gentoo-r9 kernel, some testing with SVN Mythtv but also using the utils from IVTV. -- Robin Gilks |
|
From: Steven E. <mai...@st...> - 2005-09-25 11:10:26
|
I've has perfect audio and no issues with capture. Just tried the radio support and now I can't get any audio on /dev/video0. The application "radio" shows signal strength, but I also get no audio for the radio stations. I've tried re-initialising all of the modules, but can't get audo back. I've also check that the correct inputs have been selected for video using ivtvctl. I even tried switching to a composite video feed and the audio jacks, but still no audo $ ivtvctl -p 2 $ mplayer /dev/video0 Turns out that exiting radio sets the audio volume down real low. $ ivtvctl -Y ioctl: VIDIOC_QUERYCTRL Brightness = 128 Contrast = 64 Saturation = 64 Hue = 0 Volume = 11776 Mute = 0 $ ivtvctl -y volume=65000 ioctl VIDIOC_S_CTRL ok $ mplayer /dev/video0 Now I get audio and video working fine. So whats the deal with this? Steve |
61 messages has been excluded from this view by a project administrator.