Quick update, i2c as modules did nothing to help.
I've done "modprobe ivtv newi2c=1 ivtv_debug=511", result = http://www.watchin.me.uk/ivtv2.txt and also "modprobe ivtv newi2c=0 ivtv_debug=511", result = http://www.watchin.me.uk./ivtv.txt both don't really mean a lot to me so i'm hoping someone who understands the output can help and fix whatever is the problem, as i said earlier, the modules its complaining at can all load fine by themselves using modprobe but ivtv never sees them. cheers, Mike Mike wrote: > Mark, > thanks for the suggestion but it didnt seem to change anything, the > newi2c option was there as well as the other stuff you pasted from your > modinfo. > > I'm off to try building i2c as modules and see if that helps in anyway > > If it helps this is the output from i2cdetect for the i2c bus for the > ivtv driver: > > [EMAIL PROTECTED]:/mnt# i2cdetect 2 > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c/2. > I will probe address range 0x03-0x77. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: XX XX XX XX XX XX XX XX XX XX XX XX XX > 10: XX XX XX XX XX XX XX XX 18 XX XX XX XX XX XX XX > 20: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 40: 40 XX XX XX 44 XX XX XX XX XX XX XX XX XX XX XX > 50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 60: XX 61 XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 70: XX XX XX XX XX XX XX XX > [EMAIL PROTECTED]:/mnt# lsmod > > > cheers, > Mike > > Mark Knecht wrote: >> On 7/16/06, Mike <[EMAIL PROTECTED]> wrote: >>> can anyone help with the following output when doing modprobe ivtv? >>> >>> i have the modules it complains at built and they can load fine with >>> just using modprobe. >>> if i manually load them (with modprobe) nothing changes with the output, >>> can anyone suggest any ideas of what to try / how to fix it ? >>> >>> ivtv: ==================== START INIT IVTV ==================== >>> ivtv: version 0.7.0 (tagged release) loading >> <SNIP> >>> ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) >>> ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >>> ivtv0: i2c addr 0x21 not found for command 0x4008646f! >>> ivtv0: i2c hardware 0x00000008 not found for command 0x4008646d! >>> ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >>> ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >>> ivtv0: i2c hardware 0x00000008 not found for command 0xc008561c! >> <SNIP> >> >> Hi Mike, >> I loaded ivtv-0.7for the first time this morning and it worked OK >> for me. modinfo suggests that there may be some sort of new i2c >> software in this driver. It looks like you can set >> >> newi2c=0 >> >> as a way to go back to the older stuff? Not sure: >> >> dragonfly conf.d # modinfo ivtv >> filename: /lib/modules/2.6.17-gentoo-r2/extra/ivtv.ko >> author: Kevin Thayer, Chris Kennedy, Hans Verkuil >> description: CX23415/CX23416 driver >> license: GPL >> version: 0.7.0 (tagged release) >> vermagic: 2.6.17-gentoo-r2 SMP preempt mod_unload PENTIUM4 gcc-3.4 >> depends: >> videodev,tveeprom,i2c-core,i2c-algo-bit,v4l1-compat,firmware_class >> alias: pci:v00004444d00000803sv*sd*bc*sc*i* >> alias: pci:v00004444d00000016sv*sd*bc*sc*i* >> srcversion: 5ECD5A6CE5290101AEB7F8F >> parm: newi2c:Use new I2C implementation >> default is 1 (yes) (int) >> <SNIP> >> >> Run modinfo ivtv yourself, make sure you see the same stuff I am and >> then try modprobing using some of the options. Maybe one will help. >> >> Cheers, >> Mark >> >> P.S. - ivtv is working - mythtv is totally broken though! >> >> _______________________________________________ >> ivtv-users mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-users >> > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
