On Saturday 24 February 2007 15:23, Jan Engelhardt wrote:
> On Feb 23 2007 15:47, Andrew Walrond wrote:
> >
> >I have tracked this down to a broken version of gnu cpio (latest release,
> > 2.7) which was used to create the initramfs archive. Bloody annoying
> > since this has bitten me before!
On Feb 23 2007 15:47, Andrew Walrond wrote:
>On Friday 23 February 2007 15:17, Tomasz Chmielewski wrote:
>>
>> Try to decrease the initramfs size just to know if it boots correctly.
>>
>> I.e., put just a sh/bash/ash/dash binary there (probably /dev/console
>> node, too), executed in init.
>>
>>
On Feb 23 2007 15:47, Andrew Walrond wrote:
On Friday 23 February 2007 15:17, Tomasz Chmielewski wrote:
Try to decrease the initramfs size just to know if it boots correctly.
I.e., put just a sh/bash/ash/dash binary there (probably /dev/console
node, too), executed in init.
Then, try to
On Saturday 24 February 2007 15:23, Jan Engelhardt wrote:
On Feb 23 2007 15:47, Andrew Walrond wrote:
I have tracked this down to a broken version of gnu cpio (latest release,
2.7) which was used to create the initramfs archive. Bloody annoying
since this has bitten me before! Last time I
On Friday 23 February 2007 15:17, Tomasz Chmielewski wrote:
>
> Try to decrease the initramfs size just to know if it boots correctly.
>
> I.e., put just a sh/bash/ash/dash binary there (probably /dev/console
> node, too), executed in init.
>
> Then, try to start the kernel with initramfs embedded
Andrew Walrond schrieb:
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
same procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
> Andrew Walrond schrieb:
> > On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
> > same procedure successfully on x86_64 and itanium2 servers).
> >
> > The relevent silo section looks like this:
> >
> >
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the same
procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image=/boot/2.6.20.image
label=2.6.20
initrd=/boot/2.6.20.initramfs
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the same
procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image=/boot/2.6.20.image
label=2.6.20
initrd=/boot/2.6.20.initramfs
partition=2
read-only
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the same
procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image=/boot/2.6.20.image
label=2.6.20
initrd=/boot/2.6.20.initramfs
partition=2
read-only
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the same
procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image=/boot/2.6.20.image
label=2.6.20
initrd=/boot/2.6.20.initramfs
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
same procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
image=/boot/2.6.20.image
Andrew Walrond schrieb:
On Friday 23 February 2007 13:32, Tomasz Chmielewski wrote:
Andrew Walrond schrieb:
On a Sun T1000 I am trying to boot 2.6.20 using initramfs. (I use the
same procedure successfully on x86_64 and itanium2 servers).
The relevent silo section looks like this:
On Friday 23 February 2007 15:17, Tomasz Chmielewski wrote:
Try to decrease the initramfs size just to know if it boots correctly.
I.e., put just a sh/bash/ash/dash binary there (probably /dev/console
node, too), executed in init.
Then, try to start the kernel with initramfs embedded in the
14 matches
Mail list logo
