From: Dominik Brodowski <devel@brodo.de>
To: tomas szepe <kala@pinerecords.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI in 2.5 kills kbd on Via-ACPI systems [Re: kernel 2.5.10 problems]
Date: Sun, 28 Apr 2002 00:15:39 +0200 [thread overview]
Message-ID: <02042800153901.01292@sonnenschein> (raw)
In-Reply-To: <20020427150206.A30695@louise.pinerecords.com> <28493.1019938454@www26.gmx.net>
On Saturday, 27. April 2002 22:14, tomas szepe wrote:
> > 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.
Actually it is ACPI PCI-IRQ routing which has been broken since 2.5.8-pre3;
the next acpi-release ( http://sourceforge.net/projects/acpi/ ) will include
updates for that feature. For the time being, you might try one of my
patches:
x v.9 or v.12 [for acpi-20020404(*)] of my ACPI-PIC-pci-irq
rewrite, which is available at
http://www.brodo.de/english/pub/acpi/pci_irq/
or
x "Do not use IRQ 1" at
http://www.brodo.de/english/pub/acpi/20020404/bugfixes.html
Dominik
(*) acpi-20020404 got merged into 2.5.8-pre3
next prev parent reply other threads:[~2002-04-27 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 13:02 tomas szepe
[not found] ` <28493.1019938454@www26.gmx.net>
2002-04-27 22:15 ` Dominik Brodowski [this message]
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=02042800153901.01292@sonnenschein \
--to=devel@brodo.de \
--cc=kala@pinerecords.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
all inboxes | Powered by JetHome®