All of lore.kernel.org
 help / color / mirror / Atom feed
From: Warren Turkal <wturkal-Ly1yJZSIA8M@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [BUG] linux laptop keyboard problem since 2.5.74
Date: Sat, 19 Jul 2003 01:22:57 -0500	[thread overview]
Message-ID: <200307182149.58889.wturkal@cbu.edu> (raw)

Sorry for the crosspost, but I didn't get a response originally from the 
acpi-devel list. Also, I am not subscribed to either list. Please CC me on 
replies that should go to me.

Something got merged between 2.5.73 and 74 that has messed with my system ever 
since. Some of the keys that are activated with Fn combinations are messed up.

Some of these combinations involve turning on external monitor output and 
showing battery status.

I suspect ACPI as that was the culprit last time when I could not use the Fn 
combinations at all. I compiled my kernel with acpi as modules and the 
problems happens even when not loading the modules for acpi. I also tried 
booting with acpi=off and that did not seem to change anything.

Like I said, 2.5.73 was fine and didn't lock like 2.5.74 to 2.6.0-test1 do. So 
the bug was somewhere in that revision.

I have a Gateway 600 series laptop with 256mb ram and 1.9Ghz P4. Does anyone 
know where I should start investigating for more info.

Thanks, Warren Turkal
-- 
Treasurer, GOLUM, Inc.
http://www.golum.org

WARNING: multiple messages have this Message-ID (diff)
From: Warren Turkal <wturkal@cbu.edu>
To: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: [BUG] linux laptop keyboard problem since 2.5.74
Date: Sat, 19 Jul 2003 01:22:57 -0500	[thread overview]
Message-ID: <200307182149.58889.wturkal@cbu.edu> (raw)

Sorry for the crosspost, but I didn't get a response originally from the 
acpi-devel list. Also, I am not subscribed to either list. Please CC me on 
replies that should go to me.

Something got merged between 2.5.73 and 74 that has messed with my system ever 
since. Some of the keys that are activated with Fn combinations are messed up.

Some of these combinations involve turning on external monitor output and 
showing battery status.

I suspect ACPI as that was the culprit last time when I could not use the Fn 
combinations at all. I compiled my kernel with acpi as modules and the 
problems happens even when not loading the modules for acpi. I also tried 
booting with acpi=off and that did not seem to change anything.

Like I said, 2.5.73 was fine and didn't lock like 2.5.74 to 2.6.0-test1 do. So 
the bug was somewhere in that revision.

I have a Gateway 600 series laptop with 256mb ram and 1.9Ghz P4. Does anyone 
know where I should start investigating for more info.

Thanks, Warren Turkal
-- 
Treasurer, GOLUM, Inc.
http://www.golum.org


             reply	other threads:[~2003-07-19  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19  6:22 Warren Turkal [this message]
2003-07-19  6:22 ` [BUG] linux laptop keyboard problem since 2.5.74 Warren Turkal
2003-07-25 20:33 Grover, Andrew
2003-07-25 20:33 ` 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=200307182149.58889.wturkal@cbu.edu \
    --to=wturkal-ly1yjzsia8m@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.