Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Terratec 1200 DVB-T: frontend driver not found
Hi everybody,
I've a problem installing the Terratec 1200 DVB-T. I found a lot of
posts about it in the archives, but nothing about my problem (at least
nothing with an answer attached... ;-) ).
I just installed kernel 2.6.10. I tried both the drivers shipped with
the kernel and a fresh cvs checkout (this afternoon), but I always get
from dmesg
Linux video capture interface: v1.00
saa7146: register extension 'dvb'.
saa7146: register extension 'budget dvb'.
saa7146: register extension 'budget_ci dvb'.
saa7146: register extension 'budget dvb /w video in'.
PCI: Found IRQ 10 for device 0000:00:0f.0
saa7146: found saa7146 @ mem c70d4000 (revision 1, irq 10) (0x153b,0x1157).
DVB: registering new adapter (Terratec Cinergy 1200 DVB-T).
i2c_adapter i2c-0: registered as adapter #0
i2c_adapter i2c-0: master_xfer: with 2 msgs.
adapter failed MAC signature check
encoded MAC from EEPROM was
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
i2c_adapter i2c-0: master_xfer: with 1 msgs.
i2c_adapter i2c-0: master_xfer: with 2 msgs.
KNC1-0: MAC addr = 00:0a:ac:01:a0:97
i2c_adapter i2c-0: master_xfer: with 2 msgs.
i2c_adapter i2c-0: master_xfer: with 2 msgs.
budget_av: A frontend driver was not found for device 1131/7146
subsystem 153b/1157
ciintf_init: CI interface initialised
usbcore: registered new driver Technotrend/Hauppauge USB-Nova
usbcore: registered new driver ttusb-dec
usbcore: registered new driver Driver for DiBcom based USB Budget DVB-T
device
usbcore: registered new driver cinergyT2
At first I thought it a was a hotplug problem and updated all the
hotplug stuff (still had the original Slack 9 files, tried the Slack 10
hotplug package), but it doesn't seem the right solution. First of all
the problem remains and then I noticed a detail from the posts in the
archives: the firmware uploading process starts after the frontend
driver has been "attached" (is that right?)
So I tried to trace the problem and I found that this control in file
tda1004x.c fails (because tda1004x_read_byte returns -1)
/* check if the demod is there */
if (tda1004x_read_byte(state, TDA1004X_CHIPID) != 0x46) goto error;
Here I'm completely stuck... Is there someone who can give me an hint to
continue my quest??
Thanx
Filippo
Home |
Main Index |
Thread Index