From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 11 17:37:12 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 882E88F7 for ; Fri, 11 Jul 2014 17:37:12 +0000 (UTC) Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4C976231B for ; Fri, 11 Jul 2014 17:37:12 +0000 (UTC) Received: by mail-ob0-f171.google.com with SMTP id wm4so1506348obc.30 for ; Fri, 11 Jul 2014 10:37:10 -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=5i5m8j6K9AiTRqCDzcHWWm+BuvP7suoIxgNIu+Yt2fo=; b=r3xldKyTl9QKNIYlsJR9t95ALbNRzPsWk8G102Z7dElr5f7y9SKCZ8OQ/dfdMWmJmn 5E5OFGgBNIPJ5FBqWk83QqnZzkwyIMnxRKXD8K1aAHnKlAvNfR2ngG8f8e7VRk82CEX0 CRifkXyKqlc4Q+A3rNmwFEsld2DuQDCd+yOp+ufdq87knR9NHMyHB/iTTwUW+GnxcQyn CmQPHDbDLdLkSxPp4rHh2m7oaRs88kdMj/p34Bgp/gTUf+Km7lxZFRgk8galRBoq1AnJ FHY7iGWhpCM/LMublOcR/oifLbYfkpY6Ru+2+79Rrqktq1OTsy+pKfIqyrT3Zn38P224 pFcg== MIME-Version: 1.0 X-Received: by 10.60.45.130 with SMTP id n2mr597929oem.12.1405100229406; Fri, 11 Jul 2014 10:37:09 -0700 (PDT) Received: by 10.182.29.9 with HTTP; Fri, 11 Jul 2014 10:37:09 -0700 (PDT) In-Reply-To: <53C01BB6.8080109@att.net> References: <53BF0546.70505@att.net> <53BFCBF4.2090104@att.net> <53C01BB6.8080109@att.net> Date: Fri, 11 Jul 2014 19:37:09 +0200 Message-ID: Subject: Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E From: Daniele Mazzotti To: Anthony Jenkins Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: freebsd-acpi@freebsd.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2014 17:37:12 -0000 Yep. Basically the prerequisites for compiling are ok and the procedure I followed should be correct as well. I am still getting the error when try to compile the module/crypto and I do not know why. I think I am going to write an email to the "general questions" mailing list as suggested in the handbook. Cheers, Daniele. 2014-07-11 19:15 GMT+02:00 Anthony Jenkins : > Takawata might be able to help you better than me; I'm trying to learn > this ACPI stuff myself (trying to add support for ACPI CMOS regions and fix > my own laptop's flakiness). > > If you're just running a generic kernel, I'm pretty sure all you have to > do is: > > 1. Ensure you have the system sources installed at /usr/src. > 2. Copy /usr/src/sys/$(uname -m)/conf/GENERIC to /usr/src/sys/$(uname > -m)/conf/MYKERNEL. * > 3. Edit /usr/src/sys/$(uname -m)/conf/MYKERNEL to add the 'options > ACPI_DEBUG' line. > 4. 'cd' to /usr/src. > 5. Run 'make kernel KERNCONF=MYKERNEL'. > 6. Reboot. > > * 'uname -m' prints your system architecture (e.g. 'amd64' or 'i386'); you > could simply substitute the architecture string in the paths above. > > Anthony > > > On 07/11/2014 12:10, Daniele Mazzotti wrote: > > Hi guys, > > > > thanks again for the support. > > > > @Anthony: I will try to include the options in a custom kernel and > compile > > it. As this is the first time after years I am compiling a custom kernel > it > > will take a few time I guess. > > > > Just let me know if the output of the acpidump is of any help to you. > > Cheers, > > Daniele. > > > > > > 2014-07-11 13:35 GMT+02:00 Anthony Jenkins : > > > >> Hi Daniele, > >> > >> I was just going from acpi(4) man page; you'll likely have to build a > new > >> kernel with 'options ACPI_DEBUG' added to your kernel config file, as I > >> don't know if it's even possible to turn on the logging I want at > runtime. > >> > >> [ajenkins@ajenkins-hplaptop /usr/home/ajenkins]$ grep -i acpi > >> /usr/src/sys/amd64/conf/MYKERNEL > >> device acpi > >> options ACPI_DEBUG > >> > >> I also have an 'options ACPI_DMAR' , but I don't recognize that and you > >> don't need that to debug your battery. > >> > >> Anthony > >> > >> On 07/11/2014 01:58, Daniele Mazzotti wrote: > >>> Hello Anthony, > >>> > >>> thanks for the quick reply! I tried what you suggested. > >>> > >>> loader.conf: > >>> > >>> # Module for Windows Partition & Linux Mount > >>> fuse_load="YES" > >>> autoboot_delay="5" > >>> #acpi_sony_load="YES" > >>> > >>> # Debugging Symbols for ACPI > >>> debug.acpi.layer="ACPI_BATTERY" > >>> debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" > >>> debug.acpi.enable_debug_objects="1" > >>> > >>> sysctl hw.acpi.battery: > >>> > >>> hw.acpi.battery.life: -1 > >>> hw.acpi.battery.time: -1 > >>> hw.acpi.battery.state: 7 > >>> hw.acpi.battery.units: 1 > >>> hw.acpi.battery.info_expire: 5 > >>> > >>> log/messages: > >>> > >>> cat /var/log/messages | grep acpi > >>> > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi0: on motherboard > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_ec0: >>> 0x17, ECDT> port 0x62,0x66 on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: cpu0: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: cpu1: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: cpu2: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: cpu3: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: hpet0: > >>> iomem 0xfed00000-0xfed003ff on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: atrtc0: port > >>> 0x70-0x77 irq 8 on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: attimer0: port > >>> 0x40-0x43,0x50-0x53 irq 0 on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_timer0: <24-bit timer at > >>> 3.579545MHz> port 0x408-0x40b on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: pcib0: port > >>> 0xcf8-0xcff on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: battery0: >> Battery> > >>> on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_acad0: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_lid0: >> Switch> > >>> on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_button0: on > acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_tz0: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_tz1: on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: atkbdc0: >> (i8042)> > >>> port 0x60,0x64 irq 1 on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_sony0: >> controller> > >>> on acpi0 > >>> Jul 11 07:30:47 Von-Neumann kernel: acpi_sony0: PID 0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi0: on motherboard > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_ec0: >>> 0x17, ECDT> port 0x62,0x66 on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: cpu0: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: cpu1: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: cpu2: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: cpu3: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: hpet0: > >>> iomem 0xfed00000-0xfed003ff on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: atrtc0: port > >>> 0x70-0x77 irq 8 on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: attimer0: port > >>> 0x40-0x43,0x50-0x53 irq 0 on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_timer0: <24-bit timer at > >>> 3.579545MHz> port 0x408-0x40b on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: pcib0: port > >>> 0xcf8-0xcff on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: battery0: >> Battery> > >>> on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_acad0: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_lid0: >> Switch> > >>> on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_button0: on > acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_tz0: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: acpi_tz1: on acpi0 > >>> Jul 11 07:37:54 Von-Neumann kernel: atkbdc0: >> (i8042)> > >>> port 0x60,0x64 irq 1 on acpi0 > >>> > >>> It seems to me the verbose debugging is either not enabled (perhaps I > >> made > >>> some mistakes with the loader.conf) or the debug is really enabled but > >>> there is no special output on the wrong log file. Actually I am a bit > >>> puzzled as I am not a real expert "admin". I only enjoy getting my > hands > >> on > >>> Unix on my desktop PC just for fun. > >>> > >>> However, do you think either I missed something or made anything wrong? > >>> I look forward to receiving from you. > >>> > >>> Cheers, > >>> Daniele. > >>> > >>> > >>> > >>> 2014-07-10 23:27 GMT+02:00 Anthony Jenkins >: > >>> > >>>> On 07/10/2014 16:49, Daniele Mazzotti wrote: > >>>>> Hello there, > >>>>> > >>>>> it is been a while since I finished installing Freebsd 10 on my Sony > >> Vaio > >>>>> PC and resolving (or at least I am trying to) one by one, all the > >>>> problems > >>>>> this hardware is giving me. Actually I cannot find a solution to > >>>> correctly > >>>>> display the battery level on my laptop. If I unplug my PC from the > >> power > >>>>> and type 'sysctl hw.acpi.battery' this is the result I get: > >>>>> > >>>>> hw.acpi.battery.life: -1 > >>>>> hw.acpi.battery.time: -1 > >>>>> hw.acpi.battery.state: 7 > >>>>> hw.acpi.battery.units: 1 > >>>>> hw.acpi.battery.info_expire: 5 > >>>>> > >>>>> Moreover the suspend mode is giving me some problems as well, but > this > >>>> has > >>>>> definitely a lower priority. > >>>>> > >>>>> I either tried to search for a solution on the FreeBSD Handook with > no > >>>>> luck, and google the problem a little bit, but I could not find any > >>>>> valuable help. I would be really interested to investigate the > problem > >>>>> further. Is there anyone who can help me out with this and tell me > what > >>>>> pieces of information are needed to better understand the problem? > >>>> Try enabling the ACPI_BATTERY layer and ACPI_LV_ALL_EXCEPTIONS level > in > >>>> /boot/loader.conf: > >>>> > >>>> debug.acpi.layer="ACPI_BATTERY" > >>>> debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" > >>>> debug.acpi.enable_debug_objects="1" # I assume this is how > >> you > >>>> turn on ACPI debugging without recompiling the kernel with 'options > >>>> ACPI_DEBUG' > >>>> > >>>> and running 'sysctl hw.acpi.battery' again. Post /var/log/messages > ACPI > >>>> messages about battery here. > >>>> > >>>> Anthony > >>>> > >>>>> Cheers, > >>>>> Daniele. > >>>>> _______________________________________________ > >>>>> 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 > >> " > >>> _______________________________________________ > >>> 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 > " > >>> > >> > > _______________________________________________ > > 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" > > > >