Wireless keyboard frozen in Tahrpup 64 6.06
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
Wireless keyboard frozen in Tahrpup 64 6.06
have encountered a problem with 6.06 FULL installed on an internal HD. It had been running for about a week when I installed update-flashplayer, and upon reboot (with update-flashplayer set to run at boot) the keyboard/mousepad on a remote KB froze. I can get the mousepad working by switching USB ports (the dongle). However, the keyboard remains frozen. I have uninstalled update flashplaye but this makes no difference.
Has update flashplayer modified the xorg.conf file and caused the keyboard driver not to be loaded?
Has update flashplayer modified the xorg.conf file and caused the keyboard driver not to be loaded?
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
PS. The program in question is the auto updater.
http://www.murga-linux.com/puppy/viewtopic.php?t=100523d
I neglected to mention that upon the first reboot the Nvidia driver was affected, but on a further reboot the proper resolution was restored.
http://www.murga-linux.com/puppy/viewtopic.php?t=100523d
I neglected to mention that upon the first reboot the Nvidia driver was affected, but on a further reboot the proper resolution was restored.
- spiritwild
- Posts: 181
- Joined: Mon 03 Oct 2016, 10:06
does everything work at boot? entering bios,etc?
I don't see anything in the code that would affect the input events. I just see the update folder created.
Never had a touchpad but had a keyboard once that would never signal unless you turned it off and on every time. Even with fresh batteries.
A few commands that may help debug, maybe.
evtest /dev/input/eventX
Where X = input device number
udevadm test class/input
cat /proc/bus/input/devices
udevadm info
folders of interest.....
/dev/input
/etc/udev/rules.d
any large hammer or brick.
Hopefully someone with deeper knowledge can be of more help.
I don't remember how generic inputs are loaded. Much less how the transmitter broadcast it's id.
I don't see anything in the code that would affect the input events. I just see the update folder created.
Never had a touchpad but had a keyboard once that would never signal unless you turned it off and on every time. Even with fresh batteries.
A few commands that may help debug, maybe.
evtest /dev/input/eventX
Where X = input device number
udevadm test class/input
cat /proc/bus/input/devices
udevadm info
folders of interest.....
/dev/input
/etc/udev/rules.d
any large hammer or brick.
Hopefully someone with deeper knowledge can be of more help.
I don't remember how generic inputs are loaded. Much less how the transmitter broadcast it's id.
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
Thanks for your spirited response. The keyboard is wireless, communicates via a USB dongle, and has a mousepad. Given the temporary loss of resolution on the Nvidia driver, I wondered if the lines in xorg.conf referring to inputs might have been corrupted.
Everything else seems fine, including the system bios and bootup screen. The keyboard is active during the grub phase but goes dead when X kicks in.
Bear in mind that I can't type any commands without the keyboard, so we're dead in the water here.
Something subtler, perhaps some lubricant.
Everything else seems fine, including the system bios and bootup screen. The keyboard is active during the grub phase but goes dead when X kicks in.
Bear in mind that I can't type any commands without the keyboard, so we're dead in the water here.
Something subtler, perhaps some lubricant.
- spiritwild
- Posts: 181
- Joined: Mon 03 Oct 2016, 10:06
Xorg.0.log may show something.
I have read about certain issues (bugs) in x11, not sure but it plagued a lot of people after ugrades.
I would definately find a wired keyboard though.
In my journeys, I found this to be my best fix when something goes nutty.
http://murga-linux.com/puppy/viewtopic.php?t=110090
I have read about certain issues (bugs) in x11, not sure but it plagued a lot of people after ugrades.
I would definately find a wired keyboard though.
In my journeys, I found this to be my best fix when something goes nutty.
http://murga-linux.com/puppy/viewtopic.php?t=110090
Would help to know what make and model the wireless keyboard is?
This keyboard got an on/off key/switch??
Anything like this:
Check USB port for dirt, condition of connection pins, etc....
I know you said you did this and got the mousepad working by doing this, but computers are not logical sometimes.
So, try this and see what happens.
With Tahrpup booted to desktop.
Unplug the wireless dongle that communicates with the keyboard.
Leave it unplugged for 1 to 2 minutes!!!!
Plug it back in.
Give Tahrpup a little time to discover it and hopefully re-setup.
If that was no help.
Shutdown computer to a completely powered off condition.
Keep powered off for 1 to 2 minutes!!!
Unplug the wireless dongle. (Keep it unplugged)
Boot Tahrpup To desktop.
Shutdown computer to completely powered off condition.
Keep powered off for 1 to 2 minutes!!!
Plug wireless dongle back in.
Do normal bootup.
Note:
Complete power off and 1 to 2 minute delay, is to make sure the memory is completely cleared and reset to nothing in it.
That indicates the dongle is being seen by Tahrpup and is working.I can get the mousepad working by switching USB ports (the dongle)
This keyboard got an on/off key/switch??
Anything like this:
USB ports can go bad.How do I make my wireless keyboard discoverable?
Hold down the Shift and Option keys ('Alt' on some keyboards)
Check USB port for dirt, condition of connection pins, etc....
I know you said you did this and got the mousepad working by doing this, but computers are not logical sometimes.
So, try this and see what happens.
With Tahrpup booted to desktop.
Unplug the wireless dongle that communicates with the keyboard.
Leave it unplugged for 1 to 2 minutes!!!!
Plug it back in.
Give Tahrpup a little time to discover it and hopefully re-setup.
If that was no help.
Shutdown computer to a completely powered off condition.
Keep powered off for 1 to 2 minutes!!!
Unplug the wireless dongle. (Keep it unplugged)
Boot Tahrpup To desktop.
Shutdown computer to completely powered off condition.
Keep powered off for 1 to 2 minutes!!!
Plug wireless dongle back in.
Do normal bootup.
Note:
Complete power off and 1 to 2 minute delay, is to make sure the memory is completely cleared and reset to nothing in it.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
Thanks for your further insights and suggestions.
Unfortunately a wired keyboard is impractical in this circumstance, as the unit is used as a home theatre.
The keyboard is an Adesso WKB-4200UB. It has on/off switch and a connect button, both of which I have fiddled.
Keyboard is active during GRUB phase, so USB port not a problem. In any case I have tried in 2 different ports.
Unplugged and replugged dongle as suggested, including with cold start.
Banged randomly on keys and discovered that up arrow launches mtPaint application. Riddle me that!
Much obliged for the assistance.
Unfortunately a wired keyboard is impractical in this circumstance, as the unit is used as a home theatre.
The keyboard is an Adesso WKB-4200UB. It has on/off switch and a connect button, both of which I have fiddled.
Keyboard is active during GRUB phase, so USB port not a problem. In any case I have tried in 2 different ports.
Unplugged and replugged dongle as suggested, including with cold start.
Banged randomly on keys and discovered that up arrow launches mtPaint application. Riddle me that!
Much obliged for the assistance.
- spiritwild
- Posts: 181
- Joined: Mon 03 Oct 2016, 10:06
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
-
- Posts: 328
- Joined: Wed 25 Jun 2014, 20:31
Is this the only key that's working?autumnleaves wrote:Banged randomly on keys and discovered that up arrow launches mtPaint application. Riddle me that!
Are you using Openbox/LXDE, by any chance? I remembered that someone else once reported this odd issue. (And initially forgot to mention that he was using LXDE instead of JWM.)
http://murga-linux.com/puppy/viewtopic.php?t=108919
Could the window manager have gotten messed up somehow and doesn't process key input properly anymore?
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
I tried booting from the DVD to see if I would be able to edit config files if necessary, but loaded the desktop from the hard disk install and may have destroyed the swap file. The keyboard did not work when booted from DvD, but the mouse can be revived by replugging the dongle. I quit and then tried to reboot from the HD installed pup but now none of the config files are found and it won't boot at all.
Can the install be salvaged?
Can the install be salvaged?
Can you try using it on another computer, just to see if the keyboard did not go bad?Banged randomly on keys and discovered that up arrow launches mtPaint application. Riddle me that!
If the mousepad is working.
Can you get into the menu->Setup->Mouse/keyboard Wizard?
Do anything with the keyboard settings?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
If the DVD is the exact same version of Puppy.autumnleaves wrote:I tried booting from the DVD to see if I would be able to edit config files if necessary, but loaded the desktop from the hard disk install and may have destroyed the swap file. The keyboard did not work when booted from DvD, but the mouse can be revived by replugging the dongle. I quit and then tried to reboot from the HD installed pup but now none of the config files are found and it won't boot at all.
Can the install be salvaged?
There is an option to do an install over the full install to hopefully repair it.
Booted with the DVD.
Run Puppy Universal Installer.
Choose full install.
Do a full install of Tahrpup64 to the same location as the none working full install.
Very important
During the setup for the full install you will get option to upgrade
Choose that option upgrade
Do nothing to bootloader. Old settings will still work.
When installer is finished remove DVD.
Reboot to the full install.
(Because you where running the live DVD, it may ask about making a save file. Say no.)
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
Thanks for your assistance. I have to run out for a while but will return to the problem later.
Meanwhile note that I have an old wireless keyboard by the same manufacturer and the same problem occurs with it. Both use the same model of dongle but I switched them without noting any difference.
Will report back when I have time to return to the scene of the crime.
Meanwhile note that I have an old wireless keyboard by the same manufacturer and the same problem occurs with it. Both use the same model of dongle but I switched them without noting any difference.
Will report back when I have time to return to the scene of the crime.
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
Eliminate one possible problem with the hard drive.
Corrupted file system.
Boot with the Tahrpup DVD.
The hard drive partitions cannot be mounted to do this check.
Run Gparted.
Selected to see the hard drive.
Right click on a partition.
Select check.
Should check and correct anything wrong with the filesystem (format) of the partition.
Check all of them, if you have more than one partition.
Corrupted file system.
Boot with the Tahrpup DVD.
The hard drive partitions cannot be mounted to do this check.
Run Gparted.
Selected to see the hard drive.
Right click on a partition.
Select check.
Should check and correct anything wrong with the filesystem (format) of the partition.
Check all of them, if you have more than one partition.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24
-
- Posts: 125
- Joined: Sat 08 Jan 2011, 01:24