OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: masterzen on November 02, 2004, 11:06:43 am
-
Hi all,
I am a complete newbie about Zaurus (but quite knowlegeable regarding linux/unix stuff).
I just got a SL-5600 last week, and managed to install OZ3.5.1 quite easily (after reading this forum).
I've read somewhere on ZUG, that the OZ kernel are compiled with the Cache Errata setting, and I wanted to test without it to see if that works, as a lot of people seems to run it without any problems.
So I installed OE, and managed to compile a new kernel without this setting.
BTW, OE is really nice, it built everything for me, including the toolchain !
Now, the question is how can I flash my new kernel in my zaurus without erasing completely my flash (which contains some applications and some of my data) ?
At least is it possible ?
Maybe I should generate a custom rootfs containing my stuff ?
I noticed in the kernel and the System.map resides in /boot (like any traditional non embedded linux), but I doubt replacing those files with the ones I compiled will work, right ?
Another question, related to the kernel.
I tried opie-camera and sharp-camera-support from the feed and upgrades, but I always get a kernel oops in the sharpzdc_cs module (and opie-camera then segfaults).
Do anyone have a ksymoops package for the zaurus or should I try to cross compile one, so that I can provide anyone interested more information ?
Is it possible to use the camera with OZ3.5.1 (the thing worked fine with the default sharp ROM).
-
Hello,
First, as to the data. It is relativly easy to save PIM data with an SD or CF card. Using Backup and Restore set the destination to SD (or CF) and perform a 'backup'. After the re-flash perform a 'restore'.
There was a bug in 'opie-camera' that is fixed in the 'upgrades' feed. (This name changed, it is the alternate feed and contains fixes)
Dan
-
Yes you can flash the kernel without flashing/erasing the filesystem, however it probably depends on what the particular installer.sh which you use decides to do - whether it automatically clears the user partition (I don't think it does as I've seen people talking about having stuff left over from their last ROM, but do back-up your stuff just in case)
Basically just don't put an initrd.bin file (the filesystem) on the CF/SD card and proceed as normal with just the zImage.bin (kernel) and installer.sh.
Edit: The kernel should be named zImage (without the .bin) for the 5600.
Obviously if you were to flash a different kernel version then you'd have to prepare by installing the appropriate modules before doing the flash, but in this case you'll be fine.
Si
-
I believe the correct filename is zImage rather than zImage.bin...
z.
-
Check out the ozone script (sorry, I don't have an url right now, but google should find it). It clones your Z as it is, and then you can reflash with the exact image+software you have right now and a kernel of your choice. Great for backup and testing as well!
Cheers
Philipp
-
Check out the ozone script (sorry, I don't have an url right now, but google should find it).
Every link I find resolve to the authors site which unfortunately does not exist anymore
Can someone point me to a site that actually host the file ?
Or better if someone could send it to me
-
Basically just don't put an initrd.bin file (the filesystem) on the CF/SD card and proceed as normal with just the zImage.bin (kernel) and installer.sh.
After decoding and reading the OZ updater.sh, it seems that if you don't provide the initrd.bin file, your MTD root partition won't be erased.
I'll try that (but I'd prefer to find the ozone script first )
-
There was a bug in 'opie-camera' that is fixed in the 'upgrades' feed. (This name changed, it is the alternate feed and contains fixes)
It seems I have the last version (opie-camera from feed and sharp-camera-support from upgrades).
Maybe I should build the package from oe as there might be a new version ?
-
Uhh, yeah, now THAT's a sad thing... You can download it at http://www.pipsfrank.de/public_files/ozone.tar.gz (http://www.pipsfrank.de/public_files/ozone.tar.gz) . Note that this version (its 0.11) has a small bug in it, related to the IP of the Z itself, which is in one place hardcoded in the script, but should be $Z_IP, which is defined in ozone_config. Just try it out, if you get strange error messages, you know where to look. It works for me anyway, though my Z doesn't have a standard IP, so I really don't know if it matters. If you have problems, ask
Cheer
Philipp
Edit: I looked through my version, and can't find that bug, so maybe I fixed it by hand...
-
There was a bug in 'opie-camera' that is fixed in the 'upgrades' feed. (This name changed, it is the alternate feed and contains fixes)
Umm. I'm sorry, I don't follow that. What[/] "alternate feed".
Windrose
-
Uhh, yeah, now THAT's a sad thing... You can download it at http://www.pipsfrank.de/public_files/ozone.tar.gz (http://www.pipsfrank.de/public_files/ozone.tar.gz) .
Many thanks,
Do you know if this version works with a SL-5600 ?
The author admits in the README that he never tested on this zaurus.
Thanks,
Brice
-
I believe the correct filename is zImage rather than zImage.bin...
z.
You're right, my apologies for the confusion; I don't have a 5600 so was just going from what I have to do with my 750.
Si
-
Basically just don't put an initrd.bin file (the filesystem) on the CF/SD card and proceed as normal with just the zImage.bin (kernel) and installer.sh.
Edit: The kernel should be named zImage (without the .bin) for the 5600.
Si
The upgrade went fine, but unfortunately, when booting the OZ kernel has panic'ed with something like:
VFS: can't find rootfs...
Analysis of the previous message showed that the kernel seems to partition the MTD while booting after an upgrade (maybe because the size of the kernel changed ?).
I have to look to the kernel's code...
-
masterzen, sorry, I don't know if it works with a 5600, I have a 5500. But if you find out, well, let us know
Cheers
Philipp
-
masterzen, sorry, I don't know if it works with a 5600, I have a 5500. But if you find out, well, let us know
Unfortunately it does not seem to work.
It produces an initrd, the initrd can be flashed, but the kernel won't boot...
-
Uuhhh, that's what you meant above. Sorry to hear that, it's such a useful thing... maybe there's someone around who can debug it?
Cheers
Philipp