Mailing List archive

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

[linux-dvb] ves1820 not tuning, but works OK in Windows :(



Hi :)

I'm having bother with a full-featured version 1.5 Siemens DVB-C card,
yet the same card in the same PC works fine in Win2000 with the 
technotrend 2.15 driver + application that I got on the dvbshop CD.

In Linux, if I tune to a freq I know to be correct, I get random output 
- in fact I get this same random output irrelevant of the frequency I 
tune to, or whether the cable is even plugged in! I have been using this 
card as a 'primary device' for VDR for some weeks without problems 
(using a budget DVB-T) but I now have access to a real DVB-C feed.

This is the kind of output I'm getting from dvbtune

$ dvbtune -s 6952 -f 411000000 -qam 64
Using DVB card "VES1820 based DVB-C frontend"
tuning DVB-C to 411000000, srate=6952000
polling....
Getting frontend event
Overflow error, trying again (status = -1, errno = 75)FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_CARRIER FE_HAS_VITERBI
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_TIMEDOUT
Not able to lock to the signal on the given frequency

$ dmesg
...
DVB: registering new adapter (Siemens cable card PCI rev1.5).
PCI: Found IRQ 11 for device 01:08.0
PCI: Sharing IRQ 11 with 00:1f.3
PCI: Sharing IRQ 11 with 00:1f.5
DVB: VES1820(0): setup for tuner spXXXX
DVB: VES1820(0): pwm=0x52
DVB: registering frontend 0:0 (VES1820 based DVB-C frontend)...
mt312_read: ret == -121
DVB: AV7111(0) - firm f0240009, rtsl b0250018, vid 71010068, app 
8000261b
DVB: AV7111(0) - firmware supports CI link layer interface
av7110(0): DVB-C w/o analog module detected
Siemens cable card PCI rev1.5 adapter 0 has MAC addr = 00:d0:5c:02:06:53

I have tried randomly twiddling with the PWM value, but this has made no 
difference. I've been using both the old 2003-11-08 snapshot so fondly 
held by VDR users, and also the DVB code in kernel 2.6.10-rc1 with 
identical results, so that's both recent and 1-year old code having the 
same result :(

0000:01:08.0 0480: 1131:7146 (rev 01)
        Subsystem: 110a:0000
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 64 (3750ns min, 9500ns max)
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at fdfffc00 (32-bit, non-prefetchable) 
[size=512]

Finally, I even get the same problem if I boot Windows, get a TV picture 
displayed, then warm reboot :/

Any ideas would be warmly received!

Cheers,
Gavin.





Home | Main Index | Thread Index