topic title: HP PS/2 Optical Mouse with wheel can't work in AntiX
-
Posts: 12
- Joined: 04 Jan 2012
#46
heh or just hit up a local computer store for a 3$ generic ps/2 mouse (though that HP should be a logitech)
-
Posts: 81
- Joined: 22 Mar 2012
#47
Greetings Dave,
I changed to both Protocols"PS/2" and"ImPS/2"
None of them worked after reboots.
The HP PS/2 optical mouse did not work.
I did a little discovery on my own:
while I was in init 3 I typed startx ... it booted up a plain
Debian windows manager ... not icewm ...
I accessed System Information and noticed that for Input Devices
antiX M11 486 was showing:
AT Translated Set 2 keyboard
ACPI VIrtual Keyboard Device
I would think that antiX M11 is seeing the mouse as the second device
another keyboard or a virtual keyboard.
Could this information help ... Could we deactivate this and cause to be found?
The xorg.conf from DSL 4410 is below:
During the boot up of DSL 4410, it stated:
Mouse is Generic PS/2 Wheel Mouse at /dev/psaux
I looked for the xorg.conf in DSL4410 and did not find any.
The HP PS/2 Optical wheeled mouse worked fine in DSL 4410.
I did find the following hidden files in /home/dsl:
.xserverrc
.xinitrc
If you could direct me as to where the xorg.conf file is in DSL 4410, or
how to generate it, I will post it.
I tried the X -configure it returned an error.
I changed to both Protocols"PS/2" and"ImPS/2"
None of them worked after reboots.
The HP PS/2 optical mouse did not work.
I did a little discovery on my own:
while I was in init 3 I typed startx ... it booted up a plain
Debian windows manager ... not icewm ...
I accessed System Information and noticed that for Input Devices
antiX M11 486 was showing:
AT Translated Set 2 keyboard
ACPI VIrtual Keyboard Device
I would think that antiX M11 is seeing the mouse as the second device
another keyboard or a virtual keyboard.
Could this information help ... Could we deactivate this and cause to be found?
The xorg.conf from DSL 4410 is below:
During the boot up of DSL 4410, it stated:
Mouse is Generic PS/2 Wheel Mouse at /dev/psaux
I looked for the xorg.conf in DSL4410 and did not find any.
The HP PS/2 Optical wheeled mouse worked fine in DSL 4410.
I did find the following hidden files in /home/dsl:
.xserverrc
Code: Select all
exec /usr/bin/X11/Xvesa -mouse"/dev/psaux",5 -screen 800x600x16 -shadow -nolisten tcp -I &>/dev/null
Code: Select all
# put X windows programs that you want started here.
# Be sure to add at the end of each command the &
KEYTABLE="$(getknoppixparam.lua KEYTABLE)"
DESKTOP="$(getoption.lua $HOME/.desktop wm)"
ICONS="$(getoption.lua $HOME/.desktop icons)"
umix -lf .umix 2>/dev/null
[ -f .mouse_config ] && sh .mouse_config &
# For non-US Keyboards
if [ ${KEYTABLE:0:2} !="us" ]; then
xmodmap -e"clear Mod4" -e"add Mod5 = Mode_switch" &
fi
if ["$ICONS" =="xtdesk" ]; then
for x in `ls -1 .xtdesktop/*.hide 2>/dev/null`; do rm -f ${x%.*}; done
iconsnap.lua &>/dev/null &
xtdesk.sh
elif ["$ICONS" =="dfm" ]; then
/usr/bin/dfm &
else
["$DESKTOP" =="jwm" ] && echo '<?xml version="1.0"?><JWM></JWM>' > .jwmrc-icons
fi
if egrep -qv lowram /proc/cmdline 2>/dev/null; then
dillo /usr/share/doc/dsl/getting_started.html &>/dev/null &
torsmo 2>/dev/null &
fi
[ -f".$DESKTOP.inc" ] && ~/".$DESKTOP.inc"
exec"${DESKTOP:=jwm}" 2>/dev/null
how to generate it, I will post it.
I tried the X -configure it returned an error.
-
Posts: 81
- Joined: 22 Mar 2012
#48
Osgeld,
That's a great idea ... yet ... remember what the AT keyboard
substition outcome was ... the same thing.
When I've some time I see if I can find a PS/2 mouse.
I do think I saw something somewhere that an"...SDP..." had to
be altered in the kernel.
If I get sometime I'll take a look at it and post.
That's a great idea ... yet ... remember what the AT keyboard
substition outcome was ... the same thing.
When I've some time I see if I can find a PS/2 mouse.
I do think I saw something somewhere that an"...SDP..." had to
be altered in the kernel.
If I get sometime I'll take a look at it and post.
-
Posts: 1,062
- Joined: 20 Jan 2010
#49
sorry,
I am not sure were DSL would put its xorg.conf, or how to generate one if x -configure fails.
However it appears that it is setting the mouse from the x exec line.
Perhaps you can change your xorg.conf to point to /dev/psaux instead of /dev/input/mouse.
Another option would be to add the exec line option, so -mouse /dev/psaux to the x exec line in /etc/init.d/slim.
I have not had to add anything like that before, but it is one thing I would try __{{emoticon}}__
I am not sure were DSL would put its xorg.conf, or how to generate one if x -configure fails.
However it appears that it is setting the mouse from the x exec line.
Perhaps you can change your xorg.conf to point to /dev/psaux instead of /dev/input/mouse.
Another option would be to add the exec line option, so -mouse /dev/psaux to the x exec line in /etc/init.d/slim.
I have not had to add anything like that before, but it is one thing I would try __{{emoticon}}__
-
Posts: 81
- Joined: 22 Mar 2012
#50
Greetings Dave,
No problem with the DSL4410 ... it's good learning experience.
NOW just for my clarity ... I'm going to add:
-mouse /dev/psaux
in this file /etc/init.d/slim
Once I get to the box I will modify the slim file in /etc/init.d
Thanks Dave
No problem with the DSL4410 ... it's good learning experience.
NOW just for my clarity ... I'm going to add:
-mouse /dev/psaux
in this file /etc/init.d/slim
Once I get to the box I will modify the slim file in /etc/init.d
Thanks Dave
-
Posts: 1,062
- Joined: 20 Jan 2010
#51
yes, that is correct.
But you should try the xorg.conf change first, before going to change /etc/init.d/slim IMHO
But you should try the xorg.conf change first, before going to change /etc/init.d/slim IMHO
-
Posts: 81
- Joined: 22 Mar 2012
#52
Thanks Dave ... I'll look into the slim file and not change anything.
I will look deeper into xorg.conf.
I will look deeper into xorg.conf.
-
Posts: 81
- Joined: 22 Mar 2012
#53
Greetings Dave,
Where do I add the line:
-mouse /dev/psaux in /etc/init.d/slim
my /etc/init.d/slim is below:
Thanks Dave ...
Where do I add the line:
-mouse /dev/psaux in /etc/init.d/slim
my /etc/init.d/slim is below:
Code: Select all
#!/bin/sh
# Largely adapted from xdm's init script:
# Copyright 1998-2002, 2004, 2005 Branden Robinson <branden@debian.org>.
# Copyright 2006 Eugene Konev <ejka@imfi.kspu.ru>
### BEGIN INIT INFO
# Provides: slim
# Required-Start: $local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Should-Start: xfs $named slapd
# Should-Stop: xfs $named slapd
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/stop the SLiM daemon.
### END INIT INFO
test -z"$HEED_DEFAULT_DISPLAY_MANAGER" && HEED_DEFAULT_DISPLAY_MANAGER=true
DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
DAEMON=/usr/bin/slim
PIDFILE=/var/run/slim.lock
-
Posts: 81
- Joined: 22 Mar 2012
#54
Greetings Dave,
The previous post doesn't have the entire slim file posted.
I've corrected it below:
Where do I add the line:
-mouse /dev/psaux in /etc/init.d/slim
my /etc/init.d/slim is below:
Thanks Dave ...
The previous post doesn't have the entire slim file posted.
I've corrected it below:
Where do I add the line:
-mouse /dev/psaux in /etc/init.d/slim
my /etc/init.d/slim is below:
Code: Select all
#!/bin/sh
# Largely adapted from xdm's init script:
# Copyright 1998-2002, 2004, 2005 Branden Robinson <branden@debian.org>.
# Copyright 2006 Eugene Konev <ejka@imfi.kspu.ru>
### BEGIN INIT INFO
# Provides: slim
# Required-Start: $local_fs $remote_fs
# Required-Stop: $local_fs $remote_fs
# Should-Start: xfs $named slapd
# Should-Stop: xfs $named slapd
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Start/stop the SLiM daemon.
### END INIT INFO
test -z"$HEED_DEFAULT_DISPLAY_MANAGER" && HEED_DEFAULT_DISPLAY_MANAGER=true
DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
DAEMON=/usr/bin/slim
PIDFILE=/var/run/slim.lock
SSD_START_ARGS="--pidfile $PIDFILE --name $(basename $DAEMON) --startas $DAEMON -- -d"
SSD_STOP_ARGS="--pidfile $PIDFILE --name $(basename $DAEMON) --retry TERM/5/TERM/5"
case $1 in
start)
if ["$HEED_DEFAULT_DISPLAY_MANAGER" ="true" ] &&
[ -e $DEFAULT_DISPLAY_MANAGER_FILE ] &&
["$(cat $DEFAULT_DISPLAY_MANAGER_FILE)" !="$DAEMON" ]; then
echo"Not starting X display manager (slim); it is not the default display manager."
else
echo -n"Starting X display manager: slim"
start-stop-daemon --start --quiet $SSD_START_ARGS || echo -n" already running"
echo"."
fi
;;
stop)
echo -n"Stopping X display manager: slim"
if ! [ -f $PIDFILE ]; then
echo -n" not running ($PIDFILE not found)"
else
start-stop-daemon --stop --quiet $SSD_STOP_ARGS
SSD_RES=$?
if [ $SSD_RES -eq 1 ]; then
echo -n" not running"
fi
if [ $SSD_RES -eq 2 ]; then
echo -n" not responding to TERM signals"
else
if [ -f $PIDFILE ]; then
echo -n" (removing stale $PIDFILE)"
rm $PIDFILE
fi
fi
fi
echo"."
;;
restart)
$0 stop
sleep 2
$0 start
;;
force-reload)
/etc/init.d/slim restart
;;
*)
echo"Usage: /etc/init.d/slim {start|stop|restart|force-reload}"
exit 1
;;
esac
# End of file
-
Posts: 1,062
- Joined: 20 Jan 2010
#55
__{{emoticon}}__ Sorry, was thinking of the wrong file, you should be editing /etc/slim.conf.
When editing the file place
-mouse /dev/psaux
right
xserver_arguments -nolisten tcp #!#HERE#!#
It should be around line 5, the resulting line 5 should look like
xserver_arguments -nolisten tcp -mouse /dev/psaux
When editing the file place
-mouse /dev/psaux
right
xserver_arguments -nolisten tcp #!#HERE#!#
It should be around line 5, the resulting line 5 should look like
xserver_arguments -nolisten tcp -mouse /dev/psaux
-
Posts: 81
- Joined: 22 Mar 2012
#56
Greetings Dave,
I've changed xserver_arguments in /etc/slim.conf
from:
to:
[/color]
I rebooted.
X did not start.
I logged in the terminal and typed: startx and got the following errors:
exec: 1: /usr/bin/X11/Xvesa: not found
xinit: giving up
xinit: unalbe to connet to X server: Connection refused
xinit: server error
I looked around and found this log file: slim.log in /var/log
At the end of slim.log I found below:
I've changed xserver_arguments in /etc/slim.conf
from:
Code: Select all
xserver_arguments -dpi 96 -nolisten tcp
Code: Select all
xserver_arguments -dpi 96 -nolisten tcp -mouse /dev/psaux
I rebooted.
X did not start.
I logged in the terminal and typed: startx and got the following errors:
exec: 1: /usr/bin/X11/Xvesa: not found
xinit: giving up
xinit: unalbe to connet to X server: Connection refused
xinit: server error
I looked around and found this log file: slim.log in /var/log
At the end of slim.log I found below:
Code: Select all
Fatal server error:
Unrecognized option: -mouse
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
/usr/bin/xauth: file /var/run/slim.auth does not exist
Unrecognized option: -mouse
use: X [:<display>] [option]
-a # default pointer acceleration (factor)
-ac disable access control restrictions
-audit int set audit trail level
-auth file select authorization file
-br create root window with black background
+bs enable any backing store support
-bs disable any backing store support
-c turns off key-click
c # key-click volume (0-100)
-cc int default color visual class
-nocursor disable the cursor
-core generate core dump on fatal error
-dpi int screen resolution in dots per inch
-dpms disables VESA DPMS monitor control
-deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs
-f # bell base (0-100)
-fc string cursor font
-fn string default font name
-fp string default font path
-help prints message with these options
-I ignore all remaining arguments
-ld int limit data space to N Kb
-lf int limit number of open files to N
-ls int limit stack space to N Kb
-nolock disable the locking mechanism
-logo enable logo in screen saver
nologo disable logo in screen saver
-nolisten string don't listen on protocol
-noreset don't reset after last client exists
-reset reset after last client exists
-p # screen-saver pattern duration (minutes)
-pn accept failure to listen on all ports
-nopn reject failure to listen on all ports
-r turns off auto-repeat
r turns on auto-repeat
-render [default|mono|gray|color] set render color alloc policy
-retro start with classic stipple and cursor
-s # screen-saver timeout (minutes)
-t # default pointer threshold (pixels/t)
-terminate terminate at server reset
-to # connection time out
-tst disable testing extensions
ttyxx server started from init on /dev/ttyxx
v video blanking for screen-saver
-v screen-saver without video blanking
-wm WhenMapped default backing-store
-wr create root window with white background
-maxbigreqsize set maximal bigrequest size
+xinerama Enable XINERAMA extension
-xinerama Disable XINERAMA extension
-dumbSched Disable smart scheduling, enable old behavior
-schedInterval int Set scheduler interval in msec
+extension name Enable extension
-extension name Disable extension
-query host-name contact named host for XDMCP
-broadcast broadcast for XDMCP
-multicast [addr [hops]] IPv6 multicast for XDMCP
-indirect host-name contact named host for indirect XDMCP
-port port-num UDP port number to send messages to
-from local-address specify the local address to connect from
-once Terminate server after one session
-class display-class specify display class to send in manage
-cookie xdm-auth-bits specify the magic cookie for XDMCP
-displayID display-id manufacturer display ID for request
[+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask] ] ] ]
enable/disable accessx key sequences
-ardelay set XKB autorepeat delay
-arinterval set XKB autorepeat interval
Device Dependent Usage
-modulepath paths specify the module search path
-logfile file specify a log file name
-configure probe for devices and write an xorg.conf
-showopts print available options for all installed drivers
-config file specify a configuration file, relative to the
xorg.conf search path, only root can use absolute
-configdir dir specify a configuration directory, relative to the
xorg.conf.d search path, only root can use absolute
-verbose [n] verbose startup messages
-logverbose [n] verbose log messages
-quiet minimal startup messages
-pixmap24 use 24bpp pixmaps for depth 24
-pixmap32 use 32bpp pixmaps for depth 24
-fbbpp n set bpp for the framebuffer. Default: 8
-depth n set colour depth. Default: 8
-gamma f set gamma value (0.1 < f < 10.0) Default: 1.0
-rgamma f set gamma value for red phase
-ggamma f set gamma value for green phase
-bgamma f set gamma value for blue phase
-weight nnn set RGB weighting at 16 bpp. Default: 565
-layout name specify the ServerLayout section name
-screen name specify the Screen section name
-keyboard name specify the core keyboard InputDevice name
-pointer name specify the core pointer InputDevice name
-nosilk disable Silken Mouse
-flipPixels swap default black/white Pixel values
-disableVidMode disable mode adjustments with xvidtune
-allowNonLocalXvidtune allow xvidtune to be run as a non-local client
-allowMouseOpenFail start server even if the mouse can't be initialized
-ignoreABI make module ABI mismatches non-fatal
-isolateDevice bus_id restrict device resets to bus_id (PCI only)
-version show the server version
-showDefaultModulePath show the server default module path
-showDefaultLibPath show the server default library path
vtXX use the specified VT number
-keeptty don't detach controlling tty (for debugging only)
-novtswitch don't immediately switch to new VT
-sharevts share VTs with another X server
Fatal server error:
Unrecognized option: -mouse
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
-
Posts: 12
- Joined: 04 Jan 2012
#57
Im not really pushing this, but I found one in publix (grocery store) like a couple weeks ago, optical, wheel, ps/2, 10 freaking dollars but I got it anyway, it works great though its a bit lightThat's a great idea ... yet ... remember what the AT keyboard
substition outcome was ... the same thing.
When I've some time I see if I can find a PS/2 mouse.
-
Posts: 81
- Joined: 22 Mar 2012
#58
Greetings Osgeld,
I didn't get a chance to pickup another PS/2 mouse.
Truly, I don't believe that it would yield different results.
My belief comes from the fact that your suggestion in relations
to the AT keyboard was sound due to your findings and solutions.
However, the outcome proved that the AT keyboard port and the PS/2
port giving the same results. The HP PS/2 Optical mouse continued not to work.
I am interested in using a different PS/2 mouse because if it yields
the same results as the AT keyboard, then it would definitely be a problem
with the PS/2 port (for the mouse).
I can tell you absolutely that the PS/2 mouse on this motherboard isn't
problematic based upon the fact that the HP PS/2 Optical mouse worked
perfectly well with DSL 4410 and Windows 98 SE installed.
I thank you, Osgeld ... and I look forward in seeing this HP PS/2 optical wheeled
mouse working with antiX M11 486 installed.
You know something does come to mind: Is it possible to check on the status of the
Ports in Linux ... in this case the PS/2 mouse?
I didn't get a chance to pickup another PS/2 mouse.
Truly, I don't believe that it would yield different results.
My belief comes from the fact that your suggestion in relations
to the AT keyboard was sound due to your findings and solutions.
However, the outcome proved that the AT keyboard port and the PS/2
port giving the same results. The HP PS/2 Optical mouse continued not to work.
I am interested in using a different PS/2 mouse because if it yields
the same results as the AT keyboard, then it would definitely be a problem
with the PS/2 port (for the mouse).
I can tell you absolutely that the PS/2 mouse on this motherboard isn't
problematic based upon the fact that the HP PS/2 Optical mouse worked
perfectly well with DSL 4410 and Windows 98 SE installed.
I thank you, Osgeld ... and I look forward in seeing this HP PS/2 optical wheeled
mouse working with antiX M11 486 installed.
You know something does come to mind: Is it possible to check on the status of the
Ports in Linux ... in this case the PS/2 mouse?
-
Posts: 4,164
- Joined: 20 Feb 2009
#59
only works for usb though
Edit: so you might try
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://kmuto.jp/debian/hcl/"
linktext was:"http://kmuto.jp/debian/hcl/"
====================================
2nd edit: Been looking through older aptosid bug reports for 2011 for udev since I was wondering if udev was what was killing your keyboard and mouse and saw this
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://aptosid.com/index.php?name=PNphpBB2&file=printview&t=1093&start=0"
linktext was:"http://aptosid.com/index.php?name=PNphp ... 93&start=0"
====================================
If you have a /run folder in root=/ . If me. I would rename the folder /run.backup or /run.old to keep it there in case what I am showing you does not fix your problem. That way you can restore it back to just /run.
I initially got this idea from reading these 2 threads also.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forums.debian.net/viewtopic.php?f=7&t=62880"
linktext was:"http://forums.debian.net/viewtopic.php?f=7&t=62880"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forums.debian.net/viewtopic.php?f=6&t=64927"
linktext was:"http://forums.debian.net/viewtopic.php?f=6&t=64927"
====================================
The weirdest thing I read. Recommends unplugging mouse and keyboard after it boots up to a login manager. Then replug keyboard and mouse back in. Then it works OK.
3rd edit: I may be way off base in this post and my info should be taken with a grain of salt. If you lived down the street. I could pick up a mouse and keyboard for you at a couple dollars each at a Salvation Army or Goodwill store.
Is it possible to check on the status of the
Ports in Linux ... in this case the PS/2 mouse?
Code: Select all
$ lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 045e:003c Microsoft Corp. SideWinder Joystick
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 046d:080f Logitech, Inc.
Bus 001 Device 002: ID 1058:1100 Western Digital Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Edit: so you might try
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://kmuto.jp/debian/hcl/"
linktext was:"http://kmuto.jp/debian/hcl/"
====================================
2nd edit: Been looking through older aptosid bug reports for 2011 for udev since I was wondering if udev was what was killing your keyboard and mouse and saw this
Bug report can be found atne - 07.04.2011, 17:00
Post subject:
drb wrote:
Didn't work here initially with a PS2 mouse . . . installing the aptosid udev immediately froze the mouse and keyboard forcing a hard reset . . .
Same here with PS2 mouse and keyboard.
Edit: booted with an old liveCD and removed /run, then booted aptosid. Everything seems to be working.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://aptosid.com/index.php?name=PNphpBB2&file=printview&t=1093&start=0"
linktext was:"http://aptosid.com/index.php?name=PNphp ... 93&start=0"
====================================
If you have a /run folder in root=/ . If me. I would rename the folder /run.backup or /run.old to keep it there in case what I am showing you does not fix your problem. That way you can restore it back to just /run.
I initially got this idea from reading these 2 threads also.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forums.debian.net/viewtopic.php?f=7&t=62880"
linktext was:"http://forums.debian.net/viewtopic.php?f=7&t=62880"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://forums.debian.net/viewtopic.php?f=6&t=64927"
linktext was:"http://forums.debian.net/viewtopic.php?f=6&t=64927"
====================================
The weirdest thing I read. Recommends unplugging mouse and keyboard after it boots up to a login manager. Then replug keyboard and mouse back in. Then it works OK.
3rd edit: I may be way off base in this post and my info should be taken with a grain of salt. If you lived down the street. I could pick up a mouse and keyboard for you at a couple dollars each at a Salvation Army or Goodwill store.
-
Posts: 81
- Joined: 22 Mar 2012
#60
Greetings rokytnji,
I'm grateful for your assistance.
I'll try them out once I'm at the the box.
Thanks again ... I look forward in seeing the
HP PS/2 Optical Mouse work with antiX M11 486
I'm grateful for your assistance.
I'll try them out once I'm at the the box.
Thanks again ... I look forward in seeing the
HP PS/2 Optical Mouse work with antiX M11 486