From: Steven Rostedt <rostedt@goodmis.org>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: mousedev auto load on 2.6.14-rc{2,3}
Date: Thu, 01 Dec 2005 14:20:18 -0500 [thread overview]
Message-ID: <1133464818.7130.27.camel@localhost.localdomain> (raw)
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
next reply other threads:[~2005-12-01 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 19:20 Steven Rostedt [this message]
2005-12-01 21:34 ` mousedev auto load on 2.6.14-rc{2,3} Greg KH
2005-12-01 21:46 ` Steven Rostedt
2005-12-01 21:50 ` Greg KH
2005-12-01 21:57 ` Steven Rostedt
2005-12-01 21:51 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1133464818.7130.27.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox