Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: [PATCHES] Frontend kernel i2c conversion.



Andreas Büsching wrote:
Andreas Büsching wrote:

Hi,

I just got my new DVB-T card (AverMedia 771) yesterday and ran into the same problem as Andreas. When I tried to load the mt352 module it crashed on mt352.c:827 (I guess; the line looks like BUG_ON(!state->dvb)). So I applied your patch, which definitly changed something in the behaviour. I can load the module and get the debug message 'dvbfe_mt352: Setup for Avermedia 771.'. But that seems to be everything. As I'm new to this stuff I'm not sure how to check that the card is working correctly now, but I tried the following:

- downloaded the dvb-apps from CVS
- ran dvb-apps/util/scan/dvbscan ./dvb-t/de-Bremen

what results in:

scanning dvb-t/de-Bremen
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
main:1957: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 2 No such file or directory

According to this message the mt352 is not running correctly

Also I'm not sure if I did everything else correct with the bt* driver stuff. Currently I load the following modules:

# DVB-T AverMedia 771
dvb-core
bttv i2c_hw=1 card=0x68
bt878
dvb-bt8xx
i2c-nforce2
i2c-algo-pcf

I added the i2c modules because there are some syslog messages looking like errors. These messages appear while loading the mt352 module:

i2c_adapter i2c-0: sendbytes: error - bailout.
i2c_adapter i2c-1: sendbytes: error - bailout.
i2c_adapter i2c-2: sendbytes: error - bailout.

I hope this helps to find the bug! If you need any more information just ask.

Okay here some more debug output from loding the kernel moduls like that (I applied a patch to the bttv to automatically detect my AverMedia 771):

dvb-core
bttv i2c_hw=1
bt878
dvb-bt8xx

Linux video capture interface: v1.00
bttv: driver version 0.9.14 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 0000:01:07.0, irq: 12, latency: 32, mmio: 0xe9000000
bttv0: detected: AVermedia DVB-T 771 [card=121], PCI subsystem ID is 1461:0771
bttv0: using: AVerMedia AVerTV DVB-T 771 [card=121,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00f8ff0f [init]
bttv0: using tuner=-1
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 . ok
bttv0: add subdevice "remote0"
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
bt878(0): Bt878 (rev 17) at 01:07.1, irq: 12, latency: 32, memory: 0xe9001000
attach: checking "DDC:fb0 #0"
attach: checking "DDC:fb0 #1"
attach: checking "MAVEN:fb0"
attach: checking "SMBus nForce2 adapter at 5000"
attach: checking "SMBus nForce2 adapter at 5500"
attach: checking "bt878 #0 [hw]"
find by pci: checking "bt878 #0 [hw]"
attach: "bt878 #0 [hw]", to card 0
DVB: registering new adapter (Ave).
dvbfe_mt352: Trying to attach to adapter 0x10009:DDC:fb0 #0.
i2c_adapter i2c-0: sendbytes: error - bailout.
dvbfe_mt352: Avermedia 771 not detected, maybe you should try the 'force_card' module parameter?.
dvbfe_mt352: Trying to attach to adapter 0x10009:DDC:fb0 #1.
i2c_adapter i2c-1: sendbytes: error - bailout.
dvbfe_mt352: Avermedia 771 not detected, maybe you should try the 'force_card' module parameter?.
dvbfe_mt352: Trying to attach to adapter 0x10009:MAVEN:fb0.
i2c_adapter i2c-2: sendbytes: error - bailout.
dvbfe_mt352: Avermedia 771 not detected, maybe you should try the 'force_card' module parameter?.
dvbfe_mt352: Trying to attach to adapter 0x0:SMBus nForce2 adapter at 5000.
dvbfe_mt352: Avermedia 771 not detected, maybe you should try the 'force_card' module parameter?.
dvbfe_mt352: Trying to attach to adapter 0x0:SMBus nForce2 adapter at 5500.
dvbfe_mt352: Avermedia 771 not detected, maybe you should try the 'force_card' module parameter?.
dvbfe_mt352: Trying to attach to adapter 0x10005:bt878 #0 [hw].
dvbfe_mt352: Setup for Avermedia 771.
... some new information has just arrived ...

I started debugging the mt352 module (what is quite difficult as I do not know that much about dvb und i2c kernel stuff). What I found out is that the mt352_command function is never called, what results in a messing call to dvb_register_frontend[_new], which seems to be very important.

Maybe this will help to find the problem. I will do everything I can to help you find the bug/problem.

crunchy




Home | Main Index | Thread Index