public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bartosz Szatkowski <bulislaw@linux.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Updates = slow firefox
Date: Sat, 24 Apr 2010 09:33:49 +0200	[thread overview]
Message-ID: <1272094429.6620.8.camel@bulislaw-laptop> (raw)
In-Reply-To: <g2h49bf44f11004230951x3e04dcd1g4e65b34b55b68b92@mail.gmail.com>

Dnia 2010-04-23, pią o godzinie 09:51 -0700, Grant pisze:
> >> Strangely, now my laptop's brightness adjustment doesn't work via the
> >> keyboard shortcuts.  Any ideas on that?
> >>
> >> - Grant
> >>
> > Please share the beast model :P (or maybe ive missed it).
> > in kernel config You have multiple option for backlight eg. for thinkpad
> > there is extra one in "thinkpad specific acpi" maybe You have something
> > similar for Yours stuff.
> 
> It's a Dell Vostro 1320.  The keyboard shortcuts to change brightness
> were working great until I enabled DRM in the kernel.  Can you tell me
> where in the kernel those options can be found, or part of the
> variable name that defines them?
> 
Try running xev and punching brightness keys, if you would see
"effects" (some text in terminal) then its OK :P You should change the
Acpi configs (etc/acpi/) or Gnome/KDE/Xfce/... bindings.

(if You dont know it already)
For acpi config You'll need "event id" try running acpi_listen.
eg. /etc/acpi/events/sleep:
event=ibm/hotkey HKEY 00000080 00001004
action=/etc/acpi/actions/sleep.sh

and into actions you put scripts, try using xbacklight.

If You wouldn't have any reaction in xev and acpi_listen i check the
option in kernel.
-- 
Bartosz Szatkowski
KeyFP: 1568 D5A7 B14C 0727 1C61 ACFB ABDE C08A DDB7 1F70

The freedom to redistribute copies of a program so you can help your
neighbor (freedom 2)




  parent reply	other threads:[~2010-04-24  7:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 22:06 [gentoo-user] Updates = slow firefox Grant
2010-04-19 22:12 ` deface
2010-04-19 22:43   ` Grant
2010-04-20  1:24     ` deface
2010-04-20 18:15       ` Bartosz Szatkowski
2010-04-20 18:51         ` Grant
2010-04-20 19:14           ` Bartosz Szatkowski
2010-04-21 11:26         ` Adam
2010-04-21 13:23           ` Mick
2010-04-21 19:07           ` Grant
2010-04-21 19:57             ` Mike Edenfield
2010-04-21 20:11               ` Grant
2010-04-22 16:47                 ` Grant
2010-04-22 20:18                   ` Mick
2010-04-23  9:01                   ` Bartosz Szatkowski
2010-04-23 16:51                     ` Grant
2010-04-23 17:08                       ` erdunand
2010-04-23 17:13                       ` Paul Hartman
2010-04-23 17:37                         ` Grant
2010-04-23 17:46                           ` Mike Edenfield
2010-04-23 18:21                             ` Grant
2010-04-23 18:38                             ` Dale
2010-04-24  7:33                       ` Bartosz Szatkowski [this message]
2010-04-27  2:10                         ` Grant
2010-04-27 17:00                           ` Bartosz Szatkowski
2010-04-27 17:37                             ` Grant
2010-04-27 21:31                               ` Bartosz Szatkowski
2010-04-28 16:57                                 ` Grant

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=1272094429.6620.8.camel@bulislaw-laptop \
    --to=bulislaw@linux.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