[Mplayer-dvb] Oh dear, v2.6.6 knocked out my avermedia DVB-T card

[Nico Sabbi]

David Maslen wrote:

>Nico Sabbi <nsabbi at tiscali.it> writes:
>  
>
>>can you please post:
>>1) a part of ~/.mplayer/channels.conf
>>2) the output of:
>>
>>mplayer -v dvb://ABC
>>when mplayer fails ?
>>Thanks,
>>    
>>
>
>Afraid I can't easily at present. Upgraded the kernel to 2.6.6 and now
>my DVB card won't work at all. It was working, but would time out with 2.6.5
>
>I think it's to do with the changes to the BTTV driver, but I can't
>really tell. 
>
>How would I go about collecting more information, so as to be able to
>submit a proper bug report?
>
>Now my logs look like this :(
>
>May 17 20:30:02 trinity vmunix: i2c_adapter i2c-0: master_xfer: with 1 msgs.
>May 17 20:30:02 trinity vmunix: i2c_adapter i2c-0: sendbytes: error - bailout.
>May 17 20:30:02 trinity vmunix: i2c_adapter i2c-0: master_xfer: with 1 msgs.
>May 17 20:30:02 trinity last message repeated 2 times
>May 17 20:30:02 trinity vmunix: sp887x_initial_setup: firmware upload... <7>i2c_adapter i2c-0: master_xfer: with 1 msgs.
>May 17 20:30:02 trinity vmunix: i2c_adapter i2c-0: master_xfer: with 1 msgs.
>May 17 20:30:11 trinity last message repeated 570 times
>May 17 20:30:11 trinity vmunix: done.
>
>It looks as though this might be the change (from the 2.6.6 changelog);
>
><akpm at osdl.org>
>        
>[PATCH] v4l: bttv driver update
>From: Gerd Knorr <kraxel at bytesex.org>
>        
>This patch updates the bttv driver.  Changes:
>        
>          (1) several card-specific tweaks.
>            (2) make software vs. hardware i2c configurable per TV
>          card.
>            (3) reinitialize image parameters after chip reset.
>              (4) make bttv quite by default on frame drops.
>                (5) new insmod option: "debug_latency=1" to enable
>          frame drop
>                debug messages.
>                
>                bttv is quite sensitive to irq latencies, especially
>                when capturing both
>                video and vbi.  There are several reports about
>                problems due to this, I don't
>                see that on my machines through.  (5) dumps a
>                stracktrace if the driver
>                thinks the frame drop is is caused by high latencies
>                as experiment, lets see
>                whenever that helps ... 
>
>  
>

uhm, the logs seem to indicate a problem with the i2c (bus that in your 
case is used to send
tuning parameters to the tuner/demodulator).
Are you sure you added i2c_hw=1 to the options for bttv?
You should report and ask help to linux-dvb at linuxtv.org for drivers 
related problems.

Good luck.
        Nico