From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 28 02:29:41 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D959803 for ; Mon, 28 Jan 2013 02:29:41 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by mx1.freebsd.org (Postfix) with ESMTP id 0D420200 for ; Mon, 28 Jan 2013 02:29:40 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id gm6so3220826lbb.40 for ; Sun, 27 Jan 2013 18:29:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=5ehe42/kxAwMVQ9XQ2g9ARxDXbaER1RDKMjoZZ2Jhk0=; b=mMfRVWhq9ErPgmkMwu1AWBI+c8qvN+KkgSbB034SfvoWD9LRN54FaYgXfzSnUbqkqx 3OyBeenlXnMCVDTuB0l52mxZPOBB/KgAv9kE/BytlAAOGntccvQL39WEnIQK130pZef8 l4NaIBg6llJpCa8auw2z9FGIa3f8GNkHE9slo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=5ehe42/kxAwMVQ9XQ2g9ARxDXbaER1RDKMjoZZ2Jhk0=; b=DRT92I4j1DgpQ3yWRmb2xxgrrQK3jMx/KrN0mt8YOTNPbrhuuK0oVPBftOgZQSh4SV fzoQErOC7qTlRG+tQJW9FQXe7bcPy6rS8IAwZEomDhjv/6TKOrOQeKkvTUepInX9Gdze TqFNzQkREGIaLYqM7xMx8CUuANP3UJLlXJUQXCw3hueGTH8XzDLpzM06ZarVrpJvKCtu sE54nPzG6G8cyCtGIcOYKSH/c0RwQQqNVHg3zZBPhhbG5AZVB5nTuIFRUoBh9LZavi1U XNnNS0n22cvj0Di4UaA7Jx2VW6aQrkMtwNqPFFRc5Ny82MaIupHy6AX3Hvu2WaKL56lx HObg== X-Received: by 10.112.51.175 with SMTP id l15mr4874920lbo.5.1359340179573; Sun, 27 Jan 2013 18:29:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.100.164 with HTTP; Sun, 27 Jan 2013 18:29:08 -0800 (PST) In-Reply-To: References: <20130125140953.GA1328@glenbarber.us> <20130125141202.GB1328@glenbarber.us> <20130128072023.63939e6f@X220.ovitrap.com> From: Eitan Adler Date: Sun, 27 Jan 2013 21:29:09 -0500 Message-ID: Subject: Re: what is required to support a new laptop? To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmXRp6KKpedxJMkJ4eOQ4IIku2gXsROLIIqbAT0zYgNmroqkZ1oYBK9BuZdcdzD1mKv/UMK Cc: Glen Barber , freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 02:29:41 -0000 On 27 January 2013 21:23, Kevin Oberman wrote: > On Sun, Jan 27, 2013 at 4:20 PM, Erich Dollansky > wrote: >> Hi, >> >> On Sun, 27 Jan 2013 18:24:36 -0500 >> Eitan Adler wrote: >> >>> On 27 January 2013 12:59, Kevin Oberman wrote: >>> > On Fri, Jan 25, 2013 at 9:25 PM, Eitan Adler >>> > wrote: >>> >> On 25 January 2013 14:51, Kevin Oberman 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