OESF Portables Forum

Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => Angstrom & OpenZaurus => Topic started by: nodens on April 10, 2004, 08:51:22 am

Title: OpenZaurus pseudo \'rescue disk\' - kernel boot parameters
Post by: nodens on April 10, 2004, 08:51:22 am

Hi there.

After messing up my /bin/sh symlink I had to find a way to pass kernel parameters. After digging quite a lot in the web and a little experimentation, I finally found a way.

Here is my little story, hope that might be useful :

http://clement.hermann.free.fr/zaurus (http://clement.hermann.free.fr/zaurus)

Title: OpenZaurus pseudo \'rescue disk\' - kernel boot parameters
Post by: Mickeyl on April 10, 2004, 11:38:38 am

Good report. The you-may-brick-your-Z-warning is a bit over the top though. Using the built-in updater it\'s virtually impossible to brick your Z as the maintenance flash partitions are write protected during this phase. Bricking the Z can only be done via C+D or service menu (NAND backup).

Title: OpenZaurus pseudo \'rescue disk\' - kernel boot parameters
Post by: nodens on April 10, 2004, 11:43:57 am

Well, I use the C+D method for flashing
You cannot boot at this stage. So you don\'t have any tool available. Or am I misunderstanding ? What exactly is the \"built-in updater\" ?

If there is a better way to load a new kernel, I would be glad to include it in this doc.

Title: OpenZaurus pseudo \'rescue disk\' - kernel boot parameters
Post by: Mickeyl on April 10, 2004, 01:01:39 pm

Never mind, I\'m overworked. I thought you were talking about the SL-5600, which has a built-in update menu.

That aside as long as you flash only a zImage and/or initrd.bin, you shouldn\'t be able to brick your 5500. Flashing an OSPACK is another thing though, because the bootloader is overwritten during that flash procedure.