On 06/29/2014 12:15 PM, John Talbut wrote:
There seems to be a general problem when using a static kernel and initramfs in
that the wireless drivers try to load firmware before the disks are mounted and
the /lib/firmware folder is available. Various people seem to have come across
problems with firmware not loading, some of which seem to relate to this
problem, which they have approached as if it is a problem with their particular
driver. However it seems to be a general problem and I have had it with three
different drivers.
There seems to be a number of possible approaches to this: loading the firmware
in an initramfs; changing the sequence in which wireless drivers start so that
they wait until the disks are mounted; compiling the firmware into the kernel
and loading the firmware as part of ifup. I see that the latter has been done
for one driver (http://thread.gmane.org/gmane.linux.kernel.wireless.general/3390).
What is the current situation with this problem and what needs doing?
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
What kernel version, and what wireless drivers have this problem?
At one point, there was a timeout of 30 seconds for request_firmware() calls,
and that led to problems even when the drivers were built as modules. That
situation was handled in a number of wireless drivers by using
request_firmware_nowait(); however, my understanding was that user space was
fixed to avoid the timeout. I think udev was the component that changed. What
version of that are you using?
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
