I also asked this directly of Aivils Stoss, but
may be it is more appropriate here:
I am trying the bruby patch on a Debian "sarge"
(=next official Debian system) system. It has a
package ("kernel-package") that makes building a
new kernel-image absolutely painless.
Unfortunately the patch fails on a Debian
Kernel-source of 2.4.20. I have not investigated
why, but the reason no doubt is that Debian
patches the kernel too. I don't know exactly with
what and why.
So I downloaded the 2.4.20 kernel from the kernel
ftp and of course the patch applies perfectly.
I did not make any changes to the kernel other
than the patch and compiled it.
It boots fine. There are no messages of note.
However, X does not run, complaining about the
mouse device.
If I include mousedev.o it starts, pointing X at
/dev/psaux, but the mousecursor won't move.
X will fail when I point it at /dev/input/mouse0.
The failure is "can't open <...> device does not
exist".
The nearest I can figure, since I made no changes
to the kernel or the patch, it has to be my
distro. and/or my implementation of the patch.
The /dev/input dir. already existed, with its
entries mouse0.. etc.. The link between
/dev/mouse and /dev/input/mice also exists.
To eliminate more, I ran the plain Linux 2.4.20
kernel without the patch and that also runs X
fine, either with or without mousedev, pointing X
at /dev/psaux.
I am looking for a suggestion on where to look
next on getting this great idea to run.
Unfortunately I only have Debian distros, 3 of them.
I also put the /etc/hotplug scripts in the dir.
but I don't think that has anything to do with it.
BTW, mouse is PS/2, kbd is AT, video card is
NVidia TNT AGP with 32MB. Nvidia driver is
installed and runs fine on a non-bruby system.
Thanks!
Hugo Vanwoerkom
The following signature is automatically
added by the web email service I use,
which is beyond my control:
=======================================
Help the planet each day! It's free and easy:
http://www.Care2.com/dailyaction/
|
