https://bugzilla.novell.com/show_bug.cgi?id=340342#c4
--- Comment #4 from Toni Harbaugh-Blackford 2007-11-17 17:54:25 MST ---
Is there a way to have mkinitrd be able to find out whether a module needs
firmware *without* having a hard-coded list of modules requiring firmware?
If so, then yes, it would definitely be better to have mkinitrd figure out
to load the module via udev. But I would like any solution to work in the
case of new drivers with firmware blobs that mkinitrd isn't 'expecting'.
I am running mkinitrd on the very machine that I am running the system on
afterwords. The only reason for running the mkinitrd is because the aic94xx
adapter was not included in the initrd, and I would in the end like to use the
*SATA* drive attached to that adapter.
I will provide the 'bash -x mkinitrd' in a subsequent message after I get
the system back in it's original state (I have been testing 2.6.24).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
