All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Harvell <jharvell@dogpad.net>
To: linux-hotplug@vger.kernel.org
Subject: getting my udev initrd working on 2.6.9 versus 2.6.16
Date: Tue, 20 Jun 2006 20:09:54 +0000	[thread overview]
Message-ID: <44985612.4030202@dogpad.net> (raw)

I am trying to boot a 2.6.9 kernel using a root filesystem that is an
LVM volume built on a RAID1 mirror.  The problem is that I was able to
get this working when I boot 2.6.16, but not for 2.6.9.  The linuxrc
files are shown below.

The problem is that when I execute udevstart in the 2.6.9 initrd, /dev
only gets populated with some basic stuff after executing udevstart.  In
my 2.6.16 initrd, after I execute udevtrigger, my scsi low lever driver
and my IDE driver are both loaded automatically (ata_piix and piix). 
Then when I hand load sd_mod and ide-disk, udev populates the /dev
entries for the disks and partitions.

Also, when I start a shell in the 2.6.9 initrd environment, even when I
manually load ata_piix and piix, nothing gets created in /dev for the
disks.  I was able to manually boot by mknod'ing them.

My udev config files are just the default stuff when I installed udev on
Gentoo, except that I uncommented the devmap_name rule for LVM2:

    KERNEL="dm-[0-9]*",    PROGRAM="/sbin/devmap_name %M %m",
NAME="%k", SYMLINK+="%c"


2.6.16 (working) linuxrc:

#!/bin/bash
export PATH=/sbin:/bin
mount -n -t proc proc /proc
mount -n -t sysfs sys /sys
mount -n -t tmpfs -o exec,nosuid,mode\a55 udev /dev
echo "" > /proc/sys/kernel/hotplug
udevd --daemon
udevtrigger
udevsettle
modprobe sd_mod
modprobe ide-disk
modprobe dm-mod
mknod -m 600 /dev/md1 b 9 1
mdadm -A /dev/md1 /dev/sda3 /dev/hda3
lvm vgscan
lvm vgchange -ay paris
mount -o ro /dev/paris/root /mnt
cd /mnt
bin/umount /proc
bin/umount /sys
mount --move /dev dev
sbin/pivot_root . initrd
cd /
exec sbin/init<dev/console>dev/console 2>&1


2.6.9 linuxrc:

#!/bin/bash
export PATH=/sbin:/bin
mount -n -t proc proc /proc
mount -n -t sysfs sys /sys
mount -n -t tmpfs -o exec,nosuid,mode\a55 udev /dev
echo "/sbin/udevsend" > /proc/sys/kernel/hotplug
udevd --daemon
udevstart
udevsettle
modprobe sd_mod
modprobe ide-disk
modprobe dm-mod
mknod -m 600 /dev/md1 b 9 1
mdadm -A /dev/md1 /dev/sda3 /dev/hda3
lvm vgscan
lvm vgchange -ay paris
mount -o ro /dev/paris/root /mnt
cd /mnt
bin/umount /proc
bin/umount /sys
mount --move /dev dev
sbin/pivot_root . initrd
cd /
exec sbin/init<dev/console>dev/console 2>&1


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2006-06-20 20:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44985612.4030202@dogpad.net \
    --to=jharvell@dogpad.net \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.