Mailing List Archive

On Thu, 2010-02-18 at 03:37 +0900, David Pimentel wrote:
> Hello! I just upgraded from Ubuntu 9.04 to 9.10 and the audio capture
> from my PVR is... missing.
> It isn't muted; it's not a problem with pulseaudio or alsa; i don't
> think it's vlc (the only player that seems to be compatible) and
> there's definetly an audio signal coming in.
> Oddly, I can't find the controls for volume or stereo mode anymore
> ('stereo mode extension' control does appear) with v4l2-ctl -l
> What bothers me most is that no audio stream is produced at all (ie
> it's not on low volume--there is absolutely no audio coming out of the
> card).
>
> Information:
> Driver: ivtv 66561 (aka 1.4.1?)
> Card: I/O Data G-MVP/RX

Please provide the output of

$ v4l2-ctl -d /dev/video0 --log-status

when capturing.

Also please try to capture and playback the raw PCM stream when
capturing:

$ cat /dev/video24 > foo.pcm
^C
$ aplay -f dat < foo.pcm
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo


If foo.pcm has data that looks like this:

$ xxd foo.pcm
0000000: 0000 0000 0000 0000 0000 ffff ffff ffff ................
0000010: ffff ffff 0000 0000 0000 ffff 0000 0000 ................
0000020: ffff 0000 0000 0000 ffff ffff 0000 ffff ................
0000030: ffff 0000 ffff 0000 0000 ffff 0000 ffff ................
0000040: ffff ffff 0000 0000 ffff 0000 0000 ffff ................
0000050: ffff ffff ffff 0000 ffff 0000 0000 0000 ................
0000060: ffff 0000 0000 0000 0000 0000 ffff 0000 ................
0000070: ffff 0000 0000 0000 0000 0000 0000 0000 ................
0000080: 0000 0000 ffff 0000 0000 0000 ffff 0000 ................

then you are capturing "silence" (I think), and I'll try to look into
what might be wrong.

If you have "non-silence" data in foo.pcm, then it is a sound playback
problem.

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Thank you for responding!

I couldn't get a pcm stream from video24 (nothing streaming, makes 0b
files), but video32 gave me the most interesting, rhythmic noise.
Trent Reznor would remix it into something amazing.

Obviously, it encoded something other than silence, but I don't have
any idea what it tried to encode. xxd ouput a lot of random hex.

I also tried "cat /dev/video0 > foo.mpeg" which produced a video
stream with no audio. I also put that through aplay (maybe no such a
good idea...) only to hear a magnificent hiss.

Status Log: # While inactive

[ 1574.986972] ivtv0: ================= START STATUS CARD #0
=================
[ 1574.986981] ivtv0: Version: 1.4.1 Card: I/O Data GV-MVP/RX,
GV-MVP/RX2W (dual tuner)
[ 1574.986991] ivtv0: GPIO status: DIR=0xc301 OUT=0x0200 IN=0x121e
[ 1574.986996] saa7115 2-0021: Audio frequency: 48000 Hz
[ 1574.988810] saa7115 2-0021: Input: S-Video 0
[ 1574.988814] saa7115 2-0021: Video signal: broadcast/DVD
[ 1574.988818] saa7115 2-0021: Frequency: 60 Hz
[ 1574.988822] saa7115 2-0021: Detected format: NTSC
[ 1574.988826] saa7115 2-0021: Width, Height: 720, 480
[ 1574.988833] tda9887 2-0043: Data bytes: b=0xd0 c=0x6d e=0x40
[ 1574.988839] tuner 2-0060: Tuner mode: analog TV
[ 1574.988844] tuner 2-0060: Frequency: 307.25 MHz
[ 1574.988848] tuner 2-0060: Standard: 0x00002000
[ 1574.991173] upd64031a 2-0012: Status: SA00=0x02 SA01=0x01
[ 1574.996042] upd64083 2-005c: Status: SA00=40 SA01=ff SA02=00
SA03=00 SA04=0f SA05=00 SA06=00
[ 1574.996049] vp27smpx 2-005b: Audio Mode: 1
[ 1574.996054] ivtv0: Video Input: Tuner 1
[ 1574.996057] ivtv0: Audio Input: Tuner 1
[ 1574.996061] ivtv0: Tuner: TV
[ 1574.996065] ivtv0: Stream: MPEG-2 Program Stream
[ 1574.996070] ivtv0: VBI Format: No VBI
[ 1574.996075] ivtv0: Video: 720x480, 30 fps
[ 1574.996081] ivtv0: Video: MPEG-2, 4x3, Variable Bitrate,
6000000, Peak 8000000
[ 1574.996088] ivtv0: Video: GOP Size 15, 2 B-Frames, GOP Closure
[ 1574.996094] ivtv0: Audio: 48 kHz, MPEG-1/2 Layer II, 224 kbps,
Stereo, No Emphasis, No CRC
[ 1574.996102] ivtv0: Spatial Filter: Manual, Luma 1D Horizontal,
Chroma 1D Horizontal, 0
[ 1574.996108] ivtv0: Temporal Filter: Manual, 8
[ 1574.996112] ivtv0: Median Filter: Off, Luma [0, 255], Chroma [0, 255]
[ 1574.996117] ivtv0: Status flags: 0x00200000
[ 1574.996123] ivtv0: Stream encoder MPG: status 0x0000, 0% of 4096
KiB (128 buffers) in use # While streaming, only this value changes,
to 0x0118
[ 1574.996129] ivtv0: Stream encoder YUV: status 0x0000, 0% of 2048
KiB (64 buffers) in use # I don't know if my card even supports this
or how it works
[ 1574.996136] ivtv0: Stream encoder VBI: status 0x0000, 0% of 1040
KiB (61 buffers) in use # I don't know how to use vbi :(
[ 1574.996142] ivtv0: Stream encoder PCM: status 0x0000, 0% of 324
KiB (72 buffers) in use # Nothing happening here and that bothers
me...
[ 1574.996147] ivtv0: Read MPG/VBI: 5664704/0 bytes
[ 1574.996151] ivtv0: ================== END STATUS CARD #0
==================


On Thu, Feb 18, 2010 at 9:49 AM, Andy Walls <awalls@radix.net> wrote:
> On Thu, 2010-02-18 at 03:37 +0900, David Pimentel wrote:
>> Hello! I just upgraded from Ubuntu 9.04 to 9.10 and the audio capture
>> from my PVR is... missing.
>> It isn't muted; it's not a problem with pulseaudio or alsa; i don't
>> think it's vlc (the only player that seems to be compatible) and
>> there's definetly an audio signal coming in.
>> Oddly, I can't find the controls for volume or stereo mode anymore
>> ('stereo mode extension' control does appear) with v4l2-ctl -l
>> What bothers me most is that no audio stream is produced at all (ie
>> it's not on low volume--there is absolutely no audio coming out of the
>> card).
>>
>> Information:
>> Driver: ivtv 66561 (aka 1.4.1?)
>> Card: I/O Data G-MVP/RX
>
> Please provide the output of
>
> $ v4l2-ctl -d /dev/video0 --log-status
>
> when capturing.
>
> Also please try to capture and playback the raw PCM stream when
> capturing:
>
> $ cat /dev/video24 > foo.pcm
> ^C
> $ aplay -f dat < foo.pcm
> Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 48000 Hz, Stereo
>
>
> If foo.pcm has data that looks like this:
>
> $ xxd foo.pcm
> 0000000: 0000 0000 0000 0000 0000 ffff ffff ffff  ................
> 0000010: ffff ffff 0000 0000 0000 ffff 0000 0000  ................
> 0000020: ffff 0000 0000 0000 ffff ffff 0000 ffff  ................
> 0000030: ffff 0000 ffff 0000 0000 ffff 0000 ffff  ................
> 0000040: ffff ffff 0000 0000 ffff 0000 0000 ffff  ................
> 0000050: ffff ffff ffff 0000 ffff 0000 0000 0000  ................
> 0000060: ffff 0000 0000 0000 0000 0000 ffff 0000  ................
> 0000070: ffff 0000 0000 0000 0000 0000 0000 0000  ................
> 0000080: 0000 0000 ffff 0000 0000 0000 ffff 0000  ................
>
> then you are capturing "silence" (I think), and I'll try to look into
> what might be wrong.
>
> If you have "non-silence" data in foo.pcm, then it is a sound playback
> problem.
>
> Regards,
> Andy
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Fri, 2010-02-19 at 12:24 +0900, David Pimentel wrote:
> Thank you for responding!
>
> I couldn't get a pcm stream from video24 (nothing streaming, makes 0b
> files),

So the audio clocks are not working or something along that line then
(like the analog audio to I2C audio digitizer chip is not working).


> but video32 gave me the most interesting, rhythmic noise.
> Trent Reznor would remix it into something amazing.

That's raw YUV video (only) in a Conexant specific format. It may have
sounded interesting when shoved through aplay, but you'll never hear the
TV program audio doing that. ;)


> Obviously, it encoded something other than silence, but I don't have
> any idea what it tried to encode. xxd ouput a lot of random hex.
>
> I also tried "cat /dev/video0 > foo.mpeg" which produced a video
> stream with no audio. I also put that through aplay (maybe no such a
> good idea...) only to hear a magnificent hiss.


$ mplayer foo.mpeg

would play back both audio and video in the MPEG file. aplay wouldn't
know how to parse an MPEG file.


> Status Log: # While inactive
>
> [ 1574.986972] ivtv0: ================= START STATUS CARD #0
> =================
> [ 1574.986981] ivtv0: Version: 1.4.1 Card: I/O Data GV-MVP/RX,
> GV-MVP/RX2W (dual tuner)
> [ 1574.986991] ivtv0: GPIO status: DIR=0xc301 OUT=0x0200 IN=0x121e
> [ 1574.986996] saa7115 2-0021: Audio frequency: 48000 Hz
> [ 1574.988810] saa7115 2-0021: Input: S-Video 0
> [ 1574.988814] saa7115 2-0021: Video signal: broadcast/DVD
> [ 1574.988818] saa7115 2-0021: Frequency: 60 Hz
> [ 1574.988822] saa7115 2-0021: Detected format: NTSC
> [ 1574.988826] saa7115 2-0021: Width, Height: 720, 480
> [ 1574.988833] tda9887 2-0043: Data bytes: b=0xd0 c=0x6d e=0x40
> [ 1574.988839] tuner 2-0060: Tuner mode: analog TV
> [ 1574.988844] tuner 2-0060: Frequency: 307.25 MHz
> [ 1574.988848] tuner 2-0060: Standard: 0x00002000
> [ 1574.991173] upd64031a 2-0012: Status: SA00=0x02 SA01=0x01
> [ 1574.996042] upd64083 2-005c: Status: SA00=40 SA01=ff SA02=00
> SA03=00 SA04=0f SA05=00 SA06=00
> [ 1574.996049] vp27smpx 2-005b: Audio Mode: 1


There are no status messages from the wm8739 driver. The WM8739 chip is
what converts analog audio to digital audio.

Please try these to see if the ivtv driver was able to load the wm8739
driver:

$ /sbin/lsmod | grep wm8739

... or if you even have the module built:

$ /sbin/modinfo wm8739
filename: /lib/modules/2.6.27.30-170.2.82.fc10.x86_64/kernel/drivers/media/video/wm8739.ko
license: GPL
author: T. Adachi, Hans Verkuil
description: wm8739 driver
srcversion: E4A65D54DB800B29C82E385
alias: i2c:wm8739
depends: i2c-core,v4l2-common,videodev
vermagic: 2.6.27.30-170.2.82.fc10.x86_64 SMP mod_unload
parm: debug:Debug level (0-1) (int)


Also during the load of the ivtv driver for this card, the driver should
have emitted something like this:

wm8739 2-001a: chip found @ 0x34 (ivtv i2c driver #0)


What does the output of dmesg show or what does /var/log/messages have
in it when the ivtv driver is loaded?

Unfortunately these is very little built-in debugging to se what may be
going wrong with the initialization of this chip. If it is not getting
loaded, I'll have to provide an ugly patch to you so we can get more
visibility into where the wm8739 initialization is failing. (Or you can
just add printk()'s to ivtv-driver.c:ivtv_load_and_init_modules() and
ivtv-i2c.c:ivtv_i2c_register(), if you're up to it.)

Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Sat, 2010-02-20 at 14:20 -0500, Andy Walls wrote:
> On Fri, 2010-02-19 at 12:24 +0900, David Pimentel wrote:

> > Status Log: # While inactive
> >
> > [ 1574.986972] ivtv0: ================= START STATUS CARD #0
> > =================
> > [ 1574.986981] ivtv0: Version: 1.4.1 Card: I/O Data GV-MVP/RX,
> > GV-MVP/RX2W (dual tuner)
> > [ 1574.986991] ivtv0: GPIO status: DIR=0xc301 OUT=0x0200 IN=0x121e
> > [ 1574.986996] saa7115 2-0021: Audio frequency: 48000 Hz
> > [ 1574.988810] saa7115 2-0021: Input: S-Video 0
> > [ 1574.988814] saa7115 2-0021: Video signal: broadcast/DVD
> > [ 1574.988818] saa7115 2-0021: Frequency: 60 Hz
> > [ 1574.988822] saa7115 2-0021: Detected format: NTSC
> > [ 1574.988826] saa7115 2-0021: Width, Height: 720, 480
> > [ 1574.988833] tda9887 2-0043: Data bytes: b=0xd0 c=0x6d e=0x40
> > [ 1574.988839] tuner 2-0060: Tuner mode: analog TV
> > [ 1574.988844] tuner 2-0060: Frequency: 307.25 MHz
> > [ 1574.988848] tuner 2-0060: Standard: 0x00002000
> > [ 1574.991173] upd64031a 2-0012: Status: SA00=0x02 SA01=0x01
> > [ 1574.996042] upd64083 2-005c: Status: SA00=40 SA01=ff SA02=00
> > SA03=00 SA04=0f SA05=00 SA06=00
> > [ 1574.996049] vp27smpx 2-005b: Audio Mode: 1
>
>
> There are no status messages from the wm8739 driver. The WM8739 chip is
> what converts analog audio to digital audio.


> Also during the load of the ivtv driver for this card, the driver should
> have emitted something like this:
>
> wm8739 2-001a: chip found @ 0x34 (ivtv i2c driver #0)
>

Ah. There was a change to the ivtv driver in May 2009 which put I2C IR
receiver device probing ahead of known I2C chip initialization. The
WM8739 has an I2C address that clashes with an IR receiver chip on old
boards. You likely have a version of the ivtv driver that is claiming
your WM8739 chip incorrectly as an IR chip.

A fix was checked into the ivtv driver on Nov 21, 2009.

You should get the latest version v4l-dvb drivers from

http://linuxtv.org/hg/v4l-dvb

See the terse directions here:

http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver


Regards,
Andy


_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Thank you again!

I wonder if the misconfigured driver shipped with karmic? I made the
switch from jaunty only recently, but I forgot which driver I was
using at the time (my jaunty configuration was complex, but functional)
I'll take a look at my system logs and the suggestions from your last
email as well as updating the driver.
Another question: I thought DVB and PVR didn't use the same drivers,
but there's a lot I don't know x_x. Should my card work as DVB (it
never has)?



On 2010/02/21, at 4:37, Andy Walls <awalls@radix.net> wrote:

> On Sat, 2010-02-20 at 14:20 -0500, Andy Walls wrote:
>> On Fri, 2010-02-19 at 12:24 +0900, David Pimentel wrote:
>
>>> Status Log: # While inactive
>>>
>>> [ 1574.986972] ivtv0: ================= START STATUS CARD #0
>>> =================
>>> [ 1574.986981] ivtv0: Version: 1.4.1 Card: I/O Data GV-MVP/RX,
>>> GV-MVP/RX2W (dual tuner)
>>> [ 1574.986991] ivtv0: GPIO status: DIR=0xc301 OUT=0x0200 IN=0x121e
>>> [ 1574.986996] saa7115 2-0021: Audio frequency: 48000 Hz
>>> [ 1574.988810] saa7115 2-0021: Input: S-Video 0
>>> [ 1574.988814] saa7115 2-0021: Video signal: broadcast/DVD
>>> [ 1574.988818] saa7115 2-0021: Frequency: 60 Hz
>>> [ 1574.988822] saa7115 2-0021: Detected format: NTSC
>>> [ 1574.988826] saa7115 2-0021: Width, Height: 720, 480
>>> [ 1574.988833] tda9887 2-0043: Data bytes: b=0xd0 c=0x6d e=0x40
>>> [ 1574.988839] tuner 2-0060: Tuner mode: analog TV
>>> [ 1574.988844] tuner 2-0060: Frequency: 307.25 MHz
>>> [ 1574.988848] tuner 2-0060: Standard: 0x00002000
>>> [ 1574.991173] upd64031a 2-0012: Status: SA00=0x02 SA01=0x01
>>> [ 1574.996042] upd64083 2-005c: Status: SA00=40 SA01=ff SA02=00
>>> SA03=00 SA04=0f SA05=00 SA06=00
>>> [ 1574.996049] vp27smpx 2-005b: Audio Mode: 1
>>
>>
>> There are no status messages from the wm8739 driver. The WM8739
>> chip is
>> what converts analog audio to digital audio.
>
>
>> Also during the load of the ivtv driver for this card, the driver
>> should
>> have emitted something like this:
>>
>> wm8739 2-001a: chip found @ 0x34 (ivtv i2c driver #0)
>>
>
> Ah. There was a change to the ivtv driver in May 2009 which put I2C
> IR
> receiver device probing ahead of known I2C chip initialization. The
> WM8739 has an I2C address that clashes with an IR receiver chip on old
> boards. You likely have a version of the ivtv driver that is claiming
> your WM8739 chip incorrectly as an IR chip.
>
> A fix was checked into the ivtv driver on Nov 21, 2009.
>
> You should get the latest version v4l-dvb drivers from
>
> http://linuxtv.org/hg/v4l-dvb
>
> See the terse directions here:
>
> http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver
>
>
> Regards,
> Andy
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Oh, nevermind my confusion about DVB and PVR... So they /will/ be
using the same driver package. Interesting!




On 2010/02/21, at 4:37, Andy Walls <awalls@radix.net> wrote:

> On Sat, 2010-02-20 at 14:20 -0500, Andy Walls wrote:
>> On Fri, 2010-02-19 at 12:24 +0900, David Pimentel wrote:
>
>>> Status Log: # While inactive
>>>
>>> [ 1574.986972] ivtv0: ================= START STATUS CARD #0
>>> =================
>>> [ 1574.986981] ivtv0: Version: 1.4.1 Card: I/O Data GV-MVP/RX,
>>> GV-MVP/RX2W (dual tuner)
>>> [ 1574.986991] ivtv0: GPIO status: DIR=0xc301 OUT=0x0200 IN=0x121e
>>> [ 1574.986996] saa7115 2-0021: Audio frequency: 48000 Hz
>>> [ 1574.988810] saa7115 2-0021: Input: S-Video 0
>>> [ 1574.988814] saa7115 2-0021: Video signal: broadcast/DVD
>>> [ 1574.988818] saa7115 2-0021: Frequency: 60 Hz
>>> [ 1574.988822] saa7115 2-0021: Detected format: NTSC
>>> [ 1574.988826] saa7115 2-0021: Width, Height: 720, 480
>>> [ 1574.988833] tda9887 2-0043: Data bytes: b=0xd0 c=0x6d e=0x40
>>> [ 1574.988839] tuner 2-0060: Tuner mode: analog TV
>>> [ 1574.988844] tuner 2-0060: Frequency: 307.25 MHz
>>> [ 1574.988848] tuner 2-0060: Standard: 0x00002000
>>> [ 1574.991173] upd64031a 2-0012: Status: SA00=0x02 SA01=0x01
>>> [ 1574.996042] upd64083 2-005c: Status: SA00=40 SA01=ff SA02=00
>>> SA03=00 SA04=0f SA05=00 SA06=00
>>> [ 1574.996049] vp27smpx 2-005b: Audio Mode: 1
>>
>>
>> There are no status messages from the wm8739 driver. The WM8739
>> chip is
>> what converts analog audio to digital audio.
>
>
>> Also during the load of the ivtv driver for this card, the driver
>> should
>> have emitted something like this:
>>
>> wm8739 2-001a: chip found @ 0x34 (ivtv i2c driver #0)
>>
>
> Ah. There was a change to the ivtv driver in May 2009 which put I2C
> IR
> receiver device probing ahead of known I2C chip initialization. The
> WM8739 has an I2C address that clashes with an IR receiver chip on old
> boards. You likely have a version of the ivtv driver that is claiming
> your WM8739 chip incorrectly as an IR chip.
>
> A fix was checked into the ivtv driver on Nov 21, 2009.
>
> You should get the latest version v4l-dvb drivers from
>
> http://linuxtv.org/hg/v4l-dvb
>
> See the terse directions here:
>
> http://www.ivtvdriver.org/index.php/Download#Bleeding_Edge_driver
>
>
> Regards,
> Andy
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Dear all,

I can confirm this "Card: I/O Data GV-MVP/RX" and Ubuntu 9.10
2.6.32-14-generic related problem.


>
> >> There are no status messages from the wm8739 driver. The WM8739
> >> chip is
> >> what converts analog audio to digital audio.
> >
>
With the by ubuntu provided kernel I have the following error in my log:
[ 47.586042] i2c i2c-2: Failed to register i2c client wm8739 at 0x1a (-16)
While the module wm8739 is actually loaded.


>
> > Ah. There was a change to the ivtv driver in May 2009 which put I2C
> > IR
> > receiver device probing ahead of known I2C chip initialization. The
> > WM8739 has an I2C address that clashes with an IR receiver chip on old
> > boards. You likely have a version of the ivtv driver that is claiming
> > your WM8739 chip incorrectly as an IR chip.
> >
> > A fix was checked into the ivtv driver on Nov 21, 2009.
>
> With the latest v4l-dvb looks this to be solved, I have now:
[ 4649.226812] wm8739 2-001a: chip found @ 0x34 (ivtv i2c driver #0)

(I had to disable the "firedtv" driver to compile the v4l-dvb version
"/v4l-dvb-2e0444bf93a4")

I will try to make some more recordings to verify if it is really working.
(It was quite a crisis at home with the recorder broken during the
Olympics...)

Greetings,

Han

After looking at my system log I indeed have the same message!

What do you mean by disabling the "firetv" driver? Is that done by
kernel module, a special make command when compiling, or something
else entirely?

Also, I should apologize to the administrator for sending several
mails from the wrong address. I didn't notice my phone doesn't use the
same reply address that a message was sent to (i have several
addresses forwarded to one inbox).

On Tue, Feb 23, 2010 at 2:23 PM, Han Hartgers <han.hartgers@gmail.com> wrote:
> Dear all,
>
> I can confirm this "Card: I/O Data GV-MVP/RX" and Ubuntu 9.10
> 2.6.32-14-generic related problem.
>
>>
>>
>> >> There are no status messages from the wm8739 driver.  The WM8739
>> >> chip is
>> >> what converts analog audio to digital audio.
>> >
>
> With the by ubuntu provided kernel I have the following error in my log:
> [   47.586042] i2c i2c-2: Failed to register i2c client wm8739 at 0x1a (-16)
> While the module wm8739 is actually loaded.
>
>>
>> > Ah.  There was a change to the ivtv driver in May 2009 which put I2C
>> > IR
>> > receiver device probing ahead of known I2C chip initialization.  The
>> > WM8739 has an I2C address that clashes with an IR receiver chip on old
>> > boards.  You likely have a version of the ivtv driver that is claiming
>> > your WM8739 chip incorrectly as an IR chip.
>> >
>> > A fix was checked into the ivtv driver on Nov 21, 2009.
>>
> With the latest v4l-dvb looks this to be solved, I have now:
> [ 4649.226812] wm8739 2-001a: chip found @ 0x34 (ivtv i2c driver #0)
>
> (I had to disable the "firedtv" driver to compile the v4l-dvb version
> "/v4l-dvb-2e0444bf93a4")
>
> I will try to make some more recordings to verify if it is really working.
> (It was quite a crisis at home with the recorder broken during the
> Olympics...)
>
> Greetings,
>
> Han
>
>
>
>
>
> _______________________________________________
> ivtv-users mailing list
> ivtv-users@ivtvdriver.org
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

On Sat, 2010-02-27 at 03:10 +0900, David Pimentel wrote:
> After looking at my system log I indeed have the same message!
>
> What do you mean by disabling the "firetv" driver? Is that done by
> kernel module, a special make command when compiling, or something
> else entirely?

He means, from within the v4l-dvb source tree run 'make menuconfig' and
go through the menus to disbale the firetv driver from being built.

Note, the first time you run 'make menuconfig' you may need to run it as
root, as it will build the menuconfig binary in a place where only root
has permission to write files.

Regards,
Andy



_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Dear David,

I would first just download the latest source (
http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.bz2)
unpack this with tar xvf tip.tar.bz2
go into the source and run "make" if that goes without error you can run
"sudo make install" to copy the modules, run "sudo depmod -a" and reboot
the system.

Andy is right; I got an error when I tried to do "make" and that had to do
with some development not finished on the "firetv" driver. This was a week
ago, so it is very well possible that it is repaired again. Otherwise you
have to run "make menuconfig" to disable the driver that does not work yet.

Just send the error message in case it does not works

I hope this helps.

Greetings,

Han