From: Antonio Vargas <wind@cocodriloo.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: folkert@vanheusden.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: v2.6.0-test1 - no keyboard/mouse
Date: Wed, 16 Jul 2003 00:03:44 +0200 [thread overview]
Message-ID: <20030715220344.GD2684@wind.cocodriloo.com> (raw)
In-Reply-To: <1058306246.584.1.camel@teapot.felipe-alfaro.com>
On Tue, Jul 15, 2003 at 11:57:26PM +0200, Felipe Alfaro Solana wrote:
> On Tue, 2003-07-15 at 22:46, Folkert van Heusden wrote:
> > Ehrm, hello? Has this list became silent suddenly?
> > Anyway: I just tried 2.6.0-test1 on my celeron. Boots up flawlessly. Rather
> > quick and all. X boots up, all fine.
> > Only one minor problem: the keyboard and the mouse do not work.
> > I *have* included input-core, etc.:
> > CONFIG_INPUT=y
> > CONFIG_INPUT_MOUSEDEV=y
> > CONFIG_INPUT_MOUSEDEV_PSAUX=y
> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
> > CONFIG_INPUT_EVDEV=y
> > CONFIG_INPUT_KEYBOARD=y
> > CONFIG_INPUT_MOUSE=y
> > CONFIG_INPUT_MISC=y
> > CONFIG_INPUT_PCSPKR=y
> > CONFIG_INPUT_UINPUT=y
>
> I can't think of anything except CONFIG_VGA_CONSOLE. Is it set to "y"?
what about setting these usual switches to default "y"?
It would cut a lot of problems at the first encounters
with the latest kernel.
Greets, Antonio.
--
In fact, this is all you need to know to be
a Caveman Database Programmer:
A relational database is a big spreadsheet
that several people can update simultaneously.
next prev parent reply other threads:[~2003-07-15 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 20:46 v2.6.0-test1 - no keyboard/mouse Folkert van Heusden
2003-07-15 21:35 ` Dave Jones
2003-07-15 21:57 ` Felipe Alfaro Solana
2003-07-15 22:03 ` Antonio Vargas [this message]
[not found] <Pine.LNX.4.43.0307151702570.1640-100000@morpheus>
2003-07-17 18:23 ` Folkert van Heusden
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=20030715220344.GD2684@wind.cocodriloo.com \
--to=wind@cocodriloo.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.