2.15CE doesn't show menu in IceWM, does in JWM
Put Mouse1 in both places, but nothing changed.
Also, copying the xorg.conf and the xorg.conf.intel_r_865G_Graphics_ChipVSC4elc from the 2.14 frugal to the HD install didn't change anything either.
The HD install also has
xorg.conf.intel_r_865G30_82_50_85
and
xorg.conf.intel_r_915GM_910ML_915MS_Graphics_ChipSEC0000
files. That I don't recall seeing before. But, it's been a long day.
Anyway, here's the current xorg.conf
Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...
Option "RandR" "on"
EndSection
#everything past here is auto-generated by Puppy's Xorg Wizard...
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "Monitor"
#DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "VSC"
ModelName "VA912-3SERIES"
# Comment all HorizSync and VertSync values to use DDC:
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 50.0-81.0
#UseModes "Modes0" #monitor0usemodes
EndSection
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
Section "Device"
# Available Driver options are:-
# Values: <i>: integer, <f>: float, <bool>: "True"/"False",
# <string>: "String", <freq>: "<f> Hz/kHz/MHz"
# [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "i810" #card0driver
VendorName "Intel Corporation"
BoardName "82865G Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_r_865G_Graphics_ChipVSC4e1c
Thanks for your patience.
Also, copying the xorg.conf and the xorg.conf.intel_r_865G_Graphics_ChipVSC4elc from the 2.14 frugal to the HD install didn't change anything either.
The HD install also has
xorg.conf.intel_r_865G30_82_50_85
and
xorg.conf.intel_r_915GM_910ML_915MS_Graphics_ChipSEC0000
files. That I don't recall seeing before. But, it's been a long day.
Anyway, here's the current xorg.conf
Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...
Option "RandR" "on"
EndSection
#everything past here is auto-generated by Puppy's Xorg Wizard...
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "Monitor"
#DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "VSC"
ModelName "VA912-3SERIES"
# Comment all HorizSync and VertSync values to use DDC:
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 50.0-81.0
#UseModes "Modes0" #monitor0usemodes
EndSection
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
Section "Device"
# Available Driver options are:-
# Values: <i>: integer, <f>: float, <bool>: "True"/"False",
# <string>: "String", <freq>: "<f> Hz/kHz/MHz"
# [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "i810" #card0driver
VendorName "Intel Corporation"
BoardName "82865G Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_r_865G_Graphics_ChipVSC4e1c
Thanks for your patience.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
I have a reputation for being not exactly a quitter.Mstar wrote:Thanks for your patience.
I trust that, if this is a hard-drive install, you have the drivers-set zdrv_215.sfs in the subdir / (the top directory of this hard disk)? Or, if a frugal install, that it is wherever pup_save.2fs is?
Assuming that zdrv_215.sfs is indeed where it's supposed to be...
...let's try a slight variation. Since I assume XOrg's configuration wizard (when you first rebooted fresh) put that line
Code: Select all
Option "Protocol" "IMPS/2" #mouse0protocol
...let's have faith this time that xorgwizard knows what it's doing, and let's bring things into line with xorgwizard's way of thinking, one step at a time. Right now you have:
Code: Select all
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Code: Select all
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Code: Select all
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection
Next, you now have:
Code: Select all
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Code: Select all
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
Option "Buttons" "5"
Option "Name" "Autodetection"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Code: Select all
Option "Buttons" "5"
Code: Select all
#Option "Buttons" "5"
If you are left at a # prompt, then enter xwin to restart the X server. When the desktop presently reappears, see if it works OK when you click the start button to open the menu.
Also, an unrelated suggestion. I see in the "Monitor" section the lines
Code: Select all
Section "Monitor"
#DisplaySize 380 300 # mm
Code: Select all
Section "Monitor"
DisplaySize 380 300 # mm
HTH,
SHS
Sit Heel Speak,
No joy, as they say. Nothing has changed. Tried it with and without Buttons 5 commented out.
Here is the xorg.conf file:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
#Option "Buttons" "5"
Option "Name" "Autodetection"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "Monitor"
DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "VSC"
ModelName "VA912-3SERIES"
# Comment all HorizSync and VertSync values to use DDC:
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 50.0-81.0
#UseModes "Modes0" #monitor0usemodes
EndSection
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
Section "Device"
# Available Driver options are:-
# Values: <i>: integer, <f>: float, <bool>: "True"/"False",
# <string>: "String", <freq>: "<f> Hz/kHz/MHz"
# [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "i810" #card0driver
VendorName "Intel Corporation"
BoardName "82865G Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_r_865G_Graphics_ChipVSC4e1c
One more bit of information, it does not matter which button I click on the mouse (including the scroll wheel) they all open the little window in the upper left corner of the screen when there is no window open on the desktop.
Thanks for your persistence.
No joy, as they say. Nothing has changed. Tried it with and without Buttons 5 commented out.
Here is the xorg.conf file:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us" #xkeymap0
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "IMPS/2" #mouse0protocol
Option "Device" "/dev/mouse"
#Option "Emulate3Buttons"
#Option "Emulate3Timeout" "50"
#Option "Buttons" "5"
Option "Name" "Autodetection"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5" #scrollwheel
EndSection
Section "Monitor"
DisplaySize 380 300 # mm
Identifier "Monitor0"
VendorName "VSC"
ModelName "VA912-3SERIES"
# Comment all HorizSync and VertSync values to use DDC:
Option "DPMS"
HorizSync 30.0-82.0
VertRefresh 50.0-81.0
#UseModes "Modes0" #monitor0usemodes
EndSection
Section "Modes"
Identifier "Modes0"
#modes0modeline0
EndSection
Section "Device"
# Available Driver options are:-
# Values: <i>: integer, <f>: float, <bool>: "True"/"False",
# <string>: "String", <freq>: "<f> Hz/kHz/MHz"
# [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "i810" #card0driver
VendorName "Intel Corporation"
BoardName "82865G Integrated Graphics Controller"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_r_865G_Graphics_ChipVSC4e1c
One more bit of information, it does not matter which button I click on the mouse (including the scroll wheel) they all open the little window in the upper left corner of the screen when there is no window open on the desktop.
Thanks for your persistence.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Can you take a screenshot of this mystery (Ctrl-Alt-P in 2.15CE, or else Graphics-screen capture with mtPaint, then File-Save as- and put it in say /mnt/hda1 with name Mystery_menu.png, then surf to tinypic.com, Browse to /mnt/hda1, highlight Mystery_menu.png, Open, Upload, post the resulting tinypic url (2nd or 4th box) here)?
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
Also, open an rxvt window and issue:
and post here the output. Thanks.
Code: Select all
cat /proc/bus/input/devices
Sit Heel Speak,
The screen capture was a bust. Mtpaint launched into an endless loop that would not stop until I shut down the machine.
It's a black box about 1x2 inches that says "Workspace 2" and under that "Window List".
If I have anything else in the tray (not open on the desktop) it will also be listed on separate lines. The box is only open while the button is depressed, it does not persist.
Sorry I couldn't make the capture work, but that's really all it is.
Here is the rest of the information you asked for.
sh-3.00# cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0003 Vendor=045e Product=009d Version=0041
N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd
B: EV=120003
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: LED=7
I: Bus=0003 Vendor=045e Product=009d Version=0041
N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
P: Phys=usb-0000:00:1d.0-1/input1
S: Sysfs=/class/input/input3
H: Handlers=kbd mouse1
B: EV=10000f
B: KEY=c0002 400 0 c000000 1f0001 10f80 78407 ffe739fa d971d7ff febeffdf ffefffff ffffffff fffffffe
B: REL=fc3
B: ABS=ffffff01 701ff
sh-3.00#
Thanks again for your patience and persistance.
The screen capture was a bust. Mtpaint launched into an endless loop that would not stop until I shut down the machine.
It's a black box about 1x2 inches that says "Workspace 2" and under that "Window List".
If I have anything else in the tray (not open on the desktop) it will also be listed on separate lines. The box is only open while the button is depressed, it does not persist.
Sorry I couldn't make the capture work, but that's really all it is.
Here is the rest of the information you asked for.
sh-3.00# cat /proc/bus/input/devices
I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7
I: Bus=0011 Vendor=0002 Product=0005 Version=0000
N: Name="ImPS/2 Generic Wheel Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0003 Vendor=045e Product=009d Version=0041
N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
P: Phys=usb-0000:00:1d.0-1/input0
S: Sysfs=/class/input/input2
H: Handlers=kbd
B: EV=120003
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: LED=7
I: Bus=0003 Vendor=045e Product=009d Version=0041
N: Name="Microsoft Microsoft Wireless Optical Desktop® 2.10"
P: Phys=usb-0000:00:1d.0-1/input1
S: Sysfs=/class/input/input3
H: Handlers=kbd mouse1
B: EV=10000f
B: KEY=c0002 400 0 c000000 1f0001 10f80 78407 ffe739fa d971d7ff febeffdf ffefffff ffffffff fffffffe
B: REL=fc3
B: ABS=ffffff01 701ff
sh-3.00#
Thanks again for your patience and persistance.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
@MStar:
Just to be clear: you have both the Microsoft keyboard, the Microsoft usb cordless mouse that comes with it, and a ps2 mouse, all three plugged in?
Is there a second, ordinary keyboard as well? Or is the first entry for a keyboard which you earlier had plugged-in, but not simultaneously with the Microsoft Optical one?
The keyboard(s?) and the two mice are each on its own port, i.e. the Microsoft usb cordless mouse does not plug into the Microsoft keyboard, but rather into the computer?
I have alerted two of Puppy's mouse-detection-module architects to this thread, and asked them to take a look at the info you post above, over at
http://murga-linux.com/puppy/viewtopic.php?t=17575
Let's see what they find.
Just to be clear: you have both the Microsoft keyboard, the Microsoft usb cordless mouse that comes with it, and a ps2 mouse, all three plugged in?
Is there a second, ordinary keyboard as well? Or is the first entry for a keyboard which you earlier had plugged-in, but not simultaneously with the Microsoft Optical one?
The keyboard(s?) and the two mice are each on its own port, i.e. the Microsoft usb cordless mouse does not plug into the Microsoft keyboard, but rather into the computer?
I have alerted two of Puppy's mouse-detection-module architects to this thread, and asked them to take a look at the info you post above, over at
http://murga-linux.com/puppy/viewtopic.php?t=17575
Let's see what they find.
Last edited by Sit Heel Speak on Fri 27 Apr 2007, 17:02, edited 1 time in total.
Sit Heel Speak,
The wireless mouse and keyboard are both handled through a receiver that's plugged into a USB port. They are physically separate, but communicate through the same receiver. The mouse is not plugged into the keyboard.
The PS2 mouse is plugged into the PS2 mouse port. The IBM keyboard is plugged into the PS2 keyboard port. Neither of them are MicroSoft devices. The keyboard is and old IBM Model 1391401 made in 1987, and the mouse is a G-Max optical model GM-1P.
So, there are two mice and two keyboards using a total of three ports, one USB via a single receiver, and two PS2.
HTH
Thanks again.
The wireless mouse and keyboard are both handled through a receiver that's plugged into a USB port. They are physically separate, but communicate through the same receiver. The mouse is not plugged into the keyboard.
The PS2 mouse is plugged into the PS2 mouse port. The IBM keyboard is plugged into the PS2 keyboard port. Neither of them are MicroSoft devices. The keyboard is and old IBM Model 1391401 made in 1987, and the mouse is a G-Max optical model GM-1P.
So, there are two mice and two keyboards using a total of three ports, one USB via a single receiver, and two PS2.
HTH
Thanks again.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
While waiting for some comment by Dougal and/or Jesse...
go over to
http://murga-linux.com/puppy/viewtopic.php?t=17575
and scroll down to the latest (right now it's version c, a version d may appear before you read this) puppyserialdetect .tgz. Download it to /tmp, open an rxvt window, issue
cd /tmp
rox
and left-click the .tgz to open XArchiver and Extract. Answer yes to the prompts. Back in your rox window, navigate to wherever you've unpacked the file
puppyserialdetect-static
(might be one directory down)
right-click on white space - Window - open terminal (or xterm or rxvt) and in this new console window issue
./puppyserialdetect-static
and then issue
/usr/sbin/puppyserialdetect
and post the two outputs here. If they differ, you might try copying /usr/sbin/puppyserialdetect to /usr/sbin/puppyserialdetect-old, and then copy your new puppyserialdetect-static over (overwrite the old file) /usr/sbin/puppyserialdetect ...reboot and see if this new, improved version of puppyserialdetect cures it.
go over to
http://murga-linux.com/puppy/viewtopic.php?t=17575
and scroll down to the latest (right now it's version c, a version d may appear before you read this) puppyserialdetect .tgz. Download it to /tmp, open an rxvt window, issue
cd /tmp
rox
and left-click the .tgz to open XArchiver and Extract. Answer yes to the prompts. Back in your rox window, navigate to wherever you've unpacked the file
puppyserialdetect-static
(might be one directory down)
right-click on white space - Window - open terminal (or xterm or rxvt) and in this new console window issue
./puppyserialdetect-static
and then issue
/usr/sbin/puppyserialdetect
and post the two outputs here. If they differ, you might try copying /usr/sbin/puppyserialdetect to /usr/sbin/puppyserialdetect-old, and then copy your new puppyserialdetect-static over (overwrite the old file) /usr/sbin/puppyserialdetect ...reboot and see if this new, improved version of puppyserialdetect cures it.
Sit Heel Speak,
Here's what I got in RXVT
sh-3.00# ./puppyserialdetect-static
Type:PS2-mouse|Port:/dev/input/mice
sh-3.00# /usr/sbin/puppyserialdetect
sh-3.00# /usr/sbin/puppyserialdetect
sh-3.00#
I ran the second command twice to make sure I had not screwed it up. There is no output from /usr/sbin/puppyserialdetect. The file is there, I just checked. I also clicked on the file itself, but nothing happened that I could see.
I'll try the copy and reboot and report back in a bit.
Thanks
Here's what I got in RXVT
sh-3.00# ./puppyserialdetect-static
Type:PS2-mouse|Port:/dev/input/mice
sh-3.00# /usr/sbin/puppyserialdetect
sh-3.00# /usr/sbin/puppyserialdetect
sh-3.00#
I ran the second command twice to make sure I had not screwed it up. There is no output from /usr/sbin/puppyserialdetect. The file is there, I just checked. I also clicked on the file itself, but nothing happened that I could see.
I'll try the copy and reboot and report back in a bit.
Thanks
Sit Heel Speak,
Well, during the reboot the screen message for the mouse changed from PS2 to Serial. But, now neither mouse works.
I re-named puppyserialdetect-static to puppyserialdetect, on the assumption that whatever is calling it during boot would be looking for that name. I will now go back and change it back to the original name and see what happens.
Will report back shortly.
Well, during the reboot the screen message for the mouse changed from PS2 to Serial. But, now neither mouse works.
I re-named puppyserialdetect-static to puppyserialdetect, on the assumption that whatever is calling it during boot would be looking for that name. I will now go back and change it back to the original name and see what happens.
Will report back shortly.
Sit Heel Speak,
Here's another piece of the puzzle. I can't open something that's in the bottom menu bar by clicking on it, but if I click on the item in the bottom menu bar and then hold the button down while I roll the cursor up to the window that opens at the top, then the window will open normally on the desktop when I release the button.
Don't know what to make of that, but I just noticed it and thought I'd report it.
Thanks again
Here's another piece of the puzzle. I can't open something that's in the bottom menu bar by clicking on it, but if I click on the item in the bottom menu bar and then hold the button down while I roll the cursor up to the window that opens at the top, then the window will open normally on the desktop when I release the button.
Don't know what to make of that, but I just noticed it and thought I'd report it.
Thanks again
Hi Mstar,
I've just uploaded a new edition of puppyserialdetect, 1.1d
can you please download this version and run it with the -ke options please, and post the output for us to see.
tar zxvf puppyserialdetect-1.1d.tar.gz
cd puppyserialdetect-1.1d
./puppyserialdetect -ke
This will show keyboards and mice detected naming each too, you'll probably get something like:
Type:PS2-mouse|Port:/dev/input/mice|Direct:/dev/input/mouse0|Model:ImPS/2 Generic Wheel Mouse
Type:USB-mouse|Port:/dev/input/mice|Direct:/dev/input/mice|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Type:PS2-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:AT Translated Set 2 keyboard
Type:USB-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:Microsoft Microsoft Wireless Optical
Jesse
I've just uploaded a new edition of puppyserialdetect, 1.1d
can you please download this version and run it with the -ke options please, and post the output for us to see.
tar zxvf puppyserialdetect-1.1d.tar.gz
cd puppyserialdetect-1.1d
./puppyserialdetect -ke
This will show keyboards and mice detected naming each too, you'll probably get something like:
Type:PS2-mouse|Port:/dev/input/mice|Direct:/dev/input/mouse0|Model:ImPS/2 Generic Wheel Mouse
Type:USB-mouse|Port:/dev/input/mice|Direct:/dev/input/mice|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Type:PS2-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:AT Translated Set 2 keyboard
Type:USB-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:Microsoft Microsoft Wireless Optical
Jesse
Jesse,
Here is the output:
sh-3.00# ./puppyserialdetect -ke
Type:PS2-mouse|Port:/dev/input/mice|Direct:/dev/input/mouse0|Model:ImPS/2 Generic Wheel Mouse
Type:USB-mouse|Port:/dev/input/mice|Direct:/dev/input/mice|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Type:PS2-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:AT Translated Set 2 keyboard
Type:USB-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Note: I put this in /tmp following the directions Sit Heel Speak gave me for the previous version, except that I un-tarred it using your method.
Thanks, everyone's efforts are appreciated. I know this is a very minor problem, but I do appreciate the amount of time this community is willing to spend solving it.
Here is the output:
sh-3.00# ./puppyserialdetect -ke
Type:PS2-mouse|Port:/dev/input/mice|Direct:/dev/input/mouse0|Model:ImPS/2 Generic Wheel Mouse
Type:USB-mouse|Port:/dev/input/mice|Direct:/dev/input/mice|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Type:PS2-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:AT Translated Set 2 keyboard
Type:USB-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Note: I put this in /tmp following the directions Sit Heel Speak gave me for the previous version, except that I un-tarred it using your method.
Thanks, everyone's efforts are appreciated. I know this is a very minor problem, but I do appreciate the amount of time this community is willing to spend solving it.
- Sit Heel Speak
- Posts: 2595
- Joined: Fri 31 Mar 2006, 03:22
- Location: downwind
@Mstar: the reason I had you put it in /tmp, was so that it would not permanently contaminate your system, i.e. so it would vanish when next you reboot. The /tmp subdir is not persistent (that's why it's called "temp," I presume).
So, you may have to download it fresh. Back up /usr/sbin/puppyserialdetect to /usr/sbin/puppyserialdetect-original as above (unless you already did, in which case, don't), copy the new puppyserialdetect-static to (overwriting) /usr/sbin/puppyserialdetect, shut-down-and-save, reboot so that Puppy uses the new puppyserialdetect at boot time (I think it needs to reboot for the new puppyserialdetect to take effect, but am not 100% sure), and then see if anything has changed.
So, you may have to download it fresh. Back up /usr/sbin/puppyserialdetect to /usr/sbin/puppyserialdetect-original as above (unless you already did, in which case, don't), copy the new puppyserialdetect-static to (overwriting) /usr/sbin/puppyserialdetect, shut-down-and-save, reboot so that Puppy uses the new puppyserialdetect at boot time (I think it needs to reboot for the new puppyserialdetect to take effect, but am not 100% sure), and then see if anything has changed.
Sit Heel Speak,
Sorry for not following ALL of the directions. Anyway, I put puppyserialdetect-static from puppyserialdetect-1.1d in /usr/sbin after extracting it following Jesse's directions and rebooted.
The boot message still shows the mouse as PS2, and nothing has changed with regard to the menu behavior.
Here's the output from RXVT:
sh-3.00# cd /usr/sbin
sh-3.00# puppyserialdetect-static -ke
Type:PS2-mouse|Port:/dev/input/mice|Direct:/dev/input/mouse0|Model:ImPS/2 Generic Wheel Mouse
Type:USB-mouse|Port:/dev/input/mice|Direct:/dev/input/mice|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Type:PS2-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:AT Translated Set 2 keyboard
Type:USB-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
sh-3.00#
Thanks again, everyone. Sorry the news is not better.
Sorry for not following ALL of the directions. Anyway, I put puppyserialdetect-static from puppyserialdetect-1.1d in /usr/sbin after extracting it following Jesse's directions and rebooted.
The boot message still shows the mouse as PS2, and nothing has changed with regard to the menu behavior.
Here's the output from RXVT:
sh-3.00# cd /usr/sbin
sh-3.00# puppyserialdetect-static -ke
Type:PS2-mouse|Port:/dev/input/mice|Direct:/dev/input/mouse0|Model:ImPS/2 Generic Wheel Mouse
Type:USB-mouse|Port:/dev/input/mice|Direct:/dev/input/mice|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
Type:PS2-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:AT Translated Set 2 keyboard
Type:USB-kbd|Port:/dev/input/keyboard|Direct:/dev/input/keyboard|Model:Microsoft Microsoft Wireless Optical Desktop® 2.10
sh-3.00#
Thanks again, everyone. Sorry the news is not better.
- Dougal
- Posts: 2502
- Joined: Wed 19 Oct 2005, 13:06
- Location: Hell more grotesque than any medieval woodcut
SHS pointed me to this thread in relation to the mouse problem.
I don't know if I can help with the 2 mice + 2 keyboards setting -- it does seem like something to do with Xorg, which I've never messed with.
I was wondering, though, if it might not have something to do with the protocols.
The xorgwizard contains a part (also in xwin) where the mouse protocol is "fixed". It seems like the xorg.conf that is generated by probing comes out with for **all** mice but the wizard changes it to:
USB mouse: "Protocol" "IMPS/2"
Serial mouse: "Protocol" "Microsoft"
ps/2 mouse: "Protocol" "auto"
So if you have two different mice and Puppy sees one is USB (it always chooses USB first) then **all** protocol lines will be changed to IMPS/2 -- which might not be ok with a ps/2 mouse...
(The xorgwizard also changes the ZAxisMapping lines to "4 5" -- in my case the original was "4 5 6 7". Note that to see the original output of the Xorg probing, look at the file /tmp/xorg.conf.new after you have run the xorgwizard.)
Hope this helps...
(note that to prevent the lines from being auto-modified by xwin in the future, you should remove from their ends the "#mouse0protocol" part.)
There is one thing I might have found a solution to: DoWho's problem.
If you have a USB mouse, then it is linked to /dev/input/mice.
I have found that input/mice also works with my ps/2 mouse -- puppyserialdetect actually detects my mouse as input/mice (just like a usb mouse).
That got me to thinking... the detection of the (non-legacy) mice is done by the kernel and the mice listed in /proc/input/devices, right?
/proc/input/devices actually lists my mouse as being handled by "mouse0" -- that is input/mouse0.
So maybe "input/mice" is just like our /dev/mouse, a generic name that is secretly representing the various "mouse" devices?
So what I did was change /dev/mouse from input/mice to input/mouse0 -- and it works!
So I think the solution to DoWho's multiple mice problem is to look in /proc/input/devices, find which mouse# handles his desired mouse and re-link /dev/mouse.
Say it's mouse0, just open a terminal and run then restart X...
I don't know if I can help with the 2 mice + 2 keyboards setting -- it does seem like something to do with Xorg, which I've never messed with.
I was wondering, though, if it might not have something to do with the protocols.
The xorgwizard contains a part (also in xwin) where the mouse protocol is "fixed". It seems like the xorg.conf that is generated by probing comes out with
Code: Select all
Option "Protocol" "auto"
USB mouse: "Protocol" "IMPS/2"
Serial mouse: "Protocol" "Microsoft"
ps/2 mouse: "Protocol" "auto"
So if you have two different mice and Puppy sees one is USB (it always chooses USB first) then **all** protocol lines will be changed to IMPS/2 -- which might not be ok with a ps/2 mouse...
(The xorgwizard also changes the ZAxisMapping lines to "4 5" -- in my case the original was "4 5 6 7". Note that to see the original output of the Xorg probing, look at the file /tmp/xorg.conf.new after you have run the xorgwizard.)
Hope this helps...
(note that to prevent the lines from being auto-modified by xwin in the future, you should remove from their ends the "#mouse0protocol" part.)
There is one thing I might have found a solution to: DoWho's problem.
If you have a USB mouse, then it is linked to /dev/input/mice.
I have found that input/mice also works with my ps/2 mouse -- puppyserialdetect actually detects my mouse as input/mice (just like a usb mouse).
That got me to thinking... the detection of the (non-legacy) mice is done by the kernel and the mice listed in /proc/input/devices, right?
/proc/input/devices actually lists my mouse as being handled by "mouse0" -- that is input/mouse0.
So maybe "input/mice" is just like our /dev/mouse, a generic name that is secretly representing the various "mouse" devices?
So what I did was change /dev/mouse from input/mice to input/mouse0 -- and it works!
So I think the solution to DoWho's multiple mice problem is to look in /proc/input/devices, find which mouse# handles his desired mouse and re-link /dev/mouse.
Say it's mouse0, just open a terminal and run
Code: Select all
ln -snf input/mouse0 /dev/mouse
What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind
Some say your nose
Some say your toes
But I think it's your mind
Sit Heel Speak, Jesse, Dougal, et.al.
More data points:
Cold boot with PS2 keyboard and wired USB mouse attached. Startup message showed USB mouse. Mouse worked normally with menu.
Cold boot with PS2 keyboard, PS2 mouse, and USB mouse attached. Same message, and both mice worked.
Cold boot with re-attached wireless mouse with PS2 keyboard and PS2 mouse attached. Startup message showed PS2 mouse, and menu behavior was as before -- didn't work.
Looks to me like the wireless set-up is definitely the culprit, although that isn't exactly a stunning revelation. At least conventional USB recognition works fine.
Dougal,
Your comments are way over my capability level. I don't have a clue what to do with your suggestion. I appreciate the effort, but you are talking to someone who needs to be taken by the hand and guided through these things.
As always, I am grateful for the help.
More data points:
Cold boot with PS2 keyboard and wired USB mouse attached. Startup message showed USB mouse. Mouse worked normally with menu.
Cold boot with PS2 keyboard, PS2 mouse, and USB mouse attached. Same message, and both mice worked.
Cold boot with re-attached wireless mouse with PS2 keyboard and PS2 mouse attached. Startup message showed PS2 mouse, and menu behavior was as before -- didn't work.
Looks to me like the wireless set-up is definitely the culprit, although that isn't exactly a stunning revelation. At least conventional USB recognition works fine.
Dougal,
Your comments are way over my capability level. I don't have a clue what to do with your suggestion. I appreciate the effort, but you are talking to someone who needs to be taken by the hand and guided through these things.
As always, I am grateful for the help.