Howto get r21 kernel on collie
Marcin Juszkiewicz July 27th, 2005
Method of upgrading OZ 3.5.3 into r21 kernel:
- install OZ 3.5.3 with default kernel (may be skipped if you already have 3.5.3)
- add upgrades/collie into ipkg.conf
- run
ipkg update;ipkg upgradeto get r21 kernel modules installed - copy r21 kernel from “upgrades/collie” into CF card and flash it (ONLY kernel)
- boot Zaurus and be happy user of OZ 3.5.3 with r21 kernel
That method works for me with plain OZ 3.5.3 (opie-image + 64/0 kernel). To upgrade I used r21 kernel from “upgrades/collie”.
Yeah, it’s working here!
No more suspends while playing! ;)
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
Bill
Yeah, this works on my machine, too.
Little hint if you’re not sure, if the update succeeded:
check /proc/version to see if you’re running the desired kernel.
Thanks for the great work!
after having flashed the old 32-32 kernel & opie on my sl5500, ipkg upgrade didn’t work (”no space left on device” several times).
solution was to flash the old 64-0, do the ipkg update / upgrade & reflash the fixed 32-32.
but as far as i can see i’ve got some cf hotplug problems. there’s no reaction after plugging in some cf-things…sd works.
(i’d love to post that on the forum, but i don’t like to register just for a comment…)
When it will be released the 3.5.4 version of openzaurus?
ok, I’m having a hard time with this. I’ve spent about four hours over the last three nights messing with this, and I’m not getting any closer.
Step 2 says add upgrades/collie into ipkg.conf
I did a fresh install of 3.5.3, 64-0, and used vi to make /etc/ipkg.conf read like this:
src/gz upgrades/collie http://openzaurus.org/official/unstable/3.5.3/upgrades/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 sd /media/card/packages/
When I run ipkg update;ipkg upgrade
I get the error :
Downloading http://openzaurus.org/official/unstable/3.5.3/upgrades/collie//Packages.gz
file_move: ERROR: failed to rename /tmp/ipkg-wU9wrh/Packages.gz to /tmp/ipkg.aSaXLj/upgrades/collie.gz: No such file or directory
Downloading http://openzaurus.org/official/unstable/3.5.3/upgrades//Packages.gz
Inflating http://openzaurus.org/official/unstable/3.5.3/upgrades//Packages.gz
Updated list of available packages in /usr/lib/ipkg/lists/upgrades
Downloading http://openzaurus.org/official/unstable/3.5.3/feed/base//Packages.gz
Inflating http://openzaurus.org/official/unstable/3.5.3/feed/base//Packages.gz
Updated list of available packages in /usr/lib/ipkg/lists/base
Downloading http://openzaurus.org/official/unstable/3.5.3/feed/libs//Packages.gz
Inflating http://openzaurus.org/official/unstable/3.5.3/feed/libs//Packages.gz
Updated list of available packages in /usr/lib/ipkg/lists/libs
Downloading http://openzaurus.org/official/unstable/3.5.3/feed/console/Packages.gz
Inflating http://openzaurus.org/official/unstable/3.5.3/feed/console/Packages.gz
Updated list of available packages in /usr/lib/ipkg/lists/console
Downloading http://openzaurus.org/official/unstable/3.5.3/feed/devel/Packages.gz
Inflating http://openzaurus.org/official/unstable/3.5.3/feed/devel/Packages.gz
Updated list of available packages in /usr/lib/ipkg/lists/devel
Downloading http://openzaurus.org/official/unstable/3.5.3/feed/opie/Packages.gz
Inflating http://openzaurus.org/official/unstable/3.5.3/feed/opie/Packages.gz
Updated list of available packages in /usr/lib/ipkg/lists/opie
An error ocurred, return value: 1.
Collected errors:
Nothing to be done
This sux, and I’m getting irritated. What exactly am I doing wrong? What excatly does the line I’m adding to ipkg.conf read, from start to finish? I’ve tried upgrades/collie and collie with errors on both.
This is on a 5500d, PNY 256MB sd card, with a working Linksys wifi card.
OZ 3.2 was clunky and slow, but at least it worked. Does anyone have the 3.2 feed mirrored? I’d much rather run that.
Upgrading right now, thank you for the kernel and howto :)
Note for 2.: The upgrade works ok with gpe image.
Doesn’t work for me at all.
I only get to the line where it says “Please wait: booting..”
any ideas?
Can someone generate some new initrd images with the newest kernel modules please?
Nice. But a newbie question… how do I flash the kernel only? Does this just mean
no .bin file on the CF card? Does it leave OPIE intact?
I have a couple of questions about this. Will the procedure outlined above work for my SL500 which has dsteens rboot scripts in use to boot from the sd? If not, is there a way to upgrade the kernel without going through the whole script process again?
I followed the indications and now my old Collie is OK with the new r21 kernel.
Thanks HRW !
Full paths please. Not everyone is an expert at openzaurus.
After adding the upgrades/collie feed to /etc/ipkg.conf, make sure you comment out all of the other feeds, otherwise ipkg will attempt to upgrade everything and you will run out of space on /.
Then do the ‘ipkg update && ipkg upgrade’, check for errors; then flash the new kernel, check that it flashed successfully; then you should be good to go.
Worked for me first time using the above instructions.
Si
bennettron, use
src/gz upgrades/collie http://openzaurus.org/official/unstable/3.5.3/upgrades/collie/
Cheers
Philipp
Hmmm,
src/gz upgrades/collie http://openzaurus.org/official/unstable/3.5.3/upgrades/collie/
didn’t work for me but
src/gz upgrades_collie http://openzaurus.org/official/unstable/3.5.3/upgrades/collie/
seemed to, as in it downloaded a bunch of stuff and spent some time configuring modules, but now I can’t find and upgrade directory (find / | grep -i upgrade) with any file to use for zImage.
I think upgrades_collie worked over upgrades/collie because it tried using upgrades/collie in a path and was missing a sub-directory.
Maybe I’ll just reboot and see if /proc/version works… bah, now it’s gone all flakey, won’t turn on… re-flash. So what did I do wrong? Where is the new zImage supposed to appear? Full paths help the great unwashed :-)
Detailing translation of steps:
Step 1: If you’re having problems running 3.5.3, you’ve already done this :P
Step 2: Open /etc/ipkg.cfg, add a line such as:
src/gz upgrades/collie http://openzaurus.org/official/unstable/3.5.3/upgrades/collie/
Comment other src lines to avoid disk space failure(use instructions in ipkg.cfg as an example to comment)
Step 3: Open a command prompt and type: ipkg update;ipkg upgrade
This installs the new kernel and matching modules(modules is why plain swap doesn’t work)
Step 4: Get the kernel image that matches your memory requirements(ie: the r21 kernel for a 32/32 install)
Rename to zImage on a CF card, make sure there is no initrd.bin, and flash as normal(very fast flash compared to a full flash)
This actually makes the kernel change permanent and gives you the proper memory allocation.
Step 5: Try it out.
If I had been thinking, I probably could have figured out that it was module incompatibility(step 3) that was causing failed boots.
Bah!
It works, but there’s a problem with either the CF slot detection or wireless card recognition.
I happen to have a Prism2 chipset wireless card(trendnet TEW-222CF) which has worked, if intermittently on some, with every version of OZ I’ve used(since 3.1.something) except this one(r21) and it doesn’t even see it being plugged in as far as I can tell(usually declares itself as an orinoco.
Nakarti, the reason your Orinoco WiFi card is no longer working is that the orinoco modules (orinoco-modules and orinoco-modules-cs) haven’t been rebuilt for the new kernel (r21). If you look at the output of dmesg, you should see lots of error messages indicating that the modules failed to load.
Nakarti: can you try to get that card working with hostap_cs driver instead of orinoco_cs?
Anyway orinoco-modules are available in “upgrades collie” feed. But first you will need to remove “orinoco-modules*” because names of modules was changed some time ago and I don’t have OZ 3.5.3 enviroment available here.
I’m booting off an SD card, does anything need to be copied to the SD card after the flashing?
for a functional solution >>>
http://www.hentges.net/misc/openzaurus/docs/cardfs_howto.shtml
Nakarti,
I followed your directions to the letter with a 32/32 kernel. At the point I execute ipkg update, I get the follow error:
ERROR: failed to rename /tmp/ipkg-1mMOBt/Packages.gz to /tmp/ipkg/.mj4K7X/upgrades/collie.gz: No such file or directory
The file /tmp/ipgk-1mMOBt/Packages.gz does not exist.
Hmm… It may prove complicated to implement, but I’ll give it a shot.
Especially since my Z doesn’t feel like booting…
Hopefully it will keep the drivers loaded while I upgrade so I don’t lose network when switching the orinocos…
Crap, now it won’t even boot. Flashes fine, just no boot. I think my battery might be bad but it should still start up.
Unable to test at the moment. Anybody have a good hammer suggestion?
I have experienced similar probs to those above but have resolved them. See my Zaurus post on my blog:
http://ccgi.phillips22.free-online.co.uk/wordpress/2005/10/08/5.
In it I gp through the steps I followed for installing 3.5.3, upgrading to r21 collie, and booting from the SD card.
Hope someone finds this useful,
Pete
Even after locating(disassemble Number Five!) and giving some charge to the internal battery(holy crap slow,) AND charging a full day, my zaurus is quite dead(son of a….) although it did start to boot(??) while I had it partly open, so still wondering… WTF?
Any ideas what google search or forum will help me with that?
Dar light goes on but battary haf no volt over 2.7 and the charge light is still on.
Trying to get the ipkg update/upgrade work, but without success. When I’m doing the upgrade, I got the following message:
Assuming locally installed package kernel (2.4.18-rmk7-pxa3-embedix-r18) is up to date.
And a bunch of similar ones for every module installed. And so, nothing upgrades. Why is it?
Just to clarify comment #3 by malte, after upgrading, the build date on your kernel (cat /proc/version) should be equal to that of the new kernel (check the collie/upgrade feed for the correct date).