Collie kernel update
Marcin Juszkiewicz June 30th, 2005
Today I pushed fixed 2.4.18 kernel for collie (Zaurus 5000/5500) into 3.5.3 “upgrades” feed. This version has fixed all Suspend/Resume problems:
- suspend on right-arrow button
- suspend on menu button
- suspend after resume
Update to that kernel is HIGHLY recommended.
Md5sums:
4aef6f1fac09668220b34f7a30f24c92 zImage-collie-24-8-r21.bin a46961d53eaa38ad2aa6cd09fa8c49b1 zImage-collie-32-0-r21.bin 24415d7794140e1854deaf400e5d437c zImage-collie-32-32-r21.bin dadb8903d76bddbb15f69cb0c3b62948 zImage-collie-40-24-r21.bin 9bbfb575237c2762e1aead2926f37383 zImage-collie-48-16-r21.bin 9ded1bbb4a326f9984997ea107fbda55 zImage-collie-58-6-r21.bin e179cc1991729d931f47d8031843aa0a zImage-collie-64-0-r21.bin
Complete instruction how to make it is available here.
I have just flashed my SL-5500 with the new zImage-collie-64-0-r21.bin image and the system freezes at the first boot during “configuring update-modules” step.
After a reset and a second boot the booting doesn’t start.
Then I have reflashed the Z obtaining the same results.
This is no good… :(
Wow! That’s great! Could you be so kind and post the md5 of all new kernels ?
Any chance of getting the same fix for SL-5600 ?
I appreciate the effort but my SL-5500 didn’t seem to like it. I reflashed with “zImage-collie-58-6-r21.bin” and OPIE but booting hangs at “Configuring update-modules”
There are several comments about this upgrade over in a thread on OE Forums; it seems to not install properly for a large number of people. Most of the complaints are regarding hangs on reboots. This seems to occur whether doing a “fresh install” or an upgrade of just the kernel.
The
zImage-collie-64-0-r21.bin (md5: e179cc1991729d931f47d8031843aa0a)
zImage-collie-58-6-r21.bin (md5: 9ded1bbb4a326f9984997ea107fbda55)
do not seem to work with the 3.5.3 opie image, they get stuck after the “Please wait: booting…” line appears (on one of several attempts to boot, it got as far as loading all modules, but then hung once more). Just reflashed with the stock 3.5.3 64-0 zImage (same opie image) and everything works fine again.
How do I upgrade?
Will a simple ipkg upgrade work? Or do i need to re-flash?
Thanks.
yeah, that’s great, right-arrow key bug was so annoying that i still use oz 3.5.2, now i will update, thx oz team
Thank you! Yipee!
Posting from a Collie, weeeeee I can scroll right :)
Well done on fixing an absolute showstopper.
Thanks and thanks to all the unsung hard working OZ devs!
i flashed my 5500 today with the new zImage-collie-64-0-r21.bin - kernel
and opie-filesystem “opie-image-collie-20050407173817.rootfs.jffs2″
after booting the new kernel it always hangs after “configuring update-modules”
forever
(flashing with the old kernel zImage-collie-64-0-20050407102515.bin and opie-image-collie-20050407173817.rootfs.jffs2 works ok)
what am i doing false?
The first boot after flashing starts well, but stops after showing the message “Configuring update-modules”.
I’ve waited more than one hour, with external power plugged in, and after some minutes the unit suspends itself.
I’ve tried with zImage-collie-64-0-r21.bin and zImage-collie-58-6-r21.bin.
I’ve downloaded images twice.
No success.
I’ve reflashed zImage-collie-64-0-20050627085413.bin , but it stops with warning red message in-betwwen asterisks complaining kernel version: it expects 2.4.18-rmk7-pxa3-embedix-3.5.3, but it finds 2.4.18-rmk7-pxa3-embedix- (?).
The strange side of this behaviour is that zImage-collie-64-0-20050627085413.bin was the kernel running ok before reflashing the zaurus with the new version.
Obviously I’ve renamed each time the right image to zImage and the initrd.bin is a copy of opie-image-collie-20050407173817.rootfs.jffs2
¿Any clue?
Now my zaurus 5500 is useless… and I’m sad.
Desperate, I’ve pressed CTRL+C (datebook button + C) while showing the message “Configuring update-modulesâ€?.
The script then resumes boot process, and everything looks OK (right arrow and menu don’t suspend), but at first reboot some issues are rising:
- Rebooting from “Shutdown” menu in opie reaches 100%, but then machine stays locked up, and needs hard reset.
- Rebooting from console using “reboot” gets locked after showing “Deconfiguring network interfaces” (needs hard reset).
- Boot process stops (lasts forever) at start at some points:
- “Please wait…” (needs CTRL + C)
- “Configuring network interfaces…” (needs CTRL + C)
- Then, in opie, some issues have raised:
- Kopi & Kapi die when trying to save preferences
- network interfaces don’t work:
- “Network” app in Settings does not appear on screen
- “/etc/init.d/networking restart”, doesn’t finish and cannot be stopped
- usbnet driver starts and configure usb0 interface correctly in linux PC, but not in Zaurus.
- reboot does not work, as stated before.
- chvt (or menu applet) does not change VT, leaving phisycal keyboard unusable.
Regards,
Rafa.
Am i right in assuming that this new kernel is not in the current install images?
That is, after installing i have to update it from the feed?
-raven
I know this is an ignaant response, but what process is used for just upgrading the kernel? Is it the same as OS install without the initrd.bin available?
I suspect it is particularly simple, but that suspend bug is very annoying(I thought it was panicking since it won’t resume) and I don’t remember the kernel-change instructions.
FWIW I’m still using a collie.
Well tried the kernel drop(does work, as it so happens) but it came up unbootable.
I figured it was a non-working method and did a full reinstall.
Big waste of time, since the updated kernels do not boot.
If it helps any, on a new installation it hangs on configuring ppp-dialin(that’s where it did for me, anyway.)
Score:
Busted kernel with suspend bugs: 1
Kernel hackers trying to fix it: 0
People trying to get OZ usable on their ancient SL-5500’s: ?
I had the gpe image on my Z and decided to give OPIE a try with this new kernel.
I’ve put upgrades/zImage-collie-48-16-r21.bin (zImage) and opie-image-collie-20050407173817.rootfs.jffs2 (initrd.bin) on a CF and flashed.
But when booting it stops with “Configuring update-modules”. After some minutes without changes my Collie shuts down. Something must be wrong :).
ok, screen just blanks. no shutdown.
The kernel update doesn’t seem to fix the suspend problems on SL-5000D.
At least for me. Can anyone test this with another 5000?
Well, anyway: thank you for the great work… :-)
The same thing happens here, on my Collie w/3.5.3. I tried flashing just the kernel (this actually started up for me, once), then both the kernel and the initrd, then the 3.5.3 release of the kernel and initrd and the new kernel afterwards, on the clean install.
Hi,
First: Thank you very much for your effort!!!
I am trying to flash my 5500 with the opie image in the download area:
http://www.openzaurus.org/official/unstable/3.5.3/sl5000,sl5500/opie-image-collie-20050407173817.rootfs.jffs2
and the new 64-0 kernel. It’s still in the process, and it started 90 minutes ago, how long does it take? I think it’s frozen.
Anyway, your work is great!!!
See you
E
I tried flashing just the kernel, and it mostly worked, but I had removed the usbdcore kernel module so my touchscreen didn’t work after that. I tried reinstalling that module, but didn’t have any luck so I reflashed with the 3.5.3 released opie image and the new kernel. At this point, it went through it’s initialization routine and got stuck in the same place as tapo, above. So I reflashed with the 3.5.3 released opie image and kernel and, once that was done, flashed just the new kernel. Doing this makes the machine hang at “INIT: version 2.86 booting Please wait: booting…”
BTW, Do I have to accept your cookie to post?
Is there a SL-5600 update in the works ?
same here with mine (5500G) and 64-0 zImage. :-(
Same error for me.
First boot stopped at ‘configuring update modules’.
After turning the device off and on again it hangs on ‘please wait: booting’.
SL-5500G (German version).
zImage-collie-64-0-r21.bin
opie-image-collie-20050407173817.rootfs.jffs2
Norbert
Same for me, collie with 64/0 opie image stops on “configuring update-modules”.
Used the image with the old initrd.bin.
Any suggestions?
micsto has the same problem: “stops with Configuring update-modulesâ€?
I have the same problem. It hangs at Configuring update-modules. I’m going back to the original!
Same thing for me.. This is extremely frusturating, as I do not have access to a CF reader/writer (for the time being…until I drive home). I’m now stuck with ‘Configuring update-modules’. (On the first boot after flashing with new collie kernel).. This sucks!
I’m having the same problem. First boot after flash gets to Configuring update-modules and then halts. It still responds to the keyboard (return), but doesn’t go any farther. Eventually, the screen blanks but can be brought back by pressing the “backlight” button. After over half an hour, no progress beyond “Configuring update-modules”
Is there a fix for this or have I done something wrong in my update?
Thanks.
ken
Same results on my 5500…
Any updates to this yet?
Is it a corrupted zImage file?
Can you give us the CRC or such for it to verify?
Who done deleted my comments?
I have the same problem.
As it turns out doing the flash procedure with just the zImage on there does swap the kernel, and doing so has the same ultimate results: boot failure. Swapping back (from a clean of the updated kernel, even) showing that the system hangs(the one time I did it, anyway) configuring ppp-dialin.
Going to try installing(kernel only) an older(gasp!) kernel next, will update with my results here.
I tried with 64/0+opie, it just hang up after “… tainted modules from SD”.
Gday,
i had the same prob with the new kernel the same way tapo had.
but i tested it with opie and gpe both having the prob so must be in new kernel as it worked with the org kernel.
email if u want any help with resolving the prob & maybe hosting some of my rootfs images? creating a opie & gpe image…. will have screenshot soon too ;)
-EOF-
Problems, I noticed:
1. Sometimes Z cannot be switched on and has to be master resetted
2. Sometimes it switches on, Screen appears, but then immediately switches off. Second try works.
3. Sometimes Z cannot be switched off and hangs complete
Something still seems not to work, as wished…..
Could you please tell me how to apply this upgrade?
A fresh reflash of 64/0 + opie does not work for me.
Same with me. The kernel just hangs with that message (sl5500g)…
Same thing for me–stops at “configuring update-modules” Flash back to previous zImage.
Thanks for the effort, though! And all your work on OZ!
Same thing as previous post. Also, when attempted to reboot a second time, the zaurus did not get past the first line.
Same problem here.
Seems like a little work is still necessary. ;-)
Got the same problem tbat tapo, it flashed well but got stuck after “configuring update-module”.
What can i do to correct that ?
(by the way, i had just flashed my collie two days before with 3.5.3 release and it went well)
New OZ complained profusely over use of old kernel, but functions the same as the release 3.5.3 kernel. Are we sure this is a kernel bug and not a configuration bug? I don’t recall the same issue in 3.5.2(which kernel I used.)
Is there a bugzilla or something I should be posting this to?
I have the same issue as tapo. After flashing with zImage-collie-48-16-r21.bin and opie-image-collie-20050407173817.rootfs.jffs2, the first initialisation process hangs at “Configuring update-modules”.
After this, if I reset and reboot, it hangs at “Please wait: booting…”.
I also tried flashing with the zImage-collie-40-24-r21.bin in case the 48-16 was a dodgy zImage fsr, but this behaves the same way.
Finally, I tried flashing with the same opie-image initrd and the zImage-collie-48-16-20050407102515.bin, which was successful (as expected). I then tried flashing with just the zImage-collie-48-16-r21.bin. Again, after flashing, my Z hangs at “Booting please wait…”.
What gives? :-)
Same error (it stops with “Configuring update-modules�) with zImage-collie-58-6-r21.bin and opie-image-collie-20050407173817.rootfs.jffs2
Have we done something wrong? Or is it a known bug of this collie kernel upgrade?
Sorry guys but I got this kernel I used zImage-collie-64-0-r21.bin and opie-image-collie-20050407173817.rootfs.jffs2. I had a similar result as tapo. I left it for a good ten minutes and then decided it wasn’t going to get any further. It didn’t respond to anyhting but the battery switch. Then next boot it hangs at the ‘Booting Please wait’ prompt. I’ll try flashing again just in case something went wrong during the flash.
ok Mine is doing the same thing Did yours ever boot up to opie mine seems to be hanging at that same spot.
I have exactly the same problem. Every few months I try OpenZaurus on my SL-5500G, because the last official Sharp-ROM is really old now and you don’t get any new software for it. But I never had luck to get a working system with OpenZaurus. Neither OPIE nor GPE is usable, but I think that most problems are kernel-problems.
My Idea is the following: Wouldn’t it be possible to use the latest working Sharp kernel 2.4.18.something to run OPIE or GPE? The kernel has (nearly) nothing to do with what apps you can run on a device. And the Sharp kernel works perfectly with the given hardware. So the users could actually use OpenZaurus. Or am I missing something?
Hello, I have exactly the same problem. The “regular” zImage found in /official/unstable/3.5.3/ boot as usual.
Thanks for the great job you have done till now.
Well, I have the same problem too, I have tried both the 32-32 and the 48-16 kernels on a 5500, but both don’t come past the “Configuring update-modules”.
I have gone back to the 3.2.3 kernel.
I there a way to upgrade to the new kernel without flashing the whole thing ?.
I have same problem with my 5500. I started with 64-0 and 58-6 images and they are freezing my zaurus during the first boot. ‘Configuring update-modules’ message is last that I see. After waiting a 10 minutes I did another attempt. 48-16 image was first that started for me.
I’m seeing exactly the same thing - I re-flashed using the same versions of the files that tapo used - upon boot it just sits at the ‘Configuring update-modules’ stage. Anything I type appears on the screen, so it doesn’t seem to be completely dead. Anyone got any thoughts?
From reading the forums, it seems that people have had more luck using Hentge’s Opie ROMs - http://www.hentges.net/misc/openzaurus/oz3.5.3-opie1.2.0.shtml
same problem here, it hangs at “Configuring update-modules” and wont boot.
I seem to have the same problem as tapo.
Collie 32:0 image on an SL5000
I’ve tried flashing a couple times with the same result, the first boot just stops at “Configuring update-modules”. As subsequent hard reset results in the OpenZaurus banner and “Please wait: Booting…”
Screen blanks after some time
Update: Seems to affect GPE 2.6 too, the GPE welcome screen appears, then, nothing…..
A bit of delving and I see that this problem is not un-common and being discussed on the openembedded forums, though there appears to be no resolution as yet.
I grabbed this kernel and used it with hentages and it seems good.
The performance is INCREDIBLE!
I’m having the same problem w/regards to having to CTRL-C past “Please wait; booting…”, “Configuring network interfaces…”, and hangs on suspend, both from hw key and from menu requests. Is anything being done about this? It’s been most of a month since these problems started to crop up, and although I’d really love to use OZ, I have to have use of my Z, and it has to be stable…
Does it exists any fixed method for running this kernel without any error ? (SL5500)