At 15:04 18/01/2006, Miguel González Castaños wrote:
Carl escribió:
At 12:36 18/01/2006, Miguel González Castaños wrote:
I have reviewed my configurations and I do
not see why I getting this error:
- I have deactivated modules support, so EXT3
support is within the kernel, not loaded as a module
I always thought you REQUIRED ext3 support in
the initrd image so the ext3 filesystem
that holds the kernel can be mounted.
I have read that filesystem modules should be compiled within the
kernel, not as modules, otherwise the system doesn´t boot. Initrd uses
the information in the /lib/modules/ directory to build the img file, so
I am not sure whether I have to use initrd, anyway I have tried to use
mkinitrd with a monolithic kernel and obviously didn´t work. Are you
sure of that point?
Miguel,
I am not 100% sure for a monolithic kernel as i
have never tried it. However a quick look at the Kernel-HOWTO
gives this nugget of info from the mkinitrd manpage:
mkinitrd creates filesystem images which
are suitable for use as Linux initial
ramdisk(initrd) images. Such images are often used for preloading the
block device modules (such as IDE, SCSI
or RAID) which are needed to access the
root filesystem. mkinitrd automatically
loads filesystem modules (such as
ext3 and jbd), IDE modules,all
scsi_hostadapter entries in /etc/modules.conf,
and raid modules if the systems root
partition is on raid, which makes it
simple to build and use kernels using modular device drivers.
and this from the RedHat 9 customization guide:
If the system has a SCSI adapter and the
SCSI driver was compiled as a module or if the kernel was built
with ext3 support as a module (the
default in Red Hat Linux), the initrd image is required.
My reading of those 2 snippets suggests you maybe
right in being able to omit the initrd if you have no module support.
I would however like to see something that says
"If you have no modules you don't need an initrd". And your error message does
say you can't mount the root fs. The
unknown-block(3,3) bit of the kernel panic is
interesting aswell. If i knew what device/partition
that refers to it might help but i don't. Maybe
someone on the list knows whether 3,3 relates to /dev/hda3 or not.
You could also possibly change the filesystem to
ext2 temporarily and see if that makes any odds.
Regards
Carl
-
: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
