Has anyone gotten to the bottom of this thermal calibration error with the G5? I see lots of discussion of a possible bug in ASD thermal calibration and claims that it can destroy the eeprom that stores the calibration info on the logic board.
So what's the bottom line here?
Does this error in reality indicate that the eeprom is no longer writable?
Could this simply be an issue of the inner door not sealed properly (perhaps this calibration is critically sensitive to this)?
The fans are racing as intended since the CPU's have been replaced and the calibration stored on the logic board is no longer correct. Everything is fully functional and passes all tests. The inner shield is in place and the sensor (by the rightmost tab) sees it there. The intake fan is running. I also tried another fan with no change. I suspect that some overly high sensitivity to the fan speed is not really the issue here.
I have a dual 2.5GHz G5. The liquid cooling system is completely refurbished and the system passes ASD tests. I currently have ASD 2.5.8. I see reports of success using this version so there must be some hardware related issue here.
I'd be most grateful if someone would share the trick or workaround for this.
So what's the bottom line here?
Does this error in reality indicate that the eeprom is no longer writable?
Could this simply be an issue of the inner door not sealed properly (perhaps this calibration is critically sensitive to this)?
The fans are racing as intended since the CPU's have been replaced and the calibration stored on the logic board is no longer correct. Everything is fully functional and passes all tests. The inner shield is in place and the sensor (by the rightmost tab) sees it there. The intake fan is running. I also tried another fan with no change. I suspect that some overly high sensitivity to the fan speed is not really the issue here.
I have a dual 2.5GHz G5. The liquid cooling system is completely refurbished and the system passes ASD tests. I currently have ASD 2.5.8. I see reports of success using this version so there must be some hardware related issue here.
I'd be most grateful if someone would share the trick or workaround for this.