On Jul 23, 09 23:12:16 +0200, Frieder Ferlemann wrote:
Current Memory Clock: 2075509760 seems out of range. Indeed.
Matthias Hopf schrieb: this clock seems to be more or less random. With a sequence of init 3 init 5 I got Memory Clocks of 3331032064 3768198144
OMFG. ParseTable returns CD_SUCCESS if the command table does not exist.
And in your AtomBIOS, GetMemoryClock is not implemented. So far we had
no chance to determine this situation. It could well be that other,
completely unrelated bugs have been triggered by this as well.
(Hopefully) fixed in current git now, please retest.
Matthias
--
Matthias Hopf