Re: X Strangeness with mouse after new install

2004-11-23 Thread Bob Proulx
Artimus Dink wrote:
> One thing I've found is that if I do a 'modprobe
> psmouse' prior to 'startx', then X will start straight
> away and the mouse works fine... any ideas?

I am guessing that either hotplug or discover or something else is
installed on my machine and loading that module automatically while on
your machine it is not.

Add psmouse to /etc/modules so that it is always loaded.  This was
always needed previously with woody.  It is a tried and true method.

Bob


signature.asc
Description: Digital signature


Re: X Strangeness with mouse after new install

2004-11-23 Thread Artimus Dink

> 
> Not a clue.  But is your mouse outputing
> information?  Try this.  When
> you move the mouse you should see some data from the
> device.  Break
> out of it to stop it.
> 
>   sudo od -tx1 /dev/psaux
> 
> If you have mousedev loaded then the /dev/input/mice
> should work too.
> 
>   sudo od -tx1 /dev/input/mice
> 
> If you don't see anything then there is no way that
> X11 will see
> anything either.
> 
> Bob

Sorry about the empty reply... caffiene is a bad idea
this late in the evening...

I definately get output from both sudo commands, and
'lsmod' confirms that the modules are loaded after I
manage to get X up and working.  Again, I tried adding
psmouse and mousedev to /etc/modules, but in that case
X starts but the mouse doesn't work at all.

One thing I've found is that if I do a 'modprobe
psmouse' prior to 'startx', then X will start straight
away and the mouse works fine... any ideas?






__ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 




Re: X Strangeness with mouse after new install

2004-11-23 Thread Artimus Dink

--- Bob Proulx <[EMAIL PROTECTED]> wrote:

> Artimus Dink wrote:
> > (**) Option "Device" "/dev/psaux"
> > (EE) xf86OpenSerial: Cannot open device /dev/psaux
> > No such device.
> > (EE) Configured Mouse: cannot open input device
> > (EE) PreInit failed for input device "Configured
> Mouse"
> > [...]
> > (**) Option "Device" "/dev/input/mice"
> > (EE) xf86OpenSerial: Cannot open device
> > /dev/input/mice
> > No such device.
> 
> Hmm...
> 
> > If I try 'startx' again, I get this...
> 
> That seems really bizarre to me.  I am sure most
> people are not seeing
> such strange stuff.
> 
> > someone suggested adding mousedev and pmouse to
> > /etc/modules.  If I do this, X starts on the first
> > try, but the mouse doesn't work at all.
> 
> That seems reasonable.  I usually have those on
> woody machines.  Sarge
> has both hotplug and discover and one of those loads
> those drivers for
> me at system boot time.
> 
> > I looked at /etc/X11/XF86Config-4 and found that I
> > have entries for "Configured Mouse" at
> "/dev/psaux"
> > and "Generic Mouse" at "/dev/input/mice".  This
> struck
> > me as a bit odd, but I have an x86 machine running
> > Debian Sarge... its XF86Config-4 is set up the
> same
> > way and X has always worked flawlessly.
> 
> That looks normal for me.  That is how you can have
> both a (im)ps2
> mouse and a usb mouse at the same time.
> 
> > Can someone tell me what's going on?  I've run
> Fedora
> 
> Not a clue.  But is your mouse outputing
> information?  Try this.  When
> you move the mouse you should see some data from the
> device.  Break
> out of it to stop it.
> 
>   sudo od -tx1 /dev/psaux
> 
> If you have mousedev loaded then the /dev/input/mice
> should work too.
> 
>   sudo od -tx1 /dev/input/mice
> 
> If you don't see anything then there is no way that
> X11 will see
> anything either.
> 
> Bob
> 
> 

> ATTACHMENT part 2 application/pgp-signature
name=signature.asc





__ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 




Re: X Strangeness with mouse after new install

2004-11-23 Thread Slava Risenberg
See my answer for "kdm and psaux" post
http://lists.debian.org/debian-amd64/2004/11/msg00181.html post

-- 
Slava Risenberg 




Re: X Strangeness with mouse after new install

2004-11-22 Thread Bob Proulx
Artimus Dink wrote:
> (**) Option "Device" "/dev/psaux"
> (EE) xf86OpenSerial: Cannot open device /dev/psaux
>   No such device.
> (EE) Configured Mouse: cannot open input device
> (EE) PreInit failed for input device "Configured Mouse"
> [...]
> (**) Option "Device" "/dev/input/mice"
> (EE) xf86OpenSerial: Cannot open device
> /dev/input/mice
>   No such device.

Hmm...

> If I try 'startx' again, I get this...

That seems really bizarre to me.  I am sure most people are not seeing
such strange stuff.

> someone suggested adding mousedev and pmouse to
> /etc/modules.  If I do this, X starts on the first
> try, but the mouse doesn't work at all.

That seems reasonable.  I usually have those on woody machines.  Sarge
has both hotplug and discover and one of those loads those drivers for
me at system boot time.

> I looked at /etc/X11/XF86Config-4 and found that I
> have entries for "Configured Mouse" at "/dev/psaux"
> and "Generic Mouse" at "/dev/input/mice".  This struck
> me as a bit odd, but I have an x86 machine running
> Debian Sarge... its XF86Config-4 is set up the same
> way and X has always worked flawlessly.

That looks normal for me.  That is how you can have both a (im)ps2
mouse and a usb mouse at the same time.

> Can someone tell me what's going on?  I've run Fedora

Not a clue.  But is your mouse outputing information?  Try this.  When
you move the mouse you should see some data from the device.  Break
out of it to stop it.

  sudo od -tx1 /dev/psaux

If you have mousedev loaded then the /dev/input/mice should work too.

  sudo od -tx1 /dev/input/mice

If you don't see anything then there is no way that X11 will see
anything either.

Bob



signature.asc
Description: Digital signature


X Strangeness with mouse after new install

2004-11-21 Thread Artimus Dink
I have a fresh install of Debian amd64 / pure64.  Most
everything seems to work fine, but I have a hard time
getting X started.  Initially I disabled xdm, but it
didn't help any.

Basically, I'll type 'startx', wait a few seconds and
x will fail.  The last few lines of
/var/log/XFree86.0.log read...

(II) Keyboard "Generic Keyboard" handled by legacy
driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
(EE) xf86OpenSerial: Cannot open device /dev/psaux
No such device.
(EE) Configured Mouse: cannot open input device
(EE) PreInit failed for input device "Configured
Mouse"
(II) UnloadModule: "mouse"
(**) Option "Protocol" "ImPS/2"
(**) Generic Mouse: Protocol: "ImPS/2"
(**) Option "SendCoreEvents" "true"
(**) Generic Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(EE) xf86OpenSerial: Cannot open device
/dev/input/mice
No such device.
(EE) Generic Mouse: cannot open input device
(EE) PreInit failed for input device "Generic Mouse"
(II) UnloadModule: "mouse"
(WW) No core pointer registered
No core pointer

Fatal server error:
failed to initialize core devices


If I try 'startx' again, I get this...


(II) Keyboard "Generic Keyboard" handled by legacy
driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons,
Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Configured Mouse: Buttons: 5
(**) Option "Protocol" "ImPS/2"
(**) Generic Mouse: Protocol: "ImPS/2"
(**) Option "SendCoreEvents" "true"
(**) Generic Mouse: always reports core events
(**) Option "Device" "/dev/input/mice"
(**) Option "Emulate3Buttons" "true"
(**) Generic Mouse: Emulate3Buttons, Emulate3Timeout:
50
(**) Option "ZAxisMapping" "4 5"
(**) Generic Mouse: ZAxisMapping: buttons 4 and 5
(**) Generic Mouse: Buttons: 5
(II) XINPUT: Adding extended input device "Generic
Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Configured
Mouse" (type: MOUSE)
(II) Configured Mouse: ps2EnableDataReporting:
succeeded
(II) Generic Mouse: ps2EnableDataReporting: succeeded
Warning: font renderer for ".pcf" already registered
at priority 0
Warning: font renderer for ".pcf.Z" already registered
at priority 0
Warning: font renderer for ".pcf.gz" already
registered at priority 0
Warning: font renderer for ".snf" already registered
at priority 0
Warning: font renderer for ".snf.Z" already registered
at priority 0
Warning: font renderer for ".snf.gz" already
registered at priority 0
Warning: font renderer for ".bdf" already registered
at priority 0
Warning: font renderer for ".bdf.Z" already registered
at priority 0
Warning: font renderer for ".bdf.gz" already
registered at priority 0
Warning: font renderer for ".pmf" already registered
at priority 0
(II) RADEON(0): [drm] removed 1 reserved context for
kernel
(II) RADEON(0): [drm] unmapping 8192 bytes of SAREA
0xff36a000 at 0x2a9dc4a000
=

After which X will hang, then display garbage. Usually
on the third or forth try, X starts and everything
seems to work fine.

I did a bit of Googling for similar situations, and
someone suggested adding mousedev and pmouse to
/etc/modules.  If I do this, X starts on the first
try, but the mouse doesn't work at all.

I've checked to see that the mouse devices exist...

[EMAIL PROTECTED]:~$ ls -al /dev/psaux /dev/input/mice
crw-rw  1 root root 13, 63 2004-09-18 17:53
/dev/input/mice
crw---  1 root root 10,  1 2004-09-18 17:51
/dev/psaux

I looked at /etc/X11/XF86Config-4 and found that I
have entries for "Configured Mouse" at "/dev/psaux"
and "Generic Mouse" at "/dev/input/mice".  This struck
me as a bit odd, but I have an x86 machine running
Debian Sarge... its XF86Config-4 is set up the same
way and X has always worked flawlessly.  However, I
tried removing one or the other entry on my amd64 to
see if this would help.  Either it made no difference
or X didn't work at all.

Other relevant information...

Video Card: ATI-Radeon 9200 (using debian ati driver)
Kernel Version: 2.6.9-9-amd64-k8
XFree86 version: 4.3.0.1

Can someone tell me what's going on?  I've run Fedora
on this machine without any problems (well, without
this problem), so I don't think it's a hardware
issue... I can post my entire XF86Config-4 file and my
XFree86 log files if it would help, but I thought I'd
ask first.  Thanks in advance.





__ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com