From owner-freebsd-acpi@freebsd.org Fri Oct 30 20:26:16 2015 Return-Path: Delivered-To: freebsd-acpi@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C2ACA21ADE for ; Fri, 30 Oct 2015 20:26:16 +0000 (UTC) (envelope-from aeuii@posteo.de) Received: from mout01.posteo.de (mout01.posteo.de [185.67.36.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.posteo.de", Issuer "StartCom Class 3 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 23FBA1C32 for ; Fri, 30 Oct 2015 20:26:15 +0000 (UTC) (envelope-from aeuii@posteo.de) Received: from dovecot03.posteo.de (dovecot03.posteo.de [172.16.0.13]) by mout01.posteo.de (Postfix) with ESMTPS id D3B8B209BB for ; Fri, 30 Oct 2015 21:26:13 +0100 (CET) Received: from mail.posteo.de (localhost [127.0.0.1]) by dovecot03.posteo.de (Postfix) with ESMTPSA id 3nnZsd3vzVz5vLS for ; Fri, 30 Oct 2015 21:26:13 +0100 (CET) From: aeuii@posteo.de To: Subject: Re: brightness control stopped working Date: Fri, 30 Oct 2015 21:26:15 +0100 Message-ID: <86mvv0je6w.fsf@posteo.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2015 20:26:16 -0000 > On Wed, Oct 28, 2015 at 4:55 AM, Jan Bramkamp wrote: > > > > > > On 27/10/15 22:32, aeuii at 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+ = buttons 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 comman= ds > > 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 funct= ion > > keys the output of said command will log them. The key-value pairs cont= ain > > all the information needed to write matching event handlers in devd.con= f. > > > > 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= .org > > driver update caused your problem. > > > > And don't forget to ALWAYS rebuild ports that create kernel modules aft= er > every new kernel build. This is most easily done by defining PORTS_MODULES > in /etc/src.conf. E.g. "PORTS_MODULES=3Dsysutils/acpi_call". I use GENERIC kernel. Is it correct to assume, that packages are compatible with the kernel? (I have rebuilt acpi_call, but it did not change its behavior.) Cheers, Stefan