Hi,
On 2003.03.12 20:55 "CLEM,ANTHONY (HP-USA,ex1)" wrote:
>
> Hello, I would like to install these modules you have working. Has
> there
> been enough testing so that I can install them without creating a
> brick?
mhh, like i mentioned before, flashing a new bootldr can definitly
create a brick.... i can and will not promise anything in this
direction, my decision to get(via
cvs)/config/cross-compile/flashinstall bootldr 2.19.28 based soley on
greg berenfields jornada status page where he mentioned that this
version of bootldr worked for him (it does for me too, so i make the
assumption based on two expiriences with this version that it will
work). in fact without a proper manual howto reflash a bricked jornada
720 i would not recommend this. on the other side i did not get pm to
work with the bootldr that was installed on my system when i get it. so
the decision (and the risk) is up to you. please understand this as an
disclaimer!
> Do you have installation instructions?
in the following i asume you do have a working x enviroment and tools
like pm_helper installed on your system also i asume that you have
flashed bootldr 2.19.28 with enabled pm (this is not a real howto, just
what worked for me, as an example you could have different flash
partitioning what would end up in a kernelpanic when you bootup the
system not the worst thing that could happen, this would be possible to
fix).
1. edit /boot/params
change the rootdev from "root=/dev/mtdblock/1" to
"root=/dev/mtdblock1"
if you run into trouble later (kernel panic) and you want to restore
your old value you can always give the old values temporarly to the
bootldr at the boot> prompt via "set linuxargs" and then change it
back in this file after you have booted
2. get the modified kernelsources/the binary package (if you get the
sources make everything and get the readymade kernelimage and the
modulesdirectory) (if you compile it yourself i would like to mentioned
that none of the 3.x toolchains have worked for me, the only thing that
worked for me was the /skiff/local toolchain, everything else hanged
while booting at the init of the display)
3. get them to your jornada, put the modulesdirectory into
/lib/modules, put the kernelimage into /boot (do NOT name it zImage, i
would recommend something like zImage-kernelversion)
4. reboot and do at the bootprompt (via terminal/serial cable) a "set
kernel_filename boot/zImage-kernelversion"
then type boot at the boot> prompt.
5. watch it boot, if erverything went ok you should see the login
prompt at the end (on the serial console) and the xenviroment (at the
jornada screen)
if everything had worked you should (as i mentioned before i had only
tried this at ONE jornada720 with flashrom and can therefore not make
any statement towards ALL jornada720 with flashrom)
now be able to press the on/off button and send the jornada to sleep, a
second press will resume it. the screen will not repaint then so it
looks very wild but some movements with the mousepointer fixed this for
me. also the pcmcia subsystem should work fine (suspend and resume).
when you are satisfied verify that the file zImage in your boot
directory is only a symolic link, delete that symbolic link (or if its
a file copy the file to a file zImage-oldkernelversion and delete
zImage then) make a "ln -s zImage-kernelversion zImage" in the
directory /boot .if you later want to switch back temporarly to your
old kernelversion you can always "set kernel_filename
boot/zImage-oldkernelversion" at the bootldr boot> prompt
if you have anymore questions or there is something not clear/confusing
dont hesitate to ask, i would be very happy to hear from someone if and
how this works at other jornadas720 also constructive hints etc. are
very appreciated!
kye
ps: as i am somehow unable to make a working jffs2 out of my rootimage
perhaps someone can do that then or post a working howto?
Received on Thu Mar 13 09:19:29 2003
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:46:01 EDT