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

Bug#367026: marked as done (linux-image-2.6.15-1-486: HID sermouse driver fails to detect Logitech mouse on ttyS0)

Your message dated Wed, 5 May 2010 23:43:47 +0200
with message-id <20100505214347.GA5174@galadriel.inutil.org>
and subject line Re: Nope, stll doesn't work
has caused the Debian Bug report #367026,
regarding linux-image-2.6.15-1-486: HID sermouse driver fails to detect Logitech mouse on ttyS0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
367026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367026
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.15-1-486
Version: 2.6.15-8
Severity: normal


Using the mousedev module doesn't work with sermouse, for my mouse (the 
mouse is not detected, as evidenced by udev not create a new 
/dev/input/mouse0 when modprobe sermouse is performed, and X loading, 
but with a frozen mouse pointer (because /dev/input/mice always exists 
when mousedev is in use, but there really isn't a detected mouse).

My mouse is an old Logitech (which uses the Microsoft protocol, when 
using /dev/ttyS0 for X) PS/2 mouse with a PS/2 mouse to serial computer 
adapter (which works, since specifying /dev/ttyS0 and Microsoft mode 
results in a working mouse for X).

This is probably an upstream issue, as I found one reference while 
Googling.  Unfortunately there didn't seem to be any followups, only an 
indication that it didn't work.  The URL of that message is:

http://www.ussg.iu.edu/hypermail/linux/kernel/0312.2/0778.html

Cheers,

Daniel


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (300, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.6.15-1-486
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.15-1-486 depends on:
ii  module-init-tools             3.2.2-2    tools for managing Linux
kernel mo ii  yaird [linux-initramfs-tool]  0.0.12-9   Yet Another
mkInitRD

-- debconf information:
  linux-image-2.6.15-1-486/postinst/kimage-is-a-directory:
  linux-image-2.6.15-1-486/preinst/initrd-2.6.15-1-486:
  linux-image-2.6.15-1-486/preinst/overwriting-modules-2.6.15-1-486:
true linux-image-2.6.15-1-486/postinst/create-kimage-link-2.6.15-1-486:
true linux-image-2.6.15-1-486/preinst/lilo-has-ramdisk:
  linux-image-2.6.15-1-486/preinst/lilo-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/bootloader-error-2.6.15-1-486:
  linux-image-2.6.15-1-486/prerm/removing-running-kernel-2.6.15-1-486:
true linux-image-2.6.15-1-486/preinst/elilo-initrd-2.6.15-1-486: true
  linux-image-2.6.15-1-486/postinst/depmod-error-2.6.15-1-486: false
  linux-image-2.6.15-1-486/preinst/abort-install-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/old-initrd-link-2.6.15-1-486: true
  linux-image-2.6.15-1-486/prerm/would-invalidate-boot-loader-2.6.15-1-486:
true linux-image-2.6.15-1-486/preinst/abort-overwrite-2.6.15-1-486:
  linux-image-2.6.15-1-486/postinst/old-dir-initrd-link-2.6.15-1-486:
true
linux-image-2.6.15-1-486/postinst/bootloader-test-error-2.6.15-1-486:
linux-image-2.6.15-1-486/preinst/bootloader-initrd-2.6.15-1-486: true
linux-image-2.6.15-1-486/postinst/old-system-map-link-2.6.15-1-486:
true
linux-image-2.6.15-1-486/preinst/already-running-this-2.6.15-1-486:
linux-image-2.6.15-1-486/preinst/failed-to-move-modules-2.6.15-1-486:
linux-image-2.6.15-1-486/postinst/depmod-error-initrd-2.6.15-1-486:
false

--- End Message ---
--- Begin Message --- 
On Wed, May 05, 2010 at 01:24:41AM -0400, Daniel Dickinson wrote:
> On Sat, 1 May 2010 23:08:54 +0200
> Moritz Muehlenhoff <jmm@inutil.org> wrote:
> 
> > On Wed, Feb 25, 2009 at 08:43:10PM -0500, Daniel Dickinson wrote:
> > > In response to your query; I don't have the Logitech mouse anymore
> > > but I just tested and Microsoft mice don't work so it probably is
> > > still not working for any serial mice.
> > 
> > Please report this bug upstream at the upstream bugzilla
> > (http://bugzilla.kernel.org), so that it can be investigated/
> > fixed upstream and backported for Squeeze.
> > (Product: Drivers, Component: Input Devices)
> > 
> > Once done, please add the bug number to this bug.
> > 
> > (We're asking you to file the bug report yourself, since the
> > kernel.org developers will have specific inquiries to your
> > hardware/setup)
> > 
> 
> Sorry, I gave up on serial mice and really don't care about them any
> more.  There's not enough other people like to need them for me to view
> it worthwhile from a community point of view, and I don't need it
> myself at this point.

Ok, closing the bug, then.

Cheers,
       Moritz

--- End Message ---
Reply to: