I think I finally solved this.
Basically not all files from /lib/firmware/ are copied to the initrd image,
which means that there's some mechanism, which decides what to add (and I
have no idea what that is). Looking for info, I came across some
suggestions that only the drivers compiled as ke
Note: deloptes response to my unintentional off list message
This is correct, but eeprom is expensive, so to save cost you let your device
use the PCs memory and resources. So when you start the device and load the
driver. The driver requests the firmware to be loaded from the PC - this gives
t
Note: I unintenionally sent this to deloptes (only) off list. He has already
responded, I'll copy his response to the list in a minute.
From the peanut gallery (at least with respect to this thread -- in other
words, at least a little "off thread" (but not quite off topic, imho):
I'm puzzled a
On 07/03/2020 13:50, deloptes wrote:
> Well, I build my own kernels and they all have the firmware
> directory included. Why not compare all relevant parts instead
> complaining?!I regenerate two initrd images at the same machine and system
> using
*update-initramfs -u -k all* . So I think the sa
Mikhail Morfikov wrote:
> No, this does nothing, still only the Debian kernel's initrd has the
> firmware dir included. It's really weird that this is different for
> stock and not stock kernel...
Well, I build my own kernels and they all have the firmware directory
included. Why not compare all
On 07/03/2020 00:28, deloptes wrote:
> try with the stock kernel
> modprobe -v iwlwifi
>
> or whatever the module name is and update initrd.
> Check the results
> lsinitramfs /boot/initrd.img-
No, this does nothing, still only the Debian kernel's initrd has the
firmware
Mikhail Morfikov wrote:
>> Just check the configuration in /etc/initramfs-tools/
> No, there's nothing useful for me there, so it has to be in
> some other place, hmm...
try with the stock kernel
modprobe -v iwlwifi
or whatever the module name is and update initrd.
Check the results
On 06/03/2020 18:42, deloptes wrote:
> Just check the configuration in /etc/initramfs-tools/
No, there's nothing useful for me there, so it has to be in
some other place, hmm...
signature.asc
Description: OpenPGP digital signature
Mikhail Morfikov wrote:
> No, I'm using my own kernel and not the Debian's one, but I didn't have
> to build the firmware into the kernel image before (in the case of the
> old WiFi card and old laptop). Now after I moved in to the new laptop
> I have to, and I don't know why.
>
> I just checked,
On 06/03/2020 16:49, deloptes wrote:
> I think if the intel driver is not compiled in the kernel, you do not
> have to compile the firmware.
>
> So what you are actually saying, that when you have the stock kernel
> and load the intel driver, it does not pick up the firmware?
>
> Can you confirm
Mikhail Morfikov wrote:
> I'm just asking because I had a BCM WiFi card in my previous laptop and
> that card needed firmware-brcm80211 . Now I have a new laptop, and it
> has an Intel WiFi, which needs firmware-iwlwifi . I have the same setup
> (LUKSv2+LVM), and the exact same system (it was move
On 06/03/2020 07:50, deloptes wrote:
> So if you compile the driver static in the kernel I am not sure 100%
> but it should have the firmware already somewhere to be loaded. This
> is interesting question. I think most of the usecases include using
> initrd that would have driver and firmware.
I'm
Mikhail Morfikov wrote:
> Basically there's an option to load/unload a kernel module via modprobe
> and modprobe -r . Is there a way to do this with, for instance, WiFi
> firmware? Also, what happens to the loaded firmware when you unload the
> corresponding module? And another question: when I co
Basically there's an option to load/unload a kernel module via modprobe and
modprobe -r . Is there a way to do this with, for instance, WiFi firmware?
Also, what happens to the loaded firmware when you unload the corresponding
module? And another question: when I compile a module into the kernel
14 matches
Mail list logo
