[Sisuite-devel] USB keyboard not working with SystemImager -- solved!

[Bernard Li]

Hi guys:

Okay I found out what the issue is. The USB modules are named:

uhci_hcd
ohci_hcd
ehci_hcd

etc.

But the .ko files are named with dash instead of underscore:

uhci-hcd.ko
ohci-hcd.ko
ehci-hcd.ko

The function autodetect_hardware_and_load_modules will try to load the
module with underscore but you should actually use the name with the
dash.

I guess we have two ways of fixing things - one is a hackish way and
the other is the correct way.

The hackish way is just to modprobe both underscore and dash names (I
think some modules cannot make up their mind with the naming
convention...)

The proper way is to upgrade to busybox 1.4.1 which has the
CONFIG_FEATURE_MODPROBE_FANCY_ALIAS config options.

BTW - are we in some sort of code freeze for SystemImager 3.8.0 ?

Cheers,

Bernard

[Andrea Righi]

Post by Bernard Li
uhci_hcd
ohci_hcd
ehci_hcd
etc.
uhci-hcd.ko
ohci-hcd.ko
ehci-hcd.ko
The function autodetect_hardware_and_load_modules will try to load the
module with underscore but you should actually use the name with the
dash.
I guess we have two ways of fixing things - one is a hackish way and
the other is the correct way.
The hackish way is just to modprobe both underscore and dash names (I
think some modules cannot make up their mind with the naming
convention...)
The proper way is to upgrade to busybox 1.4.1 which has the
CONFIG_FEATURE_MODPROBE_FANCY_ALIAS config options.
BTW - are we in some sort of code freeze for SystemImager 3.8.0 ?

great that the bug has been found! Personally I would prefer a hackish
fix, for now... because, yes, there is the code freeze for 3.8.0 and
upgrading busybox to 1.4.1 may introduce some unwanted and unpredictable
new bugs. I'll look if it's possible to resolve in a smart way maybe
backporting the patch...

-Andrea