I am really stuck now.
=> Twinhan in WindozeXP: seems to lock OK to correct freqs/ts (6900,
QAM64), but no PIDs are being extracted on any freq ... (twinhan software)
=> Twinhan in Linux: seems to lock OK to correct freqs/ts (6900, QAM64),
but no PIDs can be extracted on any freq ... (dvbscan)
=> However: decoder box from cable provider: working OK ! (apparently no
signal problem).
So I am starting to be believe that my card is broken somehow.
The problem is that I do not have enough experience to be sure that I am
not overlooking something. Can someone with more experience please
advise how to proceed?
I see no better option than buying another card to see if that makes a
difference. But could there be anything else that could explain why I
have these problems?
Z.
Zoilo Gomez wrote:
In the mean time, I have done some more testing with following results:
1) I have managed to install on WindozeXP with software supplied on
CDROM by Twinhan. When I choose the proper freqs and qam, the card
does acquire a lock, then spends a lot of time 'Analysing" the locked
frequency, but without any (PID) results. In contrast, it hops over
non-existing frequencies quickly, so tuning seems to be working properly.
2) On Linux I get a similar behaviour, which leads me to believe that
my software is correct. However I see no PIDs ......
Is there any clue in this dmesg log that I am overlooking? As I do not
have a copy of a dmesg log for a working system, I cannot compare to
see what is wrong:
Jul 20 11:21:50 dvbc dst(0) dst_set_freq: set Frequency 314750000
Jul 20 11:21:50 dvbc dst(0) dst_set_frontend: Set Frequency=[314750000]
Jul 20 11:21:50 dvbc dst(0) dst_set_symbolrate: set symrate 6900000
Jul 20 11:21:50 dvbc dst(0) dst_set_symbolrate: DCT-CI
Jul 20 11:21:50 dvbc dst(0) dst_write_tuna: type_flags 0x1219
Jul 20 11:21:50 dvbc dst(0) dst_comm_init: Initializing DST.
Jul 20 11:21:50 dvbc dst(0) dst_gpio_outb: mask=[ffffffff],
enbb=[0001], outhigh=[0000]
Jul 20 11:21:50 dvbc dst(0) rdc_reset_state: Resetting state machine
Jul 20 11:21:50 dvbc dst(0) dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0000]
Jul 20 11:21:51 dvbc dst(0) dst_gpio_outb: mask=[0002], enbb=[0002],
outhigh=[0002]
Jul 20 11:21:51 dvbc writing [ 09 00 04 cd 7e 00 1a f4 40 5a ]
Jul 20 11:21:51 dvbc dst(0) dst_gpio_outb: mask=[ffffffff],
enbb=[0000], outhigh=[0000]
Jul 20 11:21:51 dvbc dst(0) read_dst: reply is 0xff
Jul 20 11:21:51 dvbc dst(0) dst_wait_dst_ready: dst wait ready after 2
Jul 20 11:21:51 dvbc dst(0) read_dst: reply is 0x9
Jul 20 11:21:51 dvbc 0x0 0x4 0xcd 0x7e 0x0 0x1a 0xf4 0x40 0x5a
Jul 20 11:21:51 dvbc dst(0) dst_get_tuna: checksum failure?
Thank you and best regards,
Z.
Zoilo Gomez wrote:
I cannot seem to get the tuner to work on my Twinhan DVB-C Cab-CI.
However, I do notice that scanning goes much faster for frequencies +
QAM-rates that I do know to be correct, and slower if a purposely
mistune the frequency, or enter the wrong QAM-value (eg. 256 istead
of 64). So something seems to work, but tuning status always returns
0x00 ...
Output of "dvbscan -vvv <table>"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 314750000 6900000 0 3
tune to: 314750000:INVERSION_AUTO:6900000:FEC_NONE:QAM_64
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
WARNING: >>> tuning failed!!!
tune to: 314750000:INVERSION_AUTO:6900000:FEC_NONE:QAM_64 (tuning
failed)
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
tuning status == 0x00
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
I found the discussion in September 2005 about the tuning problems,
but AFAICS the patches are in my drivers (should be, because I
downloaded and installed using mercury last week).
How can obtain more information what is the problem?
Thank you and best regards,
Z.
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
