From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 6 23:51:12 2012 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20B601065675; Tue, 6 Mar 2012 23:51:12 +0000 (UTC) (envelope-from nm.knife@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 70E118FC14; Tue, 6 Mar 2012 23:51:11 +0000 (UTC) Received: by werl4 with SMTP id l4so4518623wer.13 for ; Tue, 06 Mar 2012 15:51:10 -0800 (PST) Received-SPF: pass (google.com: domain of nm.knife@gmail.com designates 10.216.137.97 as permitted sender) client-ip=10.216.137.97; Authentication-Results: mr.google.com; spf=pass (google.com: domain of nm.knife@gmail.com designates 10.216.137.97 as permitted sender) smtp.mail=nm.knife@gmail.com; dkim=pass header.i=nm.knife@gmail.com Received: from mr.google.com ([10.216.137.97]) by 10.216.137.97 with SMTP id x75mr9633541wei.25.1331077870696 (num_hops = 1); Tue, 06 Mar 2012 15:51:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=gsBxBbvw4nUthC8NgkWZRDPeosdNtTPmsfkO1mhUdJs=; b=x8X9hQRN3GX4BBr/OC5JyWmgUouWT7SaJIv2yxe7R7O0Jo0NeVal2jFFBrNQmXBCBX v0nu9JoJNwv7MLsTlm0DVoNea/1iIo/U/lVeCFQZWEWs35ns10e6uyGanUGdwTfcckPT BpJHBlM44aa+6pTD0XM9VNUgp4WfYcAK7Q4lx+ujP65Ct4Z8exTKQqIyivgXE2Ldn5qc ILpJIsR8LTwNnhtZzX0mIeScjsp/Q9Y29jZ/v+Akl+r5SDSMlBhOHGHPkHKZzitr4JWF dqO8B+CK24SAiBFGy3hhVN4Nv+udZE/4TAzOJYdDaPVkYA/o2kfKZO1ftt066o9kEo+q FHxw== MIME-Version: 1.0 Received: by 10.216.137.97 with SMTP id x75mr7676513wei.25.1331076306530; Tue, 06 Mar 2012 15:25:06 -0800 (PST) Received: by 10.227.198.18 with HTTP; Tue, 6 Mar 2012 15:25:06 -0800 (PST) In-Reply-To: <4F40A2D4.6000000@gmail.com> References: <4E836C06.9070405@gmail.com> <4E8374A7.90105@gmail.com> <4E9BDF13.4040006@gmail.com> <4F38211D.4070305@mehnert.org> <4F40A2D4.6000000@gmail.com> Date: Tue, 6 Mar 2012 15:25:06 -0800 Message-ID: From: =?windows-1251?B?y/7h7uzo8CDD8Ojj7vDu4g==?= To: matt , freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: x220 notes X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 23:51:12 -0000 I will be buying a X220 soon and have some questions: 1. Which wireless has better support? ThinkPad 11b/g/n Wireless (Realtek RTL8192SE / RTL8188CE) Intel Centrino Wireless-N 1000 2. I've read bad reviews about webcam having poor quality on GNU/Linux, so I would assume it will be the same on FreeBSD with webcamd and not worth the $30? (which also frees up space for 3x3 antenna) 3. Any disadvantages in usage for turning off the UEFI? 4. How far is the AMD64 kernel suspend/resume? What do you mean by video doesn't resume? 5. I'll be getting the IPS screen and want to make sure all the brightness issues won't f it up. Is there yet a working way to control brightness without interrupting the fan? Cheers. 2012/2/18 matt > I got 10-CURRENT installed on the x220 again. > > 1. Standard GENERIC kernel > 2. Buildworld/installworld from today's CVS > 3. No DRM/KMS patches or any other "factors" > 4. Witness KDB disabled in loader.conf (otherwise panic on suspend). > 5. setting hw.pci.do_power_suspend=0 wil prevent some AE_NO_METHOD > errors where it tries to set PCI express ports to D2 (the ports > themselves, I think...not the attached device) > > This is what I've found as I investigate the backlight/resume issue. I > am not very good at understanding ASL, but here's what I see. > > 1. _WAK calls a number of display related methods > 2. There are apparently brightness related calls here, as well as some > other video related calls > 3. Some of this behavior depends on /VIGD, whatever that is. > 4. The brightness calls seem to connect over LPC to the embedded controller > 5. Some of the brightness methods check OSI for WIN7 > > I will add that iasl finds 35 errors in this fine piece of lenovo work. > However, none of the errors appear to be near _wak. I've attached an > acpidump asl if it helps anyone who has a better eye for ASL and > resume/brightness problems. I think we can control brightness at least > with acpi_video, it attaches but not correctly..."active=0"...I haven't > gone back over its source in comparison with ASL yet either. Probably > acpi_ibm will work also, as the acpi methods seem to just call the > embedded controller over the lpc bus? Unfortunately it seems something > has changed with the ec, as some of the data becomes corrupt when > acpi_ibm is loaded. > > Resume obviously works fine in Win7, works 80-95% of the time in Linux > (seems like KMS fail when it doesn't resume on Linux), and it resumes > fine on FreeBSD except no video. No bad messages in logs after resume. > > Matt > > > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" > > -- Lyubomir Grigorov (bgalakazam)