From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel 3.2->3.5 upgrade unusable: keyboard borked
Date: Sun, 2 Dec 2012 09:27:00 -0600 [thread overview]
Message-ID: <20121202152700.GZ23914@server> (raw)
In-Reply-To: <201212020806.55695.michaelkintzios@gmail.com>
On Sun, Dec 02, 2012 at 08:06:43AM +0000, Mick wrote:
>
> You can check if rc-update -s -v | grep numlock (or rc-status -s | grep
> numlock) shows it being set, otherwise add it to see if this makes a
> difference.
> --
> Regards,
> Mick
Though there is no /etc/conf.d/numlock, Mick's post caused me to read
/etc/init.d/numlock ... interesting. So if your "rc-update -s -v | grep
numlock" shows numlock but no runlevel, you can determine from the
aforementioned file how it got turned on.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2012-12-02 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 3:05 [gentoo-user] kernel 3.2->3.5 upgrade unusable: keyboard borked Grant Edwards
2012-12-02 6:39 ` Yohan Pereira
2012-12-02 8:06 ` Mick
2012-12-02 11:23 ` covici
2012-12-02 15:19 ` Bruce Hill
2012-12-02 18:36 ` covici
2012-12-02 20:05 ` [gentoo-user] " Grant Edwards
2012-12-02 20:34 ` covici
2012-12-02 20:46 ` Mark Knecht
2012-12-02 21:08 ` Grant Edwards
2012-12-02 23:21 ` Mark Knecht
2012-12-03 0:09 ` Neil Bothwick
2012-12-03 1:50 ` Grant Edwards
2012-12-02 20:15 ` Grant Edwards
2012-12-02 15:27 ` Bruce Hill [this message]
2012-12-02 20:33 ` Grant Edwards
2012-12-02 20:03 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121202152700.GZ23914@server \
--to=daddy@happypenguincomputers.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox