Re: insmod bttv: init_module: No such device

From: Jens Lohmann-Hansen (jenslh_at_adslmail.dk)
Date: 09/29/03 

Date: Mon, 29 Sep 2003 19:49:52 +0200

Noone has a clue?

I wrote:

> Hi all.
>
> I hope I'm posting to the right newsgroup. Otherwise please redirect me
> :-)
>
> I'm having trouble using my Hauppauge WinTV card on a RedHat system. I've
> had it running (on said system), but after a kernel recompile (had to
> include nfs support) I can nolonger insmod bttv. I've since converted
> bttv- and i2c-use to modules.
>
> What I get is:
>
> [root@emilie bttv]# insmod bttv
> Using /lib/modules/2.4.18-10custom/kernel/drivers/media/video/bttv.o
> /lib/modules/2.4.18-10custom/kernel/drivers/media/video/bttv.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> [root@emilie bttv]#
>
> [root@emilie bttv]# lsmod
> Module Size Used by Not tainted
> tuner 10148 0 (unused)
> i2c-algo-bit 8300 0
> videodev 7904 0
> msp3400 16496 0 (autoclean) (unused)
> binfmt_misc 7044 1
> lirc_i2c 3652 0 (autoclean) (unused)
> i2c-core 18624 0 (autoclean) [tuner i2c-algo-bit msp3400
> lirc_i2c]
> lirc_dev 8928 0 (autoclean) [lirc_i2c]
> autofs 11012 0 (autoclean) (unused)
> 8139too 16000 2
> mii 1964 0 [8139too]
> ipt_limit 1568 2 (autoclean)
> ipt_state 1024 102 (autoclean)
> ipt_LOG 4128 2 (autoclean)
> ipt_REJECT 3456 2 (autoclean)
> ip_conntrack_irc 3328 0 (unused)
> ipt_MASQUERADE 2016 1 (autoclean)
> usb-ohci 19936 0 (unused)
> usbcore 70880 1 [usb-ohci]
> rtc 7516 0 (autoclean)
> [root@emilie bttv]#
>
> From the end of /var/log/messages:
>
> Sep 22 22:23:53 emilie kernel: bttv: driver version 0.7.91 loaded
> Sep 22 22:23:53 emilie kernel: bttv: using 2 buffers with 2080k (4160k
> total) for capture
> Sep 22 22:23:53 emilie kernel: bttv: Host bridge is PCI device 1039:0740
> (Silicon Integrated Systems [SiS])
>
> Do you need any more information? I've been searching the web for
> information, and it led me to remember to also insert the i2c- and
> videodev-modules - but it still doesn't work :-(
>
> Help please :-)