>> Thanks.
>>
>> David
>
>
>
> Hi David,
> Many thanks it worked!
> I was able to build the required module, now just need to load it on pxe
> boot ...
> Any idea how to add module via PXE boot or shall I open a new topic
> regarding this ?
Well, the official recommendation would be to modify the kernel config
and build a PXE image with the SDK as in:
https://coreos.com/os/docs/latest/sdk-modifying-coreos.html
If you have the module built and installed in the developer container,
you could tack it onto an existing PXE initrd with something like this
and PXE boot with the new initrd:
> alias cpio='docker run --rm --volume="$PWD:/wd" --workdir=/wd -i busybox cpio'
> cp --parents /lib/modules/*-coreos/kernel/drivers/.../module.ko .
> mkdir -p etc/systemd/system/systemd-udevd.service.requires
> echo -e '[Unit]\nDefaultDependencies=no\nBefore=systemd-udevd.service\n[Service]\nType=oneshot\nExecStart=/usr/sbin/depmod' > etc/systemd/system/depmod.service
> ln -fs ../depmod.service etc/systemd/system/systemd-udevd.service.requires/
> find etc lib/modules/*-coreos/kernel/drivers/... | cpio -oHnewc | gzip | cat coreos_production_pxe_image.cpio.gz - > new.cpio.gz
If you've confirmed that the module works for you and want it enabled
by default, you can request it here:
https://issues.coreos.com/
Or, if you'd like, you can add it yourself. Here is an example:
https://github.com/coreos/coreos-overlay/pull/3009
Thanks.
David