On Thu, 2016-06-02 at 23:09 -0600, Reinoud Koornstra wrote: > On Thu, Jun 2, 2016 at 2:16 AM, Luca Coelho <luca@xxxxxxxxx> wrote: > > This shows that you have iwlwifi-7260-16.ucode in your file system. > > But here we are reading it much later. So it's possible that the > > kernel cannot access the firmware at a very early stage (because > > the > > filesystem that contains it is not mounted yet) when you use in- > > kernel. > > > > So, first of all, please make sure they're built as modules. We > > can > > continue from there then. > > Your suggestion worked. When it's compiled as module, the > iwlwifi-7260-16.ucode loads fine. > No problems detected so far. Great! :) > It does make me think whether this is desired behavior though that > due > to the later reading we cannot have iwlwifi build in the kernel. It should work, but then you have to make sure the firmware is available at very early stages of boot. If you add it to the proper place in your initrd, the kernel should find it when the driver requests it. I didn't want to go into the details of this, because in most cases the best option is to have the driver as a module. If you really need it in-kernel, then you need to make sure all the needed pieces are available very early as well. -- Cheers, Luca. -- 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
