[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Heikki Vatiainen <hessu@cs.tut.fi>] 2.1.7 ok except gpm not ok



This is a forwarded problem report.  Thought you might like to know
about it.

--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
--- Begin Message ---
The 2.1.7 installation with 1999-02-11 disks went well and the 
default selection after reboot gave no errors, except of gpm 
which did not work.

Here's my hardware, after that I'll describe what went wrong 
with gpm:

CONFIGURATION:
  machine:    Abit BH6 mother board, Celeron 300A overclocked to 450MHz
  memory:     128MB SDRAM
  disk:       IBM Deskstar 8GB
  scsi:       none
  sound:      none
  video card: Matrox Millennium G200 (8MB)
  cd-rom:     Mitsumi 32x (IDE/ATAPI)
  net card:   3Com 905b
  mouse:      Logitech mouseman ps/2, model M-S35, 3 buttons

The mouse shown at
http://www.cpu2000.com/product_htm/log_ps2_3btn.htm
looks like the one I have, except my mouse has light gray cord 
and black and white Logitech logo :)

Anyway, I've seen lots of those and think it's quite common 
model.

When I was going through the configure phase of installation, 
and it was time for gpm to get configured, I choose to run 
gmp-mouse-test. Testing went well until it was time to try
the new mouse configuration:

 Well, it seems like your mouse is already detected:
 it is on the device "/dev/psaux", and speaks the protocol "ps2"
 **********************************************************
 Where is your mouse [/dev/ttyS0]? 
 > /dev/psaux
 What type is your mouse (or help) [ms]? 
 > ps2
 Set the responsiveness (normally not needed) []? 
 > 
 Do you want to add any additional arguments [-l "a-zA-Z0-9_.:~/\300-\326\330-\366\370-\377"]? 
 > 
 Do you want to test this configuration (y/N)? y
 gpm -m /dev/psaux -t ps2 -l "a-zA-Z0-9_.:~/\300-\326\330-\366\370-\377"
 Finish testing by typing Ctrl-D
 gpm: freopen(stderr) failed

The same thing happens also when running gpm by hand:

jopus:~# /usr/sbin/gpm -m /dev/psaux -t ps2
jopus:~# gpm: freopen(stderr) failed

As you can see, gpm dies when it tries to freopen(). I tried to 
strace it, but it was impossible to do, since it fork()s a child 
and the failure happens after that. There is no command line 
option to prevent it from backgrounding itself.

I also tried gpm packages from hamm and potato, gpm_1.13-5.deb 
and gpm_1.16.0-3.deb respectively, with no luck. However, the 
potato version uses syslog and outputs these lines when it dies:

Feb 14 17:52:23 jopus gpm[194]: oops() invoked from gpn.c(463)
Feb 14 17:52:23 jopus gpm[194]: freopen(stderr) failed: Operation not supported by device

I also tried 2.0.35 psaux module (insmod -f psaux.o), but it
did not help.

I know the mouse works, since it worked earlier with 2.1.[2-4] 
disks and works with FreeBSD. Also, when the psaux module is 
isntalled, dmesg shows this:

PS/2 auxiliary pointing device detected -- driver installed.

One thought just occurred. cat /proc/interrupts does not show 
ps2 mouse. On a 2.2.1 box it does.

jopus:~# cat /proc/interrupts 
 0:     294192   timer
 1:       1726   keyboard
 2:          0   cascade
 5:       2227   eth0
 8:          2 + rtc
13:          1   math error
14:       4452 + ide0
15:          0 + ide1

linux-2.2.1# cat /proc/interrupts 
           CPU0       
  0:   16525576          XT-PIC  timer
  1:      41683          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  7:     252227          XT-PIC  eth0
  9:     188188          XT-PIC  eth1
 10:    6391960          XT-PIC  nicstar
 12:     380042          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:     109006          XT-PIC  ide0
 15:     318023          XT-PIC  ide1
NMI:          0


Does anyone have suggestions what to do next?

// Heikki
-- 
Heikki Vatiainen                  * hessu@cs.tut.fi
Tampere University of Technology  * Tampere, Finland





--  
To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



--- End Message ---

Reply to: