mousedev auto load on 2.6.14-rc{2,3}
Hi,
Using the same config between 2.6.14 and 2.6.15-rc2 (and with rc3, haven't tried rc4). The mousedev gets auto loaded on 2.6.14 but does not with 2.6.15-rc{2,3}. Did something change to prevent the auto loading of mousedev?
So on 2.6.14, the X server starts without a problem on boot up. But now on 2.6.15-rc2 it doesn't (missing mouse pointer). Yes I know that I can add this to the modules.conf file, but I'm curious to what changed.
I'm using Debian/unstable.
-- Steve
Quoted 6 lines · Steven Rostedt
Hi,
Using the same config between 2.6.14 and 2.6.15-rc2 (and with rc3, haven't tried rc4). The mousedev gets auto loaded on 2.6.14 but does not with 2.6.15-rc{2,3}. Did something change to prevent the auto loading of mousedev?
This needs to be a FAQ somewhere. This is a known bug in Debian's hotplug/udev package that is being worked on.
It's not a kernel bug, but a userspace one. Other distros do not have this issue, perhaps I could recommend a different one for you? :)
thanks,
greg k-h
Quoted 8 lines · Greg KH
Quoted 6 lines · Steven Rostedt
Hi,
Using the same config between 2.6.14 and 2.6.15-rc2 (and with rc3, haven't tried rc4). The mousedev gets auto loaded on 2.6.14 but does not with 2.6.15-rc{2,3}. Did something change to prevent the auto loading of mousedev?
Quoted 6 lines
This needs to be a FAQ somewhere. This is a known bug in Debian's hotplug/udev package that is being worked on.
It's not a kernel bug, but a userspace one. Other distros do not have this issue, perhaps I could recommend a different one for you? :)
Actually, I never said it was a kernel bug :)
I was just wondering what changed between 2.6.14 and 2.6.15-rc2 to break debian's hotplug/udev packages.
As for another distro? Hmm. I started with Slackware, switched to RedHat because of the RPMs, toyed with Gentoo (too much work), toyed with SuSE (too commercial), then left RedHat (because of RPMs!) and have loved debian since (too much work only when I do too much, like updating a lot in the unstable release ;)
-- Steve
Quoted 13 lines · Steven Rostedt
Quoted 11 lines · Greg KH
Quoted 6 lines · Steven Rostedt
Hi,
Using the same config between 2.6.14 and 2.6.15-rc2 (and with rc3, haven't tried rc4). The mousedev gets auto loaded on 2.6.14 but does not with 2.6.15-rc{2,3}. Did something change to prevent the auto loading of mousedev?
This needs to be a FAQ somewhere. This is a known bug in Debian's hotplug/udev package that is being worked on.
Quoted 8 lines
Quoted 3 lines
It's not a kernel bug, but a userspace one. Other distros do not have this issue, perhaps I could recommend a different one for you? :)
Actually, I never said it was a kernel bug :)
I was just wondering what changed between 2.6.14 and 2.6.15-rc2 to break debian's hotplug/udev packages.
The input core changed the way it exports its information in sysfs. Now it properly shows the heirachy of input devices (look at the difference in /sys/class/input in 2.6.14 and 2.6.15-rc2.) A recent version of udev is required to be updated to handle this properly, but if you are on unstable, you should already have that change.
Hope this helps explain things.
greg k-h
Quoted 2 lines · Steven Rostedt
As for another distro? Hmm. I started with Slackware, switched to RedHat
...
Oh, if I do switch from Debian, it will probably be to Unbuntu (but that's not a far move).
-- Steve
Quoted 9 lines · Greg KH
The input core changed the way it exports its information in sysfs. Now it properly shows the heirachy of input devices (look at the difference in
/sys/class/inputin 2.6.14 and 2.6.15-rc2.) A recent version of udev is required to be updated to handle this properly, but if you are on unstable, you should already have that change.Hope this helps explain things.
Yes it does, thanks!
I guess it's time to do another apt-get update ;-)
-- Steve