|
the whole reason I included those probe attempts was
to figure out how to probe. I've heard many people say to do things
similar to what you said (result below) But is seems that the -y and
-a command line switches are not valid. [EMAIL PROTECTED]:~# /usr/local/sbin/i2cdetect -y -a 3 Error: I2CBUS argument not a number! Syntax: i2cdetect [-f] [-q|-r] I2CBUS [FIRST LAST] I2CBUS is an integer With -f, scans all addresses (NOT RECOMMENDED) With -q, uses only quick write commands for probing (NOT RECOMMENDED) With -r, uses only read byte commands for probing (NOT RECOMMENDED) If provided, FIRST and LAST limit the probing range. i2cdetect -l lists installed busses only Error: No I2C busses found! Be sure you have done 'modprobe i2c-dev' and also modprobed your i2c bus drivers Keith C wrote:
-- Thank you for your time, --==<< R i c h a r d B r o n o s k y >>==-- Before posting to a mailing list I check the following locations: http://mysettopbox.tv/phpBB2/ http://ivtvdriver.org/ http://www.gossamer-threads.com/lists/mythtv/users/ http://www.gossamer-threads.com/lists/ivtv/devel/ http://www.gossamer-threads.com/lists/ivtv/users/ http://knoppmythwiki.org/ I may have missed the answer there, in which case, please point out the article to me, but don't say "check forum X." Nearly all viruses and spyware are designed to use Microsoft internet products. Protect yourself by avoiding Internet Explorer & Outlook/Outlook Express. |
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
