You are not logged in.
Hi all, I am unable to switch between virtual consoles by pressing ctrl+alt+f1/2/3/4/5/6/7.
I boot with KDE 4.2.3 and Xorg 1.6.1no matter what I do I just cant kill x either!
I tried adding the codes in xorg.conf file in Section"ServerFlags" as
code
Option "DontZap" "no"(tried "false" and "0" as well, but still no joy)
Option "DontVTSwitch" "no"
but it doesnt work.
' I checked each and every single key in kde and ALL of them works perfectly fine! '
so i guess my keyboard and its drivers has no issues?
Anyways the strange thing is that it all startred with the Xorg 1.6, prior to that everything was fine..BUT even then sometimes I wasnt able to change the consoles and after a reboot I could!
Could there be a bug in Arch itself???(just a question!)
Last edited by kapz (2009-05-09 19:33:14)
I wonder how it would be like to use the rest 99% of my brain..:P
Registered Linux User: 487155
Offline
Switch from X to VCs with Ctrl+Alt+Fx. Switch between VCs with Alt+Fx.
That's how it's always worked for me.
Offline
Hi tomk, yes I try to do that but when I press ctrl+alt+Fx..nothing happens the KDE session runs as if nothing happened! The ctrl+alt+Fx does not work at kdm also, also if I disable kdm and logon to VC1(which is the default login screen instead of kdm) I am able to switch between consoles by pressing alt+Fx.......but if I startx from then on(by typing startx) I get three windows and a clock. Now if I type alt+f1 in any of the terminals the input it takes is 'P' and alt+f2 as ~! so definately the problem is with the X keyboard drivers. But I dont know as to how everything works fine in KDE?
Any chance of misconfigured /etc/inittab??
Edit: Added the X window experince above and changed alt+f1 to working.
Last edited by kapz (2009-05-09 11:08:11)
I wonder how it would be like to use the rest 99% of my brain..:P
Registered Linux User: 487155
Offline
Hi
0) Under KDE , open a terminal and type "kbd_mode" to see the mode of the keyboard, must be "the keyboard is in raw (scancode) mode"
1) Remove the flags related to VT switch in your xorg.conf
2) startx with TWM instead of KDE , (just edit your .xinitrc and put exec twm) This is for discard if are related to any hotkey with KDE.
3 ) Try to switch
Last edited by djgera (2009-05-09 14:52:32)
Offline
Hi djgera thank you for the advice.
I typed kbd_mode in konsole and got the message: the keyboard is in raw (scancode) mode"
Removed the flags from xorg.conf.
had put "exec twm" in .xinitrc but nothing happened! the KDE booted as normal and still am not able to switch terminals.
One Thing For Sure I know Is That If I "startx" from console the X is not taking the correct input from the keyboard! I type alt+F1 and it takes it as P!
Summary- Keyboard works normal in Console mode. Then all the KEYS work normally in KDE(4.2.3).
But in plain X session(TWM) the keyboard is not setup properly! How do I correct something like that??
I wonder how it would be like to use the rest 99% of my brain..:P
Registered Linux User: 487155
Offline
Allright!! I have managed to Alter the settings for keyboard(by experimenting)!
Ok till now I rebooted approx 14 times to experiment! lol
Now what I did is tried and tested the drivers loaded by Archbase(without X) and the one that is in use by X(the culprit).
In my xorg.conf the keyboard input in server layout is as follows:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard" <-----------Used by Arch
EndSection
so I replaced the driver in section input device as follows:
Section "InputDevice"
Identifier "Keyboard0"
Driver "xkbd" <-------------(replaced xkbd with CoreKeyboard and all is working perfect)
EndSection
Now I dont know if this workaround is temporary or something like that because I still couldn't manage to configure HAL drivers to work! (Any explanation for configuring HAL keyboard drivers are most welcomed)
One last question(a very silly one though) I searched almost everything on this page but could not find the option to mark the thread as solved. How to do that??:D
I wonder how it would be like to use the rest 99% of my brain..:P
Registered Linux User: 487155
Offline
you have to comment out exec kde, you should in most cases only have one uncommented entry in .xinitrc
To make it solved change the topic title in the first post.
Last edited by hatten (2009-05-09 19:07:22)
Offline
IC thatz why TWM wasnt starting! Thanks for the info.
I wonder how it would be like to use the rest 99% of my brain..:P
Registered Linux User: 487155
Offline