Results 1 to 5 of 5
i have a dvico fusion HDTV-DVB-t plus card and i have compiled support for the cs88xx chipset in the kernel and it get recognised proberly:
this is some relevent output ...
- 04-17-2005 #1Just Joined!
- Join Date
- Apr 2005
- Posts
- 3
DVB-T card no /dev/dvb/ node udev
i have a dvico fusion HDTV-DVB-t plus card and i have compiled support for the cs88xx chipset in the kernel and it get recognised proberly:
this is some relevent output from dmesg
so as you can see it is recognised corectly, my problem is that mythtv and the scan function from linux-dvb-* pagake both look for dvb cards in the /dev/dvb/ node but i dont have that all i get is /dev/v4l/video0,Code:Linux video capture interface: v1.00 bttv: driver version 0.9.15 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture tvaudio: TV audio decoder + audio/video mux driver tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6320,tea6420,tda8425,pic16c54 (PV951),ta8874z cx2388x v4l2 driver version 0.0.4 loaded ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI interrupt 0000:01:09.0[A] -> GSI 11 (level, low) -> IRQ 11 cx88[0]: subsystem: 18ac:db10, board: DVICO FusionHDTV DVB-T Plus [card=21,autodetected] cx88[0]/0: found at 0000:01:09.0, rev: 5, irq: 11, latency: 32, mmio: 0xe8000000 cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 cx2388x blackbird driver version 0.0.4 loaded cx2388x dvb driver version 0.0.4 loaded ACPI: PCI interrupt 0000:01:09.2[A] -> GSI 11 (level, low) -> IRQ 11 cx88[0]/2: found at 0000:01:09.2, rev: 5, irq: 11, latency: 32, mmio: 0xe9000000 cx88[0]/2: cx2388x based dvb card DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (DVICO FusionHDTV DVB-T Plus)... bt878: AUDIO driver version 0.0.0 loaded
is there something i need to do to point this card to the right nodes?
- 04-17-2005 #2Linux Engineer
- Join Date
- Jul 2003
- Location
- Uppsala, Sweden
- Posts
- 1,278
If you can't reconfigure mythtv or linux-dvb to look at /dev/v41/video0 then you can just create a symbolic link from /dev/dvb to /dev/v41/video0 you can do it like this:both look for dvb cards in the /dev/dvb/ node but i dont have that all i get is /dev/v4l/video0,
Then you should be able to rerun the configuration utility to properly detect the card.Code:ln -s /dev/v41/video0 /dev/dvb
Proud to be a GNU/Gentoo Linux user!
- 04-18-2005 #3Just Joined!
- Join Date
- Apr 2005
- Posts
- 3
Thanks for the idea but mythtv needs i think it is /dev/dvb/frontend0 and all i get in the /dev/v4l dir are video0 and vbi0,
- 04-18-2005 #4Linux Engineer
- Join Date
- Jul 2003
- Location
- Uppsala, Sweden
- Posts
- 1,278
well then symlink the real device to whatever it is that mythtv needs (/dev/dvb/frontend0)
Proud to be a GNU/Gentoo Linux user!
- 05-10-2005 #5Just Joined!
- Join Date
- May 2005
- Posts
- 1
I believe the device API for /dev/dvb/xxx devices are totally different from the /video and /v4l devices, so just symlinking won't work.
The correct devices need to be constructed for the dvb drivers - am currently looking into this myself !
However the basic point are
1) ensure you have a 2.6 kernel
2) check you have the correct drivers for your hardware - and they are getting loaded
3) if the /dev/dvb devices are not getting created - Google further !! Maybe you need to add some more udev rules.
I have looked in /usr/src/redhat/BUILD/kernel-2.6.x/Documentation/dvb text files ...


Reply With Quote
