[linux-dvb] Re: cinergyT2: which kernel/usb module to use?

[Stefan Lucke <stefan@lucke.in-berlin.de>]

On Samstag, 27. November 2004 00:16, Stefan Lucke wrote:

That was with kernel 2.4.28.
> 
> With vdr and an USB2.0 pci-controller I had two hard crashes.
> caps lock and scroll lock led flashing.
> 
> with dvbscan I get:
> stefan@jarada:/usr/src/DVB/dvb-apps/util/scan> ./dvbscan -x 0 -t 1 -u -n dvb-t/de-Berlin
> scanning dvb-t/de-Berlin
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder 522000000 0 2 9 1 1 2 0
> initial transponder 570000000 0 2 9 1 1 2 0
> initial transponder 658000000 0 2 9 1 1 2 0
> >>> tune to: 522000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
> WARNING: >>> tuning failed!!!

So now I tried it with 2.4.27pre5 and made some progress. Now after a fresh
reboot 1st time it looks the same as above. I unplugged/plugged the cinergyT2
and 2nd try of dvbscan reports:

stefan@jarada:/usr/src/DVB/dvb-apps/util/scan> ./dvbscan dvb-t/de-Berlin
scanning dvb-t/de-Berlin
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 522000000 0 2 9 1 1 2 0
initial transponder 570000000 0 2 9 1 1 2 0
initial transponder 658000000 0 2 9 1 1 2 0
>>> tune to: 522000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
0x0000 0x000b: pmt_pid 0x044c ARD -- rbb Brandenburg (running)
0x0000 0x000c: pmt_pid 0x04b0 ARD -- rbb Berlin (running)
0x0000 0x0010: pmt_pid 0x0640 ARD -- ARD-MHP-Data (running)
0x0000 0x000e: pmt_pid 0x0578 ARD -- Das Erste (running)
0x0000 0x000d: pmt_pid 0x0514 ARD -- Phoenix (running)
Network Name 'DVB-T Berlin/Brandenburg'
...
dumping lists (25 services)
..

As from lsmod:
cinergyT2               7772   0
dvb-core               61596   0  [cinergyT2]

no other dvb modules are loaded and I think dvbscan uses the cinergyT2 and not 
my nova-T pci card.

The bad thing is, that with vdr (1.3.7) I had a system freeze again (caps
lock and scroll lock continuously on).

-- 
stefan lucke