Re: USB keyboard problems / USB layout / USB xkbmap
Thank you both for your efforts! I finally had some time to look at it again: 1.) Booting into the recovery mode results in the same, i.e. z and y are changed as well as other keyboard specific issues such as Umlaute (ä.ö etc.) do not work. 2.) Executing setkbmap - query in normal mode shows that the layout is ch - although it is obviously not. Note that the problem exists due to a post also in Arch Linux, with the same keyboard and German (de) layout. 3.) I could fix it by putting a *.desktop file into /usr/share/gnome/autostart, executing setxkbmap (full path was necessary, else it did not work), i.e.: [Desktop Entry] Type=Application Exec=/usr/bin/X11/setxkbmap ch Hidden=false X-GNOME-Autostart-enabled=true Name=setkeyboard I have in the meanwhile submitted this issue as a bug to Debian concerning package X11 - although it might concern another package. greetings, chris Am 19. März 2012 18:25 schrieb Kelly Clowers kelly.clow...@gmail.com: On Mon, Mar 19, 2012 at 04:55, Christian Frey christian.frey...@gmail.com wrote: OK, let's write it up properly ;) snip Then I attached the Logitech K340 USB keyboard, the keyboard works but the language settings don't, i.e. I have obviously a GB layout. The only way to change this so far is to use: setxkbmap ch After executing this commmand, everything works fine - in the terminal as well as in GNOME, meaning I have the proper layout (I know that there are specific problems with Wheezy and USB keyboards known, and it is suggested to activate Legacy support in the BIOS. I have first to check if I have this option in the BIOS at all. Remark: Ubuntu 10.10 does not have all these problems). 2.) My etc/default/keyboard looks ok: # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL=pc105 XKBLAYOUT=ch XKBVARIANT= XKBOPTIONS=terminate:ctrl_alt_bksp BACKSPACE=guess snip Lets see, a couple of things to check. The /etc/default/keyboard file sets the console as well, so you can try rebooting and choose to go into single user mode (recovery mode). That way you can see if something at a higher runlevel (in gnome or similar) is overriding it or if it not applying in the first place. Another test would be to reboot and before running setxkbmap ch run setxkbmap -query, which will print the current setup. If it is ok at first, but gets overridden, we will have to track down what is changing it. If it is not setting it correctly in the first place, we need to figure out why. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=8+fKXTgO2y71=aVedhwRE1-ZiC=9je5cnl+itckcf...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cad5x0ead2+27tujdzoxgeco062nzl1z01p_x6grmp7cdxdn...@mail.gmail.com
USB keyboard problems / USB layout / USB xkbmap
OK, let's write it up properly ;) 1.) During Installation of Wheezy, I had to exchange my Logitech K340 with a PS/2 keyboard in order to install Wheezy as the USB-Keyboard did not react in the installer of Wheezy (although it did in the BIOS and also, interestingly, in Squeeze installer - as a test). Installation went fine, except that I would prefer that if one has choosen the system language (i.e. English), the list appearing later for countries to determine such things as currency etc. consists only of English speaking countries. Contrary, the keyboard could be choosen properly as Swiss German. So, after login (I use GNOME/WHEEZY), my old PS/2 worked properly (i.e. no z and y change or Umlaute such as ä, ö...). Then I attached the Logitech K340 USB keyboard, the keyboard works but the language settings don't, i.e. I have obviously a GB layout. The only way to change this so far is to use: setxkbmap ch After executing this commmand, everything works fine - in the terminal as well as in GNOME, meaning I have the proper layout (I know that there are specific problems with Wheezy and USB keyboards known, and it is suggested to activate Legacy support in the BIOS. I have first to check if I have this option in the BIOS at all. Remark: Ubuntu 10.10 does not have all these problems). 2.) My etc/default/keyboard looks ok: # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL=pc105 XKBLAYOUT=ch XKBVARIANT= XKBOPTIONS=terminate:ctrl_ alt_bksp BACKSPACE=guess 3.) The problem seems to be known, if looking here also in ArchLinux: http://www.loggn.de/arch-linux-xorg-deutsches-tastaturlayout-logitech-k340-tastatur-schnurlos/ If this problem is specific to K340, I do not know. So far I know that setxkbmap ch helps to solve it. How can I automatize this command such that I don't have to enter it after every startup ? In ArchLinux, it was put in autostart of openbox. GNOME has also an autostart, there I put it - but seems not to work (maybe I have to check again). Anyway, also this is not a clean solution. There should be a way to fix that properly. Thanks! Chris Am 19. März 2012 12:36 schrieb Camaleón noela...@gmail.com: On Sat, 17 Mar 2012 20:36:18 +0100, Christian Frey wrote: Hey together, Wow... what a mess. Sir, no html postings, please. (...) I have to say that I want to have the system language English and the locale Region setting set to Switzerland as well as the Keyboard. The System Setting GUI shows me that I have British English as Language, as Format UK and as Layout Swiss German keyboard. I guess it mixes somehwere up between Format and Layout. Also it was not possible during install, after choosing English as sys language to choose as Format Switzerland. However, the keyboard I could choose as Swiss one. I'm not sure to have properly understood the issue... are you saying your keyboard layout is not the desired? If yes, what's the current one and what do you want to get? If you are using a graphical DE, this can be set from the keyboard configuration settings. If you're on console, you can edit /etc/default/ keyboard file. How can I fix this issue // Thx./ A reconfigure of the keyboard configuration respectively of the locales did not really help. The Format cannot be changed in the GUI. It is not clear to me what you understand for keyboard format :-? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jk75og$6c2$7...@dough.gmane.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAD5x0EYqFLLw3EPJERhC0m+-JdA-kfihmqXWNeuVOAKUchxQ=a...@mail.gmail.com
Re: USB keyboard problems / USB layout / USB xkbmap
On Mon, 19 Mar 2012 12:55:35 +0100, Christian Frey wrote: OK, let's write it up properly ;) (...) I already replied to this in your first thread. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jk7mkb$6c2$2...@dough.gmane.org
Re: USB keyboard problems / USB layout / USB xkbmap
On Mon, Mar 19, 2012 at 04:55, Christian Frey christian.frey...@gmail.com wrote: OK, let's write it up properly ;) snip Then I attached the Logitech K340 USB keyboard, the keyboard works but the language settings don't, i.e. I have obviously a GB layout. The only way to change this so far is to use: setxkbmap ch After executing this commmand, everything works fine - in the terminal as well as in GNOME, meaning I have the proper layout (I know that there are specific problems with Wheezy and USB keyboards known, and it is suggested to activate Legacy support in the BIOS. I have first to check if I have this option in the BIOS at all. Remark: Ubuntu 10.10 does not have all these problems). 2.) My etc/default/keyboard looks ok: # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL=pc105 XKBLAYOUT=ch XKBVARIANT= XKBOPTIONS=terminate:ctrl_alt_bksp BACKSPACE=guess snip Lets see, a couple of things to check. The /etc/default/keyboard file sets the console as well, so you can try rebooting and choose to go into single user mode (recovery mode). That way you can see if something at a higher runlevel (in gnome or similar) is overriding it or if it not applying in the first place. Another test would be to reboot and before running setxkbmap ch run setxkbmap -query, which will print the current setup. If it is ok at first, but gets overridden, we will have to track down what is changing it. If it is not setting it correctly in the first place, we need to figure out why. Cheers, Kelly Clowers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAFoWM=8+fKXTgO2y71=aVedhwRE1-ZiC=9je5cnl+itckcf...@mail.gmail.com
Dell E6410, squeeze, touchpad anddddd keyboard problems
Apologies for the long post but it is along and sad story :)
I have enough ram (8Gb) on this laptop.
Maybe all the problems are related to my inabillity to disable the touchpad.
On this
syeX1
(I pushed Cntl-C otherwise it would have been a few lines of these)
sorry, that was meant to be 'system X11 functions without
/etc/X11/xorg.conf.'
As you can see in the above line sometimes the keyboard misses a pressed
key ('sye' - must have been 'system') and sometimes it repeats keys. Other
times, like when I work in Emacs with more than one buffer in split windows,
the cursor jumps to another frame and the typing continues in another
buffer.
On my previous laptop (Thinkpad R61e) I could use the following to disable
the touchpad:
/usr/bin/synclient TouchpadOff=\
`/usr/bin/synclient -l | sed -ne \
's/\(TouchpadOff *= *\)\([01]\)/\2/p' | sed -e 'y/01/10/'`
Now when I try this I get 'Couldn't find synaptics properties. No synaptics
driver loaded?'
I have created a /etc/X11/xorg.conf with the following contents:
Section InputClass
Identifier SynPS/2 Synaptics TouchPad
Option LeftEdge 1700
Option RightEdge 5700
Option TopEdge 1700
Option BottomEdge5100
Option FingerLow 25
Option FingerHigh30
Option MaxTapTime180
Option MaxTapMove220
Option VertScrollDelta 100
Option MinSpeed 0.09
Option MaxSpeed 0.6
Option HorizEdgeScroll true
Option TapButton11
Option SHMConfig true
EndSection
in the hope that it will load the synaptics driver, but that did not make
any difference.
Then I installed touchfreeze but that did not solve my problems.
Any idea how to solve this mess?
Regards.
Johann
--
Johann SpiesTelefoon: 021-808 4699
Databestuurder / Data manager
Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie
Centre for Research on Evaluation, Science and Technology
Universiteit Stellenbosch.
And there were in the same country shepherds abiding
in the field, keeping watch over their flock by night.
And, lo, the angel of the Lord came upon them, and the
glory of the Lord shone round about them: and they were
sore afraid. And the angel said unto them, Fear not:
for behold I bring you good tidings of great joy, which
shall be to all people. For unto you is born this day
in the city of David a Saviour, which is Christ the
Lord.Luke 2:8-11
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101223134401.ga17...@sun.ac.za
Re: Dell E6410, squeeze, touchpad anddddd keyboard problems
On 12/23/2010 08:44 AM, Johann Spies wrote:
Apologies for the long post but it is along and sad story :)
I have been made sad by a Dell laptop or two. ;-)
...
Maybe all the problems are related to my inabillity to disable the touchpad.
On this
syeX1
(I pushed Cntl-C otherwise it would have been a few lines of these)
sorry, that was meant to be 'system X11 functions without
/etc/X11/xorg.conf.'
As you can see in the above line sometimes the keyboard misses a pressed
key ('sye' - must have been 'system') and sometimes it repeats keys. Other
times, like when I work in Emacs with more than one buffer in split windows,
the cursor jumps to another frame and the typing continues in another
buffer.
On my previous laptop (Thinkpad R61e) I could use the following to disable
the touchpad:
/usr/bin/synclient TouchpadOff=\
`/usr/bin/synclient -l | sed -ne \
's/\(TouchpadOff *= *\)\([01]\)/\2/p' | sed -e 'y/01/10/'`
Now when I try this I get 'Couldn't find synaptics properties. No synaptics
driver loaded?'
I had the same sort of issue with a Dell Precision M70 laptop. The
answer was to change the touchpad setting in the BIOS setup program. The
wording on this one (which is actually a Lat. D810 or somesuch
motherboard / BIOS) I had to look at the boot behavior of the touchpad.
The choices weren't exactly what I would have expected. They were along
the lines of:
1. touchpad enabled
2. touchpad disabled when PS/2 mouse is connected
3. serial mouse
The one that succeeded in disabling the touchpad was the serial mouse
setting.
If you have a similar option for turning off the touchpad in your BIOS I
strongly suggest that you use it. That way, you won't have to use an
xorg.conf file and the OS doesn't have to deal with the little bugger at
all.
...
Regards.
Johann
I hope that helps.
Gilbert
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d13549c.4090...@comcast.net
Re: Dell E6410, squeeze, touchpad anddddd keyboard problems
On Thu, Dec 23, 2010 at 03:54:36PM +0200, Gilbert Sullivan wrote: I had the same sort of issue with a Dell Precision M70 laptop. The answer was to change the touchpad setting in the BIOS setup program. The wording on this one (which is actually a Lat. D810 or somesuch motherboard / BIOS) I had to look at the boot behavior of the touchpad. The choices weren't exactly what I would have expected. They were along the lines of: 1. touchpad enabled 2. touchpad disabled when PS/2 mouse is connected 3. serial mouse The one that succeeded in disabling the touchpad was the serial mouse setting. Thanks Gilbert. That has disabled the touchpad. Now let us hope the other keyboard-problems will come to an end. Immediately as I type this, it feels if the keyboard reaction is faster and so far I did not miss a character. Regards Johann -- Johann SpiesTelefoon: 021-808 4699 Databestuurder / Data manager Sentrum vir Navorsing oor Evaluasie, Wetenskap en Tegnologie Centre for Research on Evaluation, Science and Technology Universiteit Stellenbosch. And there were in the same country shepherds abiding in the field, keeping watch over their flock by night. And, lo, the angel of the Lord came upon them, and the glory of the Lord shone round about them: and they were sore afraid. And the angel said unto them, Fear not: for behold I bring you good tidings of great joy, which shall be to all people. For unto you is born this day in the city of David a Saviour, which is Christ the Lord.Luke 2:8-11 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101223144616.ga4...@sun.ac.za
Re: Dell E6410, squeeze, touchpad anddddd keyboard problems
On 12/23/2010 09:46 AM, Johann Spies wrote: Thanks Gilbert. That has disabled the touchpad. Now let us hope the other keyboard-problems will come to an end. Immediately as I type this, it feels if the keyboard reaction is faster and so far I did not miss a character. I'll keep my fingers crossed for you. My main problem with touchpads is that the tap-to-click function is enabled by default. This is probably the silliest device default I've ever seen because it causes so much trouble. It's a duplicate function since you already have buttons for doing the clicking. Not having a driver means no way to adjust sensitivity and the stupid device keeps sabotaging you as you try to work. The nasty little combination Alps touchpad / touchstick on my M70 would cause the cursor to jump while I was typing. I didn't even actually have to touch the pad or stick. Sometimes just getting near one or the other of them would cause the cursor to move. I have an expensive KVM in one of my server racks that has exactly the same problem. I wind up using an auxiliary keyboard and mouse on that rack. Dumb. Dumb. Dumb. And the manufacturer (TrippLite, are you listening?) provides no way to turn of tap-to-click. I don't remember having a problem with repeating characters, but I wouldn't doubt that the touchpad on your system may have had something to do with what you were seeing. I hope it works out for you. Regards Johann Regards, Gilbert -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d137c26.4000...@comcast.net
Re: Dell E6410, squeeze, touchpad anddddd keyboard problems
On 12/23/2010 08:44 AM, Johann Spies wrote:
Apologies for the long post but it is along and sad story :)
I have enough ram (8Gb) on this laptop.
Maybe all the problems are related to my inabillity to disable the touchpad.
On this
syeX1
(I pushed Cntl-C otherwise it would have been a few lines of these)
sorry, that was meant to be 'system X11 functions without
/etc/X11/xorg.conf.'
As you can see in the above line sometimes the keyboard misses a pressed
key ('sye' - must have been 'system') and sometimes it repeats keys. Other
times, like when I work in Emacs with more than one buffer in split windows,
the cursor jumps to another frame and the typing continues in another
buffer.
On my previous laptop (Thinkpad R61e) I could use the following to disable
the touchpad:
/usr/bin/synclient TouchpadOff=\
`/usr/bin/synclient -l | sed -ne \
's/\(TouchpadOff *= *\)\([01]\)/\2/p' | sed -e 'y/01/10/'`
Now when I try this I get 'Couldn't find synaptics properties. No synaptics
driver loaded?'
I have created a /etc/X11/xorg.conf with the following contents:
Section InputClass
Identifier SynPS/2 Synaptics TouchPad
Option LeftEdge 1700
Option RightEdge 5700
Option TopEdge 1700
Option BottomEdge5100
Option FingerLow 25
Option FingerHigh30
Option MaxTapTime180
Option MaxTapMove220
Option VertScrollDelta 100
Option MinSpeed 0.09
Option MaxSpeed 0.6
Option HorizEdgeScroll true
Option TapButton11
Option SHMConfig true
EndSection
in the hope that it will load the synaptics driver, but that did not make
any difference.
Then I installed touchfreeze but that did not solve my problems.
Any idea how to solve this mess?
Regards.
Johann
If you use a KDE distro, like PCLINUXOS, you can get synaptiks which
perfectly
disables the scratchpad as long as an external pointing device is
plugged in.
Nothing in the debian repos works, afaik.
--doug
--
Blessed are the peacemakers...for they shall be shot at from both sides. --A.
M. Greeley
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d13e0a4.4080...@optonline.net
Keyboard problems
A long time ago, probably around March or so, my keyboard was fine. I use three keyboard layouts, and I found that Alt+Capslock keychord useful for switching between the three of them. It was so set up in the Gnome preferences, and all was well. At some point later during some upgrade (I track testing with an occasional non-critical unstable package), this merry arrangement was lost, and has been broken ever since. Now the Alt+Capslock keychord isn't recognised, but if I go into the Gnome preferences and make any modifications to the keychords use for switching keyboard layouts (e.g. click and unclick one of the many other keychords available) it works again, minus the minor discomfort that the keyboard capslock LED toggles when I do the Alt+Capslock keychord. This didn't happen before. I have seen similar behaviour in other GTK+ apps. In Xchat, for instance, I like Ctrl+Shift+n and C-S-p for switching between the previous and next tab (looks similar to Emacs keychords, and feels comfortable). However, I see a very similar behaviour in that restarting Xchat makes the keychords non-functional until I go again into the Xchat preferences and again make some random change to the keychords therein and undo it immediately. What's going on? It's freeze time now, and I want this problem to get fixed when lenny releases, since my mom will be using lenny on her laptop when it releases. I need help figuring out even what package to file a bug for. Thanks, - Jordi G. H. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
overclocking AMD64 gives X mouse/keyboard problems [WAS: mouse/keyboard not responding under Xorg]
On Sat, 2008-01-05 at 20:43 +, michael wrote:
On Fri, 2008-01-04 at 12:16 +, michael wrote:
On Thu, 2008-01-03 at 15:51 +, michael wrote:
I've not managed to define precisely when I get problems but I'm
noticing
the following symptoms and was wondering if some kind soul would help me
debug what's going on in order to get to a solution? Thanks, Michael
set-up: etch, gnome (eg gnome-core 2.14.3.6), metacity 2.14.5-4 and
Dell/Logitech USB optical mouse (seems to work fine in WinXP), with
nVidia graphics card/TwinView and 2 monitors (diff resolutions)
symptoms (occasional and not sure how to repeat)
a) double clicking won't select anything
b) in evolution, clicking on a new message or folder has no effect
c) the cursor (arrowhead) disappears - if I set prefs to show cursor by
depressing 'CNTL' I get the moving rectangles but there's no cursor
there)
d) focus doesn't move to new window (as it should and usually does)
I think the following is also a symptom but not 100% sure:
e) doing ALT-TAB to move between windows does nothing on very first
ALT-TAB
If it's the keyboard that's failed then using I also cannot get Gnome
menus (it selects the top level but nothing is shown) but can use the
mouse to open more new app/windows and then at some pt the keyboard
seems to be 'reset' such that it starts working again.
I've tried KDE and that also has the keyboard not responding (eg if I
try to switch desktops quickly then the keyboard stops responding) -
opening the control centre and changing options in there appears to
'reset' the keyboard.
Any thoughts either on what's going on or how to debug it to narrow
down the issues? I've asked on the Debian mailing list but am still
stuck. I've had this line in my xorg.conf re Mouse device:
Option Protocol ImPS/2
although it's a USB mouse I'm using, but commenting it out I still see
the same issues
adding boot kernel option 'noapic' (as suggested on some fora) doesn't
help
the problem seems to be over-clocking the AMD chip. if i don't overclock
(in BIOS) all is fine. I presume X/USB/{what?} has a timing problem for
overclocking?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: (Xen + VNC ) keyboard problems
Ok keymap=es solved it On Nov 12, 2007 8:40 AM, Javier Barroso [EMAIL PROTECTED] wrote: Hi, Do you know if Xen + VNC (DOM 0 is running a vncserver than allow access to DomU ) can manage spanish (other langs?) keyboard layout when you are using vncviewer to access to DomU ? Now I can't write '|' because I don't know where is it :( ... I added keymap=es (I cann't remember the reference) to config file but it didn't work Any idea ? Thank you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
(Xen + VNC ) keyboard problems
Hi, Do you know if Xen + VNC (DOM 0 is running a vncserver than allow access to DomU ) can manage spanish (other langs?) keyboard layout when you are using vncviewer to access to DomU ? Now I can't write '|' because I don't know where is it :( ... I added keymap=es (I cann't remember the reference) to config file but it didn't work Any idea ? Thank you! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
keyboard problems on boot
Hi, I'm using a Goldtouch 4200U usb keyboard with Debian Etch, kernel 2.6.16.13. The keyboard layout resembles a laptop keyboard, with about half of the keys on the right half having dual function as a number pad. When I first start the computer, those keys don't work on the gdm login screen. If I press the Num Lock key twice (on, then off), all the keys work. Any idea what the problem is? Thanks, Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
keyboard problems with PowerBook 3400c
Got no responses on Debian-PowerPC Where can I learn how to deal with missing standard keys on PB 3400 keyboard? How do I do Shift-PageUp, Home and End (in places where Ctrl-A and Ctrl-E won't work)? How do I middle-click to paste? TIA for any help, Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
upgrade and keyboard problems
Hi. I agree it's way to lame to ask this, but since I couldn't find out by myself here is the question: I have an abnt2 keyboard and it was just perfect until my last apt-get upgrade. All keys work fine BUT the 'question mark' and '/'. This happens just on X. Here is the info: XF86Config-4 Option XkbModel abnt2 Option XkbLayout br dpkg-reconfigure console-common Looking for keymap to install: br-abnt2 By the way, I'm on the unstable tree. Thanks for any help this is really bothering me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade and keyboard problems
Em Quarta 21 Setembro 2005 10:58, gothicdoom escreveu: XF86Config-4 I've this line in addition to the listed bellow: Option XkbModel pc105 Option XkbModel abnt2 Option XkbLayout br -- Mario O.de Menezes, Ph.D. Many are the plans in a man's heart, but LinuxUser: #24626 is the Lord's purpose that prevails Pv 19.21 http://www.ipen.br/~mario -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: upgrade and keyboard problems
It's a known feature that any Xfree update will possibly break an existing config. I filed this bug (overwriting the XF86Config-4) in June: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312101 Feel free to add info to the bug report. Best regards, Hannes.
Re: Keyboard problems since last upgrade
Am Mi, den 07.04.2004 schrieb Olle Eriksson um 2:11: On Tuesday 06 April 2004 16.20, Joerg Johannes wrote: Hi everybody Last friday I upgraded my system (sid) and since then, I cannot type the less than and greater than signs anymore. When I press this key (It is a german keyboard, the key is just beside the left shift key), nothing happens. This is especially annoying when using emacs (cannot jump to the top/bottom of a buffer any more) and when trying to use pipes (cannot access the pipe symbol, which is AltGR+less than). First I suspected my keyboard was out of order, but the key works fine in text-mode. Also, I get response for it when I run xev: See if not your /etc/X11/XF86Config-4 says that your keyboard is a 104-key type keyboard. I had the exact same problem here and that was it. Setting it to 105 keys solved the problem. Olle OK, thanks. That was it. joerg -- Gib GATES keine Chance! signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Keyboard problems since last upgrade
Hi everybody Last friday I upgraded my system (sid) and since then, I cannot type the less than and greater than signs anymore. When I press this key (It is a german keyboard, the key is just beside the left shift key), nothing happens. This is especially annoying when using emacs (cannot jump to the top/bottom of a buffer any more) and when trying to use pipes (cannot access the pipe symbol, which is AltGR+less than). First I suspected my keyboard was out of order, but the key works fine in text-mode. Also, I get response for it when I run xev: KeyPress event, serial 28, synthetic NO, window 0xe1, root 0x3f, subw 0x0, time 65210, (170,227), root:(202,283), state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: KeyRelease event, serial 28, synthetic NO, window 0xe1, root 0x3f, subw 0x0, time 65244, (170,227), root:(202,283), state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: Can anybody help me please to get my pipe symbol back? Thanks, joerg PS.: xlibs co are now 4.3.0-7, I tried downgrading them to 4.3.0-5 (which were still in /var/cache/apt/archives/), but the keys did not come back. -- Gib GATES keine Chance! signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Keyboard problems since last upgrade
On Tue, 06 Apr 2004 16:20:12 +0200 Joerg Johannes [EMAIL PROTECTED] wrote: Hi everybody Last friday I upgraded my system (sid) and since then, I cannot type theless than and greater than signs anymore. [...] Also, I get response for it when I run xev: KeyPress event, serial 28, synthetic NO, window 0xe1, root 0x3f, subw 0x0, time 65210, (170,227), root:(202,283), state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: KeyRelease event, serial 28, synthetic NO, window 0xe1, root 0x3f, subw 0x0, time 65244, (170,227), root:(202,283), state 0x0, keycode 94 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: As a temporary workaround in X, you can try xmodmap -e keycode 94 = less greater I don't know if this will give you the pipe symbol back though. -- Got Backup? Jabber: Shadowdancer at jabber.fsinf.de pgp0.pgp Description: PGP signature
Re: Keyboard problems since last upgrade
On Tuesday 06 April 2004 16.20, Joerg Johannes wrote: Hi everybody Last friday I upgraded my system (sid) and since then, I cannot type the less than and greater than signs anymore. When I press this key (It is a german keyboard, the key is just beside the left shift key), nothing happens. This is especially annoying when using emacs (cannot jump to the top/bottom of a buffer any more) and when trying to use pipes (cannot access the pipe symbol, which is AltGR+less than). First I suspected my keyboard was out of order, but the key works fine in text-mode. Also, I get response for it when I run xev: See if not your /etc/X11/XF86Config-4 says that your keyboard is a 104-key type keyboard. I had the exact same problem here and that was it. Setting it to 105 keys solved the problem. Olle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: persistent keyboard problems
on Tue, 15 Jan 2002 04:06:29PM -0600, Gary Turner insinuated:
If your problems with repeated keys occurs only on certain keys, it
could very well be a hardware fault. Were it a software phenomenon,
I would expect *every* key to be affected.
i'm sure i don't fully understand this, but were it a hardware
problem, i would think that something as simple as running `xset` at
the command line wouldn't fix it ...
oh, and i just proved my own point. wow can i be stupid sometimes.
i borrowed another keyboard, plugged it in, and replicated my
problem ... had a whole nother frustrated post composed, when i looked
at *every line* of my .xsession file, and found this line stuck in
there:
/usr/X11R6/bin/xset r rate 100 255
--which was the source of my problem -- when i tried setting the
keybaord rate like that, itttwentt haaywir
lik it ddi beforeee and typeeeddd lik thiss,
hich is raather obnooxiousss, wwwoulddyou nottt
say? i guess the old version of X just interfaced with my keyboard(s)
differently.
so the problem's solved. but i still am a little confused -- (1)
while this line appears about 4th or so in the whole file, i had been
calling the correct line *last* in the file for quite a few tries.
even though i had a line above it which made the rate wrong, calling
that line afterwards should have fixed it. (2) in doing all this,
i've noticed that /usr/bin/X11/ is symlinked to /usr/X11R6/bin. why
is this? it seems redundant.
what i did manage to do in all this, however, between reboots and
/etc/init.d/xdm restarts, is to completely kill my saved WindowMaker
configurations. don't know how i did this, but they appear to be gone
::sniff:: so i'll just suck it up and re-do them. but i'm pretty
clueless as to what i did that killed them -- all i have done is
reboot, edit .xsession, and /etc/init.d/xdm {start,stop,restart}. ...
hm.
but the keyboard problem *is* solved. so, thanks for your patience
and help!
/nori
[EMAIL PROTECTED]--
-http://www.sccs.swarthmore.edu/~nori/jnl/daily.html
Re: persistent keyboard problems
also sprach nori heikkinen [EMAIL PROTECTED] [2002.01.16.0739 +0100]: i borrowed another keyboard, plugged it in, and replicated my problem ... had a whole nother frustrated post composed, when i looked at *every line* of my .xsession file, and found this line stuck in there: /usr/X11R6/bin/xset r rate 100 255 hehe. i put that there. april/may 2001'ish though... so the problem's solved. but i still am a little confused -- (1) while this line appears about 4th or so in the whole file, i had been calling the correct line *last* in the file for quite a few tries. even though i had a line above it which made the rate wrong, calling that line afterwards should have fixed it. not necessarily. xset seems to have a bug. for a while, i had to call it twice, once with 100 100, then 100 255 to get my effect. no other way would succeed. but hey, it's surely one of the oldest X tools, and noone really cares anymore i guess. (2) in doing all this, i've noticed that /usr/bin/X11/ is symlinked to /usr/X11R6/bin. why is this? it seems redundant. browse your system a little. you'll find many of those. /usr/X11R6/bin is the X11 Release 6 way of storing binaries that deal with X. but Debian sees these as binaries that are to remain in /usr/bin. so they met half way. i am actually surprised that the symlink isn't the other way around. btw: http://www.pathname.com/fhs will be able to give you a lot of background knowledge on why things are where they are. -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] if god had meant for us to be naked, we would have been born that way. pgpOXbf1FiWdr.pgp Description: PGP signature
Re: persistent keyboard problems
on Tue, 15 Jan 2002 03:09:16AM +0100, marTin insinuated: also sprach nori heikkinen [EMAIL PROTECTED] [2002.01.15.0020 +0100]: since upgrading to version 4 of X, my keyboard has been wildly erratic. (only in x, not in terminal mode.) i stuck the lines /usr/bin/X11/xset r rate 255 80 xset r rate 255 80 why twice? cuz once wasn't working. ;) in my ~/.xsession file, but they do absolutely no good, and every time i log into X, i have to `xset r rate 255 80` into the console to get it normal again. can you verify that the lines are actually called from your .xsession? have you checked ~/.xsession-errors? you might want to try echo statements around them. xset r rate 255 80 echo keyboard rate set then calling .xsession from an active shell echos keyboard rate set -- though it's not. in fact, when i call it from an active shell, it *un*sets the keyboard rate, and i have to manually re-call it. this is really pissing me off. anyone got any ideas?? it works for me. that's supposed to give you hope ;) :-P it does. i have faith. it's been suggested i just plug in another keyboard. however, i don't happen to have one lying around, and i like mine, for no real reason. i shouldn't have to do this, i think ... /nori [EMAIL PROTECTED]-- -http://www.sccs.swarthmore.edu/~nori/jnl/daily.html
Re: persistent keyboard problems
Nori Heikkinen [EMAIL PROTECTED] writes: hi all, this got lost in a thread above, and i'm clueless. since upgrading to version 4 of X, my keyboard has been wildly erratic. (only in x, not in terminal mode.) i stuck the lines /usr/bin/X11/xset r rate 255 80 xset r rate 255 80 in my ~/.xsession file, but they do absolutely no good, and every time i log into X, i have to `xset r rate 255 80` into the console to get it normal again. this is really pissing me off. anyone got any ideas?? If you're using kdm, gdm, or something similar that allows you to choose a window manager/desktop environment when logging in, you need to choose the default session for ~/.xsession to get sourced. Otherwise it'll be ignored. Perhaps this is your problem? -- Brian Nelson [EMAIL PROTECTED]
Re: persistent keyboard problems
also sprach Brian Nelson [EMAIL PROTECTED] [2002.01.15.0734 +0100]: If you're using kdm, gdm, or something similar that allows you to choose a window manager/desktop environment when logging in, you need to choose the default session for ~/.xsession to get sourced. Otherwise it'll be ignored. Perhaps this is your problem? she's an xdm purist. good point though. nori, xset from the console (manually) works? xset in .xsession, and executed from the console works? xset in .xsession, and sourced from the console works? xset in .xsession during session start works? (verify that with the echo call and ~/.xsession-errors. in general, what's .xsession-errors say? -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] as i learn the innermost secrets of the people around me, they reward me in many ways to keep me quiet. pgpkYKRJz9Vdf.pgp Description: PGP signature
Re: persistent keyboard problems
on Tue, 15 Jan 2002 10:52:29AM +0100, marTin insinuated: xset from the console (manually) works? yes. xset in .xsession, and executed from the console works? insofar as it executes the command ed after it, yes. but it doesn't set the rate when called in .xsession. xset in .xsession, and sourced from the console works? see above -- same problems. xset in .xsession during session start works? see problems above -- ed echo command just gets stuck into ~/.xsession-errors, but it doesn't set the keyboard rate. in general, what's .xsession-errors say? a lot of crap. having rm'd the entire file, running .xsession creates the following ~/.xsession-errors file: orange:~ cat .xsession-errors keyboard rate set xscreensaver-command: throttled. Identity added: /home/nori/.ssh/identity ([EMAIL PROTECTED]) /usr/bin/WindowMaker warning: WMRootMenu:invalid kbd shortcut specification Control+Meta+Backslash for entry exit i've got the lines that should be setting the keyboard rate first, but even though they seem to be working, the passphrase that i enter right after it is sensitive to a's and ss's, obviously *not* having set the keyboard rate. ~/.xsession looks like the following, if that helps at all: orange:~ cat .xsession #!/bin/sh xset r rate 255 80 echo keyboard rate set /usr/X11R6/bin/xset b 0 /usr/X11R6/bin/xset r rate 100 255 /usr/bin/X11/xrmdb test -f ~/.Xdefaults /usr/X11R6/bin/xrdb ~/.Xdefaults test -f ~/.Xresources /usr/X11R6/bin/xrdb ~/.Xresources /usr/bin/xscreensaver (sleep 5 /usr/bin/xscreensaver-command -throttle) /usr/bin/ssh-agent ~/bin/x-ssh-clients /usr/bin/X11/xset +fp $HOME/lib/fonts xset fp rehash tia, /nori [EMAIL PROTECTED]-- -http://www.sccs.swarthmore.edu/~nori/jnl/daily.html
Re: persistent keyboard problems
On Tue, 15 Jan 2002 14:29:18 -0600, Nori Heikkinen wrote: on Tue, 15 Jan 2002 10:52:29AM +0100, marTin insinuated: xset from the console (manually) works? yes. xset in .xsession, and executed from the console works? excise a bunch of stuff i've got the lines that should be setting the keyboard rate first, but even though they seem to be working, the passphrase that i enter right after it is sensitive to a's and ss's, obviously *not* having set the keyboard rate. Nori, I don't recall if this suggestion has been tried, and if so, never mind. If your problems with repeated keys occurs only on certain keys, it could very well be a hardware fault. Were it a software phenomenon, I would expect *every* key to be affected. A basic problem with any mechanical switching device (read 'key') is bounce. That is, as the switch makes, the contacts bounce back creating a break, followed by another make, followed Should the spring-rate/mass combo approach resonance, or damping be insufficient, this make-break sequence can be excessive, going on for longer than the built in delay. Which brings up 'delay.' Delay can be created as simply as putting a capacitor across the switch points, or looping a bunch of gates that latch out the switch condition after everything has settled down. These can go bad too. Any part of the above going bad can cause *your* single keystroke to be seen by the polling device as multiple strokes. So, if you haven't yet, beg borrow or steal another keyboard to see if the problem persists. gt--the pedant has left the hall Yes I fear I am living beyond my mental means--Nash
persistent keyboard problems
hi all, this got lost in a thread above, and i'm clueless. since upgrading to version 4 of X, my keyboard has been wildly erratic. (only in x, not in terminal mode.) i stuck the lines /usr/bin/X11/xset r rate 255 80 xset r rate 255 80 in my ~/.xsession file, but they do absolutely no good, and every time i log into X, i have to `xset r rate 255 80` into the console to get it normal again. this is really pissing me off. anyone got any ideas?? thanks a ton, /nori [EMAIL PROTECTED]-- -http://www.sccs.swarthmore.edu/~nori/jnl/daily.html
Re: persistent keyboard problems
also sprach nori heikkinen [EMAIL PROTECTED] [2002.01.15.0020 +0100]: since upgrading to version 4 of X, my keyboard has been wildly erratic. (only in x, not in terminal mode.) i stuck the lines /usr/bin/X11/xset r rate 255 80 xset r rate 255 80 why twice? in my ~/.xsession file, but they do absolutely no good, and every time i log into X, i have to `xset r rate 255 80` into the console to get it normal again. can you verify that the lines are actually called from your .xsession? have you checked ~/.xsession-errors? you might want to try echo statements around them. this is really pissing me off. anyone got any ideas?? it works for me. that's supposed to give you hope ;) -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] out of my mind. back in five minutes. pgpdEEkOEEsBb.pgp Description: PGP signature
Re: keyboard problems
on Sat, Mar 24, 2001 at 01:13:52AM -0500, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: I have a weird problem with my keyboard, but I'm not sure what to check to figure out the problem. I have a desktop system, and the keyboard works as expected in X and in the console. However when I ssh into my gateway box, the keyboards works fine in the commandline, but when I run a command like say nslookup, my backspace key stops working. Both systems are debian 2.2 stable. The keypad problem also occurs when I ssh to my boxes at home (telnet does the same BTW) from my sunbox at work. I don't know much about terminal emulation, keymaps, and bindings, etc so what can I read to try to troubleshoot this? I have a typical i386 style keyboard with microsoft keys at home, and a type 5c sun keyboard at work. Just a me too. Sometimes. I'll get a keyboard fsckup, generally in an X terminal, after invoking screen and bailing out of it in an unwholesome manner. No fix, but you're either not crazy or in good company. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpigsvDbp00N.pgp Description: PGP signature
keyboard problems
I have a weird problem with my keyboard, but I'm not sure what to check to figure out the problem. I have a desktop system, and the keyboard works as expected in X and in the console. However when I ssh into my gateway box, the keyboards works fine in the commandline, but when I run a command like say nslookup, my backspace key stops working. Both systems are debian 2.2 stable. The keypad problem also occurs when I ssh to my boxes at home (telnet does the same BTW) from my sunbox at work. I don't know much about terminal emulation, keymaps, and bindings, etc so what can I read to try to troubleshoot this? I have a typical i386 style keyboard with microsoft keys at home, and a type 5c sun keyboard at work. Thanks.
keyboard problems
I originally thought it was a problem with netscape, but it appears to be a larger issue. There are times when my keyboard won't respond unless I launch another application or maximize(or otherwise bring to the foreground) the window of an application already running. Only then can I go back to the original application and use the keyboard. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: keyboard problems
I originally thought it was a problem with netscape, but it appears to be a larger issue. There are times when my keyboard won't respond unless I launch another application or maximize(or otherwise bring to the foreground) the window of an application already running. Only then can I go back to the original application and use the keyboard. Check your window manager's focus settings. Try different variations of it... I've seen and heard of this before with people using Enlightenment. Good luck Hall
Re: Keyboard problems with XFree 4.0.2
Hi Christian Terboven, I recently have installed XFree86 4.0.2 on my debian potato. Everything works fine, but I can not use the AltGr+X keys (for example I can not produce an (at)-symbol). TheXkbLayout is de. Has anybody an idea what is wrong? ---end quoted text--- Section InputDevice Identifier Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys Option AutoRepeat250 60 Option Alt_L Meta Option RightAlt Meta Option RightCtl Control Option ScrollLockCompose EndSection works great here with a germany keyboard layout. -- Bye Gregor Anders |---| | eMail: Gregor Anders [EMAIL PROTECTED] ---| |Key fingerprint: 7131 4011 6D79 5467 F073 BDA1 C55E 8584 7860 C7DE| |get my GPG-key from: wwwkeys.de.pgp.net - KeyID: 0x7860C7DE| |---|
Keyboard problems with XFree 4.0.2
Hi all! I recently have installed XFree86 4.0.2 on my debian potato. Everything works fine, but I can not use the AltGr+X keys (for example I can not produce an (at)-symbol). TheXkbLayout is de. Has anybody an idea what is wrong? TIA Christian
X keyboard problems
Hi all. I have had to rebuild the system half way from scratch (messed up X). I've installed X 3.3.6 from stable as a base, and then upgraded some of X components to 4.0.2 (some apps like gimp1.2 is precompiled for 4.0.2 only). Right now 90% of the X on my system is 4.0.2,, the rest 10% 3.3.6. They both coexist happily, except for one thing... XKB doesnt work, which means that I dont have delete and backspace buttons, I have to ^H my way through my typoes. The message X spits out is this: cannot open keymap/xfree86 for reading Could not open XKB keymap, falling back to pre-XKB Can anyone please help me with this? I dont know how much code without typoes I can write :) Andrei -- First there was Explorer... Then came Expedition. This summer Coming to a street near you.. Ford Exterminator. -- Andrei Ivanov http://arshes.dyndns.org [EMAIL PROTECTED] 12402354 --
Keyboard problems
A couple of days ago I asked about my backspace key acting like my delete key in Netscape and other aps. The backspace key was deleting to the right instead of the left. Well I finally found it, but I haven't a clue as to why I had to do this: ln -sf /usr/X11R6/bin/xkbcomp /usr/X11R6/lib/X11/xkb/xkbcomp Why is my system looking in /usr/X11R6/lib/X11/xkb/xkbcomp for the keyboard layout? -- Christopher W. Aiken, Scenery Hill, Pa, USA chris at cwaiken dot com, www.cwaiken.com Current O/S: Debian 2.2 GNU/Linux
Keyboard problems with xfree86 4.0.1
Hi, A few weeks ago I upgraded to woody, and have been updating things since then. Recently, my xfree86 v3.3.6-11 (Mach64) server was thrown out and replaced with xfree86 v4.0.1, which I think is good. But now I have a problem with my keyboard. I've been trying to configure things both manually, and using xf86config, as xf86cfg does not work yet. The problem is mainly with the 'Alt Gr' key: previously I used 'Alt Gr'+2 to get @ and 'Alt Gr'+4 to get $, and so on with all the number keys. This no longer works. Also the norwegian letters 'æøå' does not work in the terminals, but works ok in netscape. This is my keyboard configuration from my v3.3.6-11, in which the above worked perfectly: Section Keyboard ProtocolStandard AutoRepeat 500 30 LeftAlt Meta RightAltMeta ScrollLock Compose RightCtlControl XkbKeycodes xfree86 XkbTypesdefault XkbCompat default XkbSymbols us(pc101) XkbGeometry pc XkbRulesxfree86 XkbModelpc104 XkbLayout no XkbVariant nodeadkeys EndSection My current keyboard configuration with v4.0.1, in which the above does not work: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout no Option XkbVariantnodeadkeys Option LeftAlt Meta Option RightAlt Meta Option ScrollLockCompose Option RightCtl Control EndSection Some log information: XFree86 Version 4.0.1d / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 27 October 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.2.18pre15 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Tue Nov 7 10:07:17 2000 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Graphics Device (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout no (**) XKB: layout: no (**) Option XkbVariant nodeadkeys (**) XKB: variant: nodeadkeys (**) |--Input Device Generic Mouse (II) Keyboard Generic Keyboard handled by legacy driver Couldn't load XKB keymap, falling back to pre-XKB keymap Any help on this would be appreciated. Thanks! Cheers, -- PhD student http://www.item.ntnu.no/~meling/ Hein Melingmailto:[EMAIL PROTECTED] Norwegian University of Science and Technology Department of Telematics, N-7491 Trondheim +47 7395 0393 (home) +47 7355 0269 (work)
Re: Keyboard problems with xfree86 4.0.1
A little follow-up information. I have still not resolved this problem, but have discovered that I can use the dk and de layout, and I wouldn't get the error message in the log: Couldn't load XKB keymap, falling back to pre-XKB keymap Any further assistance would be of enormous help. Thanks! Andre Berger wrote: Versuch mal Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout de EndSection I have tried various combinations now, using only the entries you used in your configuration. I have also tested using the de layout, and it actually worked better than no, except for a number of other keys such as yz... At least the Alt Gr key worked. I checked the log when using de and it did not report the following, as it did when using the no layout: Couldn't load XKB keymap, falling back to pre-XKB keymap Do you know what could cause this? And where do I find the keymaps that are usable. Cheers, -- PhD student http://www.item.ntnu.no/~meling/ Hein Melingmailto:[EMAIL PROTECTED] Norwegian University of Science and Technology Department of Telematics, N-7491 Trondheim +47 7395 0393 (home) +47 7355 0269 (work)
Re: Keyboard problems with xfree86 4.0.1
Hi Hein, I am having this very same problem except that I normally use the swedish keyboard layout, which is not working now, so I am very curious about some solution on this. Helgi Oern Hein Meling wrote: A little follow-up information. I have still not resolved this problem, but have discovered that I can use the dk and de layout, and I wouldn't get the error message in the log: Couldn't load XKB keymap, falling back to pre-XKB keymap Any further assistance would be of enormous help. Thanks! Andre Berger wrote: Versuch mal Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout de EndSection I have tried various combinations now, using only the entries you used in your configuration. I have also tested using the de layout, and it actually worked better than no, except for a number of other keys such as yz... At least the Alt Gr key worked. I checked the log when using de and it did not report the following, as it did when using the no layout: Couldn't load XKB keymap, falling back to pre-XKB keymap Do you know what could cause this? And where do I find the keymaps that are usable. Cheers, -- PhD student http://www.item.ntnu.no/~meling/ Hein Melingmailto:[EMAIL PROTECTED] Norwegian University of Science and Technology Department of Telematics, N-7491 Trondheim +47 7395 0393 (home) +47 7355 0269 (work) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- - *** Helgi Örn ** [EMAIL PROTECTED] * SuSE 7.0 * Debian/GNU * ** Caldera eDesktop 2.4** -
Re: Keyboard problems with xfree86 4.0.1
Hi Helgi, Currently I use the dk keyboard layout with some defects. I've had a look at the various files in /usr/lib/X11/xkb, but haven't really found anything different between dk and no versions of any files. So I don't understand why I get the error message in the log. Anyway, I just haven't had the time to look any further at this problem; so if you or anyone else finds a solution to this, I would like to hear about it. Have also sent a message on the xfree newbie list; no reply yet. Cheers, -- PhD student http://www.item.ntnu.no/~meling/ Hein Melingmailto:[EMAIL PROTECTED] Norwegian University of Science and Technology Department of Telematics, N-7491 Trondheim +47 7395 0393 (home) +47 7355 0269 (work)
mouse and keyboard problems in x 3.3.6
Good day, Thanks to help from several on this list, I am very close to getting my mouse and keyboard problems taken care of. I really appreciate the time out of your busy schedules. Here is where I'm at currently. I'm so very close to fixing both problems. My mouse works in console mode just fine, in x not so fine. The line in the /etc/gpm.conf file reads : type =PS/2, so I changed the same line to type=PS/2 in the XF86Config file. In the /etc/gpm.conf file there is a symbolic link from /dev/mouse to /etc/gpmdata. However, in the /etc/gpm.conf.file, an earlier line reads: device/etc/psaux. There is not a symbolic link between /dev/psaux to /dev/mouse. I took care of most of the keyboard problems, the only thing is that I have a microsoft natural keyboard, and I cannot use the number pad on the far right. Everything else on the keyboard works fine, and the server no longer sends me error messages when I try to start x. For your review, relevant sections of my XF86Config file as it now stands: ** keyboard section Protocol standard AutoRepeat500 5 XkbModel Microsoft EndSection *** Section Pointer ProtocolPS/2 Device /dev/gpmdata BaudRate 1200 #ZaxisMapping 4 5 Buttons3 EndSection ** X does start, and the pointer goes to the bottom of the screen, but it will only move back and forth across the bottom of the screen, but not up and down. regards, Bob Edwards [EMAIL PROTECTED] Fayetteville, Arkansas
Re: mouse and keyboard problems in x 3.3.6
On Wed, Oct 25, 2000 at 07:56:48AM -0500, Bob Edwards wrote: [...] The line in the /etc/gpm.conf file reads : type =PS/2, so I changed the same line to type=PS/2 in the XF86Config file. I just did the same thing yesterday, and I also got into trouble... In the /etc/gpm.conf file there is a symbolic link from /dev/mouse to /etc/gpmdata. However, in the /etc/gpm.conf.file, an earlier line reads: device/etc/psaux. There is not a symbolic link between /dev/psaux to /dev/mouse. I took care of most of the keyboard problems, the only thing is that I have a microsoft natural keyboard, and I cannot use the number pad on the far right. Everything else on the keyboard works fine, and the server no longer sends me error messages when I try to start x. For your review, relevant sections of my XF86Config file as it now stands: ** keyboard section Protocol standard AutoRepeat500 5 XkbModel Microsoft EndSection *** Section Pointer ProtocolPS/2 ^^ You may want to try Microsoft instead. That was given as the default protocol during my XF86Config. Well, I thought that couldn't be right (although the mouse was moving perfectly with it) as I also have a PS/2 mouse. So I changed the protocol to PS/2 and the device to /dev/psaux and the mouse was frozen forever... Device /dev/gpmdata ^^ This should be OK. BaudRate 1200 #ZaxisMapping 4 5 Buttons3 EndSection ** X does start, and the pointer goes to the bottom of the screen, but it will only move back and forth across the bottom of the screen, but not up and down. I hope the highlighted settings work for you as they do for me. Kind regards, Andreas.
keyboard problems
Something has happened to my console keyboard. The keys are all screwed up. When I press 'q' I get 'a', I have to hold down the 'shif' key to get nubmers The keyboard is only screwed up in the console. It is fine in Xwindows. Anyone know how I can get my keyboard back? Lance
x-keyboard problems
I've got keyboard working well without x. With X it works othervise, but some composed characters like ~ don't work. The keyboard is configured as a regular 101- kb and finnish layout. I've read somewhere that there exists a separate kb config program, but don't remember anymore how it is called and where I got the knowledge about it. Anybody knows how to get the kb working similar way with X as without? Used XF86Setup. - hv [EMAIL PROTECTED]
VI keyboard problems..
I can't seem to get backspace to work with gvim (or vim in an Eterm window). I've tried putting :fixdel in .vimrc but that doesn't seem to work.. help me :) -abr
Keyboard problems, LC_ALL, TERM
Dear Debianspecialists, I recently switched to Debian (2.1) from another distribution and now encounter a few problems I did not have before. I checked all written and online documentation, but could not find any help: Using kbdconfig I installed de.latin1-nodeadkeys as my default key map. It works fine, but some keys just do not work (that is keys with the German umlauts ä,ö,ü,ß. Using this keys only generates a beep, both on the console or in xterms under X11. Do you have an idea, to get this solved (if I `cat' a file with these characters, all is fine, xemacs also accepts the keys). In my earlier Linux-distrib this was no problem. When I open a ppp to my provider and telnet to another host (SunOS) debian transmit `xterm-debian' as value for the TERM variable. Where can I change this? (I need `xterm' or `vt100' , but I am too lazy typing `setenv TERM vt100 everytime I telnet to that host). Using the tcsh, I suddenly got the error message: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = (unset), LC_CTYPE = ISO-8859-1, LANG = C are supported and installed on your system. perl: warning: Falling back to the standard locale (C). What went wrong here? (I added some `complete' commands to /etc/csh.cshrc which seems to have caused this error. Strange enough it comes, when I quit netscape...). Apropos Netscape, my user is (for different reasons) not in /home/joh but in /homes/joh. All works fine ($HOME is OK, cd ~ is OK (tcsh), but if I start netscape4.07 (Debian package) It starts searching for /home/joh/.netscape, eventhough /etc/passwd says /homes/joh. Where do I have to correct this? Any hints are appreciated! Thank you very much Johannes -- Johannes Heinecke [EMAIL PROTECTED] Computerlinguistik or: [EMAIL PROTECTED] Humboldt-Universitat zu Berlin Tel: (030) 20192-553 10099 Berlin Fax: (030) 20196-729
Re: Keyboard problems, LC_ALL, TERM
Quoting Johannes Heinecke ([EMAIL PROTECTED]): When I open a ppp to my provider and telnet to another host (SunOS) debian transmit `xterm-debian' as value for the TERM variable. Where can I change this? (I need `xterm' or `vt100' , but I am too lazy typing `setenv TERM vt100 everytime I telnet to that host). My experience with SunOS is that if you put a ~/.terminfo tree on the sun with xterm-debian, everything works correctly. Just copy /etc/terminfo over recursively. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: Keyboard problems, LC_ALL, TERM
Quoting Johannes Heinecke ([EMAIL PROTECTED]): When I open a ppp to my provider and telnet to another host (SunOS) debian transmit `xterm-debian' as value for the TERM variable. Where can I change this? (I need `xterm' or `vt100' , but I am too lazy typing `setenv TERM vt100 everytime I telnet to that host). Create the file ~/.telnetrc and add something like this: the.host.name environ define TERM xterm -- Andreas Persenius [EMAIL PROTECTED]
FrameBuffer - keyboard problems
hi,
I have an S3 Trio3D video card so i had to use the framebuffer device if i
wanted a 1024x768 display.
Now i have some anoying keyboard problems. I can't use the AltGr key
anymore (it has become left-key). So any key like |@#{}[]`\ i cannot use
anymore in X.
The PgUp/PgDn and some other keys aren't working either, but i could solve
this with xmodmap. Though some people said me this is not a good
sollution.
I got the keyboard section from sombody with the same videocard and
was also using Framebuffer device and had the same problems. For him
this was a sollution, for me not. This is my keyboard section for the
moment:
Section Keyboard
ProtocolStandard #Standard|Xqueue
# XkbDisable
AutoRepeat 500 5
LeftAlt Meta
RightAltModeShift
ScrollLock Compose
RightCtlControl
XkbRulesxfree86
XkbModelpc101 #pc101|pc102|xfree86|microsoft
XkbLayout be
EndSection
Any help?
--
Bernhard DobbelsStudent Electronic Engineer
option Automation and Computersystems.
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
ICQ: 25783372
Re: FrameBuffer - keyboard problems
On Fri, Mar 05, 1999 at 01:52:22PM +0100, Bernhard Dobbels wrote:
I have an S3 Trio3D video card so i had to use the framebuffer device if i
wanted a 1024x768 display.
Now i have some anoying keyboard problems. I can't use the AltGr key
anymore (it has become left-key). So any key like |@#{}[]`\ i cannot use
anymore in X.
The PgUp/PgDn and some other keys aren't working either, but i could solve
this with xmodmap. Though some people said me this is not a good
sollution.
I got the keyboard section from sombody with the same videocard and
was also using Framebuffer device and had the same problems. For him
this was a sollution, for me not. This is my keyboard section for the
moment:
Section Keyboard
ProtocolStandard #Standard|Xqueue
# XkbDisable
AutoRepeat 500 5
LeftAlt Meta
RightAltModeShift
If you want AltGr to do the same as Alt, change that to Meta
ScrollLock Compose
RightCtlControl
XkbRulesxfree86
XkbModelpc101 #pc101|pc102|xfree86|microsoft
If it's a standard pc keyboard (or shudder a windows 95 one) that should
be pc102
XkbLayout be
EndSection
Any help?
The rest is the same as mine, but I also have the following lines:
XkbKeycodes xfree86
XkbTypesdefault
XkbCompat default
XkbSymbols us(pc101)
XkbGeometry pc
They were all put there by XF86Setup; I don't know what difference they make.
Hope that helps,
Matt
--
Matt Folwell, P2 Whewell's Court, Trinity College, Cambridge. CB2 1TQ
[EMAIL PROTECTED]
Re: FrameBuffer - keyboard problems
|If it's a standard pc keyboard (or shudder a windows 95 one) that should |be pc102 It is an original IBM keyboard manufactered in the UK in 1985, and still working very fine ;-) and it has 102 keys. But changing this line, didn't change anything in X? Maybe i've lost some file that x needs, but it doesn't complain: |XFree86 Version 3.3.3.1 / X Window System |(protocol Version 11, revision 0, vendor release 6300) |Release Date: December 29 1998 |If the server is older than 6-12 months, or if your card is newer |than the above date, look for a newer version before reporting |problems. (see http://www.XFree86.Org/FAQ) |Operating System: Linux 2.0.36 i586 [ELF] ^ ^ Can this be a problem? I have 2.2.1 i686 |Configured drivers: | FBDev: Server for frame buffer device | (Patchlevel 10): mfb, cfb8, cfb16, cfb24, cfb32 |(using VT number 12) |XF86Config: /usr/X11R6/lib/X11/XF86Config |(**) stands for supplied, (--) stands for probed/default values |(**) XKB: rules: xfree86 |(**) XKB: model: pc102 |(**) XKB: layout: be |(**) Mouse: type: MouseSystems, device: /dev/gpmdata, baudrate: 1200 |(**) Mouse: buttons: 3 |(**) FBDev: Graphics device ID: Primary Card |(**) FBDev: Monitor ID: Primary Monitor |(**) FontPath set to |/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/fonts/75dpi,/usr/X11/lib/X11/fonts/freefont,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled |(**) FBDev: Using default frame buffer video mode |(--) FBDev: Frame buffer device: VESA VGA |(--) FBDev: Video memory: 4096K @ 0xd800 |(--) FBDev: MMIO regs: 0K @ (nil) |(--) FBDev: Type 0 type_aux 0 bits_per_pixel 32 ||(--) FBDev: Hardware accelerator: None |(--) FBDev: No driver support for hardware acceleration |(--) FBDev: Using cfb32 driver |Warning: /dev/gpmdata unable to get status of mouse fd (Invalid argument) Is this normal? -- Bernhard DobbelsStudent Electronic Engineer option Automation and Computersystems. E-mail: [EMAIL PROTECTED] [EMAIL PROTECTED] ICQ: 25783372
Re: Geometry and keyboard problems in X
On Wed, 2 Sep 1998, Anders Hammarquist wrote: On Wed, Sep 02, 1998 at 09:53:07AM +0200, Johann Spies wrote: *XmTextField.translations: #override\n\ KeyosfDelete: delete-next-character() XTerm*utmpInhibit: false emacs.font: 7x14 emacs.geometry: 85x30+0+0 xpdf.geometry:80x32+0+0 pine.geometry: 101x32+0+0 xterm.geometry: 101x32+0+0 lynx.geometry:101x32+0+0 Should these be emacs*font, emacs*geometry instead of with dots? Emacs*font or emacs*font should have the desired effect (I set Emacs*font along with Emacs*menu*font and Emacs*menubar*font). emacs*geometry might/will/should result in ALL emacs windows (including menupopups etc) using that geometry. Emacs.geometry seems to be working for me (emacs.geometry didn't - strange). Thanks. That solved the problem. Johann -- | Johann Spies Windsorlaan 19 | | [EMAIL PROTECTED]3201 Pietermaritzburg | | Tel/Faks Nr. +27 331-46-1310 Suid-Afrika (South Africa) | -- And he said unto his disciples, Therefore I say unto you, Take no thought for your life, what ye shall eat; neither for the body, what ye shall put on. For life is more than meat, and the body is more than clothing. Consider the ravens, for they neither sow nor reap; they have neither storehouse nor barn; and yet God feeds them; how much better you are than the birds! Consider the lilies, how they grow; they toil not, they spin not; and yet I say unto you, that Solomon in all his glory was not arrayed like one of these. If then God so clothe the grass, which is to day in the field, and tomorrow is cast into the oven; how much more will he clothe you, O ye of little faith? And seek not what ye shall eat, or what ye shall drink, neither be ye of doubtful mind. But rather seek ye the kingdom of God; and all these things shall be added unto you. Luke 12:22-24; 27-29; 31.
Geometry and keyboard problems in X
My problem with this continue to bother me. Every time I start X I have to ajust my emacs and lyx frames because the font and geometry settings in the abovementioned files are ignored. I also have to run xkeycaps to restore the default xmodmap to get compose working in X. The contents of my .xinitrc is - xterm -geometry 101x33+0+1 -ls xterm -geometry 101x33+0+2 -ls -e lynx xmodmap ~/.xmodmap-`uname -u` pgaccess fvwm2 And my .Xresources: ! /etc/X11/Xresources ! ! This is the global Xresources file. It is used by both xdm and xinit. ! ! Fix Motif client handling of backspace/delete ! *XmTextField.translations: #override\n\ KeyosfDelete: delete-next-character() XTerm*utmpInhibit: false emacs.font: 7x14 emacs.geometry: 85x30+0+0 xpdf.geometry:80x32+0+0 pine.geometry: 101x32+0+0 xterm.geometry: 101x32+0+0 lynx.geometry:101x32+0+0 - Nothing of what is supposed to work according to .Xresources actually works. The contents of my /etx/X11/config: - # This file contains configuration flags for the X Window System. # For a description of the meanings of the flags, see # /usr/doc/X11/README.Debian run-xconsole obey-nologin allow-user-resources allow-user-modmap allow-user-xsession allow-failsafe #start-xdm #xdm-start-server no-xdm-start-server no-start-xdm - I have asked about this before but could not solve the problem. I had a system working without problems on 1.3.1. Thirteen days after upgrading to Debian 2.0 my system is still experiencing problems like this - hampering my productivity. I would really appreciate a solution. Johann -- | Johann Spies Windsorlaan 19 | | [EMAIL PROTECTED]3201 Pietermaritzburg | | Tel/Faks Nr. +27 331-46-1310 Suid-Afrika (South Africa) | -- For in much wisdom is much grief; and he that increaseth knowledge increaseth sorrow. Ecclesiastes 1:18
Re: Geometry and keyboard problems in X
On Wed, Sep 02, 1998 at 09:53:07AM +0200, Johann Spies wrote: *XmTextField.translations: #override\n\ KeyosfDelete: delete-next-character() XTerm*utmpInhibit: false emacs.font: 7x14 emacs.geometry: 85x30+0+0 xpdf.geometry:80x32+0+0 pine.geometry: 101x32+0+0 xterm.geometry: 101x32+0+0 lynx.geometry:101x32+0+0 Should these be emacs*font, emacs*geometry instead of with dots? Hamish (learning Motif but not much of an X wiz :-) -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
Re: Geometry and keyboard problems in X
On Wed, Sep 02, 1998 at 09:53:07AM +0200, Johann Spies wrote: *XmTextField.translations: #override\n\ KeyosfDelete: delete-next-character() XTerm*utmpInhibit: false emacs.font: 7x14 emacs.geometry: 85x30+0+0 xpdf.geometry:80x32+0+0 pine.geometry: 101x32+0+0 xterm.geometry: 101x32+0+0 lynx.geometry:101x32+0+0 Should these be emacs*font, emacs*geometry instead of with dots? Emacs*font or emacs*font should have the desired effect (I set Emacs*font along with Emacs*menu*font and Emacs*menubar*font). emacs*geometry might/will/should result in ALL emacs windows (including menupopups etc) using that geometry. Emacs.geometry seems to be working for me (emacs.geometry didn't - strange). Regards, /Anders -- -- Of course I'm crazy, but that doesn't mean I'm wrong. Anders Hammarquist | Mud at Kingdoms| [EMAIL PROTECTED] NetGuide Scandinavia | telnet kingdoms.se 1812| Fax: +46 31 50 79 39 http://www.netg.se | | Tel: +46 31 50 79 40
Re: Geometry and keyboard problems in X
On Thu, 3 Sep 1998, Hamish Moffatt wrote: On Wed, Sep 02, 1998 at 09:53:07AM +0200, Johann Spies wrote: *XmTextField.translations: #override\n\ KeyosfDelete: delete-next-character() XTerm*utmpInhibit: false emacs.font: 7x14 emacs.geometry: 85x30+0+0 xpdf.geometry:80x32+0+0 pine.geometry: 101x32+0+0 xterm.geometry: 101x32+0+0 lynx.geometry:101x32+0+0 Should these be emacs*font, emacs*geometry instead of with dots? After your message I tried it. I changed the periods to * and it did not make any difference. Johann -- | Johann Spies Windsorlaan 19 | | [EMAIL PROTECTED]3201 Pietermaritzburg | | Tel/Faks Nr. +27 331-46-1310 Suid-Afrika (South Africa) | -- For in much wisdom is much grief; and he that increaseth knowledge increaseth sorrow. Ecclesiastes 1:18
KEYBOARD PROBLEMS!
Content-Type: text/plain; charset=us-ascii Dear Sir/Madam, I recently decided to venture into Linux-Land, and downloaded all the = necessary files from your sites. All the procedures involving rawrite2.0 = worked fine. I inserted the Rescue disk, and Linux booted. It analysed = my system, chugging along merrily until.. it reached the monitor display = choice screen. This screen appears (in mono) with the cursor flashing under OK. = However, I cannot do anything from here. No keyboard commands, = RETURN/ENTER or arrow movements are carried out. It just sits there, = taunting me. Arrggh! Is there anything I am doing wrong? The Recue disk = is fine - clean and error free. My machine is: A custom built P5-200Mhz Intel Pentium comprising: 32MB EDO RAM 2.1GB E-IDE (Mode 4) HDD c: 500MB E-IDE (Mode 4) HDD d: 200MB Partioned drive, run from d:\ h: 8xPanasonic CD-ROM e: Sony 3.5 FDD a: Diamond Stealth 3D-2000 (S3) Videocard +2MB VRAM 15 Goldstar SVGA monitor. Cherry Keyboard (Win95) I would dearly appreciate a reply - otherwise Linux is no more! Yours sincerely, Chris Walker [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
