Hello, I have also been experimenting with a TechnoTrend DVB-C PCI card on Windows and Linux.
My experience is that even on Windows, using the TechnoTrend software, the card refuses to tune into any multiplex that uses a symbol rate of 6900 ksym/s! I really don't know why. Tuning to a 5900 ksym/s multiplex usually works and I get the tables and video OK under Windows. It also worked when the cable network was using 6000 ksym/s for these multiplexes. (This is the HTV network, I think you're here too, judging by your frequency list.) HOWEVER, I've never got the TechnoTrend card to tune to anything under Linux. I've tried the diffent zapping apps and also wrote a little program to do the tuning, but nothing has worked yet. I always get a FailureEvent which seems to indicate a frontend status of FE_SPECTRUM_INV | FE_HAS_LOCK | FE_HAS_VITERBI | FE_HAS_SYNC. Don't really know what that combination means, maybe I got some parameters wrong? I think I've tried just about every combination, though. Btw, HTV is using spectral inversion, so you'd better keep an eye out for that if you're here. The network is also developing all the time, so it's best not to rely on static frequency information for too long. The best way to keep up-to-date is to read the NIT data from the 162MHz multiplex (the "home" multiplex) and deduce other frequencies from there. PC-based software always seems a bit crappy on supporting this and requires manual information to be entered. ... PS. If anybody has a recommendation of another PCI or USB DVB-C adapter to use with Linux, I'd be glad to hear about it. The shops seem to be selling mostly DVB-T and DVB-S cards. Does Galaxis have a DVB-C card with good support under Linux? -- Kenneth Falck SWelcom Oy R&D Manager Ludviginkatu 6-8 +358 40 5103121 00130 Helsinki, Finland > -----Original Message----- > From: Lauri Pesonen [mailto:[EMAIL PROTECTED]] > Sent: 4. tammikuuta 2002 22:42 > To: [EMAIL PROTECTED] > Subject: [linux-dvb] Re: Tuning problem > > > On Fri, Jan 04, 2002 at 05:32:20PM +0100, Ralph Metzler wrote: > > Hi, > > > > I laso compiled VDR successfully. It starts and says > that it finds > > two DVB > > > cards. I tried usinf the provided channels.conf.cable > file, but the tuning > > > obviously fails since the frquencies are wrong. The > system log shows that > > > VDR tries to tune the card to the channel, so I'm > assuming that everything > > > is OK with the cards regardless of the error message > about the firmware. > > > > Tuning is independent of the firmware for DVB-C (in DVB-S > the firmware > > handles DiSEqC). Still it would be helpful to know what it said. > > Here's the whole system log when loading the modules: > > Jan 4 22:19:58 localhost kernel: i2c-core.o: i2c core module > Jan 4 22:19:58 localhost kernel: Linux video capture > interface: v1.00 Jan 4 22:19:58 localhost kernel: > i2c-core.o: driver VES1893 DVB > demodulator registered. > Jan 4 22:19:58 localhost kernel: i2c-core.o: driver VES1820 DVB > demodulator registered. > Jan 4 22:19:58 localhost kernel: i2c-core.o: driver L64781 DVB > demodulator registered. > Jan 4 22:19:58 localhost kernel: L64781: init done > Jan 4 22:19:58 localhost kernel: i2c-core.o: driver tda8083 DVB > demodulator registered. > Jan 4 22:19:58 localhost kernel: i2c-core.o: driver stv0299 DVB > demodulator registered. > Jan 4 22:19:58 localhost kernel: i2c-core.o: driver i2c TV > tuner driver > registered. > Jan 4 22:19:59 localhost kernel: saa7146_core.o: saa7146(1): bus:0, > rev:1, mem:0xd08db000. > Jan 4 22:19:59 localhost kernel: L64781: no L64781 found ... > Jan 4 22:19:59 localhost kernel: i2c-core.o: adapter saa7146(1) > registered as adapter 0. > Jan 4 22:19:59 localhost kernel: saa7146_core.o: saa7146(2): bus:0, > rev:1, mem:0xd0d5e000. > Jan 4 22:19:59 localhost kernel: L64781: no L64781 found ... > Jan 4 22:19:59 localhost kernel: i2c-core.o: adapter saa7146(2) > registered as adapter 1. > Jan 4 22:20:07 localhost kernel: wait-for-debi-done maxwait: > 500000 Jan 4 22:20:07 localhost kernel: dvb: debi test in > bootarm() failed: > 00000000 != 10325476 > Jan 4 22:20:07 localhost kernel: dvb1: AV711536924483 - firm > 1d18c010, > rtsl 20000003, vid 20000003, app 00000000 > Jan 4 22:20:07 localhost kernel: dvb: 2 dvb(s) found! > > I'm under the impression that I should see an image on the > composite out > when I load the driver. This is not the case... > > > > I'll get in touch with the cable company next ;) > > > > They should at least be able to tell you what modulation > they use, if > > they use spectrum inversion, etc. Since the TT software also fails > > maybe they are using some kind of exotic setup. > > I got the following frequency list from them, so now I know > what to look > for at least... : > > Freq. QAM Srate > 283 128 5,9 > 290 128 5,9 > 297 128 5,9 > > 146 128 6,9 > 154 128 6,9 > 162 64 6,9 > 170 128 6,9 > > > Additionally I was instructed by one of the list subscribers > to get this > stuff working on Windows first. He suggested that I should strip > everything out of my PC and try to get the cards working. I > think I'll do > that before venturing into the Linux world again... > > Thanks for all the help guys! I can't wait to get everything > working ;) > > > Ralph > > -- Lauri > > > -- > Info: > To unsubscribe send a mail to [EMAIL PROTECTED] with > "unsubscribe linux-dvb" as subject. > -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.