Hi,

When I compiled my 2.4.22 kernel with the new nvidia driver, I had lost my mouse in X. The problem was that upon bootup, the error was something like "can't locate module mousedev" or something like. I did a "find" in /lib/modules and realized that this directory did not exist in my newer kernel directory tree: "kernel/drivers/input", but it existed in others:
/usr/src/kernel-source-2.4.22-hs1# find /lib/modules/ -name "input"
/lib/modules/2.4.18-bf2.4/kernel/drivers/input
/lib/modules/2.4.22-1-686/kernel/drivers/input
/lib/modules/2.4.22-nvidia/kernel/drivers/input


This I realized only after hours of searching google why a usb mouse wouldn't work in 2.4.22. I tried a host of things, but no solution. Only a little while ago it occurred to me that the boot process is looking for a module mousedev, which doesn't seem to exist. But the little red light on the mouse blinked during the boot process and a usb mouse *was* being found. And it struck me, I had compiled the input devices support (keyboard, mouse, etc) *into* the kernel and not as modules. And usb support, at least parts of it, were compiled as modules. I recompiled the kernel with the input devices as modules and sure enough got the /kernel/drivers/input directory. Rebooted and tastes sweet taste of success when the cute cursor obeyed my commands passed through the sleek mouse :)

So, as per my understanding, compile the input devices support as modules if your bootup process complains that it couldn't find mousedev.

HTH others too, because while googling I found quite a few messages with similar symptoms but with no solutions that seemed to solve the reported problem.
regards,
->HS


Keywords:
mousedev input 2.4.22 kernel menuconfig input driver kernel boot can't cannot find module linux make-kpkg nvidia 4496
--
(Remove all underscores,_if any_, from my email address to get the correct one. Apologies for the inconvenience, but this is to reduce spam.)




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]


Reply via email to