|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Am 09.02.2012 22:12, schrieb Torfinn Ingolfsen:
Update: On Thu, Feb 9, 2012 at 12:04 AM, Torfinn Ingolfsen<tingox@xxxxxxxxx> wrote:Never mind. after adding this patch: http://patchwork.linuxtv.org/patch/9691/ and rebuilding the media drivers, the device is now detected: tingo@kg-f4:~$ dmesg | grep -i terratec [ 19.755806] dvb-usb: found a 'TerraTec DTV StarBox DVB-T/C USB2.0 (az6007)' in warm state. [ 20.949045] DVB: registering new adapter (TerraTec DTV StarBox DVB-T/C USB2.0 (az6007)) [ 23.732039] Registered IR keymap rc-nec-terratec-cinergy-xs [ 23.732442] dvb-usb: TerraTec DTV StarBox DVB-T/C USB2.0 (az6007) successfully initialized and connected.I have now tested the TerraTec H7, both with w_scan and with Kaffeine. Neither of then is able to find any channels from the H7. (The device is connected to an external power supply). However, if I connect another device (a PCTV nanoStick T2 290e) to the same cable, both w_scan and Kaffeine find all the channels for my provider, and I can watch the clear (unencrypted) ones in Kaffeine. How can I debug the H7 further?
Thank you for the hint to the usb-pid patch. That brought my h7 the first dvb pictures with linux.
We both seem to have the second revision device. My has the 0ccd:10a3 usb-id. w_scan and dvbscan find channels. With czap i have a signal (FE_HAS_LOCK) but no transport traffic. With mencoder i'm able to get an mpeg, which is corrupt, but there are pictures and sporadically sound, the device receives the dvb-c stream.
Typical mencoder statement is: skipping/duplicate frame.I didn't test dvb-t terrestrial, but under /dev/dvb i have only one adapter. Is there no need for two, one for cable, another for terrestrial?
ps:Sorry I never used a newsgroup about nttp, with this post i try to get access. I write from moz-thunderbird and don't know if this message will come through. Thanks. ;)
-- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html