All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew McGregor <andrew@indranet.co.nz>
To: Andres Salomon <dilinger@voxel.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.x inspiron touchpad breakage
Date: Fri, 10 Jan 2003 02:43:57 +1300	[thread overview]
Message-ID: <39260000.1042119837@localhost.localdomain> (raw)
In-Reply-To: <pan.2003.01.09.08.27.53.688647@voxel.net>

Works for me on an Inspiron 8000.  The trackpoint does not, which is a 
known bug.  Of course, the 3800 might be different...

Have you been bitten by the input layer configuration issue?  Here's what I 
have:

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y

Andrew

--On Thursday, January 09, 2003 03:27:54 -0500 Andres Salomon 
<dilinger@voxel.net> wrote:

> 2.5.54 and 2.5.55 do not appear to initialize the touchpad on my Dell
> Inspiron 3800.  No mouse device is detected until I plug a normal ps/2
> mouse into the laptop.  I assume this is some weird bios thing.  2.4.x
> works fine with it.  Does anyone have suggestions about where to look for
> any changed in the 2.5 series that might've broken it, or any patches that
> fix it?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>



  reply	other threads:[~2003-01-09 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09  8:27 2.5.x inspiron touchpad breakage Andres Salomon
2003-01-09 13:43 ` Andrew McGregor [this message]
2003-01-10  4:54   ` Andres Salomon
2003-01-10  8:59   ` Niels den Otter

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=39260000.1042119837@localhost.localdomain \
    --to=andrew@indranet.co.nz \
    --cc=dilinger@voxel.net \
    --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 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.