From: tomas szepe <kala@pinerecords.com>
To: dmacbanay@softhome.net
Cc: linux-kernel@vger.kernel.org
Subject: ACPI in 2.5 kills kbd on Via-ACPI systems [Re: kernel 2.5.10 problems]
Date: Sat, 27 Apr 2002 15:02:06 +0200 [thread overview]
Message-ID: <20020427150206.A30695@louise.pinerecords.com> (raw)
> 2. When ACPI support is installed the kernel gives a "Keyboard not found"
> error when booting and I have to push the reset switch to reboot. This
> problem has also been mentioned before but I don't think anyone has related
> it to the ACPI support.
You're right! I tried to point out before that my system had ignored the
keyboard since about the time of 2.5.7/2.5.8, but it didn't occur to me that
the problem could be ACPI related. Indeed, after compiling 2.5.10-dj1 (2.5.10
vanilla barfs an oops at me upon boot) w/ ACPI support turned off, I found
the system perfectly responsive again -- both mouse and keyboard work.
Thus I dare assume it's highly probable that input support has been broken
for VIA chipset-based systems by the recent ACPI changes in 2.5.x.
Cheers,
Tomas Szepe
<.config> # -- the affected .config excerpt --
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_DEBUG is not set
</.config>
--
"hello it's not like i read my mail so that you have where to offer to sell me
a giant turnip or anything else thankyou." -tomas szepe <kala@pinerecords.com>
next reply other threads:[~2002-04-27 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 13:02 tomas szepe [this message]
[not found] ` <28493.1019938454@www26.gmx.net>
2002-04-27 22:15 ` Dominik Brodowski
2002-04-29 15:10 Grover, Andrew
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=20020427150206.A30695@louise.pinerecords.com \
--to=kala@pinerecords.com \
--cc=dmacbanay@softhome.net \
--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
all inboxes | Powered by JetHome®