The uImage here should be sufficient for a fallback. Also, you should
not need a uInitrd, since everything is build in to the kernel:
http://www.cyrius.com/tmp/beta1/marvell/sheevaplug/uImage
I'm successfully running this kernel on my system:
c...@plug0:~$ dpkg -l | grep linux-image
ii linux-
* Samuele Bianchi [2010-09-22 09:04]:
> A quick question.
> What would have happened if I had launched "flash-kernel" after the update?
Your system would have booted fine.
There was an incompatible change in 2.6.32-22. Normally, when we make
incompatible changes, we change the ABI name (2.6.32-
I can confirm that it works for s-sata sheeva plug too.
thank you very much for the support.
A quick question.
What would have happened if I had launched "flash-kernel" after the update?
Da: Bob Smeets [bsme...@gmail.com]
Inviato: mercoledì 22 settembre 20
Please tell me if i'm missing something...
I should try to upload a fully working uInitrd and uImage in this way
setenv serverip 192.168.1.2 ( Ip of my pc/tftp server )
setenv ipaddr 192.168.1.81 ( ip of my e-sata sheeva plug )
tftpboot 0x0110 uInitrd
tftpboot 0x0080 uImage
saveenv
Is it
4 matches
Mail list logo
