collie and kernel from 3.5.3 upgrades

[samac]

YES!!!!!

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

and the new ZImage

IT BOOTS!!!!!

I also downloaded  http://oz.hentges.net/releases/3.5.3/T2/co...pie1.2.0-r9.bin
and this gave me a fully configured Z.

Though you should only copy the cardfs to your SD card (not fat16) as it will be renamed on a fat16 partition, and not be detected.

All seems to work just fine.

samac

[bsaunder2002]

hrw,
   Are you investigating why your kernel wont work with the default 3.5.3 gpe/opie images?  Hentges only provides opie images and I want to run gpe.   Any chance you'll provide some new sl-5500 kernels?

Bill

[ndsipa pomu]

Just upgraded by downloading the zImage for collie 64-0 version in upgrades.

renamed it and copied it to my cf card, and used the opie image from the 5000/5500 folder.

Flash seemed to go OK but now I have a big red WARNING

You are running the wrong kernel

You are running ` 2.4.18-rmk7-pxa3-embedix- `
I expect ` 2.4.18-rmk7-pxa3-embedix-3.5.3 `

Running this combination is not supported

I will sleep for 1 minute now. Use this chance to reboot the device and flash the proper kernel now!

Any thoughts?

Samac

PS I tried reflashing a second time with the same result, now going back to the original 3.5.3 64-0 zImage.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86083\"][{POST_SNAPBACK}][/a][/div]

[ndsipa pomu]

I'm getting the same problem with the newer kernel not booting on a SL-5500 Collie. I flashed just the zImage, but am getting similar problems with init not progressing.

I've tried flashing the newer kernel a couple of times, but with no luck. The original kernel will still boot however. I'm using a modifed Root on SD setup, but testing out reiserfs on the disk image (it works, but doesn't really give any advantages - it just seemed a good idea at the time).

[llarensj]

Uf, still experimenting with roms!

1- flash 3.5.2, ALL ok BUT no windows sync soft works (original cd or last intellisync from 3.13). So I get KA/PI KO/PI with PI-Sync, its a little troublesome to get it working but it finally runs fine, just it gets much memory and takes a big loadtime. Is there an intelliSync/Qtopia soft that works with 3.5.2 ?

2- flash Hentges rom, and again the suspend problem, but not so frecuently, and now the clock don't reset, but keeps the time where it freezes. I just don't understand. Is there a procedure or configuration to avoid the problem? (its just software I presume).

Arrgh I like more the opie PIM than KO/PI  

Salute la barra!

[Teletubbie]

Hi,
maybe the reason it works with hentges is, that hentges is using openssh instead of dropbear.
Cheers,
Sam

[niv]

2- flash Hentges rom, and again the suspend problem, but not so frecuently, and now the clock don't reset, but keeps the time where it freezes. I just don't understand. Is there a procedure or configuration to avoid the problem? (its just software I presume).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86992\"][{POST_SNAPBACK}][/a][/div]

I am sad to report that the bug still exist. using: 5500/3.5.3 r21/ Hentges opie

Niv

[BeKind]

To remove the warning, you need to remove/rename a script in /etc/init.d/ (checkver something like that - no Z to hand atm I'm afraid).

OK but how would you do that when the Z will not go passed the sleep message.

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

works fine for me, after a minute or two it continues booting.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86118\"][{POST_SNAPBACK}][/a][/div]

I want to upgrade the 3.5.3 kernel to the june 30 update (collie 64-0) by hrw, but I am afraid my Z will lock up on boot like this and not continue.  What do I need to do to insure this doesn't happen?

[Hrw]

I dont know why you guys have a problem with r21 kernel on collie.

My collie has OZ 3.5.3 installed after it was released, updated with upgrades and I just flashed r21 kernel and started machine. All works ok. No hangs during startup, no Big Red Warning message - just like it has to be.

If I find some time then I will backup whole machine and try to reflash kernel (r21) with opie-image and post results.

[niv]

I dont know why you guys have a problem with r21 kernel on collie.

My collie has OZ 3.5.3 installed after it was released, updated with upgrades and I just flashed r21 kernel and started machine. All works ok. No hangs during startup, no Big Red Warning message - just like it has to be.

If I find some time then I will backup whole machine and try to reflash kernel (r21) with opie-image and post results.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87065\"][{POST_SNAPBACK}][/a][/div]

cool thanks mate

[Wawrzek]

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...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86674\"][{POST_SNAPBACK}][/a][/div]

I've got the same.

SL5500 with zImage-collie-48-16-r21.bin
SanDisk 128Mb
and lates Opie.

[Dan2]

2- flash Hentges rom, and again the suspend problem, but not so frecuently, and now the clock don't reset, but keeps the time where it freezes. I just don't understand. Is there a procedure or configuration to avoid the problem? (its just software I presume).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86992\"][{POST_SNAPBACK}][/a][/div]

I also still saw some freezes (or mostly loss of keyboard use, in which case however even shutdown doesn't work properly anymore, so it really is more than that) with the June 30 kernel and Hentges rom (stock OZ 3.5.3 opie image didn't boot for me as reported by numerous others).

They seem to be network related. After I changed the network settings to not bring usbd0 up automatically, I am no longer seeing freezes while the Zaurus (a 5500G, incidentally) is outside the cradle - have been using it as calendar and etext reader for the past 5 days without needing to reboot even once finally (well until an hour ago when I put it in the cradle for the first time since then).

Putting it in the cradle or removing it from there still causes the known problems, though (but I also notice that the network appearantly reacts to usb dis-/reconnects regardless of what network settings were chosen). Perhaps this info will help a kernel hacker pin down the problem (some kernel/system call not reacting properly to a sudden change of network component availability?)...

Dan

[CoreDump]

2- flash Hentges rom, and again the suspend problem, but not so frecuently, and now the clock don't reset, but keeps the time where it freezes. I just don't understand. Is there a procedure or configuration to avoid the problem? (its just software I presume).
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86992\"][{POST_SNAPBACK}][/a][/div]

I also still saw some freezes (or mostly loss of keyboard use, in which case however even shutdown doesn't work properly anymore, so it really is more than that) with the June 30 kernel and Hentges rom (stock OZ 3.5.3 opie image didn't boot for me as reported by numerous others).
They seem to be network related. After I changed the network settings to not bring usbd0 up automatically, I am no longer seeing freezes while the Zaurus (a 5500G, incidentally) is outside the cradle - have been using it as calendar and etext reader for the past 5 days without needing to reboot even once finally (well until an hour ago when I put it in the cradle for the first time since then).

Putting it in the cradle or removing it from there still causes the known problems, though (but I also notice that the network appearantly reacts to usb dis-/reconnects regardless of what network settings were chosen). Perhaps this info will help a kernel hacker pin down the problem (some kernel/system call not reacting properly to a sudden change of network component availability?)...

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

Does your Z still crash after running

Code: [Select]

/etc/init.d/hotplug stop
and connecting / disconnecting USB?

I'll run some USB tests tonight. Never used the craddle a lot but after messing with USBnet on Akita, I'll give it a try.

Does your USB connection still work after a suspend/resume cycle?

On Akita I'm currently seeing the following behaviour:

- reboot Z
- Connect USB
- usbnet works perfectly
- disconnect USB
- suspend
- resume
- connect USB
- usbnet is b0rked until rebooting.

IIRC this was a problem on Collie as well a while ago. The work-around is unloading the USB modules prior to suspending (works perfectly on Akita).

[tontonrico]

.../...
  I have exactly the same error (keep blocked on the line 'Configuring update modules')  as you but using opie-image-collie-20050407173817.rootfs.jffs2 and zImage-collie-48-16-r21.bin (renamed of course).

.../...

I tried to flash with another r21 kernel (64-0) this is the same problem.

I re-flashed  my Z with the "original" kernel. It boots normally now.

But I would like to use the new kernel !!

[niv]

Collie , 3.5.3 r21 Hentges rom :
I had a freeze without any network what-so-ever