> 882cc204627226ffefda4e446fae3862 qtmoko-debian-gta02-v58.tar.gz
>
> a76072c1c9dce4eb2b07235f7cc307fe qtmoko-debian-gta02-v58.ubi
>
> 50baec96657802b5a053fa0ef6b777a2 uImage.bin-2.6.39-qtmoko-v58
>
checksum ok
> This is strange - it works for me. Are you booting with qi-v58.udfu?
Yep, I also
On Thu, Dec 12, 2013 at 11:10 PM, Radek Polak wrote:
> On Friday, December 13, 2013 02:59:01 AM Ben Wong wrote:
>
>> What's the checksum supposed to be for the QTMoko files?
>
> a76072c1c9dce4eb2b07235f7cc307fe qtmoko-debian-gta02-v58.ubi
> 50baec96657802b5a053fa0ef6b777a2 uImage.bin-2.6.39-qtmoko
On Fri 13 December 2013 13:25:47 Ben Wong wrote:
> Are you using dfu-util or dd to write to the NAND?
dd to write to NAND? :-o Don't do that!
That's prone to fail, since dd can't handle bad blocks, and NAND per
definitionem doesn't. That's why you got things like jffs2/ubifs
/j
--
() ascii rib
On Friday, December 13, 2013 01:25:47 PM Ben Wong wrote:
> I tried qi-v58 first then qi-v56 as a test. Neither worked. Haven't
> tried the tarball; I don't have an SD card handy and (correct me if
> I'm wrong) there's no way to unpack the tarball onto the NAND unless
> you've already booted from S
> The size should be ok. NAND is IIRC 256MB. Would you be interested to try
> jffs2? I can do it and upload quite easily.
Sure, I'd give that a shot if it's easy for you to do. I seem to have
more corruption problems from ubifs than jffs2, so wouldn't mind going
back.
—B
> Is the tarball ok at least?
Tested on the uSD and it is ok
...apart that I'm stuck at the PIN entry screen (that one with just the
notice "Please wait...") no matter how many times I restart. But from
ssh all seems to work well.
Joif
___
Openmoko co
6 matches
Mail list logo
