From owner-freebsd-acpi@FreeBSD.ORG Fri Jul 11 21:26:28 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 508CBEBA for ; Fri, 11 Jul 2014 21:26:28 +0000 (UTC) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (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 13999289C for ; Fri, 11 Jul 2014 21:26:28 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id wp18so1852482obc.34 for ; Fri, 11 Jul 2014 14:26:27 -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=kNdczDCxCwlWQLemxgERxb/FrqmyATHNjGGlmcwvQPE=; b=gPdPTgb+4GK8URi2e31Rf7pDO2VWG/Byyvs1XpsUueVxjBrKOeBJfcLhqG6K2nQW75 AKBF4zADHbbPb4Dr+D6WHuN0Jn8Yqj3UPMbb2I/PW+HdBCFCRqNWF8NjGehKCAst08Hh oziln8OF+cBkMYbsGYYXVu04Qeka1DOX9AzBlfB9WXviajcqtddIJikpQcUrCvIm+6Bu R3Q5cZncn19sA7RFBX1bGQZp0ZjL4OquyOuQDgw4ncc4z9bUVaoESM2lRKD2T0d9aPDy p99zDSA9vvRTiHmcNgBrkdWQbyu38a5F99ytqWmeP9iwT4WxKETGiNZRJnfOrdrYrXb+ PewQ== MIME-Version: 1.0 X-Received: by 10.60.52.226 with SMTP id w2mr2000883oeo.3.1405113987326; Fri, 11 Jul 2014 14:26:27 -0700 (PDT) Received: by 10.182.29.9 with HTTP; Fri, 11 Jul 2014 14:26:27 -0700 (PDT) In-Reply-To: References: <53BF0546.70505@att.net> <53BFCBF4.2090104@att.net> <53C020CE.8010205@att.net> <53C02604.9070207@att.net> Date: Fri, 11 Jul 2014 23:26:27 +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 21:26:28 -0000 Hi Anthony, here it is: $FreeBSD: release/10.0.0/Makefile 255784 2013-09-22 07:30:17Z andrew $ I will try to check how it is possible to update the code base. Cheers, Daniele. 2014-07-11 20:03 GMT+02:00 Daniele Mazzotti : > Hi Anthony, > > Thanks for the good hint. I will be searching for the revision info as > soon as I will be back home (3 hours from now more or less). > > Cheers, > Daniele. > Il 11/lug/2014 19:59 "Anthony Jenkins" ha > scritto: > > Errrr... good question :-) I got mine from Subversion, so in '/usr/src' I >> can run 'svn info' and see the revision. >> >> Your revision might be at the top of /usr/src/Makefile - it is in mine: >> >> # >> # $FreeBSD: head/Makefile 268191 2014-07-02 22:34:06Z marcel $ >> # >> >> I'm only wondering because it might be a bad copy. Might try getting the >> sources again. >> >> Thanks, >> Anthony >> >> On 07/11/2014 13:44, Daniele Mazzotti wrote: >> > Actually I think I downloaded the source code back in May when I updated >> > from RC3 to the current version. >> > >> > How can I check the code revision on my machine? >> > >> > Cheers, >> > Daniele. >> > Il 11/lug/2014 19:37 "Anthony Jenkins" ha >> > scritto: >> > >> >> I just tried a build of GENERIC + 'options ACPI_DEBUG' and it seems to >> get >> >> past the error you're seeing. What revision of the source code are you >> >> using... or where'd you get it from? >> >> >> >> Anthony >> >> >> >> On 07/11/2014 13:12, Daniele Mazzotti wrote: >> >>> Hi guys, >> >>> >> >>> everything as planned! I am getting a compiling error :-). >> >>> >> >>> This is the way i managed to update the GENERIC kernel >> >>> >> >>> # Bus support. >> >>> device acpi >> >>> options ACPI_DEBUG # Debug support for ACPI >> >>> device pci >> >>> >> >>> and this is the result of >> >>> >> >>> # *make buildkernel KERNCONF=MYKERNEL* >> >>> >> >>> >> >>> ===> crypto (depend) >> >>> @ -> /usr/src/sys >> >>> awk -f @/tools/makeobjops.awk @/opencrypto/cryptodev_if.m -c >> >>> >> >>> make[4]: stopped in /usr/src/sys/modules/crypto >> >>> *** Error code 2 >> >>> >> >>> Stop. >> >>> make[3]: stopped in /usr/src/sys/modules >> >>> *** Error code 1 >> >>> >> >>> Stop. >> >>> make[2]: stopped in /usr/obj/usr/src/sys/GENERIC >> >>> *** Error code 1 >> >>> >> >>> Stop. >> >>> make[1]: stopped in /usr/src >> >>> *** Error code 1 >> >>> >> >>> Stop. >> >>> make: stopped in /usr/src >> >>> >> >>> I googled a bit, but I could not find any valuable help and actually >> I do >> >>> not know what could be wrong as the custom kernel is essentially the >> >>> GENERIC with just one line added. >> >>> Have you ever experienced such a problem? >> >>> >> >>> Cheers, >> >>> Daniele. >> >>> >> >>> >> >>> >> >>> 2014-07-11 18:10 GMT+02:00 Daniele Mazzotti : >> >>> >> >>>> Hi guys, >> >>>> >> >>>> thanks again for the support. >> >>>> >> >>>> @Takanori: here you go http://pastebin.com/F0a2mZP4 >> >>>> @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 < >> Anthony.B.Jenkins@att.net>: >> >>>> >> >>>> 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: > >> GPE >> >>>>>> 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: > >> Timer> >> >>>>>> 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: > >> GPE >> >>>>>> 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: > >> Timer> >> >>>>>> 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 < >> Anthony.B.Jenkins@att.net >> >>> : >> >>>>>>> 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" >> >>> >> >> >> > _______________________________________________ >> > 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" >> > >> >>