Hi there, I am new to VDR and to DVB-T and I have been trying to configure VDR 1.3.34to work with 2 Hauppauge Nova-T DVB-T cards under Debian (kernel 2.6.13) and have run into some problems. Can someone confirm that the output of dmesg (below) looks to be ok in respect of the NOVA-T cards? dmesg output; cx2388x v4l2 driver version 0.0.5 loaded PCI: Found IRQ 5 for device 0000:02:0a.0 PCI: Sharing IRQ 5 with 0000:02:0a.2 PCI: Sharing IRQ 5 with 0000:02:0a.4 cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected] TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe cx88[0]: hauppauge eeprom: model=90002, tuner=76 cx88[0]: registered IR remote control cx88[0]/0: found at 0000:02:0a.0, rev: 5, irq: 5, latency: 64, mmio: 0xf4000000 cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 PCI: Found IRQ 11 for device 0000:02:0b.0 PCI: Sharing IRQ 11 with 0000:00:1d.7 PCI: Sharing IRQ 11 with 0000:02:0b.2 PCI: Sharing IRQ 11 with 0000:02:0b.4 cx88[1]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected] TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe cx88[1]: hauppauge eeprom: model=90002, tuner=76 cx88[1]: registered IR remote control cx88[1]/0: found at 0000:02:0b.0, rev: 5, irq: 11, latency: 64, mmio: 0xf1000000 cx88[1]/0: registered device video1 [v4l2] cx88[1]/0: registered device vbi1 cx2388x blackbird driver version 0.0.5 loaded When we run w_scan to generate channels.conf we get the following error; moon2:/tmp/w_scan# ./w_scan -o3 >> /var/lib/vdrdevel/channels.conf Info: using DVB adapter auto detection. Info: unable to open frontend /dev/dvb/adapter0/frontend0' Info: unable to open frontend /dev/dvb/adapter1/frontend0' Info: unable to open frontend /dev/dvb/adapter2/frontend0' Info: unable to open frontend /dev/dvb/adapter3/frontend0' main:1779: FATAL: ***** NO USEABLE DVB CARD FOUND. ***** Please check wether dvb driver is loaded and verify that no dvb application (i.e. vdr) is running. Any help would be greatly appreciated. Thanks in advance. Andrew
I demand that Andrew Herron may or may not have written...
I am new to VDR and to DVB-T and I have been trying to configure VDR 1.3.34 to work with 2 Hauppauge Nova-T DVB-T cards under Debian (kernel 2.6.13) and have run into some problems. Can someone confirm that the output of dmesg (below) looks to be ok in respect of the NOVA-T cards?
dmesg output; cx2388x v4l2 driver version 0.0.5 loaded PCI: Found IRQ 5 for device 0000:02:0a.0 PCI: Sharing IRQ 5 with 0000:02:0a.2 PCI: Sharing IRQ 5 with 0000:02:0a.4 cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T
[snip]
Probably OK.
cx88[0]: registered IR remote control
OOI, is the default mapping adequately useable on these cards? If not, I have a patch (for budget-ci, intended for use with older Nova-T cards, but probably adaptable to cx88) which will allow programming from userspace. One of the keymap loaders in dvb-utils should be useable or adaptable.
[snip]
When we run w_scan to generate channels.conf we get the following error; moon2:/tmp/w_scan# ./w_scan -o3 >> /var/lib/vdrdevel/channels.conf
w_scan? How does this differ from scan (in dvb-utils)?
Info: using DVB adapter auto detection. Info: unable to open frontend /dev/dvb/adapter0/frontend0'
[snip]
Which modules are loaded? According to the kernel configuration help, you want cx88, cx88-dvb and one of four front-end modules, in this case mt352 or cx22702. (I don't know which; my Nova-T is older and uses tda1004x.)
Does that device node exist? If so, check the permissions. If not, the answer depends on whether you're using udev.
Without udev: # cd /dev && MAKEDEV dvb
With udev: make sure that you're using the version currently in unstable. (If you still don't get device nodes, proceed as for without udev.)
Hi Darren,
Thanks for your response. You were right it was cx88-dvb that was the problem. I'll do some tests with IR tomorrow and may take you up on the offer of a copy of your patch. Thanks.
Thanks again.
Andrew
On 11/2/05, Darren Salt linux@youmustbejoking.demon.co.uk wrote:
I demand that Andrew Herron may or may not have written...
I am new to VDR and to DVB-T and I have been trying to configure VDR
1.3.34
to work with 2 Hauppauge Nova-T DVB-T cards under Debian (kernel 2.6.13) and have run into some problems. Can someone confirm that the output of dmesg (below) looks to be ok in respect of the NOVA-T cards?
dmesg output; cx2388x v4l2 driver version 0.0.5 loaded PCI: Found IRQ 5 for device 0000:02:0a.0 PCI: Sharing IRQ 5 with 0000:02:0a.2 PCI: Sharing IRQ 5 with 0000:02:0a.4 cx88[0]: subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T
[snip]
Probably OK.
cx88[0]: registered IR remote control
OOI, is the default mapping adequately useable on these cards? If not, I have a patch (for budget-ci, intended for use with older Nova-T cards, but probably adaptable to cx88) which will allow programming from userspace. One of the keymap loaders in dvb-utils should be useable or adaptable.
[snip]
When we run w_scan to generate channels.conf we get the following error; moon2:/tmp/w_scan# ./w_scan -o3 >> /var/lib/vdrdevel/channels.conf
w_scan? How does this differ from scan (in dvb-utils)?
Info: using DVB adapter auto detection. Info: unable to open frontend /dev/dvb/adapter0/frontend0'
[snip]
Which modules are loaded? According to the kernel configuration help, you want cx88, cx88-dvb and one of four front-end modules, in this case mt352 or cx22702. (I don't know which; my Nova-T is older and uses tda1004x.)
Does that device node exist? If so, check the permissions. If not, the answer depends on whether you're using udev.
Without udev: # cd /dev && MAKEDEV dvb
With udev: make sure that you're using the version currently in unstable. (If you still don't get device nodes, proceed as for without udev.)
-- | Darren Salt | d youmustbejoking,demon,co,uk | nr. Ashington, | Debian, | s zap,tartarus,org | Northumberland | RISC OS | @ | Toon Army | URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html VDR & xine
Growing old is mandatory; growing up is optional!
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
w_scan does not support dvb-s, just dvb-t & dvb-c
On 11/2/05, Darren Salt linux@youmustbejoking.demon.co.uk wrote:
[snip] w_scan? How does this differ from scan (in dvb-utils)?
[snip]