All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11: keyboard stopped working after memory upgrade
Date: Sun, 13 Mar 2005 20:20:36 +0100	[thread overview]
Message-ID: <200503132020.36968.rjw@sisk.pl> (raw)
In-Reply-To: <20050313183635.GD1427@elf.ucw.cz>

Hi,

On Sunday, 13 of March 2005 19:36, Pavel Machek wrote:
> Hi!
> 
> > I'm just having a weird problem with 2.6.11.  Namely, the keyboard stopped
> > working after I'd added more RAM to the box (Asus L5D notebok, x86-64
> > kernel).  It works on 2.6.11-mm1.
> 
> Custom DSDT? DSDTs are known to depend on ammount of memory...

Yes, but the very same DSDT works fine on 2.6.11-mm[13].  Just for the record. :-)

Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-03-13 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 13:21 2.6.11: keyboard stopped working after memory upgrade Rafael J. Wysocki
2005-03-13 18:36 ` Pavel Machek
2005-03-13 19:20   ` Rafael J. Wysocki [this message]
2005-03-13 23:48     ` Rafael J. Wysocki

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=200503132020.36968.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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.