Re: [SLE] New initrd way in SuSE-9.0

From: hugh (hughforsuse_at_comcast.net)
Date: 11/03/03

  • Next message: Basil Chupin: "[SLE] USB connected keyboard - more than a slight hassle" 
    Date: Mon, 03 Nov 2003 23:29:51 +0900
To: Gavin Henry <gavin.henry@magicfx.co.uk>

    Gavin Henry wrote:

    >On Mon, 03 Nov 2003 21:17:44 +0900
    >hugh <hughforsuse@comcast.net> wrote:
    >
    >
    >
    >>There are some critical gotchas with SuSE-9.0.
    >>Durung the update initrd's are created for all kernel images
    >>registered in the /boot/grub/menu.lst.
    >>Once it is installed, and if I custom-compile my own kernel,
    >>I need to make the initrd-2.4.23-pre9 (e.g.) against the new
    >>kernel. and I do not know how to make it.
    >>
    >>
    >
    >Do you really need it? It is only used if you have a scsi disk or something that you can't access to mount root, hence the correct module is loaded before, so you can.
    >
    >
    >

    It turned out that I really do not need it, as you said.
    What has been changed from 8.2 is the fact that
    the reiserfs.o module inside the initrd does not match
    with something in the current kernel tree. For this
    reason, I get a bunch of "undefined something
    in reiserfs.o" message during boot-up.
    That scared me greatly.

    I took the line out from /boot/grub/menu.lst which make the
    boot procedure takes the default initrd. This took care of the scary
    boot-up
    message.

    Thank you very much.

    >>The document /usr/src/linux/Documentation/initrd.txt is not
    >>sufficiently kind. The matter of the fact is that I need
    >>to figure out what to do under the SuSE environment.
    >>Can any one teach how to make it?
    >>
    >>
    >
    >Just don't compile in ramdisk and initrd support in your kernel ie. in:
    >
    >Block Devices, switch off RAM disk support and Initial RAM disk (initrd) support.
    >
    >
    >
    >>Up to 8.2, creating a new initrd for every new custom-compiled
    >>kernel was not quite critical. It appears that things changed
    >>greatly.
    >>
    >>
    >
    >Then in /boot/grub/menu.lst
    >
    >take out the initrd option when you add your own lines.
    >
    >
    >
    >
    >>Thanks.
    >>
    >>Hugh
    >>
    >>
    >>
    >>--
    >>Check the headers for your unsubscription address
    >>For additional commands send e-mail to suse-linux-e-help@suse.com
    >>Also check the archives at http://lists.suse.com
    >>Please read the FAQs: suse-linux-e-faq@suse.com
    >>
    >>
    >>
    >>
    >
    >
    >
    > 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Basil Chupin: "[SLE] USB connected keyboard - more than a slight hassle"

    Relevant Pages

    • Re: Kernel panic: initramfs problem? [SOLVED - mostly]
      ... initrd.img-2.6.18-6-686 is 4899969 bytes in size (generic kernel) ... Following up on the initrd idea.... ... with support for the initial RAM disk enabled. ... If RAM disk support is also included, ...
      (Debian-User)
    • Minimal boot CD
      ... I knew I needed some kind of sane working environment for the kernel to ... does the initrd have to be a specific ... but it still kernel panics. ... I included RAM disk support Default RAM disk size) and ...
      (comp.os.linux.embedded)
    • Re: BOOT_CS
      ... the CRC32 of the decompressed RAM disk - and stop the boot process ... another kernel version / initrd to load. ... You cannot place the decompressed initrd at a maximum address before ... address minus ramdisk size if I remember ...
      (Linux-Kernel)
    • Re: booting from ISO image on HD?
      ... >> through customized initrd files for each one. ... > between the loopback device and the underlying file (the iso image). ... I have to insmod the loop kernel module(e.g. ... how can you boot it from an initrd??? ...
      (comp.os.linux.misc)
    • Re: fsck fails during boot with 2.6.9-34.0.1.EL kernel because root filesystem is already rw mou
      ... I think there was a little fault in building the new initrd. ... The mount-command of the init-script is wrong and makes confusing, e.g.: first the root-filesystem must mount read/write, it accepts. ... It looks like in the early stage of the booting, when the kernel is using the initrd to load the ... I still do not understand why in my new initrd file, with the new kernel, the root filesystem is ...
      (RedHat)