Mailing List Archive: ivtv: devel

i2c problems with FC5 and svn ivtv 0.8.0

Index | Next | Previous | View Threaded

linuxtv at nzbaxters

May 31, 2006, 12:12 PM

Post #1 of 21 (4282 views)
Permalink

i2c problems with FC5 and svn ivtv 0.8.0

I'm not sure if anyone's following my problems with getting a new PVR-150
card and ivtv working with Fedora Core 5.

So far I've tried the following kernels: 2.6.16-1.2122_FC5 (from yum) and
also 2.6.16.16 & 2.6.16.18 from the vanilla TAR archive.
I have also tried ivtv-0.6.2 (from ivtvdriver.org) and the latest svn of
ivtv-0.8.0

I get the same results with every combination. When the ivtv/i2c etc
modules are first compiled and modprobe'd, the card works fine. If I do a
'reboot' the tveeprom either reports 'tveeprom 1-0050: Ran out of data!' or
'tveeprom 1-0050: Huh, no eeprom present (err=-121)?' and I get a bunch of
'ivtv0: i2c addr 0x44 not found for command XXX' and ivtv0: i2c hardware XXX
not found for command XXXXX'

If I unplug the PC for a few minutes and reboot, the modules load 75% of the
time - until the next reboot.

Here's the latest from dmesg:

[root [at] medi ~]# dmesg | grep tv
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.0 (development revision 3310) loading
ivtv: Linux version: 2.6.16.18 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Huh, no eeprom present (err=-121)?
tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a
Hauppauge eeprom.
ivtv0: No tuner detected, default to NTSC
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: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c addr 0x44 not found for command 0x40045613!
ivtv0: i2c addr 0x44 not found for command 0x4008646f!
ivtv0: i2c hardware 0x00000020 not found for command 0x4008646d!
ivtv0: i2c hardware 0x00000001 not found for command 0x4008646d!
ivtv0: i2c addr 0x44 not found for command 0x40045612!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c addr 0x44 not found for command 0x40045613!
ivtv0: i2c addr 0x44 not found for command 0x40045612!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

I've tried using the i2c debug tools (i2cdetect, i2cdump etc) but it really
just looks like the i2c device a)Is there when the module(s) loaded without
error or b)not there when the module(s) didn't load with no real reason as
to why i2c is sometimes there and sometimes not.

The tveeprom thing, I'm not sure about. I gather the reason it sometimes
produces an error, is because it can't find the i2c device??

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

thomaschmitz at googlemail

May 31, 2006, 12:42 PM

Post #2 of 21 (4158 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

On Wednesday 31 May 2006 21:12, Simon Baxter wrote:
> I'm not sure if anyone's following my problems with getting a new PVR-150
> card and ivtv working with Fedora Core 5.

I am sure following since I have nearly the same problem on my SuSE 10.1
system (see my posting "ivtv-0.6.x / gcc-4.1 / SUSE 10.1 problems" of
2006-05-24) for which there also have been no helpful replies.
The only thing I know is that the problem is depended on the
compiler/linker toolchain. I can only think of two reasons at
the moment:

1) a code generation bug in gcc-4.1.
2) better code optimization in gcc-4.1 breaks some assumptions of
the i2c code. The compiler has really no idea about the dependencies
needed for accessing hardware (e.g a specific store that has to
occur before a load) and may reorder C level statements at will as
long as the C semantics are preserved.

Given that everything else compiled by the gcc 4.1 looks to be fine
and how often I wrongly tried to blame a compiler for some bugs I
tend to favor 2).

Thomas

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 1:20 PM

Post #3 of 21 (4156 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

Do you think it's worth re-compiling with a <gcc-4.1??

----- Original Message -----
From: "Thomas Schmitz" <thomaschmitz [at] googlemail>
To: <ivtv-devel [at] ivtvdriver>
Sent: Wednesday, May 31, 2006 12:42 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> On Wednesday 31 May 2006 21:12, Simon Baxter wrote:
>> I'm not sure if anyone's following my problems with getting a new PVR-150
>> card and ivtv working with Fedora Core 5.
>
> I am sure following since I have nearly the same problem on my SuSE 10.1
> system (see my posting "ivtv-0.6.x / gcc-4.1 / SUSE 10.1 problems" of
> 2006-05-24) for which there also have been no helpful replies.
> The only thing I know is that the problem is depended on the
> compiler/linker toolchain. I can only think of two reasons at
> the moment:
>
> 1) a code generation bug in gcc-4.1.
> 2) better code optimization in gcc-4.1 breaks some assumptions of
> the i2c code. The compiler has really no idea about the dependencies
> needed for accessing hardware (e.g a specific store that has to
> occur before a load) and may reorder C level statements at will as
> long as the C semantics are preserved.
>
> Given that everything else compiled by the gcc 4.1 looks to be fine
> and how often I wrongly tried to blame a compiler for some bugs I
> tend to favor 2).
>
> Thomas
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 2:03 PM

Post #4 of 21 (4168 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

> Do you think it's worth re-compiling with a <gcc-4.1??

I'm going to try the'new' gcc-4.1.1

> ----- Original Message -----
> From: "Thomas Schmitz" <thomaschmitz [at] googlemail>
> To: <ivtv-devel [at] ivtvdriver>
> Sent: Wednesday, May 31, 2006 12:42 PM
> Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0
>
>
>> On Wednesday 31 May 2006 21:12, Simon Baxter wrote:
>>> I'm not sure if anyone's following my problems with getting a new
>>> PVR-150
>>> card and ivtv working with Fedora Core 5.
>>
>> I am sure following since I have nearly the same problem on my SuSE 10.1
>> system (see my posting "ivtv-0.6.x / gcc-4.1 / SUSE 10.1 problems" of
>> 2006-05-24) for which there also have been no helpful replies.
>> The only thing I know is that the problem is depended on the
>> compiler/linker toolchain. I can only think of two reasons at
>> the moment:
>>
>> 1) a code generation bug in gcc-4.1.
>> 2) better code optimization in gcc-4.1 breaks some assumptions of
>> the i2c code. The compiler has really no idea about the dependencies
>> needed for accessing hardware (e.g a specific store that has to
>> occur before a load) and may reorder C level statements at will as
>> long as the C semantics are preserved.
>>
>> Given that everything else compiled by the gcc 4.1 looks to be fine
>> and how often I wrongly tried to blame a compiler for some bugs I
>> tend to favor 2).
>>
>> Thomas
>>
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> ivtv-devel [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

thomaschmitz at googlemail

May 31, 2006, 2:07 PM

Post #5 of 21 (4162 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

On Wednesday 31 May 2006 22:20, Simon Baxter wrote:
> Do you think it's worth re-compiling with a <gcc-4.1??

Well, for me my kernel compiled on SUSE 10.0 (2.6.16.2 with a few
patches from the SUSE kernel / ivtv-0.6.x svn) with the gcc-4.0
toolchain works on SUSE 10.1 without any problems. However you will
have to make sure that every kernel module compile will use the same
compiler (e.g. don't try to compile the nvidia kernel module later
with the newer toolchain). I have not installed the old toolchain
on SUSE 10.1 but simply used the kernel/modules from my SUSE 10.0
installation. I would be really interested if this also solves
your problems.

Thomas

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 4:34 PM

Post #6 of 21 (4167 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

> I am sure following since I have nearly the same problem on my SuSE 10.1
> system (see my posting "ivtv-0.6.x / gcc-4.1 / SUSE 10.1 problems" of
> 2006-05-24) for which there also have been no helpful replies.
> The only thing I know is that the problem is depended on the
> compiler/linker toolchain. I can only think of two reasons at
> the moment:
>
> 1) a code generation bug in gcc-4.1.
> 2) better code optimization in gcc-4.1 breaks some assumptions of
> the i2c code. The compiler has really no idea about the dependencies
> needed for accessing hardware (e.g a specific store that has to
> occur before a load) and may reorder C level statements at will as
> long as the C semantics are preserved.
>
> Given that everything else compiled by the gcc 4.1 looks to be fine
> and how often I wrongly tried to blame a compiler for some bugs I
> tend to favor 2).

How did you arrive at this conclusion?

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 4:48 PM

Post #7 of 21 (4163 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

Well I updated GCC to 4.1.1 and it's the same:

1002 yum update gcc
1003 gcc -v
1006 rmmod ivtv cx25840 tuner tveeprom msp3400 wm8775 tda9887 saa7115
saa7127
1010 cd /development/svn/ivtv/
1012 make clean
1013 make
1020 make install
1021 depmod

dmesg | grep tv

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.0 (development revision 3310) loading
ivtv: Linux version: 2.6.16.18 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
tveeprom 1-0050: Huh, no eeprom present (err=-121)?
tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a
Hauppauge eeprom.
ivtv0: No tuner detected, default to NTSC
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: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c addr 0x44 not found for command 0x40045613!
ivtv0: i2c addr 0x44 not found for command 0x4008646f!
ivtv0: i2c hardware 0x00000020 not found for command 0x4008646d!
ivtv0: i2c hardware 0x00000001 not found for command 0x4008646d!
ivtv0: i2c addr 0x44 not found for command 0x40045612!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c addr 0x44 not found for command 0x40045613!
ivtv0: i2c addr 0x44 not found for command 0x40045612!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================
[root [at] medi ivtv]#

So that was a waste of time!

Any suggestions?

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 5:04 PM

Post #8 of 21 (4135 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

There's a whole bunch of kernel i2c patches relating to v4l in the latest
snapshot:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.17-rc5

I'm going to give it a go...

----- Original Message -----
From: "Thomas Schmitz" <thomaschmitz [at] googlemail>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Wednesday, May 31, 2006 2:07 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> On Wednesday 31 May 2006 22:20, Simon Baxter wrote:
>> Do you think it's worth re-compiling with a <gcc-4.1??
>
> Well, for me my kernel compiled on SUSE 10.0 (2.6.16.2 with a few
> patches from the SUSE kernel / ivtv-0.6.x svn) with the gcc-4.0
> toolchain works on SUSE 10.1 without any problems. However you will
> have to make sure that every kernel module compile will use the same
> compiler (e.g. don't try to compile the nvidia kernel module later
> with the newer toolchain). I have not installed the old toolchain
> on SUSE 10.1 but simply used the kernel/modules from my SUSE 10.0
> installation. I would be really interested if this also solves
> your problems.
>
> Thomas
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

thomaschmitz at googlemail

May 31, 2006, 5:14 PM

Post #9 of 21 (4173 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

On Thursday 01 June 2006 01:34, Simon Baxter wrote:
> > I am sure following since I have nearly the same problem on my SuSE 10.1
> > system (see my posting "ivtv-0.6.x / gcc-4.1 / SUSE 10.1 problems" of
> > 2006-05-24) for which there also have been no helpful replies.
> > The only thing I know is that the problem is depended on the
> > compiler/linker toolchain. I can only think of two reasons at
> > the moment:
> >
> > 1) a code generation bug in gcc-4.1.
> > 2) better code optimization in gcc-4.1 breaks some assumptions of
> > the i2c code. The compiler has really no idea about the dependencies
> > needed for accessing hardware (e.g a specific store that has to
> > occur before a load) and may reorder C level statements at will as
> > long as the C semantics are preserved.
> >
> > Given that everything else compiled by the gcc 4.1 looks to be fine
> > and how often I wrongly tried to blame a compiler for some bugs I
> > tend to favor 2).
>
> How did you arrive at this conclusion?
Well after a lot of tries to get ivtv to play nice on my new 10.1
installation including various permutions of 2.6.16.x kernels and ivtv
versions I finally tried to compile a known working configuration
(the one I used with SUSE 10.0) on 10.1 (by restoring the src from my
10.0 backup) and compiled it with identical configuration with
the 10.1 toolchain. The results were identical to my other tries
compiled under 10.1 (not working).

Since the kernel (and its modules) have nearly no external dependencies
except the compiler toolchain there is not much left I can think off
which could be the cause. The one thing which surprises me at the
moment is that according to your description your ivtv installation
seems to work at least sometimes. For me it is either working (gcc-4.0
compile) or not (gcc-4.1 compile).

Thomas

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 9:25 PM

Post #10 of 21 (4166 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

Nope - compiled 2.6.16-rc5 and get the same

----- Original Message -----
From: "Simon Baxter" <linuxtv [at] nzbaxters>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Wednesday, May 31, 2006 5:04 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> There's a whole bunch of kernel i2c patches relating to v4l in the latest
> snapshot:
> http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.17-rc5
>
> I'm going to give it a go...
>
>
> ----- Original Message -----
> From: "Thomas Schmitz" <thomaschmitz [at] googlemail>
> To: "Discussion list for development of the IVTV driver"
> <ivtv-devel [at] ivtvdriver>
> Sent: Wednesday, May 31, 2006 2:07 PM
> Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0
>
>
>> On Wednesday 31 May 2006 22:20, Simon Baxter wrote:
>>> Do you think it's worth re-compiling with a <gcc-4.1??
>>
>> Well, for me my kernel compiled on SUSE 10.0 (2.6.16.2 with a few
>> patches from the SUSE kernel / ivtv-0.6.x svn) with the gcc-4.0
>> toolchain works on SUSE 10.1 without any problems. However you will
>> have to make sure that every kernel module compile will use the same
>> compiler (e.g. don't try to compile the nvidia kernel module later
>> with the newer toolchain). I have not installed the old toolchain
>> on SUSE 10.1 but simply used the kernel/modules from my SUSE 10.0
>> installation. I would be really interested if this also solves
>> your problems.
>>
>> Thomas
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> ivtv-devel [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

May 31, 2006, 9:41 PM

Post #11 of 21 (4156 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

oops, mean 2.6.17-rc5
----- Original Message -----
From: "Simon Baxter" <linuxtv [at] nzbaxters>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Wednesday, May 31, 2006 9:25 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> Nope - compiled 2.6.16-rc5 and get the same
>
>
> ----- Original Message -----
> From: "Simon Baxter" <linuxtv [at] nzbaxters>
> To: "Discussion list for development of the IVTV driver"
> <ivtv-devel [at] ivtvdriver>
> Sent: Wednesday, May 31, 2006 5:04 PM
> Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0
>
>
>> There's a whole bunch of kernel i2c patches relating to v4l in the latest
>> snapshot:
>> http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.17-rc5
>>
>> I'm going to give it a go...
>>
>>
>> ----- Original Message -----
>> From: "Thomas Schmitz" <thomaschmitz [at] googlemail>
>> To: "Discussion list for development of the IVTV driver"
>> <ivtv-devel [at] ivtvdriver>
>> Sent: Wednesday, May 31, 2006 2:07 PM
>> Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0
>>
>>
>>> On Wednesday 31 May 2006 22:20, Simon Baxter wrote:
>>>> Do you think it's worth re-compiling with a <gcc-4.1??
>>>
>>> Well, for me my kernel compiled on SUSE 10.0 (2.6.16.2 with a few
>>> patches from the SUSE kernel / ivtv-0.6.x svn) with the gcc-4.0
>>> toolchain works on SUSE 10.1 without any problems. However you will
>>> have to make sure that every kernel module compile will use the same
>>> compiler (e.g. don't try to compile the nvidia kernel module later
>>> with the newer toolchain). I have not installed the old toolchain
>>> on SUSE 10.1 but simply used the kernel/modules from my SUSE 10.0
>>> installation. I would be really interested if this also solves
>>> your problems.
>>>
>>> Thomas
>>>
>>> _______________________________________________
>>> ivtv-devel mailing list
>>> ivtv-devel [at] ivtvdriver
>>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>>
>>
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> ivtv-devel [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

Jun 1, 2006, 12:28 PM

Post #12 of 21 (4142 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

I'm now running kernel 2.6.17-rc5, which included a bunch of patches
relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then recompiled
the ivtv and v4l-dvb sources from svn. I'm tempting fate saying this, but
seem to be experiencing a period of stability - except for a couple of
errors around:
tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
Hauppauge eeprom.

Biggest difference I've noticed with this combination is the order the i2c
devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they were:
Installed I2C busses:
i2c-1 unknown ivtv i2c driver #0
Algorithm unavailable
i2c-0 unknown SMBus Via Pro adapter at 5000
Algorithm unavailable

with 2.6.17-rc5 and GCC 4.1.1 they're:
Installed I2C busses:
i2c-1 unknown SMBus Via Pro adapter at 5000
Algorithm unavailable
i2c-0 unknown ivtv i2c driver #0
Algorithm unavailable

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

Jun 1, 2006, 1:27 PM

Post #13 of 21 (4143 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

Can you (and anyone else with tveeprom problems) try the following:

Tf you are running ivtv-0.6, then you need to apply the attached patch
to ivtv and recompile/install. It's not needed for ivtv-0.4.5.

Next add the newi2c=0 ivtv module option. Now load ivtv and see if this
makes any difference.

Please let me know what the result is.

Thanks,

Hans

On Thursday 01 June 2006 21:28, Simon Baxter wrote:
> I'm now running kernel 2.6.17-rc5, which included a bunch of patches
> relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then
> recompiled the ivtv and v4l-dvb sources from svn. I'm tempting fate
> saying this, but seem to be experiencing a period of stability -
> except for a couple of errors around:
> tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
> Hauppauge eeprom.
>
>
>
> Biggest difference I've noticed with this combination is the order
> the i2c devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they
> were: Installed I2C busses:
> i2c-1 unknown ivtv i2c driver #0
> Algorithm unavailable
> i2c-0 unknown SMBus Via Pro adapter at 5000
> Algorithm unavailable
>
>
>
> with 2.6.17-rc5 and GCC 4.1.1 they're:
> Installed I2C busses:
> i2c-1 unknown SMBus Via Pro adapter at 5000
> Algorithm unavailable
> i2c-0 unknown ivtv i2c driver #0
> Algorithm unavailable
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Attachments:

ivtv-newi2c.diff (5.87 KB)

linuxtv at nzbaxters

Jun 1, 2006, 1:45 PM

Post #14 of 21 (4145 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

Have done some more reboot testing, and the stability is continuing - to a
degree.

Problems that are still occuring:

1. The tveeprom on i2c 0x0050 sometimes reports errors:
tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
Hauppauge eeprom.
-although this doesn't seem to affect operation

2. The i2c tuner device fails to register, before IVTV goes looking for it:
i2c_adapter i2c-0: adapter [ivtv i2c driver #0] registered
i2c_adapter i2c-0: client [tveeprom] registered with bus id 0-0050
tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
Hauppauge eeprom.
ivtv0: No tuner detected, default to NTSC
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)

Is there a way to force IVTV to wait, or check all the i2c devices have
registered??

----- Original Message -----
From: "Simon Baxter" <linuxtv [at] nzbaxters>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Thursday, June 01, 2006 12:28 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> I'm now running kernel 2.6.17-rc5, which included a bunch of patches
> relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then recompiled
> the ivtv and v4l-dvb sources from svn. I'm tempting fate saying this, but
> seem to be experiencing a period of stability - except for a couple of
> errors around:
> tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
> Hauppauge eeprom.
>
>
>
> Biggest difference I've noticed with this combination is the order the i2c
> devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they were:
> Installed I2C busses:
> i2c-1 unknown ivtv i2c driver #0 Algorithm unavailable
> i2c-0 unknown SMBus Via Pro adapter at 5000 Algorithm
> unavailable
>
>
>
> with 2.6.17-rc5 and GCC 4.1.1 they're:
> Installed I2C busses:
> i2c-1 unknown SMBus Via Pro adapter at 5000 Algorithm
> unavailable
> i2c-0 unknown ivtv i2c driver #0 Algorithm unavailable
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

Jun 1, 2006, 1:51 PM

Post #15 of 21 (4148 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

I'm running the version currently on svn (0.8.0), but have a kernel/modules
installed with the 0.6.2. Which would you like me to test this on?

----- Original Message -----
From: "Hans Verkuil" <hverkuil [at] xs4all>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Thursday, June 01, 2006 1:27 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> Can you (and anyone else with tveeprom problems) try the following:
>
> Tf you are running ivtv-0.6, then you need to apply the attached patch
> to ivtv and recompile/install. It's not needed for ivtv-0.4.5.
>
> Next add the newi2c=0 ivtv module option. Now load ivtv and see if this
> makes any difference.
>
> Please let me know what the result is.
>
> Thanks,
>
> Hans
>
> On Thursday 01 June 2006 21:28, Simon Baxter wrote:
>> I'm now running kernel 2.6.17-rc5, which included a bunch of patches
>> relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then
>> recompiled the ivtv and v4l-dvb sources from svn. I'm tempting fate
>> saying this, but seem to be experiencing a period of stability -
>> except for a couple of errors around:
>> tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
>> Hauppauge eeprom.
>>
>>
>>
>> Biggest difference I've noticed with this combination is the order
>> the i2c devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they
>> were: Installed I2C busses:
>> i2c-1 unknown ivtv i2c driver #0
>> Algorithm unavailable
>> i2c-0 unknown SMBus Via Pro adapter at 5000
>> Algorithm unavailable
>>
>>
>>
>> with 2.6.17-rc5 and GCC 4.1.1 they're:
>> Installed I2C busses:
>> i2c-1 unknown SMBus Via Pro adapter at 5000
>> Algorithm unavailable
>> i2c-0 unknown ivtv i2c driver #0
>> Algorithm unavailable
>>
>>
>>
>> _______________________________________________
>> ivtv-devel mailing list
>> ivtv-devel [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>

--------------------------------------------------------------------------------

> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

Jun 1, 2006, 2:27 PM

Post #16 of 21 (4163 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

I've tested your patch on the 2.6.16-1.2122_FC5 as below....

-rmmod all the related modules
-patch -p0 on the 0.6.2 source (which succeeded)
-make && make install
-modprovbe ivtv

(Got the same result with a 'reboot'. I did not do a 30-second cord-out
power cycle though)

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Huh, no eeprom present (err=-121)?
tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a
Hauppauge eeprom.
ivtv0: No tuner detected, default to NTSC
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: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c addr 0x44 not found for command 0x40045613!
ivtv0: i2c addr 0x44 not found for command 0xc0045627!
ivtv0: i2c hardware 0x00000020 not found for command 0x40345622!
ivtv0: i2c addr 0x44 not found for command 0x40345622!
ivtv0: i2c addr 0x44 not found for command 0x40045612!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: i2c addr 0x44 not found for command 0x40045613!
ivtv0: i2c addr 0x44 not found for command 0x40045612!
ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c!
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

----- Original Message -----
From: "Simon Baxter" <linuxtv [at] nzbaxters>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Thursday, June 01, 2006 1:51 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> I'm running the version currently on svn (0.8.0), but have a
> kernel/modules installed with the 0.6.2. Which would you like me to test
> this on?
>
>
> ----- Original Message -----
> From: "Hans Verkuil" <hverkuil [at] xs4all>
> To: "Discussion list for development of the IVTV driver"
> <ivtv-devel [at] ivtvdriver>
> Sent: Thursday, June 01, 2006 1:27 PM
> Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0
>
>
>> Can you (and anyone else with tveeprom problems) try the following:
>>
>> Tf you are running ivtv-0.6, then you need to apply the attached patch
>> to ivtv and recompile/install. It's not needed for ivtv-0.4.5.
>>
>> Next add the newi2c=0 ivtv module option. Now load ivtv and see if this
>> makes any difference.
>>
>> Please let me know what the result is.
>>
>> Thanks,
>>
>> Hans
>>
>> On Thursday 01 June 2006 21:28, Simon Baxter wrote:
>>> I'm now running kernel 2.6.17-rc5, which included a bunch of patches
>>> relating to v4l and i2c, and have upgraded to GCC 4.1.1. Then
>>> recompiled the ivtv and v4l-dvb sources from svn. I'm tempting fate
>>> saying this, but seem to be experiencing a period of stability -
>>> except for a couple of errors around:
>>> tveeprom 0-0050: Encountered bad packet header [ff]. Corrupt or not a
>>> Hauppauge eeprom.
>>>
>>>
>>>
>>> Biggest difference I've noticed with this combination is the order
>>> the i2c devices appear on the bus. In 2.6.16.XXX and GCC 4.1.0, they
>>> were: Installed I2C busses:
>>> i2c-1 unknown ivtv i2c driver #0
>>> Algorithm unavailable
>>> i2c-0 unknown SMBus Via Pro adapter at 5000
>>> Algorithm unavailable
>>>
>>>
>>>
>>> with 2.6.17-rc5 and GCC 4.1.1 they're:
>>> Installed I2C busses:
>>> i2c-1 unknown SMBus Via Pro adapter at 5000
>>> Algorithm unavailable
>>> i2c-0 unknown ivtv i2c driver #0
>>> Algorithm unavailable
>>>
>>>
>>>
>>> _______________________________________________
>>> ivtv-devel mailing list
>>> ivtv-devel [at] ivtvdriver
>>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>>
>
>
> --------------------------------------------------------------------------------
>
>
>> _______________________________________________
>> ivtv-devel mailing list
>> ivtv-devel [at] ivtvdriver
>> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

hverkuil at xs4all

Jun 1, 2006, 2:38 PM

Post #17 of 21 (4156 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

On Thursday 01 June 2006 23:27, Simon Baxter wrote:
> I've tested your patch on the 2.6.16-1.2122_FC5 as below....
>
> -rmmod all the related modules
> -patch -p0 on the 0.6.2 source (which succeeded)
> -make && make install
> -modprovbe ivtv

I see no mention of the newi2c=0 module option. Run:

modprobe ivtv newi2c=0

Regards,

Hans

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

Jun 1, 2006, 3:01 PM

Post #18 of 21 (4143 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

> I see no mention of the newi2c=0 module option. Run:
>
> modprobe ivtv newi2c=0

sorry head like a seive.

modified modprobe.conf:
options ivtv newi2c=0 tuner=50,-1

and modprobed it as follows:
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

then a soft 'reboot'

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 18
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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)
tuner 1-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

will do some more of my reboot 'hammering' and let you know...

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

thomaschmitz at googlemail

Jun 1, 2006, 3:07 PM

Post #19 of 21 (4138 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

On Thursday 01 June 2006 22:27, Hans Verkuil wrote:
> Can you (and anyone else with tveeprom problems) try the following:
>
> Tf you are running ivtv-0.6, then you need to apply the attached patch
> to ivtv and recompile/install. It's not needed for ivtv-0.4.5.
>
> Next add the newi2c=0 ivtv module option. Now load ivtv and see if this
> makes any difference.
>
> Please let me know what the result is.

With this patch for me my tuner was detected correctly for the
first time with an gcc-4.1 compiled kernel/ivtv. And even better,
it works. I will let you know if I detect any problems later.

Thanks,
Thomas

Linux video capture interface: v1.00
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.3 (development revision 3318M) loading
ivtv: Linux version: 2.6.16.2-smp-diavoloSL101 SMP 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)
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
GSI 21 sharing vector 0xD9 and IRQ 21
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 21
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
i2c-algo-bit.o: (0) scl=1, sda=1
i2c-algo-bit.o: (1) scl=1, sda=0
i2c-algo-bit.o: (2) scl=1, sda=1
i2c-algo-bit.o: (3) scl=0, sda=1
i2c-algo-bit.o: (4) scl=1, sda=1
i2c-algo-bit.o: ivtv i2c driver #0 passed test.
tveeprom 5-0050: Hauppauge model 48134, rev J347, serial# 7112367
tveeprom 5-0050: tuner model is LG TP18PSB01D (idx 47, type 28)
tveeprom 5-0050: TV standards PAL(B/G) (eeprom 0x04)
tveeprom 5-0050: audio processor is MSP4418 (idx 25)
tveeprom 5-0050: decoder processor is SAA7115 (idx 19)
tveeprom 5-0050: has radio, has IR remote
tuner 5-0061: chip found @ 0xc2 (ivtv i2c driver #0)
saa7115 5-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
saa7127 5-0044: saa7127 found @ 0x88 (ivtv i2c driver #0)
msp3400 5-0040: MSP4418G-A2 found @ 0x80 (ivtv i2c driver #0)
msp3400 5-0040: MSP4418G-A2 supports nicam and radio, mode is autodetect and autoselect
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)
tuner 5-0061: type set to 28 (LG PAL_BG+FM (TPI8PSB01D))
ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
ivtv: ==================== END INIT IVTV ====================

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

Jun 1, 2006, 5:21 PM

Post #20 of 21 (4153 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

OK. Did a bunch of testing - and most of my problems have been resolved.

As you'll see below from the testing trail, there is still a pattern of
failure:

patched 0.6.2 sources, removed all other modules, compiled and installed
modprobe ivtv newi2c=0

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.8.0 (development revision 3310M) loading
ivtv: Linux version: 2.6.17-rc5 mod_unload 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
tveeprom 0-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 0-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is CX25841 (idx 35)
tveeprom 0-0050: decoder processor is CX25841 (idx 28)
tveeprom 0-0050: has no radio, has IR remote
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

5 x 'reboot', same as above (ALL GOOD!!)

power cycle (using nvram-wakeup after 10 mins off, cable attached) with
modprobe.conf containing 'options ivtv newi2c=0 tuner=50,-1'

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Ran out of data!
ivtv0: No tuner detected, default to NTSC
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

then...
rmmod ivtv cx25840 tuner tveeprom msp3400 wm8775 tda9887 saa7115 saa7127
modprobe ivtv

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 18
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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)
tuner 1-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

6 x 'reboots' :
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

ivtv-tune -c53 && cat /dev/video0 >> test.mpeg
then reboot

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

poweroff for 5 minutes (cable-in)
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
tveeprom 1-0050: Ran out of data!
ivtv0: No tuner detected, default to NTSC
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

rmmod ivtv cx25840 tuner tveeprom msp3400 wm8775 tda9887 saa7115 saa7127
modprobe ivtv

ivtv0: Removed Hauppauge WinTV PVR-150, card #0
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.2 (tagged release) loading
ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 20
tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX25841 (idx 35)
tveeprom 1-0050: decoder processor is CX25841 (idx 28)
tveeprom 1-0050: has no radio, has IR remote
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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)
tuner 1-0061: type set to 50 (TCL 2002N)
ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
ivtv: ==================== END INIT IVTV ====================

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

linuxtv at nzbaxters

Jun 3, 2006, 5:49 PM

Post #21 of 21 (4117 views)
Permalink

Re: i2c problems with FC5 and svn ivtv 0.8.0 [In reply to]

Hi Hans.

Sorry to contact you off-list, but as you kindly provided the patch for
'newi2c', I hoped you might be able to help again.

Your patch has solved my i2c problems, and the card is much more
functional - thanks.

What I hoped you could help with is, when the machine powers up from a cold
start I get an error on tveeprom:
> tveeprom 1-0050: Ran out of data!
> ivtv0: No tuner detected, default to NTSC
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)

if I either 'reboot' or do a 'rmmod ivtv cx25840 tuner tveeprom msp3400
wm8775 tda9887 saa7115 saa7127' and then a 'modprobe ivtv' the error
corrects itself to:
> ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
> tveeprom 0-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 0-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
> tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 0-0050: audio processor is CX25841 (idx 35)
> tveeprom 0-0050: decoder processor is CX25841 (idx 28)
> tveeprom 0-0050: has no radio, has IR remote
> tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)

Strange thing is, this problem doesn't appear to be stopping the card
working at all - I can tune, watch streams etc (although I am chasing an
LIRC problem - but I think this is specifically LIRC related (?))

Thanks again

Simon

----- Original Message -----
From: "Simon Baxter" <linuxtv [at] nzbaxters>
To: "Discussion list for development of the IVTV driver"
<ivtv-devel [at] ivtvdriver>
Sent: Thursday, June 01, 2006 5:21 PM
Subject: Re: [ivtv-devel] i2c problems with FC5 and svn ivtv 0.8.0

> OK. Did a bunch of testing - and most of my problems have been resolved.
>
> As you'll see below from the testing trail, there is still a pattern of
> failure:
>
>
>
> patched 0.6.2 sources, removed all other modules, compiled and installed
> modprobe ivtv newi2c=0
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.8.0 (development revision 3310M) loading
> ivtv: Linux version: 2.6.17-rc5 mod_unload 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> tveeprom 0-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 0-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
> tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 0-0050: audio processor is CX25841 (idx 35)
> tveeprom 0-0050: decoder processor is CX25841 (idx 28)
> tveeprom 0-0050: has no radio, has IR remote
> tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
> 5 x 'reboot', same as above (ALL GOOD!!)
>
>
> power cycle (using nvram-wakeup after 10 mins off, cable attached) with
> modprobe.conf containing 'options ivtv newi2c=0 tuner=50,-1'
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.6.2 (tagged release) loading
> ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tveeprom 1-0050: Ran out of data!
> ivtv0: No tuner detected, default to NTSC
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
> then...
> rmmod ivtv cx25840 tuner tveeprom msp3400 wm8775 tda9887 saa7115 saa7127
> modprobe ivtv
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.6.2 (tagged release) loading
> ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 18
> tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is CX25841 (idx 35)
> tveeprom 1-0050: decoder processor is CX25841 (idx 28)
> tveeprom 1-0050: has no radio, has IR remote
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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)
> tuner 1-0061: type set to 50 (TCL 2002N)
> ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
>
> 6 x 'reboots' :
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.6.2 (tagged release) loading
> ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is CX25841 (idx 35)
> tveeprom 1-0050: decoder processor is CX25841 (idx 28)
> tveeprom 1-0050: has no radio, has IR remote
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
>
>
> ivtv-tune -c53 && cat /dev/video0 >> test.mpeg
> then reboot
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.6.2 (tagged release) loading
> ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is CX25841 (idx 35)
> tveeprom 1-0050: decoder processor is CX25841 (idx 28)
> tveeprom 1-0050: has no radio, has IR remote
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
>
> poweroff for 5 minutes (cable-in)
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.6.2 (tagged release) loading
> ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> tveeprom 1-0050: Ran out of data!
> ivtv0: No tuner detected, default to NTSC
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
>
>
> rmmod ivtv cx25840 tuner tveeprom msp3400 wm8775 tda9887 saa7115 saa7127
> modprobe ivtv
>
> ivtv0: Removed Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.6.2 (tagged release) loading
> ivtv: Linux version: 2.6.16-1.2122_FC5 686 REGPARM 4KSTACKS 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-150 card (cx23416 based)
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 20
> tveeprom 1-0050: Hauppauge model 26132, rev F0B2, serial# 9400151
> tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 4)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is CX25841 (idx 35)
> tveeprom 1-0050: decoder processor is CX25841 (idx 28)
> tveeprom 1-0050: has no radio, has IR remote
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> 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)
> tuner 1-0061: type set to 50 (TCL 2002N)
> ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ==================== END INIT IVTV ====================
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel [at] ivtvdriver
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel

_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] ivtvdriver
http://ivtvdriver.org/mailman/listinfo/ivtv-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads