OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: samac on June 27, 2005, 03:20:27 pm
-
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.
-
This is a warning to ensure that those flashing to the ROM in the first place make sure they get the right kernel.
You can safely ignore it (as you know you've flashed a different kernel). 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).
Si
-
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
-
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.
-
Not for me. Gets stuck forever after the "Please wait while booting..." message (which takes about a minute to come up).
-
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.
Have you given it enough time to pass the sleep message?
I just flashed this new kernel with the 'checkversion' script in place... after a minute (no more) it continued to boot as normal.
I'm not sure why you and TimW are having problems, but I thought I would post that it works fine for me... and it fixes the arrow button problems.
Edit: This kernel has also fixed the on/off button issue that many were experiencing... I wanted to wait at least one hour with the unit off to be sure.
Thanks Hrw!
Greg
-
I'm using Daniel Steen's rboot stuff. Maybe that has something to do with it?
I'm using the 32-0 image for my SL5000D.
(And yes, I did give it enough time - as I said I get the "Please wait while booting..." after the sleep but then no more even after leaving it for 10 minutes).
-
Just a base install of OZ 3.5.3 opie 1.2, flashed fine, but wouldn't go passed the now booting message after sleeping for 60 seconds.
Perhaps you can detail how you flashed your new kernel, and then we can see if we did anything wrong.
Is there a special technique when you are upgrading the kernel, e.g. I didn't know that you could flash without the initrd.bin and therefore leave your current installation and modifications intact.
Of course I found this out after a complete fresh install !!!!
samac
-
I'm using Daniel Steen's rboot stuff. Maybe that has something to do with it?
That could be it. I'm using CoreDump's boot manager, and that still pops up before the checkversion script is used.
Greg
-
Is there a special technique when you are upgrading the kernel, e.g. I didn't know that you could flash without the initrd.bin and therefore leave your current installation and modifications intact.
You use the same technique... but 'only' place the 'zImage' on your CF-card.
Greg
-
Is there a special technique when you are upgrading the kernel, e.g. I didn't know that you could flash without the initrd.bin and therefore leave your current installation and modifications intact.
You use the same technique... but 'only' place the 'zImage' on your CF-card.
Greg
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86309\"][{POST_SNAPBACK}][/a][/div]
That's exactly what I did, on top of a clean install of 3.5.3.
So....... Why did it not work hmmmmm!!!
samac
-
Hi HRW
I just downloaded the new kernel from upgrades to my PC, renamed the file to bzImage, copied it to my CF card and then flashed my SL5500.
The boot froze at Please Wait: booting ...
(calender-c)
The boot froze at Configuring network interfaces ...
(calender-c)
Black screen, no reponses, had to reset with rear switch.
Go up 6 lines.
samac
-
The boot froze at Please Wait: booting ...
(calender-c)
The boot froze at Configuring network interfaces ...
(calender-c)
Black screen, no reponses, had to reset with rear switch.
Go up 6 lines.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86444\"][{POST_SNAPBACK}][/a][/div]
Same here except that I got all the way into opie after the second (calender-c) only to get the freeze when suspending.
-
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
-
er um...
I do the upgrade and the boot keeps in 'Configuring update modules' for more than 10 minutes, so i concluded that it freezed, so I repited the flash procedure and it freezed again.
I have a zaurus sl5500
Using this files to flash:
opie-image-collie-20050407173817.rootfs.jffs2
zImage-collie-32-32-r21.bin
of course, after renamig it to initrd.bin and zImage
-
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
-
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)
-
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)
-
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.
-
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
-
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.
-
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
-
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 (https://www.oesf.org/index.php?title=VI_notes)
-
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.
-
WHAT? the 3.5.2 don't hangs ?
er... I suppose I miss that choice...
RIGHT NOW I'm flashing it
-
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) (http://oz.hentges.net/releases/3.5.3/T2/collie/oz-opie-small-collie_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.
-
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] (http://index.php?act=findpost&pid=86510\")
- 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 (http://www.openzaurus.org/official/unstable/3.5.3/upgrades/zImage-collie-64-0-r21.bin)
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...
-
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
-
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
-
YES!!!!!
got the opie T2 Collie english from hentges (http://www.hentges.net/misc/openzaurus/oz3.5.3-opie1.2.0.shtml) (pretty minimal)
and the new ZImage (http://www.openzaurus.org/official/unstable/3.5.3/upgrades/zImage-collie-64-0-r21.bin)
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..
-
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 (http://oz.hentges.net/releases/3.5.3/T2/collie/cardfs-opie-full-collie-openzaurus_oz3.5.3-opie1.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
-
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
-
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]
-
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).
-
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!
-
Hi,
maybe the reason it works with hentges is, that hentges is using openssh instead of dropbear.
Cheers,
Sam
-
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
-
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?
-
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.
-
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
-
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] (http://index.php?act=findpost&pid=86510\")
- 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 (http://www.openzaurus.org/official/unstable/3.5.3/upgrades/zImage-collie-64-0-r21.bin)
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.
-
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
-
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
/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).
-
.../...
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 !!
-
Collie , 3.5.3 r21 Hentges rom :
I had a freeze without any network what-so-ever
-
I have yet to flash the zImage-collie-64-0-r21.bin and opie-image-collie-20050407173817.rootfs.jffs2 without it hanging at the configuring-modules.
However today I flashed with only the r21.bin and it hung on booting. After Ctrl+C it continued only to hand at starting networking and after another Ctrl+C it continued.
I am unable to start any networking services and will continue to play and troubleshoot for now.
Thanks to the developers for their time and effort.
-
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87065\"][{POST_SNAPBACK}][/a][/div]
HRW and all,
I noticed that in a couple of different cases where users have reported issues, both you and Mickeyl have been unable to reproduce the problem. Since both of you are in Europe, I thought that may be a regional issue (e.g. SL-5500 vs. SL-5500G)...Or it could be related to different manufacturer's chips used in construction or rev levels of internal firmware?
I'm just guessing here, but is it possible? Especially with the broad range of manifestations of the original problems (some had problems even after modifying /etc/device_table, some had few problems leaving device_table unmodified, etc) as well as the range of behavior with the new kernel. I know some of it is configuration options we use (for instance, I am pivoting root to the SD card), etc.
Just a thought,
--Storm
-
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87065\"][{POST_SNAPBACK}][/a][/div]
HRW and all,
I noticed that in a couple of different cases where users have reported issues, both you and Mickeyl have been unable to reproduce the problem. Since both of you are in Europe, I thought that may be a regional issue (e.g. SL-5500 vs. SL-5500G)...Or it could be related to different manufacturer's chips used in construction or rev levels of internal firmware?
I'm just guessing here, but is it possible? Especially with the broad range of manifestations of the original problems (some had problems even after modifying /etc/device_table, some had few problems leaving device_table unmodified, etc) as well as the range of behavior with the new kernel. I know some of it is configuration options we use (for instance, I am pivoting root to the SD card), etc.
Just a thought,
--Storm
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87167\"][{POST_SNAPBACK}][/a][/div]
I've had the same problem with my collie (SL-5500) bought from the UK. I'm also pivoting root to the SD card - if that's any help.
-
Hmmmm...
Anyoune with a SL-5000D who can confirm that I'm not the only one that has
a zaurus that has the suspend/resume issues even with the new kernel?
Greetings,
Andreas
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
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86676\"][{POST_SNAPBACK}][/a][/div]
-
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]
I know well that this situation is very frustrating...
The worst thing for a developer is a software that works fine on his system but not on other systems.
So I have a proposal, Hrw could release a new zImage with a "verbose debug" mode on, something that could print out useful informations to understand the problem.
I have studied linux kernel this year, but I'm not a kernel hacker, and I have buyed my Z recently, so I can't give a big help... but I (and I think everyone here) would give an help to solve this problem, also just testing if this is useful.
My nights are at OZ disposal
-
Hi,
I have a 5500 that is not working with the new kernel.
I did a compare between the working and not working kernels. I did an lsmod after booting using calender-C to get me through the new kernel boot. What I found was that there was no usbcore, net_fd and sa1100_bi, also ipv6 and ipsec show up as initialising on the new kernel. As the working kernel show net_fd and sa1100_bi as using usbdcore I assume that the loading of usbdcore is a candidate for the problems we are seeing. I am guessing that the boot hang after 2 lines is because of the inability to load usbcore or the calender-C is preventing the usbcore module load.
Does this get us any further?
I also did a compare of dmesg outputs, but the amount of information means the stuff from the start of the boot on the new kernel is missing. The dmesg buffer gets filled with a load of exception/crash information. Is there a way to extend the dmesg buffer?
Cheers,
Colin
-
Is there a way to extend the dmesg buffer?
quoting dmesg man
SYNOPSIS
dmesg [ -c ] [ -n level ] [ -s bufsize ]
....
-sbufsize
Use a buffer of size bufsize to query the kernel ring buffer. This is 16392 by default. (The
default kernel syslog buffer size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.) If
you have set the kernel buffer to be larger than the default then this option can be used to view
the entire buffer.
I hope this could help you.
-
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] (http://index.php?act=findpost&pid=86510\")
- 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 (http://www.openzaurus.org/official/unstable/3.5.3/upgrades/zImage-collie-64-0-r21.bin)
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87092\"][{POST_SNAPBACK}][/a][/div]
Same problem here.
SL-5500
Sandisk 1 GB
zImage-collie-48-16-r21
opie image
-
Success.
After using Hentges http://www.hentges.net/misc/openzaurus/oz3...opie1.2.0.shtml (http://www.hentges.net/misc/openzaurus/oz3.5.3-opie1.2.0.shtml) with OpenZaurus .r21 zImage, it boots and works faster than ever, thanks to cardfs.
The suspend resume issue is resolved. Battery life is much more realistic.
-
I did a compare between the working and not working kernels. I did an lsmod after booting using calender-C to get me through the new kernel boot. What I found was that there was no usbcore, net_fd and sa1100_bi, also ipv6 and ipsec show up as initialising on the new kernel. As the working kernel show net_fd and sa1100_bi as using usbdcore I assume that the loading of usbdcore is a candidate for the problems we are seeing. I am guessing that the boot hang after 2 lines is because of the inability to load usbcore or the calender-C is preventing the usbcore module load.
What error is returned when you try to modprobe net_fd?
Si
-
I am having the exact same problem. I've just installed a brand new OZ 3.5.3 using the default opie-64-0 zImage and the initrd.bin.
Then to upgrade the kernel, i downloaded the zImage-collie-64-0-2..> kernel from the upgrades/ area.
I then removed everything from the CF card and copied the zImage-collie-64-0-2 file to the root directory as zImage so that only the zImage was on it.
I've also tried with both the new zImage and the initrd.bin file on the CF but this produced the problems quoted below.
What am i doing wrong?
er um...
I do the upgrade and the boot keeps in 'Configuring update modules' for more than 10 minutes, so i concluded that it freezed, so I repited the flash procedure and it freezed again.
I have a zaurus sl5500
Using this files to flash:
opie-image-collie-20050407173817.rootfs.jffs2
zImage-collie-32-32-r21.bin
of course, after renamig it to initrd.bin and zImage
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86459\"][{POST_SNAPBACK}][/a][/div]
-
Sucess ish....
Collie with Hentges ROM and brandnew super kernel !
Seems a bit quicker and yipee I can scroll right...
Alas I seem to now have a different problem, now the Z does not seem to want to suspend via the cancel key and takes several attempts to suspend...
Then my darling little collie decides to be pedantic about turning back on, and seems to save those extra keystrokes to turn itself off.. So when I turning the Z back on it turns itself off.. GAH!
So at the moment I am swearing at the damn thing to suspend and then when I turn it back on the blasted thing turns itself off (usually twice) before resuming operations again
I think the naming of the models after dogs is very appropiate, sometimes I think it does thinks because it wants attention, othertimes I think it is because it wants to go warwalkies instead of browsing the net
Loving the work of the OZ team It is a fantastic platform
-
Does your Z still crash after running
/etc/init.d/hotplug stop
and connecting / disconnecting USB?
Yes, it still did (crash, that is), however manually unloading the networking modules including usbdcore (one test where I only unloaded the two modules depending on it, but not this module itself produced the usual crash after the next suspend) before removing the Z from the cradle seems to do the trick (but I could only repeat the test twice due to lack of time), thanks for the hint. And yes, after putting the Z back in the cradle, the USB connection works again even after suspend/resume.
Your description of the Akita problems actually pretty well matches what I saw on my Collie the past few days...
Dan
-
I've just finished testing USB on my Collie.
It's running a not-yet-released RC of the Hentges ROM and a custom kernel fixing the
annoying "suspend on right-arrow" bug.
USB and USBNet work perfectly fine w/o any tweaks, even after a suspend/resume cycle.
I didn't experience any freezes / crashes.
-
OK how many people are having this issue? It's obvious that this isn't going to be something easy to fix since most of the people having the problem aren't developers and the developers have working machines and probably a lack of time.
So I guess my question is, would this be a problem that developers would be willing to give priority to if there was a "bounty" of sorts offered, and if so are people willing to contribute or pledge to the bounty? If so how much do we need to raise.?
Since the sharp ROM is essentially crap, and there isn't any acceptable commercial ROM (at least that i'm aware of), so i think most of us are basically relying on OZ to become stable in order for the 5500 to actually be "useful" and not just a hunk of junk.
-
I've just finished testing USB on my Collie.
It's running a not-yet-released RC of the Hentges ROM and a custom kernel fixing the
annoying "suspend on right-arrow" bug.
USB and USBNet work perfectly fine w/o any tweaks, even after a suspend/resume cycle.
I didn't experience any freezes / crashes.
OK sounds too good to be true. Give us the details, just the usual suspects, how, who, where, what, when.
Where do we get the RC Rom?
How to install?
etc....
I would think of other questions but am too far into a bottle of 12year old single Speyside for that.
Samac
-
I've just finished testing USB on my Collie.
It's running a not-yet-released RC of the Hentges ROM and a custom kernel fixing the
annoying "suspend on right-arrow" bug.
USB and USBNet work perfectly fine w/o any tweaks, even after a suspend/resume cycle.
I didn't experience any freezes / crashes.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87393\"][{POST_SNAPBACK}][/a][/div]
You got my hopes up then, but it's not on your site as a release candidate yet.
The Kernel upgrade seems to cause more problems than it solved so I'm going back to pure hentges without the new kernel. It works so well that I've forgotten why I used to use the cancel key to suspend, and I suspect that the right scroll issue would only be a big problem if you play na lot of games, which I don't.
Thanks CoreDump your rom has restored my Collie to my affections.
Chas
-
RE: RC Image
I need to clarify a few things:
- The unreleased RC is to 99% identical with the lastest available release, there
were only changes to the altboot bootmanager IIRC.
- The kernel is probably not the kernel available from oz.org. Someone in IRC (sorry, forgot the nick) was debugging the "suspend on right-arrow" bug and I was testing the changes on my Collie and pushed the patch into OE. Using Cancel still crashes the Z during resume with this kernel. As I'm currently "Offline" at home, I really have no idea what sort of fixes the new OZ.org kernel includes. I'd have tested it if I could, but I can't.
Rest asured, once my inet @home is running, I'll release a new RC including a new Collie kernel. Might take another weel or so, though
You got my hopes up then, but it's not on your site as a release candidate yet.
The Kernel upgrade seems to cause more problems than it solved so I'm going back to pure hentges without the new kernel. It works so well that I've forgotten why I used to use the cancel key to suspend, and I suspect that the right scroll issue would only be a big problem if you play na lot of games, which I don't.
Thanks CoreDump your rom has restored my Collie to my affections.
Chas
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87505\"][{POST_SNAPBACK}][/a][/div]
You're very welcome
-
Update News for 5000D (and probably 5500):
as I reported, the kernel in the upgrade feed didn't solve the problem on SL-5000D for me.
That was the reason that I started to dig into the kernel and the oe build system.
At the moment, I've got a kernel that is working for me. First thing I found was/is a bug/issue
with open embedded: I think that the kernel config file for the 5000D has not the correct
config option set: CONFIG_COLLIE_DEV is not set. Setting this resulted in a kernel that worked.
Playing with this kernel, I found that resuming with the "Cancel" button worked only once (most
times), after another suspend the Z didn't wake up again. Is this the same with 5500 Z's?
Well, I digged into the code and patched it at the apm code. Now it seems to work.
I will do some more testing and tweaking until I will post this patch.
If anyone is interested, please contact me.
Hope this is helpful for anyone,
Andreas
-
The latest collie kernel in 3.5.3 upgrades does not boot. It flashs however boot hangs on the second boot line. I tried the cycle twice of installing the upgrade and then re-installing the origenal. Each time the upgrade failed and each time the origenal rebooted.
Is there a fix for this? Has anyone else seen this?
Thanks,
Dan
-
As far as I understand, the r21 does not work with GPE. It does work with Opie.
but I'm not sure...
I offered $25 for a bootable working 3.5.3 kernel for the SL-5500.
Let me revise the offer(I'll honor the previous one it's in some past post).
I'll give $35 for a kernel that does the following -
1- boots with the stock 3.5.3 Opie and GPE images(this can be relaxed if you provide a new GPE image to go with the new kernel
2- right arrow(and other keys) do NOT suspend the machine if you hold them down
3- the "Cancel"/Off button works: ie it
3a- suspends the machine if it's awake
3b- resumes the machine if it's suspended
(where suspend = doesn't drain the battery too fast)
4- the machine autosuspends: ie if you leave it on it'll shut itself off
5- suspend from the menu works
6- I'd really like the buzzer as dsp code to be compiled in also, how about $40 if you get that in there too
Originally I had kinda directed my offer to hrw but I'll pay anyone. Gotta work on an SL-5500.
Paypal or any method you like(that's safe for me).
Bill
bsaunder2002 at some yahoo server thats in the com domain
-
View your personal message for a offer from me. Perhaps I can help you...
Cheers,
Andreas
As far as I understand, the r21 does not work with GPE. It does work with Opie.
but I'm not sure...
I offered $25 for a bootable working 3.5.3 kernel for the SL-5500.
Let me revise the offer(I'll honor the previous one it's in some past post).
I'll give $35 for a kernel that does the following -
1- boots with the stock 3.5.3 Opie and GPE images(this can be relaxed if you provide a new GPE image to go with the new kernel
2- right arrow(and other keys) do NOT suspend the machine if you hold them down
3- the "Cancel"/Off button works: ie it
3a- suspends the machine if it's awake
3b- resumes the machine if it's suspended
(where suspend = doesn't drain the battery too fast)
4- the machine autosuspends: ie if you leave it on it'll shut itself off
5- suspend from the menu works
6- I'd really like the buzzer as dsp code to be compiled in also, how about $40 if you get that in there too
Originally I had kinda directed my offer to hrw but I'll pay anyone. Gotta work on an SL-5500.
Paypal or any method you like(that's safe for me).
Bill
bsaunder2002 at some yahoo server thats in the com domain
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88076\"][{POST_SNAPBACK}][/a][/div]
-
The latest collie kernel in 3.5.3 upgrades does not boot. It flashs however boot hangs on the second boot line. I tried the cycle twice of installing the upgrade and then re-installing the origenal. Each time the upgrade failed and each time the origenal rebooted.
Is there a fix for this? Has anyone else seen this?
Thanks,
Dan
[div align=\"right\"][a href=\"index.php?act=findpost&pid=87607\"][{POST_SNAPBACK}][/a][/div]
Dan,
I don't know of a fix, but I've had a similar - if not an identical - experience.
I was basically happy with the way I'd set up my SL-5500, so I copied the new (r21) zImage file to zImage on the root of a CF card that I've flashed from in the past. I did not place an initrd.bin file there. I flashed, but the boot hung on the second line.
No amount of patience (or keyboard intervention) made any difference, and eventually I flashed back to the older 3.5.3 kernel (the one with the power issues). At least my configuration and RAM-data survived this little experiment.
If you find a solution, let me know.
-
I don't know of a fix for uprading your kernel but if your willing to install from scratch......
I was seeing the same problems: Suspend wasn't working and I had the holding right problem with the stock openzauris zImage and the opie initrd.bin. I tried upgrading to the new openzaurus r21 kernel and had the hang on boot issues. Actually I could press Calander-C a couple of times to kill various things that were hanging the boot process but several essential things don't get loaded if you do this. Even a fresh install with the stock opie initrd.bin and any of the upgrade r21 kernels hangs the boot process too.
The fix for me was to uses the hentges initrd.bin with the openzaurus r21 upgrade kernel. The hentgres kernel still has the suspend issues but his inird.bin will boot the upgrade r21 kernel. The only issue I had was there is a version mismatch warning. Just Calander-C past this warning and modify /etc/init.d/checkversion.
The 'if' line should read:
if [ "2.4.18-rmk7-pxa3-embedix-3.5.3" != "$found" ] ; then
I don't think anyone can make the stock initrd.bin(s) and the upgrade kernel work without modifing the software installed by the initrd.bin. The openzaurus stuff probably just needs to have everything freshly built but that probably won't happen till 3.5.4.
-
Well l0nst3r provided a kernel that works for me.
- right arrow button doesnt suspend
- boots stock GPE initrd
- suspends and resumes from on/off key
Unfortunately it appears to be the 32/32 memory config. He went on vacation and wont be back till August so we'll have to wait for the 64/0 version then.
Other things that aren't resolved
- autosuspend when idle - but since the software suspend works it is probably a problem with GPE
- buzzer as dsp - supposedly there's an issue with the apm so this wasnt compiled in
Other than the memory config problem, this is a "functional" kernel for my sl-5500.
He mentioned trying to get this(and the other mem configs) posted in the feed. He said I could mail the kernel to anyone who wanted it.
I'm paying him the $35 I promised, waiting for him to get a 64/0 kernel compiled, and attempting to figure out the autosuspend when idle issue.
Bill
-
- autosuspend when idle - but since the software suspend works it is probably a problem with GPE
ipaq-sleep may need tweaking to work on Collie. I imagine you also don't have backlight control. Drop me a line and we'll see what we can do about sorting that out (I have implemented backlight control for the 2.6 kernel machines - as a shell script though - it needs to be turned into C to allow the other machines to work too).
Si
-
Regarding backlight control:
(again stock 3.5.3 GPE with l0nst3r's 32/32 kernel)
Just powered up from suspend to test(hadn't powered up for a day or so)
- system unsuspended but backlight stayed off (only on first suspend, subsequent sus/resumes turned the backlight on on resume
- touching the screen(anywhere) turned backlight on full(i think full)
- touching the light bulb in the toolbar, backlight off, scroll bar above the light bulb, - scroll bar works
- try this several times, always backlight off first but then resettable, sometimes the scrollbar is set it the upper left corner of the screen(away from light bulb)
- backlight state seems to be remembered between susp/resume
Bill
- autosuspend when idle - but since the software suspend works it is probably a problem with GPE
ipaq-sleep may need tweaking to work on Collie. I imagine you also don't have backlight control. Drop me a line and we'll see what we can do about sorting that out (I have implemented backlight control for the 2.6 kernel machines - as a shell script though - it needs to be turned into C to allow the other machines to work too).
Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88754\"][{POST_SNAPBACK}][/a][/div]
-
QUOTE(llarensj @ Jun 30 2005, 03:09 PM)
er um...
I do the upgrade and the boot keeps in 'Configuring update modules' for more than 10 minutes, so i concluded that it freezed, so I repited the flash procedure and it freezed again.
I have a zaurus sl5500
Using this files to flash:
opie-image-collie-20050407173817.rootfs.jffs2
zImage-collie-32-32-r21.bin
of course, after renamig it to initrd.bin and zImage
I'm having the same problem also. It will not proceed past update modules.
This is on a brand new sl5500, with the zImage 64-0.
Thank you.
-
QUOTE(llarensj @ Jun 30 2005, 03:09 PM)
I'm having the same problem also. It will not proceed past update modules.
This is on a brand new sl5500, with the zImage 64-0.
Thank you.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88769\"][{POST_SNAPBACK}][/a][/div]
And if you don't reset it halfway, but wait for, say an hour?
-
koen,
Not sure if you were asking specific to a particular initrd(opie or gpe), but...
with the stock GPE initrd, the r21 NEVER completes booting.
I retested just to be sure by:
- removing l0n3star's working 32/32 kernel(works with GPE)
- reflashing both the 64/0 r21 kernel and the stock 3.5.3 GPE initrd
=> all lights work fine, boot fails
It hangs at the GPE banner screen and never goes forward. About every 10 minutes(guessing) it suspends, pressing the On/Off instantly resumes unfortunately back to the GPE banner screen...
I've been "unsuspending" it over and over for the last 4 hours...still the GPE banner.
(GPE banner = not booted as far as I can tell, with lonestars and the stock kernel, I'd get kernel messages and eventually a login screen...r21 dont do that)
It only takes about 5 minutes to test this. Would someone with authority test this and update the posting on the main www.openzaurus.org site. R21 is NOT working on my sl-5500 with GPE...(and it appears only to hobble along with opie).
pps- calendar c/ calendar x/fn c/fn x do nothing when it's hung at the GPE banner...
Bill
pppps- people please read the entire thread before posting, it's not that long, and you'll discover - by george it don't work - then you wont want to post - "guess what it doesnt work for me" we know it wont work for you! Build a new kernel and post "I've got a new kernel, and it works for me, please test it"
(yes I make that statement - I'm paying lonestar $35 for his working kernel that he gave me...hopefully when he gets back mid august he'll compile a 64/0 version...hopefully someone else would do that before but...)
pppppps- if you want the 32/32 kernel that works(yeah boots and sus/resumes) with stock GPE initrd then email me or tell me where to put it. lonestar said I could give it away...
(pppppppps- want my email addr? read the thread it's in there)
ppppppppps- don't panic, have a nice day
QUOTE(llarensj @ Jun 30 2005, 03:09 PM)
I'm having the same problem also. It will not proceed past update modules.
This is on a brand new sl5500, with the zImage 64-0.
Thank you.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88769\"][{POST_SNAPBACK}][/a][/div]
And if you don't reset it halfway, but wait for, say an hour?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88813\"][{POST_SNAPBACK}][/a][/div]
-
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!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=86992\"][{POST_SNAPBACK}][/a][/div]
You can use Qtopia 1.7, a free download, to sync. I use it wirelessly to sync with the opie PIM and Outlook.
-
http://openzaurus.org/wordpress/2005/07/27...rnel-on-collie/ (http://openzaurus.org/wordpress/2005/07/27/howto-get-r21-kernel-on-collie/)
-
It appears that the 64/0 r21 kernel does NOT work with the stock GPE initrd.
Any ideas?
Bill
-
Did you upgrade the kernel modules as specified in hrw's link to oz.org?
Si
-
I posted this on the main page and forgot to post it here...
Yep I upgraded the modules at least did a "ipkg upgrade"...
here's the long story...
This kernel does not seem to work for GPE…
I did the following:
- reflashed 3.5.3 stock gpe and kernel
- booted, configured USB, setup upgrades(+ all other) feed on my laptop
- ipkg update
- ipkg upgrade
both of these appeared to work fine
- deleted all files off of my CF
- copied zImage-collie-64-0-r21.bin to my CF as zImage
- reflashed
- rebooted
=> this leaves me with the GPE banner screen and does NOT boot
the system does not respond to fn-c or calendar-c
Does anyone have any suggestions for gpe?
oh how I wish opie ran on dietX11
-
ok, I now have a working kernel.
l0nst3r compiled a 64/0 SL-5500 kernel for me that works with the stock gpe initrd.bin, doesn't have the right arrow suspend bug, and seems to suspend/resume almost perfectly...
If someone figured out how to get r21 working with the gpe initrd then please let me know.
Otherwise, if you wanna gpe with 3.5.3 and not have a lot of bugs...I have the kernel for you. I'll post it somewhere if someone lets me know where...somehow.
Bill
-
Aaargh, I'm sure I posted somewhere saying that I'd get 'round to upgrading, but I can't for the life of me find that post.
Anyway, I upgraded my collie to 3.5.3 and saw the suspend issue, then I added the upgrades/collie feed as a new feed, commented out all of the others (to ensure that only the kernel modules would be upgraded), did 'ipkg update && ipkg upgrade', flashed the new kernel and it all works perfectly.
That was with an opie image, I'll grab a GPE image and see how that goes next,
Anyway, this is just a post to say that it does work ,
Si
-
I am trying to get rid of suspend issues that have started to occur after installing OZ 3.5.3 on my SL-5500. Using 64-0 config, with /home and /opt pointing to /media/card/home and /media/card/opt respectively.
Trying to fix:
1. Sometimes, Z resumes, but keyboard freezes. Am not able to suspend / shutdown Z. An attempt to do so freezes the PDA.
2. Upon semi-hard reboot (Change battery / Normal Operation), Z comes up, but loses date information. Everything gets reset to Aug 8th 2005, 8 am (or something like that)
Issue Synopsis: Flashing seems to do nothing. The kernel version still remains the same.
Details:
Following instructions from http://openzaurus.org/wordpress/2005/07/27...rnel-on-collie/ (http://openzaurus.org/wordpress/2005/07/27/howto-get-r21-kernel-on-collie/) Here is the exact set of steps I followed:
add upgrades/collie into ipkg.conf
run ipkg update;ipkg upgrade to get r21 kernel modules installed
root@collie:/media/card/home/root# cat /etc/ipkg.conf
(.... comments sniped ....)
src/gz kernel http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/
src/gz machine http://www.openzaurus.org/official/unstable/3.5.3/feed/machine/collie
src/gz upgrades http://openzaurus.org/official/unstable/3.5.3/upgrades/
src/gz base http://openzaurus.org/official/unstable/3.5.3/feed/base/
src/gz libs http://openzaurus.org/official/unstable/3.5.3/feed/libs/
src/gz console http://openzaurus.org/official/unstable/3.5.3/feed/console
src/gz devel http://openzaurus.org/official/unstable/3.5.3/feed/devel
src/gz opie http://openzaurus.org/official/unstable/3.5.3/feed/opie
dest root /
dest cf /media/cf/packages/
dest sd /media/card/packages/
dest ram /media/ram/packages/
root@collie:/media/card/home/root# ipkg update
(.... snip ....)
root@collie:/media/card/home/root# ipkg upgrade
(.... snip ....)
copy r21 kernel from “upgrades/collie†into CF card and flash it (ONLY kernel)
agautam@GentooDesktop ~/OZ/3.5.3 $ wget http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/zImage-collie-64-0-r21.bin
(.... snip ....)
11:13:59 (242.50 KB/s) - `zImage-collie-64-0-r21.bin' saved [911,468/911,468]
agautam@GentooDesktop ~/OZ/3.5.3 $ wget http://www.openzaurus.org/official/unstable/3.5.3/upgrades/collie/zImage-collie-64-0-r21.bin.md5
(.... snip ....)
11:14:05 (595.70 KB/s) - `zImage-collie-64-0-r21.bin.md5' saved [61/61]
agautam@GentooDesktop ~/OZ/3.5.3 $ cp zImage-collie-64-0-r21.bin zImage
agautam@GentooDesktop ~/OZ/3.5.3 $ md5sum zImage
e179cc1991729d931f47d8031843aa0a zImage
agautam@GentooDesktop ~/OZ/3.5.3 $ cat zImage-collie-64-0-r21.bin.md5
e179cc1991729d931f47d8031843aa0a zImage-collie-64-0-r21.bin
agautam@GentooDesktop ~/OZ/3.5.3 $ scp zImage root@collie:/media/cf
Heres my flashing procedure:
1. Make sure that the only file I have on CF card is zImage
2. Make sure the CF card is FAT
3. shutdown collie
4. Switch mode to "Change Battery"
5. Remove battery cover.
6. Make sure power is connected
7. Press C D and the internal battery reset button.
.... Both the mail and battery lights light up
.... After approx 10 seconds (I timed it), they both switch off
8. Press the internal battery reset button.
9. Place battery cover back
10. Switch to "Normal Operation"
11. Press and hold Cancel button for a second and release
.... observe collie start ...
After collie starts up, I try to verify the kernel version:
root@collie:/media/card/home/root# cat /proc/version
Linux version 2.4.18-rmk7-pxa3-embedix-3.5.3 (hrw@home) (gcc version 2.95.3 20010315 (release)) #1 Thu, 30 Jun 2005 11:18:23 +0200
root@collie:/media/card/home/root# uname -a
Linux collie 2.4.18-rmk7-pxa3-embedix #1 Thu, 30 Jun 2005 11:18:23 +0200 armv4l unknown
boot Zaurus and be happy user of OZ 3.5.3 with r21 kernel
Would love to be one :)
Any ideas / tips to get the kernel upgraded would be greatly appreciated.
Thanks
Ajay
()
-
After collie starts up, I try to verify the kernel version:
root@collie:/media/card/home/root# cat /proc/version
Linux version 2.4.18-rmk7-pxa3-embedix-3.5.3 (hrw@home) (gcc version 2.95.3 20010315 (release)) #1 Thu, 30 Jun 2005 11:18:23 +0200
root@collie:/media/card/home/root# uname -a
Linux collie 2.4.18-rmk7-pxa3-embedix #1 Thu, 30 Jun 2005 11:18:23 +0200 armv4l unknown
Any ideas / tips to get the kernel upgraded would be greatly appreciated.
Look again into upgrades/collie directory and show WHEN I build r21 kernel. Then look again into /proc/version and compare both dates.
And next time use proper thread - I will move both posts to correct one.
-
Thanks for the reply hrw. Appreciated.
Look again into upgrades/collie directory and show WHEN I build r21 kernel. Then look again into /proc/version and compare both dates.
umm... not sure if I understand what you mean. What to look for in upgrades/collie? I can see the new kernel modules and other packages. These got upgraded when with ipkg upgrade.
I do see that the date /proc/version shows, and the timestamp on the r21 kernel at upgrades/collie are the same (june 30, 05). Is that what you meant for me to check?
Do the timestamps being same indicate that the upgrade was sucessful?
And next time use proper thread - I will move both posts to correct one.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=94891\"][{POST_SNAPBACK}][/a][/div]
In my defense... I did read this thread before posting, but didn't really find much discussion about r21 kernel, so I posted a new post.
Anyway, coming back to the topic...
If the timestamps show that the kernel was infact upgraded, what should I do about the suspend issues that I am facing (relisted below) ? Any pointers would be greatly appreciated.
Trying to fix:
1. Sometimes, Z resumes, but keyboard freezes. Am not able to suspend / shutdown Z. An attempt to do so freezes the PDA.
2. Upon semi-hard reboot (Change battery / Normal Operation), Z comes up, but loses date information. Everything gets reset to Aug 8th 2005, 8 am (or something like that)
Thanks
Ajay
-
1. it's not APM problem but usbnet related modules "sa1100_bi net_fd usbdcore" are loaded in wrong order - blame Sharp/Lineo
2. rm /etc/timestamp IIRC - collie has RTC, PXA based zauruses does not
-
1. it's not APM problem but usbnet related modules "sa1100_bi net_fd usbdcore" are loaded in wrong order - blame Sharp/Lineo
[div align=\"right\"][a href=\"index.php?act=findpost&pid=95165\"][{POST_SNAPBACK}][/a][/div]
What is the correct order?
Can I insmod them in the correct order?
Here is the current order:
root@collie:/media/card/Documents/text# lsmod
Module Size Used by Tainted: PF
sa1100_bi 22924 0 (unused)
net_fd 16636 1
usbdcore 22504 0 [sa1100_bi net_fd]
usbdmonitor 5448 0 (autoclean)
kbdsim 1216 0
sharp_mmcsd_m 25792 2
rfcomm 33512 0
l2cap 17316 2 [rfcomm]
bluez 32632 1 [rfcomm l2cap]
ipv6 152344 -1
ipsec 280008 0 (unused)
2. rm /etc/timestamp IIRC - collie has RTC, PXA based zauruses does not
[div align=\"right\"][a href=\"index.php?act=findpost&pid=95165\"][{POST_SNAPBACK}][/a][/div]
Thanks
Ajay
-
usbdcore
net_fd
sa1100_bi
By default it should work via simple "modprobe sa1100_bi" but this require normal modprobe or patched busybox - I don't remember what was on collie with OZ 3.5.3 but remember that my collie flashed with 3.5.3 had it working.
-
Hi HRW,
the upgrade worked twice for me, but each time after the upgrade my CF-WLan card stops working!!??!!
The syslog says:
Unable to handle kernel paging request at virtual adress 000e0031
It is an TrendNet TEW-222CF (works normally as Orinoco)
It worked before, as I did the upgrade with it.
Any Ideas
TIA
robbb
-
robbb: remove "orinoco-modules*" and install newer ones from upgrades collie (http://openzaurus.org/official/unstable/3.5.3/upgrades/collie/) feed. I hope that they will work.
I forgot about them - I rebuilded hostap-modules because I have prism2 based card so it was easy to catch that something does not work. Sorry.
-
Thanx HRW,
finally working for me!!