Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Oct 2015 13:37:00 -0700
From:      Kevin Oberman <rkoberman@gmail.com>
To:        Jan Bramkamp <crest@rlwinm.de>
Cc:        "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>
Subject:   Re: brightness control stopped working
Message-ID:  <CAN6yY1snOMjwqo-Ec74Jg2F_rranD1=fvfMiaV6n%2Bqc6ZA1NgA@mail.gmail.com>
In-Reply-To: <5630B7CA.4040300@rlwinm.de>
References:  <86vb9s9eva.fsf@posteo.de> <5630B7CA.4040300@rlwinm.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 28, 2015 at 4:55 AM, Jan Bramkamp <crest@rlwinm.de> wrote:

>
>
> On 27/10/15 22:32, aeuii@posteo.de wrote:
>
>> Hello freebsd-acpi@,
>>
>> I have lenovo ThinkPad Edge E145 laptop and the LCD brightness control
>> stopped working somewhere between 10.2-RELEASE and 10.2-RELEASE-p6.
>>
>> I used to adjust the brightness using Fn-=E2=98=BC- and Fn-=E2=98=BC+ bu=
ttons and it
>> always worked (during boot, in X, text console).  Now, it works only
>> in the loader, before the system boots.
>>
>> I tried alternative methods listed below, but non had any effect.
>>
>> Please help! ;)
>>
>> Thank you in advance,
>> Stefan
>>
>>
>> ** acpi_call
>>
>> acpi_call -v -p '\VBRU'
>>
>> Path: \VBRU
>> Number of arguments: 0
>> ioctl: Device not configured
>>
>> no effect
>>
>
> Is the acpi_call kernel module loaded?
>
> ** acpi_ibm
>>
>> sysctl dev.acpi_ibm.0.lcd_brightness=3D7
>>
>> values change, but no effect
>>
>>
>> ** acpi_video
>>
>> sysctl hw.acpi.video.lcd0.brightness=3D50
>> hw.acpi.video.lcd0.brightness: 50 -> #
>>
>> no effect
>>
>>
>> pressing Fn+(sun)+- buttons has no effect, but logs:
>>
>> can't evaluate \134_SB_.PCI0.VGA_.LCD_._BQC - AE_NOT_FOUND
>>
> If the buttons generate events for devd you can execute whatever commands
> work for you. `cat /var/run/devd.pipe` logs all events consumed by devd
> from /dev/devctl. If the acpi_ibm module generates events for the functio=
n
> keys the output of said command will log them. The key-value pairs contai=
n
> all the information needed to write matching event handlers in devd.conf.
>
> Did you try xbacklight? The changes between 10.2-RELEASE and
> 10.2-RELEASE-p6 shouldn't break your backligh controls. However lots of
> ports changed in that timeframe and maybe one of those changes e.g. a X.o=
rg
> driver update caused your problem.
>
> And don't forget to ALWAYS rebuild ports that create kernel modules after
every new kernel build. This is most easily done by defining PORTS_MODULES
in /etc/src.conf.  E.g. "PORTS_MODULES=3Dsysutils/acpi_call".
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1snOMjwqo-Ec74Jg2F_rranD1=fvfMiaV6n%2Bqc6ZA1NgA>