Debian Install failure: Hash Sum Mismatch
Quakeman1 at gmx.net
Thu Aug 28 14:04:54 CEST 2008
Interesting is, that i updated my NAND uboot to the latest version in
which was from 27.8 at the time i downloaded it and it displays
"1.3.2-moko12" at bootscreen. The last version before i used to update
was from a few weeks before from another location and this version has a
date in the version which shows from when it was.
The NOR bootloader also says "1.3.2-moko12" at the bootprompt, why i
don't really know if i upgraded or downgraded my NAND bootloader. ;)
It is a bit confusing that the newest bootloader image now uses the
nearly same identification string as the quite old one in the NOR flash.
Joseph Reeves wrote:
> I've set the clock speed down and, after a couple of attempts, I
> managed to get all stages of the install script to complete. When
> trying to boot, however, I am told that I've got an incorrect magic
> number and am kicked backed to the u-boot screen. I assumed I had an
> old u-boot (it's never been updated since it left the
> pre-mass-production production line) but the latest version gives the
> same result. It's reported as:
> root at om-gta02:~# grep Bootloader /dev/mtdblock1
> Neo1973 Bootloader U-Boot 1.3.2-moko12
> root at om-gta02:~# grep Bootloader /dev/mtdblock0
> Neo1973 Bootloader U-Boot 1.3.2-rc2-dirty-moko12
> Although, is this the latest? Yes, I know there's a lot on the lists
> about u-boot already, but please somebody take pity on me ;)
> The latest u-boot version according to
> http://www.denx.de/wiki/U-Boot/ReleaseCycle is 1.3.4; 1.3.2 was
> released on 09 Mar 2008 and the Debian wiki lists success with the
> "latest version" released on 2008-08-05.
> Off topic, but there does seem to be a problem on the wiki about
> finding out release dates and version numbers - it takes a lot to stay
> on top of it all.
> Any ideas about my current problem would be greatly appreciated.
> 2008/8/27 Nathan Kinkade <nath at nkinka.de>:
>> 2008/8/27 Joseph Reeves <iknowjoseph at gmail.com>:
>>> Thanks Nathan, that sounds encouraging.
>>> I've not found anything too useful yet:
>>> root at om-gta02:~# find /sys | grep clock
>>> root at om-gta02:~# cat
>>> root at om-gta02:~#
>>> But I'll keep looking around.
>> This is probably it: /sys/module/glamo_mci/parameters/sd_max_clk
>> Openmoko community mailing list
>> community at lists.openmoko.org
> Openmoko community mailing list
> community at lists.openmoko.org
More information about the community