public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: "Maciej Soltysiak" <solt@dns.toxicfilms.tv>
Cc: "Kernel Mailinglist" <linux-kernel@vger.kernel.org>
Subject: No mouse wheel under 2.6.1 [Was: Re: Where are 2.6.x upgrade notes?]
Date: 14 Jan 2004 02:45:25 -0500	[thread overview]
Message-ID: <873caj0y96.fsf_-_@stark.xeocode.com> (raw)
In-Reply-To: <003801c3d9c4$2c2dead0$0e25fe0a@southpark.ae.poznan.pl>

"Maciej Soltysiak" <solt@dns.toxicfilms.tv> writes:

> > Upgrade FAQ somewhere like there was with 2.4?
>
> Kind of, yes. A lengthy document, but still...
> I think the 'Known Gotchas' section could be extended by
> new problems that might appear. ALSA being muted issue
> is not included there.

Well I think ALSA being muted will catch lots of people. As luck would have it
it was the one thing I knew about in advance and it didn't help. As far as I
can tell the Alsa i810 driver just doesn't produce audio at all. I tried both
the kernel source and the 1.0.1 source. Thankfully the OSS drivers still work.

But I'm still stuck with no mouse wheel. I'm really weirded out by this. I've
tried both /dev/psaux and /dev/input/mouse0 and neither allow X to receive
anything for the mouse wheel. 

I'm using protocol MousemanPlusPS/2 with this logitech M-C48 mouse, which has
always worked fine in the past. I just verified it still works fine under
2.4.23pre4 with the same version of X.

Does it work for anyone else?

-- 
greg


  parent reply	other threads:[~2004-01-14  7:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  7:55 Where are 2.6.x upgrade notes? Greg Stark
2004-01-13 10:58 ` Maciej Soltysiak
2004-01-13 19:59   ` Dave Jones
2004-01-14  7:45   ` Greg Stark [this message]
2004-01-14  7:51     ` No mouse wheel under 2.6.1 [Was: Re: Where are 2.6.x upgrade notes?] Ralf Hildebrandt
2004-01-14 23:57     ` Thomas Molina
2004-01-17 15:20     ` Joaquim Fellmann
2004-01-17 20:37       ` Greg Stark
2004-01-17 23:18         ` Vojtech Pavlik

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=873caj0y96.fsf_-_@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=solt@dns.toxicfilms.tv \
    /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