Help - Search - Members - Calendar
Full Version: Openzaurus For C1000 And C3000
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > C1000/3x00 General discussions
Mickeyl
is there.
fastscirocco
QUOTE(Mickeyl @ Apr 30 2005, 08:06 AM)
is there.
*


And now another rom for the C3000, I guess when it rains it pours?

OK, any reason to not install Cacko3k and use this one...hmmm?

Good work guys!
albertr
Good work and congrats to Mickey and OZ crew! Please keep it coming...
-albertr
jh
QUOTE(Mickeyl @ Apr 30 2005, 05:06 AM)
is there.
*


Awesome! Thanks!! C1000 gets here on Monday and I'll dive right in.

jason
offroadgeek
This is a great start mickeyl! It was nice to see OZ on my 1000... though I'll have to come back to OZ after the special keys are working (FN especially). A couple other small things I noticed:

1. the right Shift key doesn't work
2. the screen doesn't go blank after closing the lid (the settings were correct in the Light & Power app)

Looking forward to more progress!
lpotter
QUOTE(fastscirocco @ Apr 30 2005, 11:55 PM)
QUOTE(Mickeyl @ Apr 30 2005, 08:06 AM)
is there.
*


And now another rom for the C3000, I guess when it rains it pours?

OK, any reason to not install Cacko3k and use this one...hmmm?

Good work guys!
*



cause it's not based on the Sharp rom?
euroclie
Congratulations, Mickey! This looks very promising!

The installation was smooth, the look & feel is impressive.

The on/off button didn't work on my 3000, I had to select the "Suspend" menu to switch off the device. Also, I ran a few games while I was in the doctor's waiting room so that my 4 years old boy kept quiet, and the key are definitely not adapted to the clamshell design (in Tetris, for instance). Didn't dig very much to know if these could be re-configured quickly, though... wink.gif

The home button didn't work either, which meant closing every app upon exit to get back to the launcher...

Some icons in various programs are really tiny (probably look great in 320x240, though, but not that impressive in 640x480), but that's a personal taste issue, nothing remotely close to a bug! wink.gif

All in all, a lot of minor bugs that I'm sure will be corrected easily, so I have great expectations for this ROM!

I had to reflash Cacko because I'm already sort of commited to beta testing it, but I'll sure have a look regularly to follow the progress of the OZ ROM! I'll certainly reflash it again as soon as it is more useable (because, despite the fact that I can't resist beta testing everything I can grab, I still need my Zaurus in the everyday life! wink.gif ).

Choice is great... biggrin.gif

Happy Zaurusing to you all!
madeddie
Is there an easy way to get back to the original Sharp Rom?
Booting with the OK key -> option 3 -> option 1 -> Yes does not work, I guess
it's because it tries to boot with the wrong kernel?

--
edwin
offroadgeek
QUOTE(madeddie @ May 3 2005, 11:00 AM)
Is there an easy way to get back to the original Sharp Rom?
Booting with the OK key -> option 3 -> option 1 -> Yes does not work, I guess
it's because it tries to boot with the wrong kernel?

--
edwin
*


yes, there is. if you made a nand backup before flashing to OZ, then you can just do a nand restore. See trisoft's site for the necessary downloads (if you don't already have your own nand backup) and instructions.
madeddie
QUOTE(offroadgeek @ May 3 2005, 10:18 PM)
yes, there is.  if you made a nand backup before flashing to OZ, then you can just do a nand restore.  See trisoft's site for the necessary downloads (if you don't already have your own nand backup) and instructions.
*


I'm not sure the NAND is messed up, It looks more like the kernel and data
on the internal harddrive, although a backup for those is downloadable too,
so, I'll be alright *rummages around for CF card writer* smile.gif

thanks

--edwin
Mickeyl
OZ/C3000 contains three parts: kernel (goes to special partition on NAND), bootstrap-image (goes to NAND), opie (harddisk) - which means you need to restore these three to get back to the SharpROM. You can do that with the updater.sh and the three files shipped in the C3000 OS update.
madeddie
I can boot to the emergency prompt without a problem, I guess that's another
kernel than the one that boots the ROMs.

Does the zero'ing procedure use this special kernel or the ROM starting one?

--edwin
w14
Edwin,

I think you're missing the point a bit. The point ORG and Mickeyl are making is that the NAND contains the OS's three parts - the kernel, bootstrap image and the root filesystem.

So you're NAND is not messed up, as such. It has OZ on it. But the easiest way to get back to a stock Sharp image is to do as ORG suggests, get a NAND backup file, put it on a media card of some kind, and do a NAND restore.

Or you can do as Mickeyl suggests and reflash with the Sharp OS update files and updater.sh.

Good luck.

Mike.
madeddie
Thank you, but I didn't miss that point, I know the OZ kernel en bootstrap image are in the NAND (the opie image is in de hdimage.tar.gz file on /dev/hda1 though), but, what you seem to miss is that there's a fallback linux install somewhere else that doesn't seem to be affected by OZ (and it shouldn't as far as I can tell).

I was just wondering if that emergency linux install uses the same kernel as the standard bootproces (it doesn't seem to be, because this one shows the Sharp boot image) and if it's true that this emergency linux install uses a different kernel, I was wondering if that kernel is used by the zero'ing proces or the standard kernel.

It's quite a normal question IMHO, I'm not afraid to flash the NAND, i've done it before, I'm just wondering about how the proces works.

To clarify, by zero'ing proces I mean starting holding the OK button -> Opt 3 -> Opt 1 -> Y, so a factory default reset. It uses a hdimage file on /dev/hda1 _and_ a kernel, i'm wondering which kernel.

The emergency linux install is reached by booting holding D+B, that one seems to boot from an entirely different kernel.
Mickeyl
Since there are only two kernels on a Zaurus, I suspect the emergency kernel is zImage2 - the same as used when you are updating the device. When you zero the device there's probably no kernel running at all, since this seems to be completely implemented in diagnostics code.

Speaking about that... I'd really like to have that code released smile.gif
iamasmith
QUOTE(Mickeyl @ May 4 2005, 09:38 AM)
Since there are only two kernels on a Zaurus, I suspect the emergency kernel is zImage2 - the same as used when you are updating the device. When you zero the device there's probably no kernel running at all, since this seems to be completely implemented in diagnostics code.

Speaking about that... I'd really like to have that code released smile.gif
*


Zeroing is handled on Sharp ROMs by the /root/etc/rc.d/rc.rofilesys

It picks up some parameters which seem to be added to the boot process by using option 3,1 on the Japanese menu.. it does actually boot into the live Linux when you do this. If you wanted to implement this for OZ then you really need to look at that file..

Look around this area.....
CODE
....
#ZAURUS_RESET=HARD
if [ "$ZAURUS_RESET" = "HARD" ]; then

STRING=$"Starting filesystem: "
msg -n $STRING

# mount /home
/sbin/eraseall $RW_MTD 2> /dev/null > /dev/null
mount -t jffs2 -o rw,noatime $RW_MTDBLK /home
cd /
tar xf /root/.home_default.tar
....


Hope this helps the efforts,

Andy
Mickeyl
I don't see why we should use this in OZ. We have /home on the harddisk, not on a mtdblock.
iamasmith
Wasn't particularly hinting at the mtdblock.. if you take a look at the whole script you will see the HDD handling in there too for zeroing the device.

Attached for your perusal.
offroadgeek
QUOTE(madeddie @ May 4 2005, 12:43 AM)
what you seem to miss is that there's a fallback linux install somewhere else that doesn't seem to be affected by OZ (and it shouldn't as far as I can tell).
*

QUOTE(madeddie @ May 4 2005, 12:43 AM)
It's quite a normal question IMHO, I'm not afraid to flash the NAND, i've done it before, I'm just wondering about how the proces works.
*

We might not have missed that had you actually asked this in the first place. Your original question:

QUOTE
Is there an easy way to get back to the original Sharp Rom?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.