OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: 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]
-
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.
-
Thanks Mickeyl .. will work on that.
-
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
-
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
-
Just take a newer eraseall from the mtdutils.
-
Sorry for asking, but I\'m not quite sure how to use \'eraseall\' ?
Thanks again.
Nicoo
-
yeah same here! any documentation I can have a look at??
-
./eraseall --help
Btw., make sure to unmount your fs before using eraseall.
-
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.
-
I advise you to check how updater.sh works. Decrypt it (tool is on my http://www.vanille.de/tools (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.
-
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
-
Definitly... if someone comes up with a success story, a modified updater.sh and the necessary tools, we put that up on openzaurus.org.
-
i will give it a whirl asap. Thanks for the explanation.
Nicoo
-
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.
-
I\'m afraid you\'re on your own there. Next time I do a release I\'ll remember to also compile a kernel with debug out. I\'m not able to do one now, because all my resources go into OpenEmbedded.
-
Mickey,
You\'ve got a c750 haven\'t you? What\'s the difference (in terms of getting the flashing to work)? or was it just luck (or a lack thereof)?
(I\'m interested as I\'m tempted to upgrade when I get the chance).
Si
-
Well, I have seen quite a few C760 users around in the forums who have 3.3.6pre1 running... maybe they could do a NAND Block test on their machine for us?
-
Well, I have seen quite a few C760 users around in the forums who have 3.3.6pre1 running... maybe they could do a NAND Block test on their machine for us?
I\'ve got 3.3.6pre1 running on my C760. If someone would tell me how to do a NAND Block test (and explain if it could mess my Z up,) I\'ll give it a go.
Lance
-
use eraseall from cacko/x11 installer, that in tools.tar tools/bin/eraseall
-
You\'ve got a c750 haven\'t you? What\'s the difference (in terms of getting the flashing to work)? or was it just luck (or a lack thereof)?
Yes, I have a c750 and I have yet to hear about someone with a c750 and flashing problems. Everything went fine for the first time and every time later - maybe it\'s the flash for the second bank on the c760/c860 coming from a lower quality production.
-
All right, on my own I figured out _my_ problem: corrupted
(or, rather, interrupted) download of initrd.bin.
It would have been much better if md5sums file was also present... And my guess is that at least some of the problems
that people are reporting stem from this \"issue\".
Btw, it made no difference of what version of eraseall to use -
looking at the source it does not do anything special with bad
blocks - just if some error occurs on erasing some 16k block
it reports an error and proceeds with erasing the next 16k block.
Also, attempting to start opie-sh howto results in error - inability to find the howto itself. Is it supposed to be this way (i.e. if this is a known issue) ?
Thanks,
Alex Y.