On 2018-06-09 14:15, Alexander Kapshuk wrote: > I had a look at the source code for kmod-25. If I read it right, dmesg > should have records along the lines of: > kmod-25/libkmod/libkmod-module.c:886: INFO(mod->ctx, "Failed > to insert module '%s': %m\n", path); > > modprobe returns Exec format error.
> Now, if my understanding of the source code above is right, you either > have CONFIG_X86_32 set in your kernel, e.i. your Elf_Ehdr is set to > Elf32_Ehdr, or the module's header is for the architecture that is > different from what is expected by the kernel. The former is definitely false. If the latter holds, it is not due to any action on my part, but due to how the module is built by the kernel build system (at the same time as the kernel proper). Again, I strongly suspect this is due to all the "objtool" churn in 4.9.106 and later. I'm afraid I'm at the limit of my patience diving into this for now. You see, I have to remove the broken kernel from grub manually every time (and then re-add it for another test), otherwise it breaks unattended boots. Sorry about that. Maybe in a few days I'll have time to sit down and track it properly. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet and on broken lists which rewrite From, fetch the TXT record for no-use.mooo.com.
