From owner-freebsd-x11@FreeBSD.ORG Sat May 19 03:34:35 2012 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E2C3010656D0 for ; Sat, 19 May 2012 03:34:34 +0000 (UTC) (envelope-from kob6558@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 6D16E8FC0C for ; Sat, 19 May 2012 03:34:34 +0000 (UTC) Received: by werg1 with SMTP id g1so2852012wer.13 for ; Fri, 18 May 2012 20:34:33 -0700 (PDT) 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 :cc:content-type; bh=Yq5yhb4QHzFVdreF+EbsodwmmUJDsADdjMIf6GbVX9o=; b=s4Fm+Ko+cfXnyo5lZd+gdDvng221DWdr4pKIEfiR6yxbyJMjyKBCBZQhah4Oe1t6t9 DKB7IOLGSJgu6fTabUZg5RpQAqShYPniF1v+un5/Y+SmWF8zB2fnvHoVcIcGczHYBn/g tL4rsi8F273bGDw0UfkOmvKWKag4HCTzr6btsgSzjqN+OamzCaQQ6weO30r/56uOwUjV 7c4VqU1QX//yN5lRCWpJMRW0qpC5HcSWJhtNriRfC3crafmh2mGXJghajh5C+TW53R/V YmgQ4ZvyeHMfhBYPtKy4w/o7Lf8Ca8tbDrzFho8iQ6QfEaeTgKO0ZYvSnPOyvwRVt6G+ w47Q== MIME-Version: 1.0 Received: by 10.180.85.129 with SMTP id h1mr7106600wiz.2.1337398473293; Fri, 18 May 2012 20:34:33 -0700 (PDT) Received: by 10.223.155.80 with HTTP; Fri, 18 May 2012 20:34:33 -0700 (PDT) In-Reply-To: <4FB6AACA.2040206@gmail.com> References: <4FB503A6.8000506@gmail.com> <20120517220343.GY2358@deviant.kiev.zoral.com.ua> <4FB6AACA.2040206@gmail.com> Date: Fri, 18 May 2012 20:34:33 -0700 Message-ID: From: Kevin Oberman To: user10508@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-x11@freebsd.org Subject: Re: pcbsd9-stable-20120505 snapshot - howto enable intel rc6 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2012 03:34:35 -0000 On Fri, May 18, 2012 at 1:02 PM, wrote: > Kevin Oberman@ > > Thank you for your suggestion. > > hint.acpi_throttle.0.disabled=1 was in /boot/loader.conf, I added > hint.p4tcc.0.disabled=1 and rebooted. Unfortunately, these changes to > /boot/loader.conf had no effect on the thermal or battery life problems I've > been experiencing. > > Konstantin Belousov@ > > Thank you for your suggestion. It reminded me that I neglected to report > that screen artifacts appeared as system temperature increased. No surprise > about that right? Initially few in number and small in area, over time, the > number of artifacts and the size of affected areas increased. Redraws, > manual or application related, removed the artifact. > > In researching the problems I've been experiencing, I found comments about > initial releases of intel's X driver on linux. Early software had poor > battery life and thermal problems on laptops. > > So far so good. To me this means that there is nothing unusual about the > initial freebsd release of kms support for the intel sandybridge IGA. > > I installed linux-mint debian eddition which was released just a few days > ago. This release of linux uses a linux 3.2 kernel and for X, > intel-2.18.0-1. > > This combination results in normal battery life and no thermal problems. > > Given the close relationship between linux kernel changes and intel driver > changes, it may be premature to assume that just using X intel-2.18.0 on a > freebsd stable kernel will solve everything. > > On a well ventilated server, I think this initial release of kms support may > be good to go. > > For laptops, I don't think its quite there yet. > > I'm going to wait for RC6 functionality to percolate into X for Intel. When > its ready, I'm confident it will solve the problems I've been experiencing. FWIW, I am running on a laptop with Intel-KMS driver with none of the power or thermal issues you are having. ThinkPad T520 Sandybridge. My cores are currently at 51 and 55 degrees with a load average of about .5, so pretty calm. Something is different in your system that is triggering the problem. I just don't know about hardware or software. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com