Difference between revisions of "Talk:Activating Numlock on Bootup"

From ArchWiki
Jump to: navigation, search
(Problem with /dev/tty?)
 
(.sh extension)
(13 intermediate revisions by 6 users not shown)
Line 1: Line 1:
Hi. I tried to use this code
+
== Extending getty@.service ==
 +
For many months I used this method, and it caused huge instability problems
 +
that I couldn't track down... Putting that service in exactly as described
 +
causes VTs to flicker and go black and unresponsive about half of the time.
  
for tty in /dev/tty?; do /usr/bin/setleds -D +num < "$tty"; done
+
Maybe we should put a warning at least?
  
in my startup scripts. However, there are a lot more consoles in my system (not only 1..6). The command
 
  
ls /dev/tty?
+
== <s> .sh extension </s> ==
 
+
as of KDE. script workaround as described didn't work for me.  
outputs ten different special files (tty0 to tty9). The command ls /dev/tty*  outputs at least four dozens of them.
+
adding .sh extension and pre-kde startup did the trick
 
+
--[[User:Josephk|Josephk]] ([[User talk:Josephk|talk]]) 16:58, 23 February 2013 (UTC)
The problem is, when using /dev/tty?, the script tries to set numlock on for the X session - but in a strange way: the LED is on, but the numerical keyboard works like arrow keypad.
+
: Page updated. Thanks. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 12:55, 11 November 2013 (UTC)
 
+
In order to get it working, I have to press NumLock twice: on the first press, the LED becomes off (the num pad still works as arrow keypad), on the second press, LED becomes on and the pressing the keys produce numbers.
+
 
+
(I found the problem was also reported in RedHat forums, see [https://bugzilla.redhat.com/show_bug.cgi?id=250236#c0].)
+
 
+
My suggestion is to use only
+
 
+
for tty in /dev/tty{1..6}
+
 
+
which will turn the numlock on for the text consoles (and not for the X session), and use numlockx in KDM/GDM/SLiM, as described below in the wiki page.
+
 
+
--[[User:Ptsl|Ptsl]] 05:13, 4 December 2009 (EST)
+

Revision as of 12:55, 11 November 2013

Extending getty@.service

For many months I used this method, and it caused huge instability problems that I couldn't track down... Putting that service in exactly as described causes VTs to flicker and go black and unresponsive about half of the time.

Maybe we should put a warning at least?


.sh extension

as of KDE. script workaround as described didn't work for me. adding .sh extension and pre-kde startup did the trick --Josephk (talk) 16:58, 23 February 2013 (UTC)

Page updated. Thanks. -- Fengchao (talk) 12:55, 11 November 2013 (UTC)