Hi All,

After a fair bit of googling, and delving into areas well beyond my current linux understanding, i am at a loss to get my Avermedia DVB-T 777 card working.
I understand that the card is based onthe saa7134 chipset, but it doesnt seem to be a supported card (in the cardlist).
Anyone got any tips to set me off in the right direction?

Cheers,

Nathan

Last post in here:

http://mysettopbox.tv/phpBB2/viewtopic.php?t=4233

has a patch that might work. Of course, you need to patch the kernel source, and recompile. Not easy, and I don't even know if the version of the kernel in R5A16 supports this frontend.

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

Thanks Nigel,

I found that earlier, but am still learning the patch/rebuild kernel stuff.
I hope there is an easier method, but at the moment, it seems to be the only way.
A few questions if anyone has the answers:
1) Should /sbin/lspci be listing the PCI card even without drivers loaded?
2) When i do a modprobe, dmesg states that the saa7134 drivers load (but no saa7134[0]...etc). Should i be seeing more stuff in dmesg? I assume that my problem is before this step.
3) Do i need to modprobe dvb-core and saa7134-dvb for my card to be detected?

Or will none of this work as my card is not in the driver supported cardlist?

Thanks

Ok, so i
1) Put the card into another PCI slot
2) modprobe dvb-core
3) modprobe dvb-saa7134 (or saa7134-dvb)

and things start showing up in the dmesg/lspci

dmesg:
saa7130/34: v4l2 driver version 0.2.13 loaded
saa7130/34: snapshot date 2005-07-08
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
saa7134[0]: found at 0000:00:0a.0, rev: 1, irq: 10, latency: 32, mmio: 0xe2000000
saa7134[0]: subsystem: 1461:2c05, board: UNKNOWN/GENERIC [card=0,insmod option]
saa7134[0]: board init: gpio is f600
saa7134[0]: i2c eeprom 00: 61 14 05 2c 00 00 00 00 00 00 00 00 00 00 00 00
saa7134[0]: i2c eeprom 10: 00 ff 82 0e ff 20 ff ff ff ff ff ff ff ff ff ff
saa7134[0]: i2c eeprom 20: 01 40 01 02 02 03 03 01 08 ff 00 a8 ff ff ff ff
saa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
saa7134[0]: registered device video0 [v4l2]
saa7134[0]: registered device vbi0

lspci:
00:0a.0 Multimedia controller: Philips Semiconductors SAA7134 (rev 01)

I try starting up tvtime, but no show. The tuner doesnt appear to be registering (black screen in tvtime). I will go through
1) rmmod saa7134
2) modprobe saa7134 card=0 tuner=(1-60)
3) tvtime

and see if any tuners are going to go... not sure what to expect here, but I'll give it a shot. Otherwise its time to learn how to patch and compile kernels...

OK. So that means the driver has recognised the chipset on the card, but not the particular ROMS, IO addresses, et c. Applying the aforementioned patch would probably get you past this, but it can be tricky.



I think tvtime is for analogue TV only. It won't do anything with a digital TV card. You would need to use the DVB utilities' scan program to see if the card is correctly configured, et c

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

Hi Nigel,

Thanks for the response. I'm currently in kernel rebuild mode. I've not done it before, so its taking some "learning time". I think im getting there though. I've
1) dowloaded the src for 2.6.13
2) applying patches for 2.6.13 (from http://www.linuxhq.com/)
3) applying the diff in the above article (http://mysettopbox.tv/phpBB2/viewtopic.php?t=4233 )

I built the kernel with no .config (not sure where it came from), but i found a link for rebuilding kernels in FC4 (http://www.mjmwired.net/resources/mjm-kernel-fc4.html), so am statring again using that howto as the guide, and putting my specific patches in along the way.

I think i'm on the way, if it works i'll post back... if not, i spose i'll post back too

Thanks

Nathan

I dont think you want to apply the patch from from http://www.linuxhq.com/. That is probably the patch to convert 2.6.12 to 2.6.13 (so you dont have to download all of the kernel source).

Start with steps 1 and 3 and then get cesman's config file (copy it to .config in your kernel source dir) from the /boot directory.

Then do "make menuconfig" to enable the DVB for saa7134 support (in Device Drivers->Media->Video for Linux I think from memory).

Starting with no .config is asking for a world of problems.

before i ran the patch i had a squizz at the saa7134-cards.c file, and it didnt have the parts in it referenced by the diff in the other article (for example there was no:

},{
.vendor = PCI_VENDOR_ID_PHILIPS,
+ .device = PCI_DEVICE_ID_PHILIPS_SAA7133,
+ .subvendor = 0x1461, /* Avermedia Technologies Inc */
+ .subdevice = 0x2c05, /* Avermedia DVB-T 777 */
+ .driver_data = SAA7134_BOARD_PHILIPS_TOUGH,
+
+ },{
+ .vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7130,
.subvendor = PCI_VENDOR_ID_PHILIPS,
.subdevice = 0x2004

Looking into the 2.6.13 patch, it had this reference, and all the definitions for PHILIPS_TOUGH. When i did the 2.6.13 patch, the saa7134-cards.c file had the above bolded stuff in it. Then I applied the diff in the other article, and the saa7134-cards.c looked like it should (avermedia 777 stuff).

Does this make sense, or am i completely off track?

Are you saying that the saa7134-cards.c in the vanilla 2.6.13 sources doesn't have a section that looks like this:


The patch is just saying make a section that looks like this above the section containing ".subdevice = 0x2004":

yup, thats what i found... but i just downloaded the src at work, and had a look, and the section below does exist... so i musta coqed something up last night...

},{
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7130,
.subvendor = PCI_VENDOR_ID_PHILIPS,
.subdevice = 0x2004,
.driver_data = SAA7134_BOARD_PHILIPS_TOUGH,
},{

So, theres no need to patch as you said 2 hours ago... thanks for the tips!

So whens the next version of knoppmyth due out

I think I can safely say on cesman's behalf: When its done. (and he doesnt appreciate being asked).

Good thing I didn't ask him then

Any luck with the 777?

Hope you guys have more luck with the 777 than i have had.

Have tryed a few variations on the patch with little success, the saa7134-dvb driver stil dosnt recognise the front end.

Any idea what chipset is in the front end? have popped the top but all you see is the back of the circuit board