Puppy 1.0.4 hangs when selecting Serial Mouse (intermittent)
Puppy 1.0.4 hangs when selecting Serial Mouse (intermittent)
I have an ancient Windows 98 PC. When I boot from the Live CD it asks for my Keyboard (UK) and then for my mouse type (Serial) and then the port (ttyS1). In brackets is what I type. It then displays the screen to select a video display mode but the mouse does not work so I cannot select one!
I have tried CTRL-ALT-BACKSPACE and rm /etc/mousedevice and xwin to try all the other port options - always with the same hang up.
When I fitted a PS/2 mouse and selected PS/2 instead of serial everything worked but I would prefer to work with my serial mouse.
Any ideas as to what I am doing wrong when I have my serial mouse fitted?
Thanks
ICPUG
I have tried CTRL-ALT-BACKSPACE and rm /etc/mousedevice and xwin to try all the other port options - always with the same hang up.
When I fitted a PS/2 mouse and selected PS/2 instead of serial everything worked but I would prefer to work with my serial mouse.
Any ideas as to what I am doing wrong when I have my serial mouse fitted?
Thanks
ICPUG
Thanks guys.
I don't actually type the brackets. They were put in my post for convenience. Also I have tried ttyS0, even though my mouse is on COM port 2.
I have also tried moving the mouse to COM Port 1 (and using ttyS0) but still no luck. I DO have an internal modem that according to Windows is on COM3 and uses the same interrupt as COM1 and wonder if this has anything to do with the problem.
I am heartened to see Lobster has the same problem. I too have a scroll mouse. At least it is not just me. Irritating bug though.
Once again thanks for the contributions.
ICPUG
I don't actually type the brackets. They were put in my post for convenience. Also I have tried ttyS0, even though my mouse is on COM port 2.
I have also tried moving the mouse to COM Port 1 (and using ttyS0) but still no luck. I DO have an internal modem that according to Windows is on COM3 and uses the same interrupt as COM1 and wonder if this has anything to do with the problem.
I am heartened to see Lobster has the same problem. I too have a scroll mouse. At least it is not just me. Irritating bug though.
Once again thanks for the contributions.
ICPUG
Me too (at least for my Linux training). I had the same problem with my old serial mouse. The solution is to sort out the serial port settings either ttyS0 or S1 or S2I have an ancient Windows 98 PC.
etc. I had already installed another distro of Linux on my PC before I loaded Puppy, so I knew which port my modem was living on. During Puppy setup, If you accidentally assign the serial mouse port the same port the modem is living on - your PC will
hang - at least mine did.
Puppy 1.0.4 hangs when selecting Serial Mouse
I have the same problem; The system I tried Puppy on has a serial mouse on ttys0. Puppy 1.0.4 cd boots to the gui screen but doesn't seem to recognise the mouse.
I've tried following the suggested procedure of CTRL-ALT-BKSPC, rm /etc/mousedevice and xwin, and entering serial and ttys0, but the only result of that has been loss of the ps/2 keyboard as well as the serial mouse (typing in serial when prompted for mouse type, resulted in both the default ps/2 mouse driver AND the ps/2 keyboard driver being disabled).
Simply confirming the port the mouse is on (ttys0 in this case) isn't enough to correct the problem.
I've tried following the suggested procedure of CTRL-ALT-BKSPC, rm /etc/mousedevice and xwin, and entering serial and ttys0, but the only result of that has been loss of the ps/2 keyboard as well as the serial mouse (typing in serial when prompted for mouse type, resulted in both the default ps/2 mouse driver AND the ps/2 keyboard driver being disabled).
Simply confirming the port the mouse is on (ttys0 in this case) isn't enough to correct the problem.
Guys - I got my serial mouse to be recognised.
Viewing other posts in this forum about other problems I saw a mention that it is good to boot into Puppy from a cold start. What I normally do quite often is to do a bit of work in Windows and then restart to boot Puppy. This is what I call a warm boot.
I tried starting Puppy immediately after turning on the PC. This time my serial mouse, now located permanently on ttyS0 in case it clashes with the modem on the other port, was recognised! At this point I did not define it as a wheel mouse just in case this caused problems.
A quick test showed that now the pup001 file had been created I could do a warm boot as well!
Whether this remains a permanent solution or just a happy accident remains to be seen, but at least it shows a serial mouse can be recognised.
ICPUG
Viewing other posts in this forum about other problems I saw a mention that it is good to boot into Puppy from a cold start. What I normally do quite often is to do a bit of work in Windows and then restart to boot Puppy. This is what I call a warm boot.
I tried starting Puppy immediately after turning on the PC. This time my serial mouse, now located permanently on ttyS0 in case it clashes with the modem on the other port, was recognised! At this point I did not define it as a wheel mouse just in case this caused problems.
A quick test showed that now the pup001 file had been created I could do a warm boot as well!
Whether this remains a permanent solution or just a happy accident remains to be seen, but at least it shows a serial mouse can be recognised.
ICPUG
My serial mouse decided to not work again last night. This is with the same pup001 that worked previously! However it was an intermittent problem. I restarted my PC a few times. Sometimes it worked. Sometimes it didn't.
I got the most success when I waited the 10 seconds at the boot prompt. I NEVER got it working when I pressed ENTER to start the default.
ICPUG
I got the most success when I waited the 10 seconds at the boot prompt. I NEVER got it working when I pressed ENTER to start the default.
ICPUG
Mouse problem here also, and started the similar to the initial post.ICPUG wrote:My serial mouse decided to not work again last night. This is with the same pup001 that worked previously! However it was an intermittent problem. I restarted my PC a few times. Sometimes it worked. Sometimes it didn't.
I got the most success when I waited the 10 seconds at the boot prompt. I NEVER got it working when I pressed ENTER to start the default.
ICPUG
I tried changing the mouse settings to see if I could get the built-in toggle and keys on my IBM 600X to work and the mouse stopped working at all.
I could not find any key combo that allows me to make anything happen on the desktop, so I cannot change the mouse settings.
I was using a USB mouse and have tried serial and ps/2 mice to no avail. I have rebooted several times and still nothing works.
Can anyone tell me how to heal my Puppy ... ? doc
Fixed the problem. Booted Puppy from the CD in HD mode (entered 3 as the boot parameter) then used the options to select a ps/2 mouse.edoc wrote: Mouse problem here also, and started the similar to the initial post.
I tried changing the mouse settings to see if I could get the built-in toggle and keys on my IBM 600X to work and the mouse stopped working at all.
I could not find any key combo that allows me to make anything happen on the desktop, so I cannot change the mouse settings.
I was using a USB mouse and have tried serial and ps/2 mice to no avail. I have rebooted several times and still nothing works.
Can anyone tell me how to heal my Puppy ... ? doc
Now I need to uninstall Suse to clean things up and figure out how to convince the 600X to recognize the USB stick -- BIOS only knows HDD1, 2, 3, 4, FDD, CD-ROM and Network.
doc