From: carbonated beverage <ramune@net-ronin.org>
To: sparclinux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: mouse in 2.6.8-rc1 not working
Date: Mon, 12 Jul 2004 11:36:29 +0000 [thread overview]
Message-ID: <20040712113629.GA3151@net-ronin.org> (raw)
Hi all,
The mouse attached to the Type 5 keyboard on my Ultra 5
stopped working when I upgraded from 2.6.7-rc3 to 2.6.8-rc1.
Previously, even with 2.6.7-rc3, I had to boot into 2.4.x
and "wiggle" the mouse to get it initialized. 2.6.7-rc3
recognizes that a mouse is attached. 2.6.8-rc1 doesn't.
Doing a cat /dev/input/mouse0:
2.6.7-rc3 w/o booting into 2.4.x first:
Nothing is read.
2.6.8-rc1 regardless of 2.4.x being used:
mouse device isn't seen.
2.6.7-rc3 after initializing moue under 2.4.x:
works.
CONFIG_SERIAL_SUNCORE=y
CONFIG_SERIAL_SUNZILOG=y
CONFIG_SERIAL_SUNSU=y
CONFIG_SERIAL_SUNSAB=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X\x1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Yv8
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_SUNKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_SPARCSPKR=y
-- DN
Daniel
WARNING: multiple messages have this Message-ID (diff)
From: carbonated beverage <ramune@net-ronin.org>
To: sparclinux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: mouse in 2.6.8-rc1 not working
Date: Mon, 12 Jul 2004 04:36:29 -0700 [thread overview]
Message-ID: <20040712113629.GA3151@net-ronin.org> (raw)
Hi all,
The mouse attached to the Type 5 keyboard on my Ultra 5
stopped working when I upgraded from 2.6.7-rc3 to 2.6.8-rc1.
Previously, even with 2.6.7-rc3, I had to boot into 2.4.x
and "wiggle" the mouse to get it initialized. 2.6.7-rc3
recognizes that a mouse is attached. 2.6.8-rc1 doesn't.
Doing a cat /dev/input/mouse0:
2.6.7-rc3 w/o booting into 2.4.x first:
Nothing is read.
2.6.8-rc1 regardless of 2.4.x being used:
mouse device isn't seen.
2.6.7-rc3 after initializing moue under 2.4.x:
works.
CONFIG_SERIAL_SUNCORE=y
CONFIG_SERIAL_SUNZILOG=y
CONFIG_SERIAL_SUNSU=y
CONFIG_SERIAL_SUNSAB=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_SUNKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_SPARCSPKR=y
-- DN
Daniel
next reply other threads:[~2004-07-12 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 11:36 carbonated beverage [this message]
2004-07-12 11:36 ` mouse in 2.6.8-rc1 not working carbonated beverage
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=20040712113629.GA3151@net-ronin.org \
--to=ramune@net-ronin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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.