Try turning on all the debugging options for the various drivers, and
look at the system log while you're modprobing them.
Clay
Mike Westkamper wrote:
Since I had no response to my pleas for help when it was complicated, here
is a simple question...
I do a modprobe bttv and get the following...
mode: NORMAL
Module matching i2c-core: /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-core.o
=============================================
/sbin/insmod -s /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-core.o
[root@SaltRiver /root]# modprobe -dvs i2c-algo-bit
================================i2c-algo-bit.o: i2c bit algorithm module
=============
Module i2c-core
kname i2c-core
objkey i2c-core
names: i2c-core
mode: NORMAL
Module matching i2c-core: /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-core.o
=============================================
=============================================
Module i2c-algo-bit
kname i2c-algo-bit
objkey i2c-algo-bit
names: i2c-algo-bit
mode: NORMAL
Module matching i2c-algo-bit:
/lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-algo-b
it.o
=============================================
/sbin/insmod -s /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-algo-bit.o
[root@SaltRiver /root]# modprobe -dvs videodev
=============================================
Module videodev
kname videodev
objkey videodev
names: videodev
mode: NORMAL
Module matching videodev:
/lib/modules/2.4.2-2/kernel/drivers/media/video/videod
ev.o
=============================================
/sbin/insmod -s /lib/modules/2.4.2-2/kernel/drivers/media/video/videodev.o
[root@SaltRiver /root]# modprobe -dvs bttv
=============================================
Module videodev
kname videodev
objkey videodev
At which time the kernel hangs hard. Must power cycle to get going again.
How do I determine what is hanging it?
Thanks for any help.
Mike
_______________________________________________
Video4linux-list mailing list
Video4linux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/video4linux-list
