[arch-projects] [mkinitcpio][PATCH 00/19] Break all the things!

Dave Reisner d at falconindy.com
Mon May 14 09:50:24 EDT 2012

On Mon, May 14, 2012 at 10:37:38AM +0200, Thomas Bächler wrote:
> Am 13.05.2012 19:57, schrieb Dave Reisner:
> > The final unlisted change is what I referred to earlier about udev. Since the udev
> > hook would be handling its own startup/shutdown, we'd simply yank those if blocks
> > out of /init and carry on. I've been testing this and it works quite well.
> I haven't looked through your patchset yet, but here is the bad part
> about udev:
> In the past, udev needed to run before the modules listed in MODULES=
> from mkinitcpio.conf were loaded. Otherwise, firmware loading would
> fail, and almost everyone with MODULES="radeon" would be very unhappy! I
> know that some things have changed regarding firmware loading since
> then, but this is likely still an issue in some form - and even if it
> isn't, it is a good idea to have a firmware helper present before doing
> anything.

Excellent point -- was curious about this myself. I asked Kay about

08:50         kay  » it will be catched with the coldplug run, yes
08:50         kay  » but if udev runs in intramfs, and there is no firmware
                     file, the request will be canceled
08:51  falconindy  » yeah, this is initramfs
08:51  falconindy  » so settle will play catchup and things will
                     just work (hopefully)
08:57         kay  » settle?
08:57         kay  » trigger will
08:58  falconindy  » even better
08:58         kay  » but if udev from initramfs still runs and
                     there is no firmware file, all is discarded

So it seems to me that we're covered here since we assume that the
firmware is present (or else its a bug in mkinitcpio). I'd like to get
someone with perhaps a radeon to confirm this via my working branch and
a modified udev hook (I can provide this), but I guess the worst case
scenario is that we file a bug.


More information about the arch-projects mailing list