[syslinux] Booting new kernels
Gene Cumm
gene.cumm at gmail.com
Sun May 18 14:35:36 PDT 2014
On May 18, 2014 3:12 PM, "Alexey Orishko" <alexey.orishko at gmail.com> wrote:
>
> On Sun, May 18, 2014 at 7:08 PM, Gene Cumm <gene.cumm at gmail.com> wrote:
> >> > On 05/16/2014 01:35 PM, Tal Lubko wrote:
> >> > > For some reason when I use kernel 3.7.1 and above the system
crashes
> > during boot and I have no reason why.
> >> Consider a lack of init or otherwise improper initrd (cpio format,
> > compression, etc). Consider trying your old kernel with new initrd
and/or
> > new kernel with old initrd to start diagnosis.
> >>
> >> --Gene
> >
> > [ 0.000000] Kernel command line: root=/dev/sda1 initrd=rootfs.ext2
> > console=ttyS0,115200 BOOT_IMAGE=bzImage
> >
> > [ 0.297992] Unpacking initramfs...
> > [ 0.298619] Initramfs unpacking failed: junk in compressed archive
> > [ 0.299718] Freeing initrd memory: 5636k freed
>
> If GPT used instead of MBR, no initrd required...
>
> Regards,
> Alexey
GPT versus MBR makes no difference. Storage adapter and its driver location
is more critical, followed by tools for decryption.
[ 0.710918] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK
1.4. PQ: 0 ANSI: 5
[ 0.712510] sd 0:0:0:0: [sda] 40960 512-byte logical blocks: (20.9
MB/20.0 MiB)
[ 0.983947] VFS: Mounted root (vfat filesystem) readonly on device 8:1.
Sounds like the user meant to have init in the initrd and possibly not have
root on sda1 but the initrd is in an inappropriate format (ie not cpio.gz
that's typical for initramfs).
--Gene
More information about the Syslinux
mailing list