Re: Problem with Compro T200 (TDA1004x) and tuning Hi
Hi Mike, Am Dienstag, den 23.11.2010, 13:36 + schrieb Mike Martin: On 22 November 2010 19:43, hermann pitton hermann-pit...@arcor.de wrote: Am Montag, den 22.11.2010, 15:08 + schrieb Mike Martin: On 22 November 2010 06:08, hermann pitton hermann-pit...@arcor.de wrote: Hi Mike, Am Sonntag, den 21.11.2010, 17:58 + schrieb Mike Martin: I am trying to tune channels with this card (which seems to be installed OK). However the output is Using DVB card Philips TDA10046H DVB-T tuning DVB-T (in United Kingdom) to 497833000 Hz polling Getting frontend event FE_STATUS: polling polling polling usually, in the UK, this can be caused by the missing ability to detect some frequencies offsets by the tda10046. Since you have already a minus of 167000Hz, typically for the UK, in your initial scan/tuning file, this most common problem likely can be excluded. So there are eventually three variants causing the problem on a first idea. 1. They changed to 498 MHz. (or did change something else too, auto is your friend in the initial scan file then, except for the freq.) tried that no difference 2. Your overall signal is not good enough. well up until friday I was using a HVR900, until it decided to refuse to believe it was plugged into a USB2 bus, and it was working fine 3. You sit on some kernel with some bug. [...] Well, it is still very easy to install the latest remaining v4l-dvb from hg/mercurial for a quick test too. I don't have your hardware, but all my stuff is still fine there so far. AFAIR, your device, added by Hartmut, has some sort of TD1316 without an extra tda9887 IF demodulator for analog reception soldered outside of the tuner on the PCB. However, it is in a loop for eeprom auto detection on the side of the bridge. If that fails, and for my experience four of five attempts to fiddle with that later did fail, you don't have a chance for any DVB either. You might have to force the card number in such a case, but I'm still far away from what might be going on and your report is without any details so far. Cheers, Hermann One problem is the last time I used it - it worked. Although that was in a different location/PC yup, I know too it did work for years. Current system P4 Fedora 14, stock kernel output scandvb scanning uk-Aberdare_auto using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 474167000 3 9 9 6 2 4 4 initial transponder 482167000 3 9 9 6 2 4 4 initial transponder 497833000 3 9 9 6 2 4 4 initial transponder 506167000 3 9 9 6 2 4 4 initial transponder 521833000 0 2 9 3 0 0 0 initial transponder 530167000 0 2 9 3 0 0 0 tune to: 474167000:INVERSION_AUTO:BANDWIDTH_AUTO:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_AUTO WARNING: tuning failed!!! One thing I forgot about, you might have to force the bandwidth too. If that still fails, you might be on the road for bisecting through the previous patches. I can't even tell, how reliable bisecting can work currently. However, it might be worth to test with the remaining v4l-dvb mercurial code as a start. Cheers, Hermann -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with Compro T200 (TDA1004x) and tuning Hi
On 22 November 2010 06:08, hermann pitton hermann-pit...@arcor.de wrote: Hi Mike, Am Sonntag, den 21.11.2010, 17:58 + schrieb Mike Martin: I am trying to tune channels with this card (which seems to be installed OK). However the output is Using DVB card Philips TDA10046H DVB-T tuning DVB-T (in United Kingdom) to 497833000 Hz polling Getting frontend event FE_STATUS: polling polling polling usually, in the UK, this can be caused by the missing ability to detect some frequencies offsets by the tda10046. Since you have already a minus of 167000Hz, typically for the UK, in your initial scan/tuning file, this most common problem likely can be excluded. So there are eventually three variants causing the problem on a first idea. 1. They changed to 498 MHz. (or did change something else too, auto is your friend in the initial scan file then, except for the freq.) tried that no difference 2. Your overall signal is not good enough. well up until friday I was using a HVR900, until it decided to refuse to believe it was plugged into a USB2 bus, and it was working fine 3. You sit on some kernel with some bug. Case one and two are not hard to come through, for case three, the remedies are slipping away. You might have to install some latest .rc-git stuff, likely without support for your graphics card, coming up in vesa mode only, try to record something, and boot back into some kernel with support for displaying the record, we all have HDTV these days ... It might look like that, since the mobile devices and webcams took it all over here ;) Cheers, Hermann -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with Compro T200 (TDA1004x) and tuning Hi
Am Montag, den 22.11.2010, 15:08 + schrieb Mike Martin: On 22 November 2010 06:08, hermann pitton hermann-pit...@arcor.de wrote: Hi Mike, Am Sonntag, den 21.11.2010, 17:58 + schrieb Mike Martin: I am trying to tune channels with this card (which seems to be installed OK). However the output is Using DVB card Philips TDA10046H DVB-T tuning DVB-T (in United Kingdom) to 497833000 Hz polling Getting frontend event FE_STATUS: polling polling polling usually, in the UK, this can be caused by the missing ability to detect some frequencies offsets by the tda10046. Since you have already a minus of 167000Hz, typically for the UK, in your initial scan/tuning file, this most common problem likely can be excluded. So there are eventually three variants causing the problem on a first idea. 1. They changed to 498 MHz. (or did change something else too, auto is your friend in the initial scan file then, except for the freq.) tried that no difference 2. Your overall signal is not good enough. well up until friday I was using a HVR900, until it decided to refuse to believe it was plugged into a USB2 bus, and it was working fine 3. You sit on some kernel with some bug. [...] Well, it is still very easy to install the latest remaining v4l-dvb from hg/mercurial for a quick test too. I don't have your hardware, but all my stuff is still fine there so far. AFAIR, your device, added by Hartmut, has some sort of TD1316 without an extra tda9887 IF demodulator for analog reception soldered outside of the tuner on the PCB. However, it is in a loop for eeprom auto detection on the side of the bridge. If that fails, and for my experience four of five attempts to fiddle with that later did fail, you don't have a chance for any DVB either. You might have to force the card number in such a case, but I'm still far away from what might be going on and your report is without any details so far. Cheers, Hermann -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with Compro T200 (TDA1004x) and tuning Hi
Hi Mike, Am Sonntag, den 21.11.2010, 17:58 + schrieb Mike Martin: I am trying to tune channels with this card (which seems to be installed OK). However the output is Using DVB card Philips TDA10046H DVB-T tuning DVB-T (in United Kingdom) to 497833000 Hz polling Getting frontend event FE_STATUS: polling polling polling usually, in the UK, this can be caused by the missing ability to detect some frequencies offsets by the tda10046. Since you have already a minus of 167000Hz, typically for the UK, in your initial scan/tuning file, this most common problem likely can be excluded. So there are eventually three variants causing the problem on a first idea. 1. They changed to 498 MHz. (or did change something else too, auto is your friend in the initial scan file then, except for the freq.) 2. Your overall signal is not good enough. 3. You sit on some kernel with some bug. Case one and two are not hard to come through, for case three, the remedies are slipping away. You might have to install some latest .rc-git stuff, likely without support for your graphics card, coming up in vesa mode only, try to record something, and boot back into some kernel with support for displaying the record, we all have HDTV these days ... It might look like that, since the mobile devices and webcams took it all over here ;) Cheers, Hermann -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
