[linux-dvb] Problems loading drivers for Avermedia DVB-T 761 card

[Bjarne Steinsbø <bjarne@steinsbo.com>]

Hi,

I'm new to this list, and since the archive for the last couple of weeks 
of August seems to be missing, I would like to apologize if these 
problems have already been reported.

I've never had this card up and running, and I won't bore you with all 
combinations that I've tried.  Unfortunately, I can't even guarantee 
that the card is working 100% OK in Windows, since the software I've got 
on the windows side is for viewing TV only, while the only broadcasted 
signals I've got access to (and what I intend to use it for) is 
data/networking.  But the latest drivers seems to at least load OK in 
Win2K.

For Linux, my latest attempt has been made using this environment:

No Linux distribution as such, my setup is based on an older version of 
LFS.
Kernel version is 2.6.8.1,
bttv is a recent snapshot from CVS, dated app. August 30,
dvb-kernel is a recent snapshot from CVS, dated app. August 30.
Compiler is gcc-3.3
Machine is a K7, single-CPU, Asus motherboard with VIA chipsets.

Kernel has been configured with basic support for video4linux (seems to 
be the only way to get the "videodev" module), but with no support for 
DVB.  The makefile in dvb-kernel/build-2.6 has been modified to link in 
the CVS-versions of the needed include files from bttv.

I don't think it matters much at this stage, but the device nodes have 
been made using the latest MAKEDEV scripts.

Compilation seemed OK, but with warnings about missing CRCs.
Looking at the module dependencies and "modprobe -v", I'm pretty certain 
that the intended modules are the ones loaded.

Module load order is as written in the "avermedia.txt" file, i.e. 
dvb-core, bttv, bt878, dvb-bt8xx, and finally sp887x.  I used "modprobe" 
throughout, instead of a mix of "modprobe"s and "insmod"s, but I don't 
think that should matter.  Also, I copied the dvb modules to 
/lib/modules/2.6.8.1/dvb and ran "depmod -a" to get the module loader to 
recognize them.

For debug purposes, I added some options to my modprobe.conf file, 
although they didn't all seem to work.  The i2c_debug=3 option to 
i2c-algo-bit certainly did produce a lot of output...

Please see attached syslog file for details.  It got so big that I 
removed the middle part and compressed the remainder...   I think the 
interesting parts are at the begining and maybe the end, and I've left 
that in.

Although it all ends in tears with a kernel oops, I suspect that the 
real problem is much earlier.  dvb-bt8xx is "unable to determine DMA 
core of card 0", and during the loading of the firmware to the frontend, 
there is a "sendbytes: error - bailout." message from i2c.  I would 
guess that one or both of those errors are the significant ones.  BTW, 
when trying to load sp887x before dvb-bt8xx, I still get similar errors.

Does any of this make sense to anybody?  Any ideas what I might be doing 
wrong or if this is caused by bugs in the drivers?

Regards,

Bjarne

Attachment: syslog_dvb.gz
Description: Unix tar archive