Some USB keyboard troubles.
Hi I have been running debian unstable for a while now - and not had any problems - currently was running a custom 2.4.16 with ext3 patch. I have had a USB mouse for quite a while - and so had the USB support for mice installed in my kernel. Recently however my PS/2 keyboard port died a relatively sudden death. Replacement of my motherboard under waranty was going to be 2 weeks so I decided that instead I would just invest in a USB keyboard. I dual boot with win2k - which works fine with my new keyboard - I enabled BIOS support for USB keyboards - so that I was able to operate my lilo and winnt boot loader successfully. However - booting into debian resulted in no keyboard activity. A bit of research led me to believe that this was probably because I had not enabled USB Keyboard support - and the normal USB support was disabling my BIOS support. Hoped that there was some boot parameter i could give lilo to disable USB - but there wasnt. So I pulled out the trusty rescue disk. Rescue disk doesnt have USB support - so I thought that I would be good to go ... and compile myself a new kernel with the proper support. However the only progress I made from this was discovering that my keyboard was being disabled a bit earlier than I had thought. I am getting Keyboard - Timeout - No AT keyboard present? (hmmm thats from memory - but close) it repeats twice before continuing onwards - the keyboard is non-functional from that point onwards (as demonstrated by caps/num/scroll-lock not operating the lights any more) Rebooting back into my custom kernel - I notice that indeed the same error messages are being displayed - to the same effect. (although theres a set of 2 characters in brackets after each line - different for each of the error lines. Any advice, redirection to a better place to ask even :), would be great. Gareth Pearce - nano sized contributor to open source.
Re: Some USB keyboard troubles.
My appologies for sending this - my problem is no longer a problem, I had this in my send queue from last night - and it sent before I got a chance to stop it. My ps/2 port spontaneously started working again :P (in fact - if i dont have something plugged into it it now stuffs up - maybe i should get it fixed eventually after all) - so I was able to get in and compile a kernel with proper usb keyboard support. Although I think this situation might be a problem for people trying to install linux without the option of a ps/2 keyboard, but since my ps/2 port has been playing up - maybe it was confusing the linux keyboard driver. Gareth Pearce - Original Message - From: Gareth Pearce [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, January 23, 2002 2:40 AM Subject: Some USB keyboard troubles. Hi I have been running debian unstable for a while now - and not had any problems - currently was running a custom 2.4.16 with ext3 patch. I have had a USB mouse for quite a while - and so had the USB support for mice installed in my kernel. Recently however my PS/2 keyboard port died a relatively sudden death. Replacement of my motherboard under waranty was going to be 2 weeks so I decided that instead I would just invest in a USB keyboard. I dual boot with win2k - which works fine with my new keyboard - I enabled BIOS support for USB keyboards - so that I was able to operate my lilo and winnt boot loader successfully. However - booting into debian resulted in no keyboard activity. A bit of research led me to believe that this was probably because I had not enabled USB Keyboard support - and the normal USB support was disabling my BIOS support. Hoped that there was some boot parameter i could give lilo to disable USB - but there wasnt. So I pulled out the trusty rescue disk. Rescue disk doesnt have USB support - so I thought that I would be good to go ... and compile myself a new kernel with the proper support. However the only progress I made from this was discovering that my keyboard was being disabled a bit earlier than I had thought. I am getting Keyboard - Timeout - No AT keyboard present? (hmmm thats from memory - but close) it repeats twice before continuing onwards - the keyboard is non-functional from that point onwards (as demonstrated by caps/num/scroll-lock not operating the lights any more) Rebooting back into my custom kernel - I notice that indeed the same error messages are being displayed - to the same effect. (although theres a set of 2 characters in brackets after each line - different for each of the error lines. Any advice, redirection to a better place to ask even :), would be great. Gareth Pearce - nano sized contributor to open source. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Keyboard troubles...
Christian Pernegger wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've skimmed the German_HOWTO, played with console-tools and generally familiarized myself a bit with keymaps and the like - here's what I've come up with... The default loaded keymap is de-latin1-nodeadkeys which is the correct one. The relevant entries are: keycode 12 = ssharpquestionbackslash keycode 26 = +udiaeresis +Udiaeresis keycode 39 = +odiaeresis +Odiaeresis keycode 40 = +adiaeresis +Adiaeresis As long as diaeresis means umlaut that should be correct. '/usr/bin/showkey -m' displays the correct characters for all keys, but the results on the console are: szlig; does cursor up auml; Auml; does nothing at all uuml; beeps Uuml; does nothing ouml; Ouml; beeps Help! Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5geb8txWmQklOL8URAonBAJ0Y7pLcPKPBbfnN0afsbFVRbxIZkACgjao8 5JvKabu+X9onCeZ4Zhv0zPk= =K9jP -END PGP SIGNATURE- To display sharp S and umlauts with bash you may edit a file named '.inputrc' which contains just three lines: set meta-flag on set convert-meta off set output-meta on Put this file into your home directory. I hope this helps. Andreas
Re: Keyboard troubles...
On Fri, Jul 28, 2000 at 03:50:29AM +0200, Christian Pernegger wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How can I configure my box to work correctly with a German keyboard? [snip] I'll gladly accept even an RTFM if you tell me which one. :) there is a german-howto. try setting $LANG to de_DE there is also a german [EMAIL PROTECTED] list. Schoen Gruesse nach Oesterreich. -- Thomas Guettler Office: [EMAIL PROTECTED] http://www.interface-business.de Private: [EMAIL PROTECTED] http://yi.org/guettli
RE: Keyboard troubles...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 -Original Message- From: Thomas Guettler [mailto:[EMAIL PROTECTED] Sent: Friday, July 28, 2000 8:45 AM To: debian-user@lists.debian.org Subject: Re: Keyboard troubles... On Fri, Jul 28, 2000 at 03:50:29AM +0200, Christian Pernegger wrote: How can I configure my box to work correctly with a German keyboard? there is a german-howto. Ah, good. try setting $LANG to de_DE This will set the system language to German, complete with translated messages where supported - that's too much :) there is also a german [EMAIL PROTECTED] list. Ain't gonna subscribe to another list if I can help it at all. I thought this might be a problem with updating from t-c-2 to t-c-3. Schoen Gruesse nach Oesterreich. Danke. Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5gY6dtxWmQklOL8URAnLaAKD0a/wHoB0APUXnjdJ4gxXhbCDunwCcDl+n C8DEpuJH2jRAmXstnMgxr3Q= =4Clm -END PGP SIGNATURE-
RE: Keyboard troubles...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How can I configure my box to work correctly with a German keyboard? During installation I selected de-latin1-nodeadkeys, here's what I got: * emacs will accept umlauts and the such when I'm on the local console * but when I'm logged in via ssh, other, even more arcane symbols appear. * On a shell prompt the special keys consistently do nothing. I installed using potato-testcycle-2 cds and recently updated to testcycle-3. I'll gladly accept even an RTFM if you tell me which one. :) I've skimmed the German_HOWTO, played with console-tools and generally familiarized myself a bit with keymaps and the like - here's what I've come up with... The default loaded keymap is de-latin1-nodeadkeys which is the correct one. The relevant entries are: keycode 12 = ssharpquestionbackslash keycode 26 = +udiaeresis +Udiaeresis keycode 39 = +odiaeresis +Odiaeresis keycode 40 = +adiaeresis +Adiaeresis As long as diaeresis means umlaut that should be correct. '/usr/bin/showkey -m' displays the correct characters for all keys, but the results on the console are: szlig; does cursor up auml; Auml; does nothing at all uuml; beeps Uuml; does nothing ouml; Ouml; beeps Help! Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5geb8txWmQklOL8URAonBAJ0Y7pLcPKPBbfnN0afsbFVRbxIZkACgjao8 5JvKabu+X9onCeZ4Zhv0zPk= =K9jP -END PGP SIGNATURE-
Keyboard troubles...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 How can I configure my box to work correctly with a German keyboard? During installation I selected de-latin1-nodeadkeys, here's what I got: * emacs will accept umlauts and the such when I'm on the local console * but when I'm logged in via ssh, other, even more arcane symbols appear. * On a shell prompt the special keys consistently do nothing. I installed using potato-testcycle-2 cds and recently updated to testcycle-3. I'll gladly accept even an RTFM if you tell me which one. :) Christian -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5gOa9txWmQklOL8URAh0tAJ9/CvCmhF7hyktJrJrLCXl0XtC1EQCeLfr1 8QdllJxrf0A0Xi08dZNtvIg= =hvXP -END PGP SIGNATURE-
