Missing Kernel Modules moving from AX88U to AX86 Pro

[Jeffrey Young]

Hello everyone.

I have upgraded my router from the AX88U (388.8) to a AX86U Pro. I use UPS NUT on my router to monitor my UPS and have the Router issue shutdown commands as required when the UPS reports it is near exhaustion.

When I tried to setup NUT on the AX86U Pro (also running 388.4), I noticed that the kernel modules hid.ko and input-core are missing from the /lib directory. They were on my AX88U and also there for the AC86U and AC68U. UPS NUT requires these modules to talk to the UPS. The third required module usbhid.ko is present in this release.

Since the AX88U and AX86U Pro use different version kernels, I doubt I can just copy the modules over.

@RMerlin , Knowing there is no quick fix to this, I am wondering if there is a chance that these two modules can be included in the next release? In the meantime, I will see if I can find them on the web for the 4.19.183 kernel.

UPDATE:

Looks like this kernel version does not need hid.ko and the module input-core is now called usbcore.ko

Once I modified my startup script with the new renamed kernel module, NUT is a happy camper again.

Cheers

 

[RMerlin]

Both CONFIG_HID and CONFIG_INPUT are enabled, and compiled as part of the kernel rather than as external modules. You can view config options through zcat /proc/config.gz .

If it doesn't work, then you need tp specify which specific additionnal module your device is requiring.

 

[Digilog]

Its another reason to scrutinize OEMs and their routers made after 2000.

Because it seem they just throw these things together and either rely on users to fix or solve problems, or just ignore you entirely. Besides the obvious hope that they bank on you to buy a more modern model even though the device should last for a few decades.

 

[RandomUser777]

Its another reason to scrutinize OEMs and their routers made after 2000.

Because it seem they just throw these things together and either rely on users to fix or solve problems, or just ignore you entirely. Besides the obvious hope that they bank on you to buy a more modern model even though the device should last for a few decades.

??? so the consumer/end-user needs to dig into the firmware for devices made over the last 24 years (and forward) before purchasing?

 

[RMerlin]

Its another reason to scrutinize OEMs and their routers made after 2000.

Because it seem they just throw these things together and either rely on users to fix or solve problems, or just ignore you entirely. Besides the obvious hope that they bank on you to buy a more modern model even though the device should last for a few decades.

What are you talking about? He's referring to something that I explicitely added to Asuswrt-Merlin, has nothing to do with OEM firmware at all...

 

[Digilog]

??? so the consumer/end-user needs to dig into the firmware for devices made over the last 24 years (and forward) before purchasing?

you would think that wouldn't be an issue with established companies