[solved] keyboard not working correctly on vc/1

eldragon · 2009-02-18 18:39:38

the behaviour is quite odd.

when i hit ctrl-alt-f1, and switch to the first virtual console, trying to login, or even type doesnt work quite as it should.

example, i try to login: this is what i get:

lappy login: elragn
password:

when the user name should be eldragon, if i type each letter at a time, until i get it to work, i can type correctly, and its not always the same letters that dont work. of course, the password comes in blank, and sometimes, when i get it all right, i can login, and the effect contiues

this is not a hardware issue, other virtual consoles work ok, and the keyboard works fine under Xorg.

so, what could be wrong with this vc? anyone got a clue? ive searched the wiki, bug reports, google, and the forums (not in this order) for an answer but i came up empty.

PD. if im posting in the wrong forum, please move it where it should go

Last edited by eldragon (2009-03-22 18:08:54)

frp · 2009-03-13 20:03:36

Hi,
Since the problem is in the vc's, and the keymap is loaded "pre Xorg", I'd start by doing some tests there.
I'm still a learner myself, so this might not work, or it might, either way, you've got nothing to loose

First of all check logs for errors, maybe something pops out.
If no errors on logs, than here's what I would do if I were you:
(backup /etc/rc.conf , /etc/inittab , /etc/locale.gen to some directory)

1. Let's start by isolating the problem by not going to gdm->gnome automatically, so you can test vc's themselfs more efficiently and quicker.
take out gdm from the DAEMONS line in /etc/rc.conf (something like this)

DAEMONS=(syslog-ng network netfs crond alsa hal fam)

2. let your /etc/inittab be like you have in this section (id:3)

## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:

and comment everything here:

# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null

3. do you use a non-us keyboard?
check your rc.conf for the 1st lines, mainly your KEYMAP

LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="your.timezone.here"
KEYMAP="your.keymap.here"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

confirm that your keymap exists in /usr/share/kbd/keymaps and double confirm the name is right, example:
for US keyboard the file is 'us.map.gz' so KEYMAP="us" (take out .map.gz); in case your keyboard is not US, check the name, as some have more letters than others
(usually /usr/share/kbd/keymaps/i386/qwerty unless your pc is not i386 or qwerty ofc )

4. reboot pc.
You'll be in vc/1.
Now, instead of jumping in consoles with ctr-alt-Fx, try jumping just with Alt+Fx. (if it doesn't work, go ctrl+alt+fx ofc)
Do Alt+F2 and start typing as normal, anything and manything at any speed and confirm is good. Don't press enter. Just testing keystrokes.
Do Alt+F3, Alt+F4, Alt+F5 and test the same for each vc.
Now for the final and problematic one, go Alt+F1 and test.
If it's good, then probably your problem is on X/gdm/gnome or anything that is loading after vc, or if you changed your keymap, then that was the faulty thing.
If it's not good, keep on reading

5. don't enter in vc/1, rather jump to vc/2 or 3 or something and enter as root, let's edit your /etc/rc.conf again.
copy to a piece of paper your 1st options in case they are different from below:

LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="your.timezone.here"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

basicly is trying to put it to a default state. Put your options just like they are above, except TIMEZONE, you can put yours, I don't remember default one.

Reboot and test again just like in step 4.
If it doesn't work, you might give a look at /etc/locale.gen and just uncomment these 2 lines:

#en_SG.UTF-8 UTF-8  
#en_SG ISO-8859-1  
en_US.UTF-8 UTF-8  
en_US ISO-8859-1  
#en_ZA.UTF-8 UTF-8  
#en_ZA ISO-8859-1

leave every other line commented. in case you had some of your own uncommented, copy to a paper wich ones were, and comment them.

write in console

locale-gen

let it end generating the locales, reboot, and step 4 again.

6. Still not working, let's try to put things bad proposedly! Change your KEYMAP to another one, if qwerty, just choose another qwerty language, all letters should be on same place, except for punctuation ofc.
Reboot and try again as step 4.
Still not working? Change the LOCALE and keep your wrong qwerty keyboard. (LOCALE will probably change some words, like password to it's LOCALE language, etc).
Reboot and try again as step 4.
Still not working? ok, final attempt, change back your LOCALE and your KEYMAP to the values you had before, the correct ones.
Reboot and try again as step 4.

7. If still not working, well, for now I don't know much more. Take in consideration that the boot process goes through several steps, the error might be in one of those steps. One last thing you can try, altho I think it works just in DE/WM modes, I've read in some posts (here or not, can't remember) that by pressing Ctrl-Alt-K you can change your keyboard layout, assuming you have a second one, and use them for different things, I think the example I read on the post was something like, you wanna code in english but talk in irc in russian for example.
I kinda doubt it works, but if it also activates in vc's mode, then you could have pressed it accidently (like when doing ctrl-alt-fx, your finger slipped ).
press ctrl-alt-k, type a few letters, press ctrl-alt-k again, type more letters, and you'll see if it does something or not.
Again, just try, you got nothing to loose

One thing I noticed, is that when trying to put some characters on vc as username, it acts as delete, some even erase the all line in one go and some don't do nothing, some of the characters were # @ £ §.

8. Since it didn't work, let's put everything as it was.
8.1. go to /etc/inittab and put like this:
(comment id:3, uncomment id:5 // uncomment x:5:...gdm...)

## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:

# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null

8.2. edit /etc/rc.conf and DON'T put back the gdm on daemons line.
Alter the 1st lines ranging from LOCALE to USECOLOR to the ones you copied to a paper.

8.3. comment/uncomment the locales on /etc/locale.gen as you have on paper and run in console

 locale-gen

8.4. you're set, reboot and you're on gdm->gnome again. (still no vc/1 working tho )

note: in your initial /etc/iniitab you had id:3 uncommented and gdm on daemons, so you would go automatically to gdm as you started your pc, but, what if something happens and you need to go to another mode before gdm runs? you couldn't do it easily with gdm on daemons.
If you put it like I wrote above, when you turn on the pc, it's the same, you go automatically to the gdm, but, in case something happens, you can always go to another mode before gdm runs, by doing the following (read here on wiki or foruns, will put link when I find it)
Pc reboots and you're on GRUB, press 'e', choose the kernel and press 'e' again, go to the end of the line where it says 'ro', and add a 3 to the end, to look like this 'ro 3', press 'b' (boot) and you're on mode 3 without going to gdm

But ofc, this is just a choice, if you prefer to have as you had it, by all means, just put gdm on daemons line, and your /etc/inittab as initially, that's the beauty of Linux, it's to your fit

Good Luck!

eldragon · 2009-03-14 23:51:07

i havent had the time to set what you suggest, will do it sometime in the week, during dead hours.. will report back when i do, thanks for the reply.

eldragon · 2009-03-15 14:12:37

ok, first thing i tried, before messing with the entire process was to disable gdm, and it did work as expected. now im going to set the inittab to get into X instead of the daemon and see if it works this way. i hope it does

thanks for the entire debug post.

frp · 2009-03-22 14:52:34

any news on this?

eldragon · 2009-03-22 18:08:33

frp wrote:

any news on this?

yes, it was actually gdm as a daemon that was acting weird, switching to the inittab solution (which actually brings more advantages) fixed it for me.

another issue that got resolved with this is that the shutdown process wasnt showing up correctly, this fixed too.

thanks a lot fot the help, im marking this solved now

frp · 2009-03-23 01:52:39

Nice!
happy to know it's working

Arch Linux

#1 2009-02-18 18:39:38

[solved] keyboard not working correctly on vc/1

#2 2009-03-13 20:03:36

Re: [solved] keyboard not working correctly on vc/1

#3 2009-03-14 23:51:07

Re: [solved] keyboard not working correctly on vc/1

#4 2009-03-15 14:12:37

Re: [solved] keyboard not working correctly on vc/1

#5 2009-03-22 14:52:34

Re: [solved] keyboard not working correctly on vc/1

#6 2009-03-22 18:08:33

Re: [solved] keyboard not working correctly on vc/1

#7 2009-03-23 01:52:39

Re: [solved] keyboard not working correctly on vc/1

Board footer