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

From ArchWiki
Jump to: navigation, search
(Problem with /dev/tty?)
 
(systemd service -> AUR Package)
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Hi. I tried to use this code
+
--[[User:Josephk|Josephk]] ([[User talk:Josephk|talk]]) 16:58, 23 February 2013 (UTC)== systemd service -> AUR Package ==
  
for tty in /dev/tty?; do /usr/bin/setleds -D +num < "$tty"; done
+
In reference to to the 12/22 modification by Hgabreu I've created a little service who launch the script described here : [https://wiki.archlinux.org/index.php/Activating_Numlock_on_Bootup#Console]
  
in my startup scripts. However, there are a lot more consoles in my system (not only 1..6). The command
+
It works fine on my computer so I created a package on AUR, for sharing this little thing with the community.
 +
It doesn't depend on a deprecated file from initscript, (/etc/rc.local), it's full systemd :D
  
ls /dev/tty?
+
You can try to install it :
 +
numlockontty package
 +
[https://aur.archlinux.org/packages/numlockontty/]
  
outputs ten different special files (tty0 to tty9). The command ls /dev/tty*  outputs at least four dozens of them.
+
the service name is numLockOnTty, so you just have to enable it.
  
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.
+
If you think it's useful, we can edit the page to add theses instruction (in proper snglish because mine is a little poor and pretty awful... sorry I'm french ^^")
 +
--[[User:Ybalrid|Ybalrid]] ([[User talk:Ybalrid|talk]]) 19:37, 2 January 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.
+
It's me again, peoples ask me to change the name of the packet, so now it will be systemd-numlockontty
 +
--[[User:Ybalrid|Ybalrid]] ([[User talk:Ybalrid|talk]]) 23:54, 2 January 2013 (UTC)
  
(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
+
as of KDE. script workaround as described didn't work for me.  
 
+
adding .sh extension and pre-kde startup did the trick
for tty in /dev/tty{1..6}
+
--[[User:Josephk|Josephk]] ([[User talk:Josephk|talk]]) 16:58, 23 February 2013 (UTC)
 
+
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 16:58, 23 February 2013

--Josephk (talk) 16:58, 23 February 2013 (UTC)== systemd service -> AUR Package ==

In reference to to the 12/22 modification by Hgabreu I've created a little service who launch the script described here : [1]

It works fine on my computer so I created a package on AUR, for sharing this little thing with the community. It doesn't depend on a deprecated file from initscript, (/etc/rc.local), it's full systemd :D

You can try to install it : numlockontty package [2]

the service name is numLockOnTty, so you just have to enable it.

If you think it's useful, we can edit the page to add theses instruction (in proper snglish because mine is a little poor and pretty awful... sorry I'm french ^^") --Ybalrid (talk) 19:37, 2 January 2013 (UTC)

It's me again, peoples ask me to change the name of the packet, so now it will be systemd-numlockontty --Ybalrid (talk) 23:54, 2 January 2013 (UTC)


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)