declan.moriartyt at ntlworld.ie
Tue Feb 17 01:50:50 PST 2004
On Mon, Feb 16, 2004 at 09:24:20PM +0100, eklirmr at wanadoo.fr enlightened us thusly
> In the last few days I've built LFS 5.0 on two different PCs, a Dell
> Dimension H266 and a more recent Dell Dimension D4100. There were no
> problems on either machine. Now I'm installing some libraries and
> utilities, following the BLFS book; no problems on the H266, and just
> one small problem on the D4100.
> I've installed gpm on both machines. On the D4100, when gpm runs at
> startup, I get the following:
> error [mice.c (18770]: imps2: PS/2 mouse failed to read id, assuming
> standard PS/2.
> The mouse behaves very strangely and so does the screen. But if I
> then do ./gpm restart, there are no error messages, and everything
> works fine.
> Both PCs do indeed have a PS/2 mouse, and I've altered the boot
> scripts to echo the values of $MDEVICE and $PROTOCOL to be sure that
> they're passed correctly. This doesn't happen on the H266, but it
> happens every time on the D4100, and it also happens when I install
> gpm on the old LFS 3.0 system on the D4100.
> >>From looking in Google and the gpm man page, I've seen that there can
> be a conflict between gpm and X, but I haven't installed X on the
> D4100 yet.
> OK, it's a minor problem and it's easily cured, but I'd like to know
> why it happens. Does anyone have any ideas?
Most of these things are protocol related. If you take a look at the gpm
man page. Try starting and stopping it manually
gpm -k kills it (check /var/run/gpm.pid is gone)
-m /dev/whatever your device is
-t protocol (type)
-o extra options; This is where the reading comes in.
At a wild guess, the mouse starts at a different communication setup
than gpm defaults to. The attempts to adjust are not 100%, but second
time it starts singing.
With best Regards,
More information about the blfs-support