Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: parisc-linux@lists.parisc-linux.org
Cc: Andy Walker <andy@puszczka.com>
Subject: Re: [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34]
Date: Tue, 9 Mar 2004 11:03:28 +0100	[thread overview]
Message-ID: <200403091103.29310.deller@gmx.de> (raw)
In-Reply-To: <25271.193.161.152.244.1078745317.squirrel@www.puszczka.com>

On Montag, 8. März 2004 12:28, Andy Walker wrote:
> I've a B132L running Gentoo. With 2.4 I had the PS/2 keyboard working fine
> throught a Raritan Compuswitch KVM, but the mouse (wireless Intellimouse
> clone - 2 buttons pluss roller/middle) was dead. Decided to try out 2.6
> partly to excercise udev, but mostly in the hope that all the input layer
> work and PS/2 changes would bring the mouse to life. I should probably add
> that there are two PCs on the KVM - one running 2.6.3 and one running
> 2.4.24. Both run the mouse and keyboard flawlessly.
> 
> To the point. I grabbed 2.6.3-pa0 from Gentoo hppa-dev-kernel, configured
> and compiled it. The keyboard and mouse are both dead. I downloaded
> 2.6.4-rc1-pa2 from cvs.parisc-linux.org but the result is exactly the same.
> Some info below. Clues anybody?
....
> # Input Device Drivers
> #
> CONFIG_INPUT_KEYBOARD=y
> # CONFIG_KEYBOARD_ATKBD is not set

Please enable this one (CONFIG_KEYBOARD_ATKBD), and....

> # CONFIG_KEYBOARD_SUNKBD is not set
> # CONFIG_KEYBOARD_XTKBD is not set
> # CONFIG_KEYBOARD_NEWTON is not set
> CONFIG_KEYBOARD_HIL=y
> CONFIG_INPUT_MOUSE=y
> # CONFIG_MOUSE_PS2 is not set

this one too.

In the latest 2.6 kernel series, we switched from a parisc-only
PS/2 mouse/keyboard driver to the standard linux kernel PS/2
mouse keyboard drivers.

Helge

  parent reply	other threads:[~2004-03-09 10:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 11:28 [parisc-linux] No PS2 keyboard/mouse on B132L, 2.6.[34] Andy Walker
2004-03-09  5:36 ` Grant Grundler
2004-03-09 11:27   ` Andy Walker
2004-03-09 21:16     ` Matthew Wilcox
2004-03-09 21:04   ` Matthew Wilcox
2004-03-10  4:59     ` Grant Grundler
2004-03-09 10:03 ` Helge Deller [this message]
     [not found]   ` <28565.193.161.152.244.1078828435.squirrel@www.puszczka.com>
2004-03-09 21:59     ` Helge Deller
2004-03-09 22:21       ` Andy Walker
2004-03-14  7:37   ` [parisc-linux] " Martin Schulze
2004-03-14 15:28     ` M. Grabert
2004-03-14 18:12       ` Martin Schulze
2004-03-14 19:55         ` Helge Deller
2004-03-14 20:28           ` Martin Schulze
2004-03-14 21:19             ` Helge Deller
2004-03-15 17:14               ` [parisc-linux] " Martin Schulze
2004-03-15 19:46                 ` [parisc-linux] " Helge Deller
2004-03-15 20:02                   ` Andy Walker
2004-03-18  9:55                   ` Martin Schulze
2004-03-14 19:48     ` Helge Deller
2004-03-14 20:49       ` [parisc-linux] " Martin Schulze
2004-03-15  0:31         ` Grant Grundler
2004-03-15  8:42           ` Martin Schulze
2004-03-15 15:05             ` Martin Schulze
2004-03-15 22:47               ` Helge Deller
2004-03-14 20:47     ` [parisc-linux] " Martin Schulze
2004-03-14 21:24       ` Helge Deller
  -- strict thread matches above, loose matches on Subject: below --
2004-03-09 11:05 [parisc-linux] " Andy Walker
2004-03-08 11:03 Andy Walker

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=200403091103.29310.deller@gmx.de \
    --to=deller@gmx.de \
    --cc=andy@puszczka.com \
    --cc=parisc-linux@lists.parisc-linux.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