All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "Terje Fĺberg" <terje_fb@yahoo.no>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.5.73 - keyboard failure, repost no. 3
Date: Thu, 26 Jun 2003 22:45:17 +0200	[thread overview]
Message-ID: <20030626224517.C5633@ucw.cz> (raw)
In-Reply-To: <20030623203224.1180.qmail@web12902.mail.yahoo.com>; from terje_fb@yahoo.no on Mon, Jun 23, 2003 at 10:32:24PM +0200

On Mon, Jun 23, 2003 at 10:32:24PM +0200, Terje Fĺberg wrote:
> 
> Hi all, 
> 
> (and yes, I read the post-halloween docs!)
> 
> Just a note on the side: 2.5.73 fails to make use of
> the keyboard on my Mitac 8375 Laptop. It correctly
> identifies the controller AND the keyboard, but no
> keypresses are recognized.
> 
> What can I do to track this down?

	#define DEBUG

in

	drivers/input/serio/i8042.c

then recompile and send me the output of that.

> 
> This problem exists at least since 2.5.67.  Linux-2.4 
> runs perfectly.
> 
> Please see the .config and kernel output
> ...
> pc110pad: I/O area 0x15e0-0x15e4 un use.
> i8042.c: Detected active multiplexing controller, rev
> 1.1
> serio: i8042 AUX0 port at 0x60,0x64 irq 12
> serio: i8042 AUX1 port at 0x60,0x64 irq 12
> Synaptics Touchpad, model 1
>   Firware: 5.1
>   180 degree mounted touchpad
>   Sensor: 15
>   new absolute packet format
>   Touchpad has extended capability bits
>   -> four buttons
>   -> multifinger detection
>   -> palm detection
>  input: Synaptics Synaptics Touchpad on isa0060/serio3
> serio: i8042 AUX3 port at 0x60,0x64 irq 12
> serio: i8042 AUX4 port at 0x60,0x64 irq 12
> input: AT Set 2 keyboard on isa006 0/serio0
> serio: i8042 KBD port at 0x60,0x64 irq1
> ...
> 

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2003-06-26 20:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-22 18:53 Linux 2.5.73 Linus Torvalds
2003-06-22 20:06 ` Alex Goddard
2003-06-22 20:15   ` Andrew Morton
2003-06-22 22:53     ` Greg KH
2003-06-22 23:31       ` Andrew Morton
2003-06-22 20:46 ` Florin Iucha
2003-06-22 21:17   ` Alex Goddard
2003-06-22 21:45     ` Alex Goddard
2003-06-22 21:58     ` Alex Goddard
2003-06-23  2:52       ` Greg KH
2003-06-22 23:44 ` 2.5.73: ALSA ISA pnp_init_resource_table compile errors Adrian Bunk
2003-06-23  0:08   ` Adam Belay
2003-07-03  2:53     ` Adrian Bunk
2003-07-03 19:03       ` Adam Belay
2003-07-04 12:11         ` Adrian Bunk
2003-07-15 22:47           ` Adam Belay
2003-07-16 18:22             ` Adrian Bunk
2003-07-16 18:43               ` Adam Belay
2003-07-19 22:03                 ` Adrian Bunk
2003-07-20  5:59                 ` Jochen Hein
2003-08-09 20:40                 ` Adrian Bunk
2003-06-23  0:31 ` 2.5.73: acorn.c compile error Adrian Bunk
2003-06-23 10:13 ` Linux 2.5.73 - Won't compile using oldconfig - config attached vlad
2003-07-02 14:31   ` John Covici
2003-07-02 16:38     ` Greg KH
2003-06-23 20:32 ` Linux 2.5.73 - keyboard failure, repost no. 3 Terje Fåberg
2003-06-26 20:45   ` Vojtech Pavlik [this message]
2003-06-27 14:22     ` Terje Fåberg
2003-06-27 19:03       ` Vojtech Pavlik
2003-06-28  9:11         ` Terje Fåberg
2003-06-28  9:37           ` Vojtech Pavlik
2003-06-28 11:40             ` Terje Fåberg

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=20030626224517.C5633@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terje_fb@yahoo.no \
    /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.