[3935] in Release_7.7_team
We can buy the S50!
daemon@ATHENA.MIT.EDU (Bill Cattey)
Thu Jul 17 18:02:01 2003
From: Bill Cattey <wdc@MIT.EDU>
To: owls@mit.edu
Cc: release-team@mit.edu
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1058479319.15076.106.camel@tokata.mit.edu>
Mime-Version: 1.0
Date: 17 Jul 2003 18:01:59 -0400
IBM today delivered the exact test system.
I confirmed that the new installer successfully installs the system.
One snag: I was a teeny bit careless and didn't notice that the
system ships with a USB scroll-wheel optical mouse instead of the
basic PS2 3 button mouse.
Popular linux lore is that USB mice "just work".
Well that's fine if you don't mind waiting an extra half minute for the
X server to start!
This probably is not a big deal for private systems, but I think it
would be an issue for quickstations, and probably with clusters. My own
sense was, "What's wrong? Why isn't X starting?".
IBM has agreed to take up the slack and hand us different mice rather
than starting the custom configuration clock again.
Mitch and I have done additional testing, and our current observation is
that if you install with a PS2 mouse plugged in, the USB mouse works
fine thereafter. What's probably going on is that the mouse discovery
logic is inverted.
QUESTION: Do we want to request a DIFFERENT custom build with the ole
reliable mouse?
RECOMMENDATION: NO. Let's just go with what we have, install PS2 mice
to start, and continue to pursue a software remedy, expecting USB mice
to be ok long term.
-wdc
