Can someone offer some idea of where to look for the hangup problem. Here is the most concise way I can show it... Any help/direction will be greatly appreciated. [root@SaltRiver /root]# modprobe -dv 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 /lib/modules/2.4.2-2/kernel/drivers/media/video/videodev.o Using /lib/modules/2.4.2-2/kernel/drivers/media/video/videodev.o Symbol version prefix '' [root@SaltRiver /root]# modprobe -dv i2c-core ============================================= Mi2c-core.o: i2c core module odule 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 ============================================= /sbin/insmod /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-core.o Using /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-core.o Symbol version prefix '' [root@SaltRiver /root]# modprobe -dv i2c-algo-bit ============================================= Mi2c-algo-bit.o: i2c bit algorithm module odule 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 /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-algo-bit.o Using /lib/modules/2.4.2-2/kernel/drivers/i2c/i2c-algo-bit.o Symbol version prefix '' [root@SaltRiver /root]# modprobe -dv bttv ============================================= Module videodev kname videodev (it hangs hard here, must power cycle to get out...)
