Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Can't tune to any channels with dvb-c in Sweden. Help needed.



Hi,

I can't seem to get my DVB-c 2.1 card to work at all. I live in Stockholm, Sweden and my cable provider is ComHem. I'm running 2.4.22 at the moment and the 1.0.1 linuxtv-driver modules (dvb-ttpci, dvb-core and ves1820) seem to load ok (could someone please verify this...):

========================================================
DVB: registering new adapter (Technotrend/Hauppauge PCI rev2.1 or 2.2).
PCI: Found IRQ 11 for device 00:11.0
PCI: Sharing IRQ 11 with 00:07.2
PCI: Sharing IRQ 11 with 00:09.0
DVB: VES1820(0): setup for tuner sp5659c
DVB: VES1820(0): pwm=0x00
DVB: registering frontend 0:0 (VES1820 based DVB-C frontend)...
RequestParameter error
DVB: AV71150654(0) - firm 44000000, rtsl 04042e00, vid 07680000, app 00000000
DVB: AV71150654(0) - no firmware support for CI link layer interface
av7110: Warning, firmware version 0x0000 is too old. System might be unstable!
outcom error
outcom error
av7110(0): adac type set to 0
outcom error
outcom error
Technotrend/Hauppauge PCI rev2.1 or 2.2 adapter 0 has MAC addr = 00:d0:5c:02:cb:1c
========================================================
bartlet root # lsmod
Module Size Used by Not tainted
dvb-ttpci 310836 0 (unused)
ves1820 5056 1
dvb-core 43588 3 [dvb-ttpci ves1820]
========================================================

Is any of the "firmware version 0x0000 is too old", "outcom error" or "RequestParameter error" something to worry about?

Ok. So far so good. Now I want to try and scan for channels. I made this simple "initial-tuning-data-file" that I think should be resonable (by looking at the channels.conf of other people who also have ComHem as a provider):

========================================================
bartlet scan # cat dvb-c/se-ComHem
# ComHem
# freq sr fec mod
C 354000000 6875000 NONE QAM64
C 362000000 6875000 NONE QAM64
C 378000000 6875000 NONE QAM64
C 346000000 6875000 NONE QAM64
C 386000000 6875000 NONE QAM64
C 306000000 6875000 NONE QAM64
========================================================

And running the scan-program gives this:

========================================================
bartlet scan # ./scan -v dvb-c/se-ComHem
scanning dvb-c/se-ComHem
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 354000000 6875000 0 3
initial transponder 362000000 6875000 0 3
initial transponder 378000000 6875000 0 3
initial transponder 346000000 6875000 0 3
initial transponder 386000000 6875000 0 3
initial transponder 306000000 6875000 0 3
>>> tune to: 354000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
>>> tuning status == 0x1f
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 362000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
>>> tuning status == 0x1f
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 378000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
>>> tuning status == 0x1f
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 346000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
>>> tuning status == 0x1f
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 386000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
>>> tuning status == 0x1f
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
>>> tune to: 306000000:INVERSION_AUTO:6875000:FEC_NONE:QAM_64
>>> tuning status == 0x1f
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
dumping lists (0 services)
Done.
========================================================

While I run scan, there's also some output in the /var/log/syslog-file that looks something like this:

========================================================
Oct 4 01:34:52 bartlet outcom error
Oct 4 01:34:52 bartlet outcom error
Oct 4 01:34:52 bartlet outcom error
Oct 4 01:34:52 bartlet outcom error
Oct 4 01:34:54 bartlet StopHWFilter error
Oct 4 01:34:54 bartlet outcom error
Oct 4 01:34:54 bartlet StartHWFilter error
Oct 4 01:34:54 bartlet StartHWFilter error
Oct 4 01:34:54 bartlet StartHWFilter error
Oct 4 01:34:55 bartlet outcom error
Oct 4 01:34:55 bartlet outcom error
Oct 4 01:35:00 bartlet StopHWFilter error
Oct 4 01:35:10 bartlet StopHWFilter error
Oct 4 01:35:10 bartlet outcom error
========================================================

I have also tried dvbtune with the -m flag lots of different frequencies that should have data, but there seems to be no signal there at all. Example:

========================================================
bartlet dvbtune # ./dvbtune -f 314000000 -s 6875 -qam 64
Using DVB card "VES1820 based DVB-C frontend"
tuning DVB-C to 314000000, srate=6875000
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_CARRIER FE_HAS_VITERBI
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_TIMEDOUT FE_HAS_CARRIER FE_HAS_VITERBI
Not able to lock to the signal on the given frequency
========================================================
bartlet dvbtune # ./dvbtune -f 314000000 -s 6875 -qam 64 -m
Signal=32896, Verror=0, SNR=0dB, BlockErrors=0, ()
Signal=32896, Verror=0, SNR=0dB, BlockErrors=0, ()
Signal=32896, Verror=0, SNR=0dB, BlockErrors=0, ()
Signal=32896, Verror=0, SNR=0dB, BlockErrors=0, ()
========================================================

Any suggestions? I'm going insane over this. I think I have tried everything (both with 2.4.22-kernel/linuxtv-1.0.1 _and_ 2.6.0-test6-kernel/dvb-kernel). I have also tried to switch antenna cables (short and long ones).

Please help.




Regards,
Erik
Stockholm, Sweden


--
<http://erik.tjernlund.net/webblogg/>






--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index