Your message dated Sat, 13 Dec 2008 12:42:03 +0100
with message-id <[email protected]>
and subject line Closing
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 [email protected]
immediately.)
--
367026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367026
Debian Bug Tracking System
Contact [email protected] 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 ---
The mail address of the submitter bounces, closing the bug.
Cheers,
Moritz
--- End Message ---
