* Initrd and ramdisk support
@ 2006-09-28 19:47 Stephan Wiebusch
2006-09-29 8:10 ` Jan Engelhardt
0 siblings, 1 reply; 3+ messages in thread
From: Stephan Wiebusch @ 2006-09-28 19:47 UTC (permalink / raw)
To: linux-kernel
Hi!
After a very long session of searching for the reason for error messages like
Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers
Unpacking initramfs...<0>Kernel panic - not syncing: no cpio magic
i luckily was able to determine the malefactor. There was the initrd support
built into the kernel while the ramdisk driver was just built as a module.
Is it senseful to have the possibility to built the Initramfs/Initrd-support
without having the ramdisk driver forced to be integrated also?
King regards from Germany
Stephan Wiebusch
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Initrd and ramdisk support
2006-09-28 19:47 Initrd and ramdisk support Stephan Wiebusch
@ 2006-09-29 8:10 ` Jan Engelhardt
2006-09-29 9:13 ` Michael Tokarev
0 siblings, 1 reply; 3+ messages in thread
From: Jan Engelhardt @ 2006-09-29 8:10 UTC (permalink / raw)
To: Stephan Wiebusch; +Cc: linux-kernel
>Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers
>Unpacking initramfs...<0>Kernel panic - not syncing: no cpio magic
>
>i luckily was able to determine the malefactor. There was the initrd support
>built into the kernel while the ramdisk driver was just built as a module.
>
>Is it senseful to have the possibility to built the Initramfs/Initrd-support
>without having the ramdisk driver forced to be integrated also?
I hardly see a point in using initrd support without ramdisk. Where would you
store the initrd on instead?
Jan Engelhardt
--
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Initrd and ramdisk support
2006-09-29 8:10 ` Jan Engelhardt
@ 2006-09-29 9:13 ` Michael Tokarev
0 siblings, 0 replies; 3+ messages in thread
From: Michael Tokarev @ 2006-09-29 9:13 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: Stephan Wiebusch, linux-kernel
Jan Engelhardt wrote:
>> Unpacking initramfs...<0>Kernel panic - not syncing: bad gzip magic numbers
>> Unpacking initramfs...<0>Kernel panic - not syncing: no cpio magic
>>
>> i luckily was able to determine the malefactor. There was the initrd support
>> built into the kernel while the ramdisk driver was just built as a module.
>>
>> Is it senseful to have the possibility to built the Initramfs/Initrd-support
>> without having the ramdisk driver forced to be integrated also?
>
> I hardly see a point in using initrd support without ramdisk. Where would you
> store the initrd on instead?
I build kernels without ramdisk built into, but using initramfs, for quite some
time already. There was a patch somewhere around 2.6.15 or so, that removed
dependency of INITRD from RAMDISK, just a small Kconfig change. Now it's in
the mainline. For initramfs, there's no need for ramdisk - it reads the FS
image from memory (as passed to by loader), and unpacks it into ramfs - no
ramdisk is involved here.
/mjt
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-09-29 9:13 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-28 19:47 Initrd and ramdisk support Stephan Wiebusch
2006-09-29 8:10 ` Jan Engelhardt
2006-09-29 9:13 ` Michael Tokarev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox