From owner-freebsd-acpi@freebsd.org Tue Oct 27 21:34:01 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 D8EADA1CF6D for ; Tue, 27 Oct 2015 21:34:01 +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 67F031C1C for ; Tue, 27 Oct 2015 21:34:00 +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 2A646207AD for ; Tue, 27 Oct 2015 22:32:42 +0100 (CET) Received: from mail.posteo.de (localhost [127.0.0.1]) by dovecot03.posteo.de (Postfix) with ESMTPSA id 3nlmTk1lJZz5vMs for ; Tue, 27 Oct 2015 22:32:42 +0100 (CET) From: aeuii@posteo.de To: freebsd-acpi@freebsd.org Subject: brightness control stopped working Date: Tue, 27 Oct 2015 22:32:41 +0100 Message-ID: <86vb9s9eva.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: Tue, 27 Oct 2015 21:34:01 -0000 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+ butto= ns 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 ** 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 From owner-freebsd-acpi@freebsd.org Wed Oct 28 11:55:58 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 ADDE8A1FE27 for ; Wed, 28 Oct 2015 11:55:58 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76FA510CD for ; Wed, 28 Oct 2015 11:55:58 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from crest.local (unknown [87.253.189.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id 2856217BD4 for ; Wed, 28 Oct 2015 12:55:55 +0100 (CET) Subject: Re: brightness control stopped working To: freebsd-acpi@freebsd.org References: <86vb9s9eva.fsf@posteo.de> From: Jan Bramkamp Message-ID: <5630B7CA.4040300@rlwinm.de> Date: Wed, 28 Oct 2015 12:55:54 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <86vb9s9eva.fsf@posteo.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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: Wed, 28 Oct 2015 11:55:58 -0000 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-☼- and Fn-☼+ 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=7 > > values change, but no effect > > > ** acpi_video > > sysctl hw.acpi.video.lcd0.brightness=50 > 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 function keys the output of said command will log them. The key-value pairs contain 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.org driver update caused your problem. From owner-freebsd-acpi@freebsd.org Wed Oct 28 20:37:01 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 AA7BEA208B2 for ; Wed, 28 Oct 2015 20:37:01 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7005217C1 for ; Wed, 28 Oct 2015 20:37:01 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oiao187 with SMTP id o187so12086397oia.3 for ; Wed, 28 Oct 2015 13:37:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=0MyH3U0ynIvK4qd4Av/sAxTAj8/A+pVJb7xRYhdiQGI=; b=OPCMpFTDkTGajXrAsYxqYQL2+HQxYj/9uJsUD40uRuskVfxGRA/D+NDghd6WK+tE8G NGtPjSB4sHIjn9lpq9+h/zmI3famE6dzgFj7KA3PVj8UYjfvLeg2Pjl8ZyWq5KQGDRJi MybNjfMff9Vur0zXEDUNvtYiP6NcBfBirxz92TJapKGIxy7b1TA3FNaATce3G50YD630 g+R4hINIJ1hATIY2mrdDCj1FPz33NrK0HkbFCAEZm6/pSvH8Z2Ytl+PlsttsB1skuboT fXju0hZRuxbL+dASR871LY5c7s8fnTh0qjN9efdiygoYE73xLOEf4SvfyhkGqtOdxru0 Yo+A== MIME-Version: 1.0 X-Received: by 10.202.220.212 with SMTP id t203mr32512413oig.73.1446064620710; Wed, 28 Oct 2015 13:37:00 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.108.210 with HTTP; Wed, 28 Oct 2015 13:37:00 -0700 (PDT) In-Reply-To: <5630B7CA.4040300@rlwinm.de> References: <86vb9s9eva.fsf@posteo.de> <5630B7CA.4040300@rlwinm.de> Date: Wed, 28 Oct 2015 13:37:00 -0700 X-Google-Sender-Auth: tVBJ1QpoExWWQSCP254sk0t-WtY Message-ID: Subject: Re: brightness control stopped working From: Kevin Oberman To: Jan Bramkamp Cc: "freebsd-acpi@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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: Wed, 28 Oct 2015 20:37:01 -0000 On Wed, Oct 28, 2015 at 4:55 AM, Jan Bramkamp 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 From owner-freebsd-acpi@freebsd.org Fri Oct 30 20:23:07 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 B4904A21A87 for ; Fri, 30 Oct 2015 20:23:07 +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 7C8821BC6 for ; Fri, 30 Oct 2015 20:23:06 +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 12104208B0 for ; Fri, 30 Oct 2015 21:22:57 +0100 (CET) Received: from mail.posteo.de (localhost [127.0.0.1]) by dovecot03.posteo.de (Postfix) with ESMTPSA id 3nnZns2Hy2z5vN5 for ; Fri, 30 Oct 2015 21:22:57 +0100 (CET) From: aeuii@posteo.de To: Subject: Re: brightness control stopped working Date: Fri, 30 Oct 2015 21:22:50 +0100 Message-ID: <86pozwjecl.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:23:07 -0000 > 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+ b= uttons 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? yes > > ** 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 function keys the output of said command will log them. The > key-value pairs contain all the information needed to write matching > event handlers in devd.conf. `cat /var/run/devd.pipe` does not log any brightness related events. Even if it did, I not able to change the LCD brightness in any way after the kernel is loaded. > 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. I realized that the problem could have occured between 10.1 and 10.2. But I do not think it is port related, because previously I was able to change the brightness with keyboard buttons during any stage of the boot process and afterwards (with and without X). 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