On 27 January 2013 21:23, Kevin Oberman <kob6...@gmail.com> wrote: > On Sun, Jan 27, 2013 at 4:20 PM, Erich Dollansky > <erichsfreebsdl...@alogt.com> wrote: >> Hi, >> >> On Sun, 27 Jan 2013 18:24:36 -0500 >> Eitan Adler <li...@eitanadler.com> wrote: >> >>> On 27 January 2013 12:59, Kevin Oberman <kob6...@gmail.com> wrote: >>> > On Fri, Jan 25, 2013 at 9:25 PM, Eitan Adler <li...@eitanadler.com> >>> > wrote: >>> >> On 25 January 2013 14:51, Kevin Oberman <kob6...@gmail.com> wrote: >>> >>> There are several threads in the archives of acpi@ and mobile@ >>> >>> discussing this. Most things are pretty easy. Use xev to find the >>> >>> events generated by the volume buttons. >>> >> >>> >> I'm handling the volume keys with xbindkeys. >>> >> >>> >>> Mute and the ThinkLight (if >>> >>> your system has one) should work as is. >>> >> >>> >> Mute does not function - I am using xbindkeys to handle it. The >>> >> "video" key generates no event. >>> >> >>> >>> Brightness is a bit bigger issue as Lenovo has completely >>> >>> revamped it These buttons don't generate events. :-( >>> >> >>> >> Where *should* they be handled? How do they work on windows? >>> >> >>> >> FWIW they seem to change hw.acpi.video.brightness, but change >>> >> nothing visible on the screen. >>> >> >>> >>> You can install the acpi_call >>> >>> port and use it to set the brightness, but it is a pain as it >>> >>> does not allow for setting incremental changes, only absolute >>> >>> values.(16 of them). >>> >> >>> >> Any pointers for what to look at? I have no idea what I'm doing >>> >> w.r.t. computers ^W ACPI. >>> > >>> > Install sysutils/acpi_call >>> > kldload acpi_call >>> > acpi_call -p '\VBRC' -i [0-15] >>> > >>> > There seem to be some differences on the range, but in my T530 0=off >>> > and 15=full. >>> > >>> > Unfortunately, the brightness functions do not generate X events >>> > and I have not seen any posts on how to tie them to anything to >>> > adjust brightness. >>> >>> >>> [2881 root@gravity ~ ]#acpi_call -p '\VBRC' -i 1 >>> Unknown object type '0' >>> [2882 root@gravity ~ !5!]#acpi_call -p '\VBRC' -i 2 >>> Unknown object type '0' >>> [2883 root@gravity ~ !5!]#acpi_call -p '\VBRC' -i 0 >>> Unknown object type '0' >>> [2884 root@gravity ~ !5!]#acpi_call -p '\VBRC' -i 15 >>> Unknown object type '0' >>> >>> >> >> I can confirm that this works on an X220: >> >> acpi_call -p '\VBRC' -i $value >> >> It also works lower case for me. >> >> Erich > > Probably won't help, but can you confirm that acpi_call is loaded (kldstat)?
Yes. I get different errors if it isn't. -- Eitan Adler _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
