Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Sudden motion sensor dissapears

Hi,
I have an issue with the sudden motion sensor on my computer.With the latest mac os x 10.4.10 the sensor always appears in the system profiler on warn starts (ie, when I reboot) but never on cold starts when I turn on the computer). I've tried with the original mac os disk that came with the PB with version 10.4.0 and the sensor always appears. I've tried with a retail mac os 10.4.6 mac os x installation disk and the sensor only appears with warm starts. I've updates 10.4.0 to 10.4.10 and I have the same problem, this upgrade done from system update and with the combo updater.
the only consequence is that widgets like Level don't work. Starting the computer takes like 1 second more and in the system.log log I get the error:
Oct 8 00:29:31 localhost kernel[0]: IOI2CController::clientReadI2C cmd key:1017, B:1, A:b0 S:25, L:1, M:3 status:0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: -IOI2CController::clientReadI2C status = 0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: AMS::readBytes ERROR: failed to read from I2C
Oct 8 00:29:31 localhost kernel[0]: AMS::shockIntHandler ERROR: failed to read the byte
Oct 8 00:29:31 localhost kernel[0]: IOI2CController::clientWriteI2C cmd key:1019, B:1, A:b0 S:25, L:1, M:2 status:0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: -IOI2CController::clientWriteI2C status = 0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: AMS::writeBytes ERROR: failed to write to I2C
Oct 8 00:29:31 localhost kernel[0]: AMS::clearInterrupt ERROR: failed to write the bytes, retval = 0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: AMS::shockIntHandler ERROR: failed to clear the interrupt, retval = 0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: IOI2CController::clientReadI2C cmd key:101b, B:1, A:b0 S:0, L:1, M:3 status:0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: -IOI2CController::clientReadI2C status = 0xe00002ed
Oct 8 00:29:31 localhost kernel[0]: AMS::readBytes ERROR: failed to read from I2C
Oct 8 00:29:31 localhost kernel[0]: AMS::checkResult ERROR: failed to read the bytes
Oct 8 00:29:31 localhost kernel[0]: AMS::writeCommand ERROR: failed to check the result code
Oct 8 00:29:31 localhost kernel[0]: AMS::startApp ERROR: failed to send kStartAppComm
Oct 8 00:29:31 localhost kernel[0]: AMS::start ERROR: startApp failed

Apple has this kb article http://docs.info.apple.com/article.html?artnum=300781 but doesn't help much and this forum has reports from other people but with older versions of tiger and that got fix with version 10.4.3.

I've aldo used the AMSTracker program to report data from the sensor without problems (would that indicate the sensor works ok?)

Can anybody help me solve this error?
TIA

Message was edited by: PerseP

Message was edited by: PerseP

Ppowerbook 1.5Ghz 15", Mac OS X (10.4.10)

Posted on Oct 9, 2007 7:23 AM

Reply
6 replies

Oct 9, 2007 1:00 PM in response to PerseP

Update:
mac os x 10.4.0 to 10.4.7 to 10.4.8 to 10.4.9 to 10.4.10 works always.
mac os x 10.4.0 to 10.4.10 via combo update works only with hot starts.

In the post http://discussions.apple.com/thread.jspa?threadID=228309 they've found that in versions 10.4.0, 10.4.1 and 10.4.2 of mac os x the the motion sensors appears properly in the system profile but with update 10.4.3 Apple seems to break this until they've released version 10.4.7 which fixes it again.

Oct 11, 2007 1:48 AM in response to Jrsy Man

Yes I have,
with all my tiger installations I got to the conclusion that the sudden motion sensor only shows up always if I have install mac os update 10.4.7 no matter what updayes I've had before or after.
My intention is to keep the forum thread Problem with Sudden Motion Sensor after 10.4.3 Update open to the new tiger updates

Sudden motion sensor dissapears

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.