[lordeagle]

Thanks for your detailed explanation. I have the Kobo-stuff installed on the reader, and SSH/dropbear setup works like a charm over W-LAN.

Usbnet drivers remain a problem. I tried to compile my own usbnet.ko from scratch.
The compilation worked seemingly successful, though I can't bring 'insmod' to load it.

[root@kobo usbeth]# insmod usbnet.ko 
insmod: can't insert 'usbnet.ko': invalid module format
[root@kobo usbeth]# uname -a
Linux kobo 4.9.77 #1 SMP PREEMPT cc00b601cb7c-20230619T134503-B0619134601 armv7l GNU/Linux
[root@kobo ~]# cat /proc/version 
Linux version 4.9.77 (yuming@yuming-VirtualBox) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT cc00b601cb7c-20230619T134503-B0619134601
[root@kobo usbeth]# file usbnet.ko 
usbnet.ko: ELF 32-bit LSB relocatable, ARM, EABI5 version 1 (SYSV), BuildID[sha1]=90ac8f5579045c60902540c793476212da9d918f, with debug_info, not stripped
[root@kobo usbeth]#

modinfo against the same file on my host:

modinfo ./usbnet.ko 
filename:       /home/lordeagle/Downloads/./usbnet.ko
license:        GPL
description:    USB network driver framework
author:         David Brownell
srcversion:     AE8ADE73ECA9BD4DC9C75B0
depends:        mii
intree:         Y
vermagic:       4.9.77 SMP preempt mod_unload modversions ARMv7 p2v8 
parm:           msg_level:Override default message level (int)

Is there any evidence that my compilation process is wrong?
See https://github.com/ivy-rew/kobo-kern...psa2E/build.sh

Originally Posted by elinkser

Note that the Kobo Libra Colour, a MediaTek device like your Elipsa 2e, is using Secure Boot, which requires a signed kernel.
https://www.mobileread.com/forums/sh...52&postcount=1

Maybe try something like "dmesg | grep hash" to see if you get similar messages as for the Libra Colour?

Here's a LWN article on Verified U-Boot:
https://lwn.net/Articles/571031/

Or do we have to assume that secure-boot makes my own modules getting rejected?

Originally Posted by elinkser

But can someone compile unsigned kernel modules and add them to a signed kernel?
Apparently not:
https://android.stackexchange.com/qu...forcing-kernel

Following this explanation, I must assume that my attempts are not leading anywhere. Unless I get the device to flash a full kernel, which I wouldn't risk to experiment with without any foreknowledge