From: Matthias Hentges <mailinglisten@hentges.net>
To: Len Brown <len.brown@intel.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>, linux-kernel@vger.kernel.org
Subject: Re: [2.6.10-rc1-mm2] keyboard / synaptics not working
Date: Tue, 02 Nov 2004 19:18:02 +0100 [thread overview]
Message-ID: <1099419482.4687.5.camel@mhcln03> (raw)
In-Reply-To: <1099377976.13831.195.camel@d845pe>
Hello Len,
Am Dienstag, den 02.11.2004, 01:46 -0500 schrieb Len Brown:
[...]
> With the unmodified -mm2 tree, please build with CONFIG_PNPACPI=n
> and give that a go.
Setting CONFIG_PNPACPI=n ( which can be found in drivers/pnp btw, for
all those reading this thread ) indeed fixes the problem.
As does applying your remove_driver.patch ( with CONFIG_PNPACPI=y) from
the other other thread.
Both work-arounds also fix the asus_acpi kernel module which either
wouldn't load at all (no such device) or would load but do nothing
(empty /p/a/asus).
HTH
--
Matthias Hentges
Cologne / Germany
[www.hentges.net] -> PGP welcome, HTML tolerated
ICQ: 97 26 97 4 -> No files, no URL's
My OS: Debian SID. Geek by Nature, Linux by Choice
next prev parent reply other threads:[~2004-11-02 18:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 18:03 [2.6.10-rc1-mm2] keyboard / synaptics not working Alexander Gran
2004-11-01 0:55 ` Dmitry Torokhov
2004-11-01 2:01 ` Matthias Hentges
2004-11-01 2:31 ` Dmitry Torokhov
2004-11-01 2:45 ` Matthias Hentges
2004-11-01 4:42 ` Dmitry Torokhov
2004-11-01 19:22 ` Matthias Hentges
2004-11-02 6:46 ` Len Brown
2004-11-02 18:18 ` Matthias Hentges [this message]
2004-11-01 14:22 ` Alexander Gran
2004-11-01 15:30 ` Jesus Delgado
2004-11-01 16:10 ` Juergen Quade
2004-11-01 17:28 ` Valdis.Kletnieks
2004-11-05 1:47 ` Jesus Delgado
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 12:47 Matthieu Castet
2004-11-04 12:15 matthieu castet
2004-11-04 18:05 ` Matthias Hentges
2004-11-05 4:33 ` Valdis.Kletnieks
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=1099419482.4687.5.camel@mhcln03 \
--to=mailinglisten@hentges.net \
--cc=dtor_core@ameritech.net \
--cc=len.brown@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox