Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] 2.6.3 dvb modprobe
Hello,
using vanilla kernel 2.6.3 and Hauppauge Nexus-s Rev. 2.2 I like to
automatically load the dvb modules using /lib/modules/modprobe.conf:
alias char-major-81 dvb-ttpci
alias char-major-250 dvb-ttpci
alias /dev/dvb/* dvb-ttpci
alias /dev/dvb/adapter0/* dvb-ttpci
alias /dev/video* dvb-ttpci
install dvb-ttpci /sbin/modprobe --ignore-install dvb-ttpci; \
/sbin/modprobe stv0299
With the above I can load the 1.1.0 modules and start the Debian sid
vdr-daemon as root like this:
$ modprobe dvb-ttpci
$ lsmod
Module Size Used by
evdev 9344 0
stv0299 10884 0
dvb_ttpci 80524 0
dvb_core 58772 2 stv0299,dvb_ttpci
saa7146_vv 49792 1 dvb_ttpci
video_buf 20612 1 saa7146_vv
saa7146 19108 2 dvb_ttpci,saa7146_vv
v4l1_compat 14468 1 saa7146_vv
v4l2_common 6400 1 saa7146_vv
videodev 9600 1 saa7146_vv
firmware_class 9088 1 dvb_ttpci
crc32 4608 2 dvb_ttpci,dvb_core
ttpci_eeprom 3072 1 dvb_ttpci
... ... . ...
$ /etc/init.d/vdr start -> fine.
$ xawtv -c /dev/video0 -> works ok
$ kvdr -> works as well. So far so good.
But when I omit the initial modprobe "dvb-ttpci" while the modules are
not yet loaded then "strace vdr-kbd -c /etc/vdr" gives:
access("/dev/dvb/adapter0/frontend0", F_OK) = 0
open("/dev/dvb/adapter0/frontend0", O_RDONLY) = -1 ENODEV (No such device)
and "strace xawtv -c /dev/video" similarily:
open("/dev/video", O_RDWR|O_LARGEFILE) = -1 ENODEV (No such device)
Probably my understanding of /dev/video0 (v4l) and /dev/dvb/adapter0
(v4l2) is insufficient, but according to the above aliases in
/lib/modules/modprobe.conf it should load the modules on demand, but
doesn't.
Or am I asking too much for auto-loading of the modules when the
device files are opened by the application?
--
Achim Löbbert - aloebbert@gmx.de
--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.
Home |
Main Index |
Thread Index