Author Topic: OZ 3.3.6-pre1 + 860 = big fat failure !! (Read 7468 times)

Nicoo · « **on:** January 29, 2004, 11:46:48 pm »

2 days ago, I received my new 860 from dynamism .. WOW !
yesterday, I installed the cracko rom , works great !!
today I decided to install OZ 3.3.6-pre1 ...
2 seconds ago I had to admit that I fucked my new friend
GAME OVER

Well seriously, I did follow the README.FIRST file instructions and everything seemed to work pretty well until I hit this command line terminal asking me for a login/passwd. Well I\'m not scared of console but here the problem is that I cannot enter any login. I mean all roman character keys have no echo and all the special keys print an unicode char. I notice that the key \'M\' is somehow remapped to \'Enter\' but that\'s just not enough to log in.
The booting process seems to work fine but for some reason Opie is not loading and fail over to console mode. I have to admit that I am a complete newbie concerning PDA and I have no idea of what is the next step for me.
So if someone could help me out, it would be much appreciated...
Thx,

Nicoo

ps1: I have formatted my card under Windows (FAT 16)
ps2: I have checked the MD5sum
ps3: My only mean to access my CF-card is through the Z; this one being half-bricked won\'t help much.[/i]

Mickeyl · « **Reply #1 on:** January 30, 2004, 05:51:26 am »

Some C-models come with a couple of bad blocks in flash. The eraseall binary in the Sharp Updater RAMdisk doesn\'t remap these, so it is possible that your filesystem is trashed after that. This may be the reason for Opie not starting. There\'s nothing we can do about that except to include our own tools (i.e. eraseall) with the next versions of OZ.

Nicoo · « **Reply #2 on:** January 30, 2004, 06:59:00 am »

Thanks Mickeyl .. will work on that.

sdchew · « **Reply #3 on:** January 31, 2004, 04:52:42 am »

Quote

Some C-models come with a couple of bad blocks in flash. The eraseall binary in the Sharp Updater RAMdisk doesn\'t remap these, so it is possible that your filesystem is trashed after that. This may be the reason for Opie not starting. There\'s nothing we can do about that except to include our own tools (i.e. eraseall) with the next versions of OZ.

Ahh I guess this is the reason why my OZ 3.3.6pre1 installation never did work on my C760... I did a NAND Test and it does detect a single bad block in flash

Nicoo · « **Reply #4 on:** February 01, 2004, 03:27:59 pm »

I did a RAND test too and I have 5 bad blocks

Mickeyl: Does this eraseall tool already exist for OZ ? If not, I could start working on that if you were to give some
kind of guidance.
I\'d really like to try OZ out. !

Nicoo

Mickeyl · « **Reply #5 on:** February 01, 2004, 05:14:58 pm »

Just take a newer eraseall from the mtdutils.

Nicoo · « **Reply #6 on:** February 01, 2004, 09:25:25 pm »

Sorry for asking, but I\'m not quite sure how to use \'eraseall\' ?
Thanks again.

Nicoo

sdchew · « **Reply #7 on:** February 01, 2004, 11:15:39 pm »

yeah same here! any documentation I can have a look at??

Mickeyl · « **Reply #8 on:** February 02, 2004, 04:08:58 am »

./eraseall --help

Btw., make sure to unmount your fs before using eraseall.

alexy · « **Reply #9 on:** February 02, 2004, 01:10:34 pm »

Mickey, I think this is quite an important thing and could be the reason for many recent
install failures reported here. Could you please elaborate on how exactly to workaround
this issue, i.e on what stage to run eraseall and how it can be fixed in the next release?
I would document it myself but unfortunately, I do not have full understanding
of this NAND stuff.

Thanks a lot,

Alex Y.

Mickeyl · « **Reply #10 on:** February 02, 2004, 05:29:27 pm »

I advise you to check how updater.sh works. Decrypt it (tool is on my http://www.vanille.de/tools ) and you\'ll see in which stage eraseall is called. Now the only magic is to ship the new eraseall with the updater.sh on the CF (or whatever) and alter updater.sh to call the new eraseall.

lardman · « **Reply #11 on:** February 02, 2004, 07:00:18 pm »

Assuming this will fix these problems (and I know nothing about it bar what I\'ve read as I only have a 5500) is it worth adding it posthumously to the images which have already been released in an attempt to get more people to use (and hopefully develop for) OZ?

Si

Mickeyl · « **Reply #12 on:** February 03, 2004, 05:22:10 am »

Definitly... if someone comes up with a success story, a modified updater.sh and the necessary tools, we put that up on openzaurus.org.

Nicoo · « **Reply #13 on:** February 03, 2004, 01:35:49 pm »

i will give it a whirl asap. Thanks for the explanation.

Nicoo

alexy · « **Reply #14 on:** February 09, 2004, 11:59:11 am »

OK, I tried to play yesterday with eraseall...
Background: C760, some badblocks in NAND. Flashing with
stock zimage, initrd,a nd updater.sh results in OZ booting, logo
appearing and cursor flashing on the left (right under the logo).
That\'s it

So, I compiled eraseall from the CVS of mtd using 2.95.3 toolchain
and statically linking it (just in case). Changed updater.sh to call
./eraseall instead of /sbin/eraseall and placed the newly compiled
\"eraseall\" binary along with updated and re-encoded updater.sh
to CF. After flashing - exactly the same result...

Btw, flashing went normally with all the proper messages and with no errors.

Mickey, any other word of advice on how to proceed here?
Btw, there was no problems with 3.3.5.

I am just wondering if anyone could manage to install 3.3.6-pre1
on C760?

Thanks,

Alex Y.

News:

Author Topic: OZ 3.3.6-pre1 + 860 = big fat failure !! (Read 7468 times)