Hi, I have a TwinHan Vision Plus DVB-T card... and I'm really getting to the end of my tether with it! Ok, deep breaths, explain the problem. For the past few weeks (it seems longer), I have been trying to get this card to work correctly (Slackware 10.1 on an Athlon 3200+). To make matters worse, I have actually had it working (with what I think was a 2.6.11.6 kernel). However, I had to recompile the kernel to add in some other hardware, which I obviously did on returning from the pub one Saturday evening, and I forgot to backup the config. It has never worked since. Yeah, I might have "modified" some other bits at this point too (can't quite remember) :( I have tried all sorts of 2.6 kernel (up to the latest 2.6.11.11), but I now think that it must be something other than the kernel, possibly the dbv-apps? However, I have tried everything with these too. The linuxtv-dvb-apps-1.1.0 and the latest CVS snapshots compile fine, but I always get the same error when I try to use one of the apps (explained below). Basically, the DVB modules seem to be loaded correctly: modprobe bttv i2c_hw=1 card=0x71 modprobe dst modprobe dvb-bt8xx Which gives the following output in dmesg: bttv: driver version 0.9.15 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). PCI: Found IRQ 11 for device 0000:00:0a.0 PCI: Sharing IRQ 11 with 0000:00:0a.1 PCI: Sharing IRQ 11 with 0000:01:00.0 bttv0: Bt878 (rev 17) at 0000:00:0a.0, irq: 11, latency: 32, mmio: 0xd7800000 bttv0: detected: Twinhan VisionPlus DVB-T [card=113], PCI subsystem ID is 1822:0001 bttv0: using: Twinhan DST + clones [card=113,insmod option] bttv0: gpio: en=00000000, out=00000000 in=00f500ff [init] bttv0: using tuner=4 bttv0: add subdevice "dvb0" bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). PCI: Found IRQ 11 for device 0000:00:0a.1 PCI: Sharing IRQ 11 with 0000:00:0a.0 PCI: Sharing IRQ 11 with 0000:01:00.0 bt878(0): Bt878 (rev 17) at 00:0a.1, irq: 11, latency: 32, memory: 0xd7000000 DVB: registering new adapter (bttv0). dst_check_ci: recognize DTTDIG DST type : terrestrial DST type flags : DVB: registering frontend 0 (DST DVB-T)... The following device files are created: crwxrwxrwx 1 root root 212, 4 2005-06-04 18:56 /dev/dvb0.demux0 crwxrwxrwx 1 root root 212, 5 2005-06-04 18:56 /dev/dvb0.dvr0 crwxrwxrwx 1 root root 212, 3 2005-06-04 18:57 /dev/dvb0.frontend0 crwxrwxrwx 1 root root 212, 7 2005-06-04 18:56 /dev/dvb0.net0 I create symlinks to these in /dev/dvb/adapter0: lrwxrwxrwx 1 root video 16 2005-06-04 18:57 demux0 -> /dev/dvb0.demux0 lrwxrwxrwx 1 root video 16 2005-06-04 18:57 dvr0 -> /dev/dvb0.demux0 lrwxrwxrwx 1 root video 16 2005-06-04 18:57 frontend0 -> /dev/dvb0.demux0 lrwxrwxrwx 1 root video 16 2005-06-04 18:57 net0 -> /dev/dvb0.demux0 However, when I then try to use tzap to tune into a station (having previously created a valid ~/.tzap/channels.conf (when it was working) I get the following error: ./tzap -r "BBC ONE" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/wolvie/.tzap/channels.conf' ERROR: ioctl FE_GET_INFO failed (Invalid argument) Going back a step, if I try to recreate the channels file, I also get the same error: bash-3.00$ ./dvbscan ./dvb-t/uk-CrystalPalace | tee channels.conf scanning ./dvb-t/uk-CrystalPalace using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' main:2219: FATAL: FE_GET_INFO failed: 22 Invalid argument Many thanks in advance to anyone who can help me with this, 'coz it is quite literally driving me crazy. Once I have solved this problem, I will be able to divert all my energies to preventing myself from messing around with my comps in future when (very) drunk :p Wolvie
