Re: fastboot/async and initramfs: How am I supposed to know when devices are finished initializing?

[Arjan van de Ven <arjan@infradead.org>]

On Sun, 29 Mar 2009 18:02:41 +0200
Thomas Bächler <thomas@archlinux.org> wrote:

> Okay, I have this problem in 2.6.29 with the "fastboot" option and in 
> today's linux-2.6.git.
> 
> In initramfs, we run the following commands:
>      /sbin/udevd --daemon
>      /sbin/udevadm trigger
>      /sbin/udevadm settle
> Among other things, this loads the ata_piix on my machine. On older 
> kernels I could assume that after these commands, /dev/sda* existed

not if you have CONFIG_SCSI_SCAN_ASYNC set though..

> and I could immediately access them (in my case, I run cryptsetup on 
> /dev/sda6). But now, the devices don't exist here, but are only
> created a second or so later. As a result, the initramfs script has
> already bailed out as it couldn't find /dev/sda6 and assumed that the
> hard drive didn't exist.

the CONFIG_SCSI_WAIT_SCAN method (basically loading that module to wait
for the scans to finish) will work for you......


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org