Hi Kevin, On Tue, 2002-12-17 at 01:54, Kevin Bowen wrote: > I have a /dev/video/ directory which contains several devices, I think > unrelated to the tuner, then I have devices /dev/video0 through > /dev/video3 - which is, I'm told, how it's supposed to be - video0 is the > tuner, video1-3 are composite input etc. xawtv properly detects and defaults > to the tuner on video0. No, video[0-3] are *devices*. BTTV is *only* device 0 (video0). Each device cna have multiple inputs, which can be set by applications (inputs include tuner, composite, etc.). > Now here's a question which will reveal my newbitude ;) - whats the > distinction between insmod and modprobe, and when do I use them? Currently modprobe reads /etc/modules.conf, insmod doesn't. modprobe also preloads other needed modules (such as i2c-core/-algo-bit and videodev for bttv) by looking which symbols are missing for the module to load correctly and checking which modules provide these symbols. > I'm doing neither, they are loaded automatically (i see tuner related > entries in my modules.conf - apparently placed there automatically by > redhat). I dont have an options line specified, although based on someone > else's advice, I tried previously doing modprobe tuner type=2 (I think) with > no effect.. however the module was at that time already loaded. Do I need to > remove the module, then reload it with the option? Yes. rmmod or modprobe -r. Ronald -- Ronald Bultje <rbultje@xxxxxxxxxxxxxxxxxxx> Linux Video/Multimedia developer
