View Single Post
Old 10-30-2016, 09:47 AM   #81
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by aconicq1 View Post
kernel version: 3.0.35-lab126

dmesg | tail after loading modules:
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mousedev: PS/2 mouse device common for all mice
So they load without any error messages.
IIRC - they where built for 3.0.35 but you can check with
modinfo /full/path/and/filename.ko
(full path so you are certain to get the new ones)

What is your starting point with re-compiling the modules?
I.E: Background.

As in:
Have you compiled the kernel and kernel modules for anything before?
What is your working environment (MacOSx, Windoze, Linux, *BSD, other)?
Details like that about what you have to work with.

= = = = =

Since the modules seem to load without any errors, the problem is most likely your model has a different event device ordering than the scripting expects.
This is a load time / run time variation from what is expected.

The current release does not support hotplug, so it can't support u-dev, which means the event devices can't be 'stabilized' by the kernel's auto-loader and supporting software.

Which means the code has to be hand-tweaked per device.
knc1 is offline   Reply With Quote