Am 18.03.2023 um 10:46 schrieb Norbert Lange:
Hello,
BusyBox first tries to pass the module the the kernel via
filedescriptor, this method only accepts uncompressed files. Yielding
that error message.
Only then it will decompress the module and try again.
Regards, Norbert.
Ok, understood.
However, why even does it not work with the filedescriptor
Kernel setting
[*] Support in-kernel module decompression
should enable this to work not needing the modprobe to fallback to
uncompress and try it again - or not?
https://bugs.busybox.net/show_bug.cgi?id=14041
On Sat, 18 Mar 2023, 10:41 Service IIT (Mayer EMI),
<[email protected]> wrote:
Am 18.03.2023 um 02:57 schrieb Khem Raj:
> On Fri, Mar 17, 2023 at 2:10 PM Service IIT (Mayer EMI)
> <[email protected]> wrote:
>> Hi
>>
>> Can somone help how to get rid of the message "Invalid ELF
header magic:
>> !=ELF" of busybox when using moprobe with compressed kernel modules
>>
> Something is not in ELF format. Can you provide more details of what
> you are trying to do?
Having compiled the kernel (6.1.19) with
Module compression mode (XZ) --->
[*] Support in-kernel module decompression
Having compiled busybox with
Archival Utilities --->
[*] Make tar, rpm, modprobe etc understand .xz data
[*] Make tar, rpm, modprobe etc understand .gz data
Modules are succesfully compressed compiled
Booting up brings
"Invalid ELF header magic: !=ELF" message for each loaded module,
modules are loaded and working (show up in lsmod and functionality
is given)
running modprobe manually have the same result
>> BusyBox v1.36.0 (2023-03-17 16:25:58 UTC) multi-call binary.
--
- M -
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
