From owner-freebsd-acpi@FreeBSD.ORG Mon Oct 9 11:09:08 2006 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EF5A16A403 for ; Mon, 9 Oct 2006 11:09:08 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 051A943D98 for ; Mon, 9 Oct 2006 11:08:31 +0000 (GMT) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k99B8F8j071422 for ; Mon, 9 Oct 2006 11:08:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k99B8EuD071419 for freebsd-acpi@FreeBSD.org; Mon, 9 Oct 2006 11:08:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 9 Oct 2006 11:08:14 GMT Message-Id: <200610091108.k99B8EuD071419@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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: Mon, 09 Oct 2006 11:09:08 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/54756 acpi ACPI suspend/resume problem on CF-W2 laptop o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 o kern/55822 acpi No ACPI power off with SMP kernel o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/64002 acpi acpi problem o i386/67273 acpi [hang] system hangs with acpi and Xfree o i386/72566 acpi ACPI, FreeBSD disables fan on Compaq Armada 1750 o i386/79080 acpi acpi thermal changes freezes HP nx6110 o i386/79081 acpi ACPI suspend/resume not working on HP nx6110 o i386/80426 acpi [APIC] [panic] 5.4-RC3 still panic when boot on ASUS P o i386/87568 acpi [ACPI] [REGRESSION] 6.0-STABLE needs ACPI disabled but 11 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/67309 acpi zzz reboot computer (ACPI S3) o i386/69750 acpi Boot without ACPI failed on ASUS L5 o i386/73822 acpi [request] add thermal support to ACPI o kern/73823 acpi [feature request] acpi / power-on by timer support f kern/74030 acpi Unplugging AC causes battery % to stay locked at 98% f kern/90871 acpi ACPI problems with ASUS A8N-VM-CSM o kern/97383 acpi Volume buttons on IBM Thinkpad crash system with ACPI o kern/98171 acpi [acpi] ACPI 1304 / 0501 errors on Acer 5024WLMi Laptop o kern/103365 acpi [acpi] acpi poweroff doesn't work with geli device att 9 problems total. From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 10 05:40:18 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF38416A492 for ; Tue, 10 Oct 2006 05:40:18 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C7A843D53 for ; Tue, 10 Oct 2006 05:40:18 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.46.150] Received: from [10.0.5.50] (ppp-71-139-46-150.dsl.snfc21.pacbell.net [71.139.46.150]) by ylpvm15.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id k9A5eIsd000305; Tue, 10 Oct 2006 01:40:18 -0400 Message-ID: <452B323B.6050908@root.org> Date: Mon, 09 Oct 2006 22:40:11 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Jacques Garrigue References: <20061007.184902.07645150.garrigue@math.nagoya-u.ac.jp> In-Reply-To: <20061007.184902.07645150.garrigue@math.nagoya-u.ac.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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, 10 Oct 2006 05:40:18 -0000 Jacques Garrigue wrote: > Hi, > > I've just installed FreeBSD 6.2-BETA2 on a Vaio VGN-TX92S, which is a > Centrino laptop with a Core Solo U1400, ICH7 chipset. > > After a bit of fiddling, I can use most features: > * Xorg in 1368x768 mode (nothing to do) > * integrated ethernet (just had to add the board ID to if_fxp.c) > * wireless (download and compile wpi-freebsd.tgz) > * HDA audio (download and compile hdac driver, as snd_hda didn't > compile) > * USB, pccard, bluetooth (nothing to do) > > So I should be happy, but I have two problems. > > The most usual one is that it doesn't resume after suspend: acpiconf > -s3 does go to sleep, but it hangs on resume. I don't know if there is > an easy solution, but I would take any hint. This is a faq -- try disabling APIC: hint.apic.0.disabled="1" > The more unusual one is that it gets rather hot. After a few minutes, > the fan starts, and never stops. The temperature reading quickly goes > to 58C, and stays there, but may go to 65C under load (the machine > feels actually hot.) I even got some hang-ups that look like > overheat. Under windows it gets hot at times, but not that easily. > Note that cpufreq seems to work: when idle, the frequency goes down to > 100MHz. Try without some device drivers loaded (wpi, hda, etc.) See if that makes a difference. Also, see the acpi man page for cpu idling, namely setting hw.acpi.cpu.cx_lowest=C3. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 10 07:54:00 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 298AD16A403 for ; Tue, 10 Oct 2006 07:54:00 +0000 (UTC) (envelope-from garrigue@math.nagoya-u.ac.jp) Received: from kurims.kurims.kyoto-u.ac.jp (kurims.kurims.kyoto-u.ac.jp [130.54.16.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B3B743D45 for ; Tue, 10 Oct 2006 07:53:59 +0000 (GMT) (envelope-from garrigue@math.nagoya-u.ac.jp) Received: from localhost (orion [130.54.16.5]) by kurims.kurims.kyoto-u.ac.jp (8.13.7/8.13.7) with ESMTP id k9A7rufJ005172; Tue, 10 Oct 2006 16:53:57 +0900 (JST) Date: Tue, 10 Oct 2006 16:54:04 +0900 (JST) Message-Id: <20061010.165404.74754637.garrigue@math.nagoya-u.ac.jp> To: nate@root.org From: Jacques Garrigue In-Reply-To: <452B323B.6050908@root.org> References: <20061007.184902.07645150.garrigue@math.nagoya-u.ac.jp> <452B323B.6050908@root.org> X-Mailer: Mew version 5.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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, 10 Oct 2006 07:54:00 -0000 From: Nate Lawson > > I've just installed FreeBSD 6.2-BETA2 on a Vaio VGN-TX92S, which is a > > Centrino laptop with a Core Solo U1400, ICH7 chipset. [...] > > The most usual one is that it doesn't resume after suspend: acpiconf > > -s3 does go to sleep, but it hangs on resume. I don't know if there is > > an easy solution, but I would take any hint. > > This is a faq -- try disabling APIC: > hint.apic.0.disabled="1" Thanks, that almost did the trick. If I also disable the hda sound driver, then I can suspend and resume. (With hda on, it goes directly to power off... but then this is not the official driver) The bad news is that if_wpi doesn't come back after sleep. But again, this is an early version of the driver, there seems to be some support for suspend/resume in, but it might have some pitfalls. If there is any wpi expert around, here are the messages I get around the suspend/resume: wpi0: link state changed to DOWN ACPI-0370: *** Error: No installed handler for fixed event [00000002] wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory wpi0: could not lock memory setting h/w config fffff7ff wpi0: could not lock memory wpi0: could not lock memory firmware_get: insufficient privileges to load firmware image wpi_ucode wpi0: could not load firmware image 'wpi_ucode' wpi0: could not lock memory wpi0: could not lock memory > > The more unusual one is that it gets rather hot. After a few minutes, > > the fan starts, and never stops. The temperature reading quickly goes > > to 58C, and stays there, but may go to 65C under load (the machine > > feels actually hot.) I even got some hang-ups that look like > > overheat. Under windows it gets hot at times, but not that easily. > > Note that cpufreq seems to work: when idle, the frequency goes down to > > 100MHz. > > Try without some device drivers loaded (wpi, hda, etc.) See if that > makes a difference. Also, see the acpi man page for cpu idling, namely > setting hw.acpi.cpu.cx_lowest=C3. I tried this, with only C2, as C3 does not seem to be available for this cpu currently. (The Intel docs talk of a "very deep sleep" mode, so this may be lacking in the FreeBSD support.) Anyway, thank you very much for your answers. At least I got to sleep, and this is a huge improvement. --------------------------------------------------------------------------- Jacques Garrigue Nagoya University garrigue at math.nagoya-u.ac.jp JG From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 10 08:37:03 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7B2B16A40F for ; Tue, 10 Oct 2006 08:37:03 +0000 (UTC) (envelope-from garrigue@math.nagoya-u.ac.jp) Received: from kurims.kurims.kyoto-u.ac.jp (kurims.kurims.kyoto-u.ac.jp [130.54.16.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B3DA43D5C for ; Tue, 10 Oct 2006 08:37:02 +0000 (GMT) (envelope-from garrigue@math.nagoya-u.ac.jp) Received: from localhost (orion [130.54.16.5]) by kurims.kurims.kyoto-u.ac.jp (8.13.7/8.13.7) with ESMTP id k9A8awbt006691; Tue, 10 Oct 2006 17:36:59 +0900 (JST) Date: Tue, 10 Oct 2006 17:37:07 +0900 (JST) Message-Id: <20061010.173707.08072970.garrigue@math.nagoya-u.ac.jp> To: nate@root.org From: Jacques Garrigue In-Reply-To: <20061010.165404.74754637.garrigue@math.nagoya-u.ac.jp> References: <20061007.184902.07645150.garrigue@math.nagoya-u.ac.jp> <452B323B.6050908@root.org> <20061010.165404.74754637.garrigue@math.nagoya-u.ac.jp> X-Mailer: Mew version 5.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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, 10 Oct 2006 08:37:03 -0000 A few additions, as my previous post was incomplete. > From: Nate Lawson > > > The most usual one is that it doesn't resume after suspend: acpiconf > > > -s3 does go to sleep, but it hangs on resume. I don't know if there is > > > an easy solution, but I would take any hint. > > > > This is a faq -- try disabling APIC: > > hint.apic.0.disabled="1" > > Thanks, that almost did the trick. If I also disable the hda sound > driver, then I can suspend and resume. Actually, I also needed "sysctl hw.acpi.reset_video=1" since the default changed to 0. > > > The more unusual one is that it gets rather hot. After a few minutes, > > > the fan starts, and never stops. The temperature reading quickly goes > > > to 58C, and stays there, but may go to 65C under load (the machine > > Try without some device drivers loaded (wpi, hda, etc.) See if that > > makes a difference. Also, see the acpi man page for cpu idling, namely > > setting hw.acpi.cpu.cx_lowest=C3. > > I tried this, with only C2, as C3 does not seem to be available for > this cpu currently. (The Intel docs talk of a "very deep sleep" mode, > so this may be lacking in the FreeBSD support.) I was wrong. When I tried first the supported modes were only C1 and C2, but using sysctl again later I found that C3 and even C4 were available. I wonder why it changes while running. I tried with C4, but I get no significant change in temperature. Since the main problem is hang-up from overheat, is there any progress in having powerd slow the CPU when the temperature is too high? Jacques Garrigue From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 10 11:13:56 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5958B16A492 for ; Tue, 10 Oct 2006 11:13:56 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mx18.yandex.ru (smtp2.yandex.ru [213.180.200.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39A3043D45 for ; Tue, 10 Oct 2006 11:13:54 +0000 (GMT) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([81.18.142.225]:57609 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S475149AbWJJLNu (ORCPT ); Tue, 10 Oct 2006 15:13:50 +0400 X-Comment: RFC 2476 MSA function at smtp2.yandex.ru logged sender identity as: bu7cher Message-ID: <452B806C.9070808@yandex.ru> Date: Tue, 10 Oct 2006 15:13:48 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Nate Lawson References: <20061007.184902.07645150.garrigue@math.nagoya-u.ac.jp> <452B323B.6050908@root.org> In-Reply-To: <452B323B.6050908@root.org> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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, 10 Oct 2006 11:13:56 -0000 Nate Lawson wrote: >> The most usual one is that it doesn't resume after suspend: acpiconf >> -s3 does go to sleep, but it hangs on resume. I don't know if there is >> an easy solution, but I would take any hint. > > This is a faq -- try disabling APIC: > hint.apic.0.disabled="1" I have the same problem. (on the Maxselect GT3000) And this solution help me. But my display don't wake up. I've tried with reset_video and without, but have no results. After my test i have in /var/log/messages: Oct 10 11:29:44 btr-nb sudo: butcher : TTY=ttyv0 ; PWD=/usr/home/butcher ; USER=root ; COMMAND=/usr/sbin/acpiconf -s 3 Oct 10 11:29:45 btr-nb acpi: suspend at 20061010 11:29:45 Oct 10 11:29:56 btr-nb kernel: pci0: Failed to set ACPI power state D2 on \_SB_.PCI0.USB0: AE_BAD_PARAMETER Oct 10 11:30:09 btr-nb kernel: wakeup from sleeping state (slept 00:00:21) Oct 10 11:30:09 btr-nb kernel: battery0: battery initialization start Oct 10 11:30:09 btr-nb kernel: battery0: battery initialization done, tried 1 times Oct 10 11:30:09 btr-nb kernel: atapicam3: detached Oct 10 11:30:09 btr-nb acpi: resumed at 20061010 11:30:09 Oct 10 11:30:57 btr-nb kernel: acpi_button0: power button pressed Sometimes after resuming i can ping my notebook from the network. I think resuming partially works. Nate can you help me? Can you reply to my older message? http://docs.freebsd.org/cgi/mid.cgi?452208B0.7030604 -- WBR, Andrey V. Elsukov From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 10 14:20:40 2006 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4267016A535; Tue, 10 Oct 2006 14:20:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F32D43D7E; Tue, 10 Oct 2006 14:20:38 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k9AEKb1g087487; Tue, 10 Oct 2006 10:20:37 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: acpi@freebsd.org Date: Tue, 10 Oct 2006 10:20:31 -0400 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610101020.32041.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Tue, 10 Oct 2006 10:20:37 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/2018/Tue Oct 10 08:04:40 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: mobile@freebsd.org Subject: [PATCH] UP APIC suspend/resume support -- Please test 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, 10 Oct 2006 14:20:40 -0000 No one has tested this yet, so I guess folks missed it. Can someone with otherwise working suspend/resume on a system with APIC please test http://www.freebsd.org/~jhb/patches/apic_resume.patch and let me know if suspend/resume works? Note that it doesn't add SMP support, so you'll still need to disable SMP (either via kern.smp.disabled or by removing SMP from the kernel config) to test. Thanks. -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Oct 10 17:35:32 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0042416A407 for ; Tue, 10 Oct 2006 17:35:31 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4136143D80 for ; Tue, 10 Oct 2006 17:35:23 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.46.150] Received: from [10.0.5.50] (ppp-71-139-46-150.dsl.snfc21.pacbell.net [71.139.46.150]) by ylpvm12.prodigy.net (8.13.7 out spool5000 dk/8.13.7) with ESMTP id k9AHZJss019004; Tue, 10 Oct 2006 13:35:20 -0400 Message-ID: <452BD9D2.5030609@root.org> Date: Tue, 10 Oct 2006 10:35:14 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Jacques Garrigue References: <20061007.184902.07645150.garrigue@math.nagoya-u.ac.jp> <452B323B.6050908@root.org> <20061010.165404.74754637.garrigue@math.nagoya-u.ac.jp> <20061010.173707.08072970.garrigue@math.nagoya-u.ac.jp> In-Reply-To: <20061010.173707.08072970.garrigue@math.nagoya-u.ac.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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, 10 Oct 2006 17:35:32 -0000 Jacques Garrigue wrote: > A few additions, as my previous post was incomplete. > >> From: Nate Lawson >>>> The most usual one is that it doesn't resume after suspend: acpiconf >>>> -s3 does go to sleep, but it hangs on resume. I don't know if there is >>>> an easy solution, but I would take any hint. >>> This is a faq -- try disabling APIC: >>> hint.apic.0.disabled="1" >> Thanks, that almost did the trick. If I also disable the hda sound >> driver, then I can suspend and resume. > > Actually, I also needed "sysctl hw.acpi.reset_video=1" since the > default changed to 0. > >>>> The more unusual one is that it gets rather hot. After a few minutes, >>>> the fan starts, and never stops. The temperature reading quickly goes >>>> to 58C, and stays there, but may go to 65C under load (the machine >>> Try without some device drivers loaded (wpi, hda, etc.) See if that >>> makes a difference. Also, see the acpi man page for cpu idling, namely >>> setting hw.acpi.cpu.cx_lowest=C3. >> I tried this, with only C2, as C3 does not seem to be available for >> this cpu currently. (The Intel docs talk of a "very deep sleep" mode, >> so this may be lacking in the FreeBSD support.) > > I was wrong. When I tried first the supported modes were only C1 and > C2, but using sysctl again later I found that C3 and even C4 were > available. I wonder why it changes while running. I tried with C4, but > I get no significant change in temperature. It changes based on AC line status. See the acpi man page or /etc/defaults/rc.conf ("cx" lines) to see. > Since the main problem is hang-up from overheat, is there any progress > in having powerd slow the CPU when the temperature is too high? Passive cooling is already supported in 6-stable and 7-current. -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 01:26:39 2006 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2F4F16A403 for ; Wed, 11 Oct 2006 01:26:39 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74D2D43D55 for ; Wed, 11 Oct 2006 01:26:39 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k9B1Qba9048713; Tue, 10 Oct 2006 21:26:37 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Tue, 10 Oct 2006 21:26:21 -0400 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200610102126.24853.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/2020/Tue Oct 10 14:11:22 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: [PATCH] ACPI-CA 20060912 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: Wed, 11 Oct 2006 01:26:40 -0000 FYI, merge from the latest ACPI-CA (downloaded from Intel web site) and the patch against HEAD is here: http://people.freebsd.org/~jkim/acpica-import-20060912.diff.gz (Note: There are removed files and added files. Don't forget '-p' option when you patch.) ACPI-CA change log from the last import is here: http://people.freebsd.org/~jkim/acpica_changes_20051021_20060912.txt I am not going to import it any time soon because the changes are too big. I have to warn you that it is lightly tested only on amd64 but I believe it is fairly usable. If anybody's interested (esp. with i386 and ia64), feel free to try it and give me feedback. Thanks, Jung-uk Kim From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 09:05:51 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E10716A417 for ; Wed, 11 Oct 2006 09:05:51 +0000 (UTC) (envelope-from mikael.tanskanen@pp.inet.fi) Received: from pne-smtpout3-sn2.hy.skanova.net (pne-smtpout3-sn2.hy.skanova.net [81.228.8.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5B4B43D5E for ; Wed, 11 Oct 2006 09:05:50 +0000 (GMT) (envelope-from mikael.tanskanen@pp.inet.fi) Received: from hoasb-ff0fdd00-35.dhcp.inet.fi (80.221.15.35) by pne-smtpout3-sn2.hy.skanova.net (7.2.075) id 451773CD000D6170 for freebsd-acpi@freebsd.org; Wed, 11 Oct 2006 11:05:49 +0200 From: Mikael To: freebsd-acpi@freebsd.org Date: Wed, 11 Oct 2006 12:08:02 +0300 User-Agent: KMail/1.9.4 References: <200610102126.24853.jkim@FreeBSD.org> In-Reply-To: <200610102126.24853.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610111208.03315.mikael.tanskanen@pp.inet.fi> Subject: newbie has ACPI problem 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: Wed, 11 Oct 2006 09:05:51 -0000 Hello As I am new to FreeBSD and could not find anything useful by googling around I decided to ask from here. In FreeBSD7-CURRENT acpi works for my laptop (Fujitsu Siemes Amilo A1650) but FreeBSD6.1-STABLE (or 6.2 RC1) did give me lot of error messages with different error codes. Mostly about fails in TZS stuff.. Everytime my cpu get more work and fans start spinning faster i got error messages printed on screen. Other problem is that my clock speeds is running too fast. For example in boot screen the time counter speeds almost in double speed. And since this is laptop with dynamically changing cpu frequencies and fan speeds I really would like to have acpi enabled :) In Linux(2.6.17) and Windows these things work....but I REALLY would like replace them with FreeBSD. SO...THE QUESTION (finally) Is it possible to use freebsd6,1 stable with custom kernel acpi module from freebsd7-current? or any other way for newbie to get his ACPI working, -mikael From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 14:31:19 2006 Return-Path: X-Original-To: acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8710216A412; Wed, 11 Oct 2006 14:31:19 +0000 (UTC) (envelope-from nork@FreeBSD.org) Received: from sakura.ninth-nine.com (sakura.ninth-nine.com [219.127.74.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id D46C043D46; Wed, 11 Oct 2006 14:31:18 +0000 (GMT) (envelope-from nork@FreeBSD.org) Received: from nadesico.ninth-nine.com (nadesico.ninth-nine.com [219.127.74.122]) by sakura.ninth-nine.com (8.13.8/8.13.8/NinthNine) with ESMTP id k9BEVG0q019625; Wed, 11 Oct 2006 23:31:16 +0900 (JST) (envelope-from nork@FreeBSD.org) Date: Wed, 11 Oct 2006 23:31:13 +0900 From: Norikatsu Shigemura To: John Baldwin Message-Id: <20061011233113.7446a3ab.nork@FreeBSD.org> In-Reply-To: <200610101020.32041.jhb@freebsd.org> References: <200610101020.32041.jhb@freebsd.org> X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.8.20; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (sakura.ninth-nine.com [219.127.74.121]); Wed, 11 Oct 2006 23:31:16 +0900 (JST) Cc: acpi@FreeBSD.org, mobile@FreeBSD.org Subject: Re: [PATCH] UP APIC suspend/resume support -- Please test 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: Wed, 11 Oct 2006 14:31:19 -0000 On Tue, 10 Oct 2006 10:20:31 -0400 John Baldwin wrote: > No one has tested this yet, so I gues folks missed it. Can someone with > otherwise working suspend/resume on a system with APIC please test > http://www.freebsd.org/~jhb/patches/apic_resume.patch and let me know if > suspend/resume works? Note that it doesn't add SMP support, so you'll > still need to disable SMP (either via kern.smp.disabled or by removing > SMP from the kernel config) to test. Thanks. Perfect!! in my Panasonic CF-R4 (Let's note/Toughbook) on 6.2-PRERELEASE. FreeBSD melfina.ninth-nine.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #25: Wed Oct 11 22:51:01 JST 2006 nork@melfina.ninth-nine.com:/usr/obj/usr/src/sys/MELFINA i386 : Oct 11 23:15:46 melfina kernel: ioapic0: Changing APIC ID to 1 Oct 11 23:15:46 melfina kernel: ioapic0 irqs 0-23 on motherboard : Oct 11 23:17:10 melfina acpi: suspend at 20061011 23:17:10 Oct 11 23:17:13 melfina kernel: ioapic_suspend: not implemented! Oct 11 23:17:24 melfina kernel: cpu0: Cx states changed Oct 11 23:17:24 melfina kernel: wakeup from sleeping state (slept 00:00:12) Oct 11 23:17:24 melfina kernel: rl0: link state changed to DOWN Oct 11 23:17:24 melfina kernel: ichsmb0: irq 0x02 during -1 Oct 11 23:17:24 melfina acpi: resumed at 20061011 23:17:24 Oct 11 23:17:24 melfina kernel: rl0: link state changed to UP Oct 11 23:18:10 melfina kernel: can't re-use a leaf (directional_scrolls)! Oct 11 23:18:10 melfina kernel: can't re-use a leaf (low_speed_threshold)! Oct 11 23:18:10 melfina kernel: can't re-use a leaf (min_movement)! Oct 11 23:18:10 melfina kernel: can't re-use a leaf (squelch_level)! From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 14:50:55 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60F8E16A416 for ; Wed, 11 Oct 2006 14:50:55 +0000 (UTC) (envelope-from John@utzweb.net) Received: from marley.grokthis.net (marley.grokthis.net [69.93.78.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BAB43D7B for ; Wed, 11 Oct 2006 14:50:54 +0000 (GMT) (envelope-from John@utzweb.net) Received: from [192.168.1.6] (c-71-197-214-178.hsd1.or.comcast.net [71.197.214.178]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by marley.grokthis.net (Postfix) with ESMTP id 3CAF6F101D for ; Wed, 11 Oct 2006 10:50:55 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-acpi@freebsd.org From: John Utz Date: Wed, 11 Oct 2006 07:50:49 -0700 X-Mailer: Apple Mail (2.752.2) Subject: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Wed, 11 Oct 2006 14:50:55 -0000 i've been working on i8k utils off and on for several months. (lately it's been what i've been doing whilst i sit at my daughter's gymnastics class) so several of the api's work, ie turning the fans on and off, etc. buttons *still* dont work. :-( at this point, i want to start working on hXRing the kernel module. as currently coded, it writes to /proc. i would prefer to not have to require the proc lkm for this to work, i'd rather do it the bsd way. so, umm, what *is* the bsd way ? :-) tnx! johnu From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 16:01:38 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0C4716A4B3 for ; Wed, 11 Oct 2006 16:01:38 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D82C43D78 for ; Wed, 11 Oct 2006 16:01:33 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.39.204] Received: from [10.0.5.50] (ppp-71-139-39-204.dsl.snfc21.pacbell.net [71.139.39.204]) by ylpvm43.prodigy.net (8.13.8 out.dk.spool/8.13.8) with ESMTP id k9BG1T7N010416; Wed, 11 Oct 2006 12:01:30 -0400 Message-ID: <452D1555.10801@root.org> Date: Wed, 11 Oct 2006 09:01:25 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Mikael References: <200610102126.24853.jkim@FreeBSD.org> <200610111208.03315.mikael.tanskanen@pp.inet.fi> In-Reply-To: <200610111208.03315.mikael.tanskanen@pp.inet.fi> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: newbie has ACPI problem 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: Wed, 11 Oct 2006 16:01:38 -0000 Mikael wrote: > In FreeBSD7-CURRENT acpi works for my laptop (Fujitsu Siemes Amilo A1650) > but FreeBSD6.1-STABLE (or 6.2 RC1) did give me lot of error messages with > different error codes. Mostly about fails in TZS stuff.. > > Everytime my cpu get more work and fans start spinning faster i got error > messages printed on screen. That will be fixed once acpi-ca is stabilized and then merged to 6-stable. > Other problem is that my clock speeds is running too fast. For example in boot > screen the time counter speeds almost in double speed. > > And since this is laptop with dynamically changing cpu frequencies and fan > speeds I really would like to have acpi enabled :) Don't use TSC as a timecounter when also using cpufreq. There is already a check for this in the cpufreq code, but maybe it doesn't work when TSC is selected at boot? sysctl kern.timecounter.hardware="i8254" or sysctl kern.timecounter.hardware="acpi-fast" http://lists.freebsd.org/pipermail/freebsd-current/2003-August/008718.html If it works, put it in /etc/sysctl.conf -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 16:05:07 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DC7F16A40F for ; Wed, 11 Oct 2006 16:05:07 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19AED43DAA for ; Wed, 11 Oct 2006 16:04:49 +0000 (GMT) (envelope-from nate@root.org) X-ORBL: [71.139.39.204] Received: from [10.0.5.50] (ppp-71-139-39-204.dsl.snfc21.pacbell.net [71.139.39.204]) by ylpvm12.prodigy.net (8.13.7 out spool5000 dk/8.13.7) with ESMTP id k9BG4lrA002045; Wed, 11 Oct 2006 12:04:47 -0400 Message-ID: <452D161A.5040509@root.org> Date: Wed, 11 Oct 2006 09:04:42 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: John Utz References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> In-Reply-To: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Wed, 11 Oct 2006 16:05:07 -0000 John Utz wrote: > i've been working on i8k utils off and on for several months. > > (lately it's been what i've been doing whilst i sit at my daughter's > gymnastics class) > > so several of the api's work, ie turning the fans on and off, etc. > > buttons *still* dont work. :-( > > at this point, i want to start working on hXRing the kernel module. > > as currently coded, it writes to /proc. > > i would prefer to not have to require the proc lkm for this to work, i'd > rather do it the bsd way. > > so, umm, what *is* the bsd way ? :-) It looks like "i8k" is the Dell hotkeys/PM driver. Use sysctl as the interface. See the other drivers in /sys/dev/acpi_support for a good template (i.e., acpi_toshiba.c). -- Nate From owner-freebsd-acpi@FreeBSD.ORG Wed Oct 11 17:07:25 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 98CEE16A407 for ; Wed, 11 Oct 2006 17:07:25 +0000 (UTC) (envelope-from john@utzweb.net) Received: from marley.grokthis.net (marley.grokthis.net [69.93.78.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A3AB44016 for ; Wed, 11 Oct 2006 17:01:40 +0000 (GMT) (envelope-from john@utzweb.net) Received: from utzweb.net (marley.grokthis.net [127.0.0.1]) by marley.grokthis.net (Postfix) with ESMTP id D311FF1024; Wed, 11 Oct 2006 13:01:13 -0400 (EDT) Received: from 69.93.78.27 (proxying for 216.254.62.194) (SquirrelMail authenticated user john-utzweb-net); by utzweb.net with HTTP; Wed, 11 Oct 2006 13:01:17 -0400 (EDT) Message-ID: <35862.69.93.78.27.1160586077.squirrel@69.93.78.27> In-Reply-To: <452D161A.5040509@root.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> Date: Wed, 11 Oct 2006 13:01:17 -0400 (EDT) From: john@utzweb.net To: "Nate Lawson" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Wed, 11 Oct 2006 17:07:25 -0000 > John Utz wrote: >> i've been working on i8k utils off and on for several months. >> >> (lately it's been what i've been doing whilst i sit at my daughter's >> gymnastics class) >> >> so several of the api's work, ie turning the fans on and off, etc. >> >> buttons *still* dont work. :-( >> >> at this point, i want to start working on hXRing the kernel module. >> >> as currently coded, it writes to /proc. >> >> i would prefer to not have to require the proc lkm for this to work, i'd >> rather do it the bsd way. >> >> so, umm, what *is* the bsd way ? :-) > > It looks like "i8k" is the Dell hotkeys/PM driver. yah, i forgot to mention that. sorry. > Use sysctl as the interface. hokydoky! > See the other drivers in /sys/dev/acpi_support for a good > template (i.e., acpi_toshiba.c). i shall look again at that, tnx! johnu > -- > Nate > > From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 03:07:08 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF17B16A416 for ; Thu, 12 Oct 2006 03:07:08 +0000 (UTC) (envelope-from garrigue@math.nagoya-u.ac.jp) Received: from kurims.kurims.kyoto-u.ac.jp (kurims.kurims.kyoto-u.ac.jp [130.54.16.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 073A443D55 for ; Thu, 12 Oct 2006 03:07:07 +0000 (GMT) (envelope-from garrigue@math.nagoya-u.ac.jp) Received: from localhost (orion [130.54.16.5]) by kurims.kurims.kyoto-u.ac.jp (8.13.7/8.13.7) with ESMTP id k9C375rZ006385; Thu, 12 Oct 2006 12:07:06 +0900 (JST) Date: Thu, 12 Oct 2006 12:07:03 +0900 (JST) Message-Id: <20061012.120703.59465247.garrigue@math.nagoya-u.ac.jp> To: nate@root.org From: Jacques Garrigue In-Reply-To: <452BD9D2.5030609@root.org> References: <20061010.165404.74754637.garrigue@math.nagoya-u.ac.jp> <20061010.173707.08072970.garrigue@math.nagoya-u.ac.jp> <452BD9D2.5030609@root.org> X-Mailer: Mew version 5.1 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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: Thu, 12 Oct 2006 03:07:08 -0000 From: Nate Lawson > >>> Also, see the acpi man page for cpu idling, namely > >>> setting hw.acpi.cpu.cx_lowest=C3. > >> I tried this, with only C2, as C3 does not seem to be available for > >> this cpu currently. (The Intel docs talk of a "very deep sleep" mode, > >> so this may be lacking in the FreeBSD support.) > > > > I was wrong. When I tried first the supported modes were only C1 and > > C2, but using sysctl again later I found that C3 and even C4 were > > available. I wonder why it changes while running. I tried with C4, but > > I get no significant change in temperature. > > It changes based on AC line status. See the acpi man page or > /etc/defaults/rc.conf ("cx" lines) to see. Thanks. With this I can keep it low. But this does not change the original strange behaviour: if I boot with AC on, I only get C1 and C2 listed, but if I boot on battery I get C1 to C4. The supported modes do not seem to change after boot. > > Since the main problem is hang-up from overheat, is there any progress > > in having powerd slow the CPU when the temperature is too high? > > Passive cooling is already supported in 6-stable and 7-current. OK, I've set _PSV to 60.0C, which should have protected me against overheat. I verified that the CPU slows when over 60.0C. But just as I was writing this mail (and extracting the Linux kernel sources, don't ask me why...) I experienced again a strange unexpected reboot. Just before reboot, the sysctl node dev.cpu.0 had disappeared! The temperature was over 60C, but not that high. By the way, the acpi_thermal man page seems to be wrong about setting temperatures through sysctl: it says that you should use an integer temperature in celsius, but if I do that I get "Invalid argument". Actually I had to set in 1/10 of Kelvin (ie 3332), after reading kernel sources. Last unrelated points (This is probably not the place to write them): * if_wpi doesn't seem to work with WEP for me :-( * I tried the latest snd_hda driver (10/01), but I cannot suspend when using it * (maybe more related) output to external display doesn't seem to work, even if I reboot with the display connected (it just succeeds in garbling the internal LCD.) There is no option about it in the BIOS settings. * while hot keys do not work, brightness can be controlled through acpi_sony sysctl's. Jacques From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 04:46:04 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F145F16A407 for ; Thu, 12 Oct 2006 04:46:04 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D24C043D79 for ; Thu, 12 Oct 2006 04:46:02 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 47561 invoked from network); 12 Oct 2006 04:46:10 -0000 Received: from ppp-71-139-39-204.dsl.snfc21.pacbell.net (HELO ?10.0.5.50?) (nate-mail@71.139.39.204) by root.org with ESMTPA; 12 Oct 2006 04:46:10 -0000 Message-ID: <452DC86F.7060102@root.org> Date: Wed, 11 Oct 2006 21:45:35 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Jacques Garrigue References: <20061010.165404.74754637.garrigue@math.nagoya-u.ac.jp> <20061010.173707.08072970.garrigue@math.nagoya-u.ac.jp> <452BD9D2.5030609@root.org> <20061012.120703.59465247.garrigue@math.nagoya-u.ac.jp> In-Reply-To: <20061012.120703.59465247.garrigue@math.nagoya-u.ac.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: Sony Vaio VGN-TX92S 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: Thu, 12 Oct 2006 04:46:05 -0000 Jacques Garrigue wrote: > From: Nate Lawson > >>>>> Also, see the acpi man page for cpu idling, namely >>>>> setting hw.acpi.cpu.cx_lowest=C3. >>>> I tried this, with only C2, as C3 does not seem to be available for >>>> this cpu currently. (The Intel docs talk of a "very deep sleep" mode, >>>> so this may be lacking in the FreeBSD support.) >>> I was wrong. When I tried first the supported modes were only C1 and >>> C2, but using sysctl again later I found that C3 and even C4 were >>> available. I wonder why it changes while running. I tried with C4, but >>> I get no significant change in temperature. >> It changes based on AC line status. See the acpi man page or >> /etc/defaults/rc.conf ("cx" lines) to see. > > Thanks. With this I can keep it low. > But this does not change the original strange behaviour: if I boot > with AC on, I only get C1 and C2 listed, but if I boot on battery I > get C1 to C4. The supported modes do not seem to change after boot. The BIOS decides that. We should get a notify that Cx states changed and re-evaluate the settings. That support is not done yet so you're stuck with whatever you get on boot. >>> Since the main problem is hang-up from overheat, is there any progress >>> in having powerd slow the CPU when the temperature is too high? >> Passive cooling is already supported in 6-stable and 7-current. > > OK, I've set _PSV to 60.0C, which should have protected me against > overheat. I verified that the CPU slows when over 60.0C. > But just as I was writing this mail (and extracting the Linux kernel > sources, don't ask me why...) I experienced again a strange unexpected > reboot. Just before reboot, the sysctl node dev.cpu.0 had disappeared! > The temperature was over 60C, but not that high. Sounds like a bug or hardware problem. > By the way, the acpi_thermal man page seems to be wrong about setting > temperatures through sysctl: it says that you should use an integer > temperature in celsius, but if I do that I get "Invalid argument". > Actually I had to set in 1/10 of Kelvin (ie 3332), after reading > kernel sources. I think you need a "C" to indicate celsius. Example: ="60C" The sysctl user program translates for Celsius, Fahrenheit ("120F"), and Kelvin (no letter). -- Nate From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 16:01:13 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FD3D16A415 for ; Thu, 12 Oct 2006 16:01:13 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77F7343D6B for ; Thu, 12 Oct 2006 15:59:39 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GY2xa-0001zy-00; Thu, 12 Oct 2006 17:59:02 +0200 Date: Thu, 12 Oct 2006 17:59:02 +0200 To: john@utzweb.net Message-ID: <20061012155902.GX4945@poupinou.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> <35862.69.93.78.27.1160586077.squirrel@69.93.78.27> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <35862.69.93.78.27.1160586077.squirrel@69.93.78.27> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 16:01:13 -0000 On Wed, Oct 11, 2006 at 01:01:17PM -0400, john@utzweb.net wrote: > > John Utz wrote: > >> i've been working on i8k utils off and on for several months. > >> > >> (lately it's been what i've been doing whilst i sit at my daughter's > >> gymnastics class) > >> > >> so several of the api's work, ie turning the fans on and off, etc. > >> > >> buttons *still* dont work. :-( > >> > >> at this point, i want to start working on hXRing the kernel module. > >> > >> as currently coded, it writes to /proc. > >> > >> i would prefer to not have to require the proc lkm for this to work, i'd > >> rather do it the bsd way. > >> > >> so, umm, what *is* the bsd way ? :-) > > > > It looks like "i8k" is the Dell hotkeys/PM driver. > > yah, i forgot to mention that. sorry. > > > Use sysctl as the interface. > > hokydoky! > > > See the other drivers in /sys/dev/acpi_support for a good > > template (i.e., acpi_toshiba.c). > > i shall look again at that, tnx! > Well... Read carrefully: http://lists.freebsd.org/pipermail/freebsd-chat/2006-October/004315.html if you want your driver to be added to the tree.. Maybe you should consider to write a port, that's should resolve the legal issue. -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 16:02:26 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D45D16A47E for ; Thu, 12 Oct 2006 16:02:26 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 738F543E47 for ; Thu, 12 Oct 2006 16:01:05 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GY2z9-00020T-00; Thu, 12 Oct 2006 18:00:39 +0200 Date: Thu, 12 Oct 2006 18:00:39 +0200 To: Nate Lawson Message-ID: <20061012160039.GY4945@poupinou.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <452D161A.5040509@root.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: John Utz , freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 16:02:26 -0000 On Wed, Oct 11, 2006 at 09:04:42AM -0700, Nate Lawson wrote: > John Utz wrote: > >i've been working on i8k utils off and on for several months. > > > >(lately it's been what i've been doing whilst i sit at my daughter's > >gymnastics class) > > > >so several of the api's work, ie turning the fans on and off, etc. > > > >buttons *still* dont work. :-( > > > >at this point, i want to start working on hXRing the kernel module. > > > >as currently coded, it writes to /proc. > > > >i would prefer to not have to require the proc lkm for this to work, i'd > >rather do it the bsd way. > > > >so, umm, what *is* the bsd way ? :-) > > It looks like "i8k" is the Dell hotkeys/PM driver. Use sysctl as the > interface. See the other drivers in /sys/dev/acpi_support for a good > template (i.e., acpi_toshiba.c). > i8k is not an ACPI driver. I'm working on a acpi_dell one but I'm waiting a D620 (hint, hint :) -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 16:28:21 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B164016A4A0 for ; Thu, 12 Oct 2006 16:28:21 +0000 (UTC) (envelope-from john@utzweb.net) Received: from marley.grokthis.net (marley.grokthis.net [69.93.78.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 086F443D73 for ; Thu, 12 Oct 2006 16:28:06 +0000 (GMT) (envelope-from john@utzweb.net) Received: from [192.168.1.6] (c-71-197-214-178.hsd1.or.comcast.net [71.197.214.178]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by marley.grokthis.net (Postfix) with ESMTP id 74384F1019; Thu, 12 Oct 2006 12:28:04 -0400 (EDT) In-Reply-To: <20061012155902.GX4945@poupinou.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> <35862.69.93.78.27.1160586077.squirrel@69.93.78.27> <20061012155902.GX4945@poupinou.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <9C9E50D2-66A9-49AD-B0F8-1A242126DF4B@utzweb.net> Content-Transfer-Encoding: 7bit From: John Utz Date: Thu, 12 Oct 2006 09:27:58 -0700 To: Bruno Ducrot X-Mailer: Apple Mail (2.752.2) Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 16:28:21 -0000 On Oct 12, 2006, at 8:59 AM, Bruno Ducrot wrote: > On Wed, Oct 11, 2006 at 01:01:17PM -0400, john@utzweb.net wrote: >>> John Utz wrote: >>>> i've been working on i8k utils off and on for several months. >>>> >>>> (lately it's been what i've been doing whilst i sit at my >>>> daughter's >>>> gymnastics class) >>>> >>>> so several of the api's work, ie turning the fans on and off, etc. >>>> >>>> buttons *still* dont work. :-( >>>> >>>> at this point, i want to start working on hXRing the kernel module. >>>> >>>> as currently coded, it writes to /proc. >>>> >>>> i would prefer to not have to require the proc lkm for this to >>>> work, i'd >>>> rather do it the bsd way. >>>> >>>> so, umm, what *is* the bsd way ? :-) >>> >>> It looks like "i8k" is the Dell hotkeys/PM driver. >> >> yah, i forgot to mention that. sorry. >> >>> Use sysctl as the interface. >> >> hokydoky! >> >>> See the other drivers in /sys/dev/acpi_support for a good >>> template (i.e., acpi_toshiba.c). >> >> i shall look again at that, tnx! >> > > > Well... Read carrefully: > http://lists.freebsd.org/pipermail/freebsd-chat/2006-October/ > 004315.html > gyahh! > if you want your driver to be added to the tree.. > wow. this is a very interesting grey area, because i have made some very trivial formatting changes to said function. so were i to contribute the code, it would not violate the 'law' of gpl (because the code is textually different now) but i think it would violate the 'spirit' and that counts for just as much in my book. > Maybe you should consider to write a port, that's should resolve the > legal issue. that's an interesting idea. it might also be a reasonable exercise to genuinely rearchitect the asm and use a rewritten version; recall that 'study' is a blessed use of gpl code. but, let's be clear, the political issues are irrelevant until i have something that works in a meaningful way. right now all i can do is call a crappy little command line utility that requires me to know the adressess to poke into eax. :-) in any case, Bruno, i am *deeply* appreciative of you taking the time to point this out! > > -- > Bruno Ducrot > > -- Which is worse: ignorance or apathy? > -- Don't know. Don't care. > From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 16:43:29 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80A2016A407 for ; Thu, 12 Oct 2006 16:43:29 +0000 (UTC) (envelope-from John@utzweb.net) Received: from marley.grokthis.net (marley.grokthis.net [69.93.78.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79EDC43DE8 for ; Thu, 12 Oct 2006 16:42:12 +0000 (GMT) (envelope-from John@utzweb.net) Received: from [192.168.1.6] (c-71-197-214-178.hsd1.or.comcast.net [71.197.214.178]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by marley.grokthis.net (Postfix) with ESMTP id AD4D7F101A; Thu, 12 Oct 2006 12:41:40 -0400 (EDT) In-Reply-To: <20061012160039.GY4945@poupinou.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> <20061012160039.GY4945@poupinou.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <9CBF3A89-3007-4752-9981-DECDDFE1A749@utzweb.net> Content-Transfer-Encoding: 7bit From: John Utz Date: Thu, 12 Oct 2006 09:41:33 -0700 To: Bruno Ducrot X-Mailer: Apple Mail (2.752.2) Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 16:43:29 -0000 On Oct 12, 2006, at 9:00 AM, Bruno Ducrot wrote: > On Wed, Oct 11, 2006 at 09:04:42AM -0700, Nate Lawson wrote: >> John Utz wrote: >>> i've been working on i8k utils off and on for several months. >>> >>> (lately it's been what i've been doing whilst i sit at my daughter's >>> gymnastics class) >>> >>> so several of the api's work, ie turning the fans on and off, etc. >>> >>> buttons *still* dont work. :-( >>> >>> at this point, i want to start working on hXRing the kernel module. >>> >>> as currently coded, it writes to /proc. >>> >>> i would prefer to not have to require the proc lkm for this to >>> work, i'd >>> rather do it the bsd way. >>> >>> so, umm, what *is* the bsd way ? :-) >> >> It looks like "i8k" is the Dell hotkeys/PM driver. Use sysctl as the >> interface. See the other drivers in /sys/dev/acpi_support for a good >> template (i.e., acpi_toshiba.c). >> > > i8k is not an ACPI driver. I'm working on a acpi_dell one but I'm > waiting a D620 (hint, hint :) > yah, it's a combination of SMM and DMI, no acpi involved. so technically, i suppose i shouldn't discuss it on this list. however, this certainly seems like the best place to ask questions about this since it's seems like SMM+DMI is the neanderthal fork with ACPI being the cromagnon fork (which i guess make PnP austrolopithicus). > -- > Bruno Ducrot > > -- Which is worse: ignorance or apathy? > -- Don't know. Don't care. > From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 18:04:51 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE49916A4C8 for ; Thu, 12 Oct 2006 18:04:51 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D23543E9F for ; Thu, 12 Oct 2006 18:03:11 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GY4t4-0002FR-00; Thu, 12 Oct 2006 20:02:30 +0200 Date: Thu, 12 Oct 2006 20:02:30 +0200 To: John Utz Message-ID: <20061012180230.GA4945@poupinou.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> <20061012160039.GY4945@poupinou.org> <9CBF3A89-3007-4752-9981-DECDDFE1A749@utzweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9CBF3A89-3007-4752-9981-DECDDFE1A749@utzweb.net> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 18:04:52 -0000 On Thu, Oct 12, 2006 at 09:41:33AM -0700, John Utz wrote: > > On Oct 12, 2006, at 9:00 AM, Bruno Ducrot wrote: > > >On Wed, Oct 11, 2006 at 09:04:42AM -0700, Nate Lawson wrote: > >>John Utz wrote: > >>>i've been working on i8k utils off and on for several months. > >>> > >>>(lately it's been what i've been doing whilst i sit at my daughter's > >>>gymnastics class) > >>> > >>>so several of the api's work, ie turning the fans on and off, etc. > >>> > >>>buttons *still* dont work. :-( > >>> > >>>at this point, i want to start working on hXRing the kernel module. > >>> > >>>as currently coded, it writes to /proc. > >>> > >>>i would prefer to not have to require the proc lkm for this to > >>>work, i'd > >>>rather do it the bsd way. > >>> > >>>so, umm, what *is* the bsd way ? :-) > >> > >>It looks like "i8k" is the Dell hotkeys/PM driver. Use sysctl as the > >>interface. See the other drivers in /sys/dev/acpi_support for a good > >>template (i.e., acpi_toshiba.c). > >> > > > >i8k is not an ACPI driver. I'm working on a acpi_dell one but I'm > >waiting a D620 (hint, hint :) > > > > yah, it's a combination of SMM and DMI, no acpi involved. I misunderstood Nate. I thought he suggested to put your driver under /sys/dev/acpi_support. I was wrong, he only suggested you should look at for example acpi_toshiba in order to implement some sysctl hooks. Sorry for confusion. > so technically, i suppose i shouldn't discuss it on this list. Well, on the other hand we discuss stuff that don't belong to ACPI, as for example cpufreq.. I guess we can discuss stuff related to power management in general. > however, this certainly seems like the best place to ask questions > about this since it's seems like SMM+DMI is the neanderthal fork > with ACPI > being the cromagnon fork (which i guess make PnP austrolopithicus). ACPI still need to go SMM at least for telling the BIOS to switch to ACPI mode (instead of Legacy). It's a transitional phase I believe, but the transition takes a very long time. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 18:14:17 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B740A16A403 for ; Thu, 12 Oct 2006 18:14:17 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A34343DDF for ; Thu, 12 Oct 2006 18:13:18 +0000 (GMT) (envelope-from nate@root.org) Received: (qmail 21128 invoked from network); 12 Oct 2006 18:13:24 -0000 Received: from ppp-71-139-39-204.dsl.snfc21.pacbell.net (HELO ?10.0.5.50?) (nate-mail@71.139.39.204) by root.org with ESMTPA; 12 Oct 2006 18:13:24 -0000 Message-ID: <452E85AF.70106@root.org> Date: Thu, 12 Oct 2006 11:13:03 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Bruno Ducrot References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> <20061012160039.GY4945@poupinou.org> <9CBF3A89-3007-4752-9981-DECDDFE1A749@utzweb.net> <20061012180230.GA4945@poupinou.org> In-Reply-To: <20061012180230.GA4945@poupinou.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: John Utz , freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 18:14:17 -0000 Bruno Ducrot wrote: > On Thu, Oct 12, 2006 at 09:41:33AM -0700, John Utz wrote: >> so technically, i suppose i shouldn't discuss it on this list. > > Well, on the other hand we discuss stuff that don't belong to ACPI, > as for example cpufreq.. I guess we can discuss stuff related to > power management in general. Yep, I think this is the best list for power management discussions. >> however, this certainly seems like the best place to ask questions >> about this since it's seems like SMM+DMI is the neanderthal fork >> with ACPI >> being the cromagnon fork (which i guess make PnP austrolopithicus). > > ACPI still need to go SMM at least for telling the BIOS to switch to > ACPI mode (instead of Legacy). It's a transitional phase I > believe, but the transition takes a very long time. And actually, ACPI is just a standard wrapper around nonstandard SMM code. So instead of needing a driver for every BIOS version, you just have one API. In practice, the ACPI standard moves so slowly that you get acpi_toshiba, acpi_sony, acpi_dell, etc. for supporting features that don't yet have a standard API. With a little bit of work, I think all the features they support (backlight, hotkeys, etc.) do have a defined ACPI interface but for whatever reason they don't make that effort. -- Nate