I get a similar thing from i2c-io. It almost always repeats as failed, succeeded, failed, succeeded for i2c-io, while i2c-load fails many times before succeeding.
~~~~~~BEGIN CONSOLE OUTPUT~~~~~~~~~ root@gumstix-custom-verdex:~$ i2c-io 0x0b info ERROR: I2cTransfer: ioctl failed: Connection refused (111) ERROR: I2cReadBlock failed ERROR: Unable to retrieve information from i2c address 0x0b root@gumstix-custom-verdex:~$ i2c-io 0x0b info version: 2 minVersion: 1 SVN Revision: 22 ~~~~~~END CONSOLE OUTPUT~~~~~~~~~
I can get around this by using the serial interface between the gumstix and robostix in the short-term, but this is really important in the long term because I have a magnetometer that I need to talk to over i2c, so I
need to figure out what's up with my i2c bus. The i2c-test utilities work just fine, and I think my power supply is fairly clean (putting ceramic caps on the power didn't change anything).