This is what udev's userspace helper is looking at, so that finds the file just fine.
The interesting question here is why the kernel wants to load requests iwlwifi-6000-5.ucode. I. e. where does the -5 come from? It seems the in-kernel loader and the "firmware:" module field are doing something different?
We ship /lib/firmware/ iwlwifi- 6000-4. ucode in linux-firmware, which is also what the module advertises:
$ modinfo iwlwifi|grep 6000 6000g2b- 6.ucode 6000g2a- 5.ucode 6000-4. ucode
firmware: iwlwifi-
firmware: iwlwifi-
firmware: iwlwifi-
This is what udev's userspace helper is looking at, so that finds the file just fine.
The interesting question here is why the kernel wants to load requests iwlwifi- 6000-5. ucode. I. e. where does the -5 come from? It seems the in-kernel loader and the "firmware:" module field are doing something different?