collie and kernel from 3.5.3 upgrades

[samac]

renamed the file to bzImage

Wrong name. It should be called 'zImage'

Check that the flash did actually occur (like the lights were on for about 30sec)


Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86455\"][{POST_SNAPBACK}][/a][/div]

Err, typo, it was zImage that I copied to the CF card, should of noticed that one myself.

Sorry

Samac

[bsaunder2002]

zImage-collie-64-0-r21.bin does not work for me

SL-5500, gpe image from sl5000,sl5500

copy zImage-collie... to zImage on a vfat formatted 64mb CF card
copy gpe image to initrd.bin on CF card

move switch to "replace battery"
take off cover
open keyboard tray
hold C & D keys down
press reset button on back
both lights come on
release keys and wait
eventually both lights go off
press reset
replace batt cover
move switch to normal operation
press on/off/cancel button

At this point, screen goes black, the boot penguin comes up
a couple of lines are printed
then screen goes white with the GPE 2.6 / powered by OE logo
it hangs at this point
fn/c
cal/c
nothing makes it go past this screen...

what's funny is that before I thought when the penguin appeared lots of kernel boot messages appear, even after the GPE logo screen showed up, lots of kernel messages appeared.

Those are helpful to indicate that something is working...

repeated the flash process using the standard sl5000,sl5500 gpe initrd.bin and the zImage-collie-64-0 ie the 3.5.3 originals....

this worked fine...
ok I was wrong about kernel messages under the penguin logo...after flashing with the standard zImage/gpe the
penguin appeard
a couple lines of text
then the GPE/OE logo screen
then lots of kernel messages written on top of logo
then a black screen with X cursor
then the touch screen calibration app...
this takes approximately 3 minutes (maybe less but definately not longer)

So the zImage-collie-64-0-r21.bin image hangs at the GPE/OE logo screen and never goes further.  

Any suggestions?
Bill
ps- I'm going to research other ways to flash.  I've always used C&D/reset but I keep seeing things about updater.sh(which by the way when I edit it shows binary data what gives is it a shell script or a binary, if it's a binary DONT call it .sh)

[llarensj]

Well, I give up.

I downloaded the opie-collie and the upgraded zImage from another machine with a diferent ISP (just in case...).

I flash It twice and get the same result: freezing in 'configuring update'. I assumed that after 20 minutes of 'configuring update' the machine is effectively hanged (don't tell me that showld wait more, sigh!).

Oh, the hard is a SL5500

Well, now Im a happy (?!) user of a crapy Sharp ROM 3.13

Is there another alternative to that rom?

(of course I'm lurking the openzaurus files hoping there will be another upgrade to flash arrrgggggghhh)

[HeavyWeaponDude]

I too have a similar problem, on the same hardware.
I've a SL-5500. I've followed the standard flashing procedure
who had always worked fine.
I've tried with zImage-collie-64-0-r21.bin (renamed zImage of course)
and opie-image-collie-20050407173817.rootfs.jffs2 (renamed initrd.bin).
The flashing go smoothly, but on startup the Z freezes on "configure update-modules".
Twice the flashing for twice the same result.

[niv]

I too have a similar problem, on the same hardware.
I've a SL-5500. I've followed the standard flashing procedure
who had always worked fine.
I've tried with zImage-collie-64-0-r21.bin (renamed zImage of course)
and opie-image-collie-20050407173817.rootfs.jffs2 (renamed initrd.bin).
The flashing go smoothly, but on startup the Z freezes on "configure update-modules".
Twice the flashing for twice the same result.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86510\"][{POST_SNAPBACK}][/a][/div]

me too

[PrOtOn]

I too have a similar problem, on the same hardware.
I've a SL-5500. I've followed the standard flashing procedure
who had always worked fine.
I've tried with zImage-collie-64-0-r21.bin (renamed zImage of course)
and opie-image-collie-20050407173817.rootfs.jffs2 (renamed initrd.bin).
The flashing go smoothly, but on startup the Z freezes on "configure update-modules".
Twice the flashing for twice the same result.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86510\"][{POST_SNAPBACK}][/a][/div]

Make sure you have power cable connected.
 I have the same hardware and have flashed at least 3 times with no problems. I'm still setting up the way I want, so I'm sure I will flash a couple of more times.

[llarensj]

Well, but what I don't understand is what is the difference between a sucessfull flashing and a failure? If the system not only boots, but take a series of steps before freezing, I necessarily reach to the conclusion that the flashing was fine (hey may be I'm wrong hehe) and the problem is other: I don't know, may be a specific incompatibility between the zImage (wich is the component that change) and some sort of specific hardware combination (what a hell, may be which works fine have US chips and the wrong have taiwanese chip, for to say something).

I say this because I flashed this series (all with 32-32 memory usage):

OZ 3.5.3 with 20050407 zImage (OK)
OZ 3.5.3 with bad version check zImage (2 times FAIL)
OZ 3.5.3 with 20050407 zImage (OK)
OZ 3.5.3 with last zImage (4 times FAIL)
OZ 3.5.3 with 20050407 zImage (OK)
SHARP 3.13 (OK)
OZ 3.5.3 with last zImage (2 times FAIL)
SHARP 3.13 (OK)

All times, except the first 2, with a clean CF that only have the files to be flashed.

This drives me to conclude that the problem is in the zImage and/or hardware combination and not in the flashing procedure

[niv]

it basiclly hangs when it is supposed to make the ssh keys.
It may cinsume more power then, but it shuldn't be updating the flash at this point right? so what would a power cord change.

Hell I will give it a try l8r

OT: I like the fact that I am new here and allready updating the wiki :-)
Linky

[HeavyWeaponDude]

Make sure you have power cable connected.
 I have the same hardware and have flashed at least 3 times with no problems. I'm still setting up the way I want, so I'm sure I will flash a couple of more times.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86557\"][{POST_SNAPBACK}][/a][/div]

I have connected the power each time I flashed.
As llarensj says me too believe that if the system boots but hangs during boot
is not a flashing problem but a system problem. But being a newbie too, maybe
I'm just plain wrong.
However since I still have plenty to learn about the Z I'm keeping to experiment with
the old 3.5.2.

[llarensj]

WHAT? the 3.5.2 don't hangs   ?
er... I suppose I miss that choice...  
RIGHT NOW I'm flashing it  

[gds]

Success report!

I was having serious problems with this kernel as well (hanging at various points in the boot, either right at the "booting..." stage, or on the updating modules stage). I just tried again today with a different initrd and it seems to have worked.

I used hrw's new kernel (http://www.openzaurus.org/official/unstable/3.5.3/upgrades/zImage-collie-64-0-r21.bin). As an initrd I used hentges opie-small (in http://oz.hentges.net/releases/3.5.3/T2/co...e_T2-EN.tar.gz). Flashed my 5500 with just the two files on a CF card and the boot went fine. I haven't tested much yet but I've rebooted a few times and it looks good. I even managed a pivot-root onto my SD card.

I get the warning about a mismatched kernel version because the hentges root disc expects a different version number, but you can just edit /etc/init.d/checkversion to fix that.

[m3xican]

I too have a similar problem, on the same hardware.
I've a SL-5500. I've followed the standard flashing procedure
who had always worked fine.
I've tried with zImage-collie-64-0-r21.bin (renamed zImage of course)
and opie-image-collie-20050407173817.rootfs.jffs2 (renamed initrd.bin).
The flashing go smoothly, but on startup the Z freezes on "configure update-modules".
Twice the flashing for twice the same result.
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

- SL-5500
- 256MB kingston CF
- [a href=\"http://www.openzaurus.org/official/unstable/3.5.3/sl5000,sl5500/gpe-image-collie-20050407173817.rootfs.jffs2]opie last release[/url]
- new collie kernel 64-0

And the same problem...
I have repeated twice the flashing procedure and the Z freezes on  "configure update-modules".

Flashing works fine with the previous 3.5.3 rom.

Please, fix this problem...

[l0n3star]

Hi,

I've tried this update with a SL-5000D and it worked without any problems (except
the wrong kernel issue when booting).

BUT:

I still have the suspend/resume issues!!!

This fix doesn't seem to work with SL-5000D (at least with mine). For example:
Pressing Right-Button or Menu at the "waiting one minute state" does suspend my
Zaurus.

Any Ideas?

Greetings,

Andreas

P.S.: Same with OZ 3.5.2, only working Version for me is 3.5.1

[Storm]

Ok, I downloaded the Collie r21 zImage file and flashed my SL-5500. I am using one of the pivot root scripts so everything runs off of the SD card (1GB Sandisk).

I get the hang at the "configuring network devices..." prompt. cal-c gets me past it. Funny, though, that I don't get the kernel mismatch message.

Opie comes up fine, but any attempt to suspend (either with the cancel switch or with the O menu item), or it appears anything which calls apm locks the zaurus requiring a trip to the battery switch...
For instance, running apm --suspend from a konsole immediately hands me back a prompt, but the Z is effectively locked at this point. Just as I did with some of the initial bootup stuff, I left it sitting for 30 minutes or more.

Is there a fix for this yet? In the interim, I will redownload and reflash r21, and if that doesn't work, probably flash back to the original zImage in the interim.

Thanks,
--Storm

[niv]

YES!!!!!

got the opie T2 Collie english from hentges (pretty minimal)

and the new ZImage

IT BOOTS!!!!!

ok off to config my wifi and finally get a browser going.

Thanks a lot!

P.S
I did have the power cord connected all the way..