OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: grog on December 11, 2004, 01:18:03 pm
-
Hi all. Just re-downloaded the OZ images & can't seem to get GPE to work. I went through the entire process twice (flash & format) & each time after the format I get the GPE splash screen & it just sits there. The second time I left it for half an hour, so I wouldn't think it takes *that* long to initiliaze.
Formerly I've had the original Sharp, thKompany & OZ OPIE 3.5.1 working on it. I''m flashing OPIE 3.5.2 right now.
Thanks in adnvance for any tips you can offer.
-
Me again. So it doesn't seem to be a GPE issue but an OZ 3.5.2 one. My Z freezes when I try to use the OPIE image too ;?<. Anybody else having these problems?
-
You sure the kernel flashed correctly?
What did updater.sh say? Or what did you name the files, check md5sum too.
Si
-
lardman Posted on Dec 12 2004, 08:05 AM
You sure the kernel flashed correctly?
How can I tell?
What did updater.sh say?
Nothing out of the ordinary AFAIK. I'll flash it again & check.
Or what did you name the files,
[root@zaurus /mnt/card/ROMs/OZ-3.5.2]# ls -l
-rwxrwxrwx 1 root root 94208 Dec 11 17:44 bootstrap-image.rootfs.img
-rwxrwxrwx 1 root root 13680640 Dec 11 17:39 gpe-image.rootfs.img
-rwxrwxrwx 1 root root 12320768 Dec 11 17:39 initrd.bin
-rwxrwxrwx 1 root root 12320768 Dec 11 17:39 opie-image.rootfs.img
-rwxrwxrwx 1 root root 5059 Dec 11 17:38 updater.sh
-rwxrwxrwx 1 root root 985160 Dec 11 17:38 zImage
check md5sum too.
I hate to admit my newbiness & ask, but how do I do that? :0
thks
-
Ok, you need to rename one of these files:
-rwxrwxrwx 1 root root 13680640 Dec 11 17:39 gpe-image.rootfs.img
-rwxrwxrwx 1 root root 12320768 Dec 11 17:39 opie-image.rootfs.img
to 'initrd.bin'.
'gpe...' is X windows based.
'opie...' is Qtopia based.
You only need 3 files:
initrd.bin
updater.sh
zImage.bin
so you can skip the rest.
Good luck,
radioz
-
You only need 3 files:
initrd.bin
updater.sh
zImage.bin
Uh huh. And using zImage.bin rather than just plain zImage is the change that will solve your problem (the documentation is confusing -- see this (https://www.oesf.org/forums/index.php?showtopic=9060) thread). The .img files on there are, I believe, unlikely to hinder the ROM being flashed.
-
You only need 3 files:
initrd.bin
updater.sh
zImage.bin
Uh huh. And using zImage.bin rather than just plain zImage is the change that will solve your problem
BINGO!! (I think) Actually the '.bin' extention isn't what my problem is (look at my file listing). But I just noticed that my rootfs file is named 'zimage' & NOT 'zImage'
I'll try it again & report back. THANKS
-
You only need 3 files:
initrd.bin
updater.sh
zImage.bin
Uh huh. And using zImage.bin rather than just plain zImage is the change that will solve your problem (the documentation is confusing -- see this (https://www.oesf.org/forums/index.php?showtopic=9060) thread). The .img files on there are, I believe, unlikely to hinder the ROM being flashed.
After reading this I decoded an updater.sh from the OZ d/l for a 5600 and it's target is 'zImage' not 'zImage.bin'... the C-7xx may be different.
Greg
-
Yes, this is confusing. My understanding is that this is the current naming requirement, however the updater.sh decides the filenames it wants, so this could change in the future for other machines which use updater.sh.
sl5500/5000D
----------------
zImage & initrd.bin
sl5600
-------
zImage & initrd.bin & updater.sh
C7xx/C8xx
-------------
zImage.bin & initrd.bin & updater.sh
To tell the truth I don't think the case of the filename matters at all as FAT16 isn't case sensitive (all filenames are stored in upper case I think).
Check md5sums against those provided in the download directory (in a file called md5*). Do a google for "windows md5sum" for an executable which will calculate md5sums (or there was one posted on the forum in the past couple of days).
Si
-
After reading this I decoded an updater.sh from the OZ d/l for a 5600 and it's target is 'zImage' not 'zImage.bin'... the C-7xx may be different.
Greg
Quite possibly. I'm sure it always used to be just zImage, for the 5500 anyway. But Mickey definitely says 'zImage.bin' (actually, he doesn't capitalise the 'i', but we'll forgive him that) in that other thread, and that seems to have worked. Of course, that's talking about the C700, and I don't know how far the 5600 and C700 differ in terms of flashing. The originally confusing instructions (http://www.openzaurus.org/web/index.php?option=com_content&task=view&id=22&Itemid=44) whose naming scheme Mickey contradicts conflate the two. *shrugs* Let's hope some sort of messing around with the filename fixed grog's problem.
-
Let's hope some sort of messing around with the filename fixed grog's problem.
That did do it. Thanks you guys for talking me through the problem :?).
And WOW! Am I impressed with OZ-GPE. *THIS* is the reason I bought a Z in the first place. Linux + X, don't get much better than that. Pretty cool. All I have to do now is figure out the network settings to get the usb conection to work with windoze & I'm off to the races.
thanks again
-
The originally confusing instructions whose naming scheme Mickey contradicts conflate the two. *shrugs* Let's hope some sort of messing around with the filename fixed grog's problem.
I've notified (more than a week ago) Rich Simpson (the OZ.org web admin) that this entry is incorrect and have asked him to alter it which he said he'd do once OZ.org comes back up.
Si