On Thu, Jan 19, 2012 at 15:05, Allin Cottrell <cottrell@xxxxxxx> wrote: > On Tue, 17 Jan 2012, Kay Sievers wrote: > >> On Tue, Jan 17, 2012 at 15:08, Allin Cottrell <cottrell@xxxxxxx> wrote: >>> >>> With udev-177 plus kmod4 (also with kmod3) I'm seeing this from dmesg on >>> boot-up: >>> >>> iwlwifi 0000:03:00.0: request for firmware file \ >>> 'iwlwifi-6000g2a-5.ucode' failed. >>> >>> The file in question is in /lib/firmware, which is the firmware-path set >>> for >>> udev. >>> >>> It seems, though, that the error message is somehow spurious, since I >>> also >>> see this (shortly after the above): >>> >>> iwlwifi 0000:03:00.0: loaded firmware version 17.168.5.3 build 42301 >>> >>> and version 17.168.5.3 corresponds to iwlwifi-6000g2a-5. So just a >>> cosmetic >>> problem? >> >> You see the same when you rmmod/modprobe the module? > > Hmm, in fact yes. If I rmmod then modprobe iwlwifi using the > module-init-tools binaries I now see the same pattern of a failure message > immediately followed by a report that the firmware is loaded. The funny > thing is that I wasn't seeing the failure message (using the same 3.2.1 > kernel) before updating udev 175 -> 177. > >> Please enable timestamps in printk, and provide the entire output of >> dmesg, so we can see in which context of the bootup this happens. Hmm, I don't see that here. The log does not show anything obvious. You are sure, you don't have the old firmware loader installed along with the new udev, right? There is no /lib/udev/rules.d/50-firmware* file, right? Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
