From: Andrew Benton <b3nt@ukonline.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: Kernel Firmware Loading
Date: Wed, 02 Nov 2005 23:22:13 +0000 [thread overview]
Message-ID: <43694A25.4050201@ukonline.co.uk> (raw)
In-Reply-To: <4365DBD9.2040407@ukonline.co.uk>
Alexander E. Patrakov wrote:
> I wrote:
>
>>
>> The /sbin/hotplug script should contain the following:
>>
>> #!/bin/sh
>> [ "$1" != "firmware" ] || [ "$ACTION" != "add" ] || [ ! -f
>> "/lib/firmware/$FIRMWARE" ] || exit 0
>
> This was wrong, sorry. Should be:
>
> [ "$SUBSYSTEM" != "firmware" ] || [ "$ACTION" != "add" ] || [ ! -f
> "/lib/firmware/$FIRMWARE" ] && exit 0
>
It doesn't matter, it makes no difference, the kernel seems to just ignore the initrd and boot as normal. The error I posted from the logs is there whether I use the initrd or not. I did look for errors before, but not very well so I didn't notice it (sorry).
I don't have any more time to waste working on this initramfs nonsense at the moment. I may return to it later if nothing else turns up, but I don't want to. I don't see why the kernel can't wait until userspace has been mounted before it tries to load the firmware.
Andy
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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
next prev parent reply other threads:[~2005-11-02 23:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 8:54 Kernel Firmware Loading Andrew Benton
2005-10-31 9:37 ` Alexander E. Patrakov
2005-10-31 10:04 ` Andrew Benton
2005-10-31 10:59 ` Duncan Sands
2005-10-31 10:59 ` Alexander E. Patrakov
2005-10-31 11:08 ` Marco d'Itri
2005-10-31 11:18 ` Duncan Sands
2005-10-31 11:50 ` Marco d'Itri
2005-10-31 13:10 ` Kay Sievers
2005-10-31 13:27 ` Duncan Sands
2005-10-31 14:35 ` Kay Sievers
2005-10-31 14:41 ` Duncan Sands
2005-10-31 14:54 ` Kay Sievers
2005-10-31 16:29 ` linas
2005-10-31 16:33 ` Marco d'Itri
2005-10-31 21:15 ` Andrew Benton
2005-11-01 9:48 ` Duncan Sands
2005-11-01 11:15 ` Andrew Benton
2005-11-01 15:56 ` Alexander E. Patrakov
2005-11-01 16:59 ` linas
2005-11-01 21:19 ` Andrew Benton
2005-11-02 2:09 ` Alexander E. Patrakov
2005-11-02 6:20 ` Alexander E. Patrakov
2005-11-02 6:28 ` Alexander E. Patrakov
2005-11-02 23:22 ` Andrew Benton [this message]
2005-11-03 8:08 ` Duncan Sands
2005-11-04 14:46 ` Alexander E. Patrakov
2005-11-04 14:52 ` Duncan Sands
2005-11-04 15:14 ` Alexander E. Patrakov
2005-11-07 15:48 ` Patrick Mansfield
2005-11-08 8:16 ` Alexander E. Patrakov
2005-11-08 17:54 ` Greg KH
2005-11-08 18:37 ` Patrick Mansfield
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=43694A25.4050201@ukonline.co.uk \
--to=b3nt@ukonline.co.uk \
--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.