Date: Fri, 11 Jul 2014 19:12:23 +0200 From: Daniele Mazzotti <kappei84@gmail.com> To: Anthony Jenkins <Anthony.B.Jenkins@att.net>, takawata@init-main.com Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E Message-ID: <CAC=ypSV36Dk_3a30OeCxmowqnM5iqcJkM%2B4qKgsOTNTEzmztSQ@mail.gmail.com> In-Reply-To: <CAC=ypSULmXU2HBpG2gf2J=9_o-sLccECud%2Be9KUg6-ppz7phww@mail.gmail.com> References: <CAC=ypSVopgcL82FpqJosmgFeRkeeevP0RG-GrAEZD2YQyi%2BPrg@mail.gmail.com> <53BF0546.70505@att.net> <CAC=ypSUe0_09pTMFsMKw4u3J=Kb8Q_uV0g6%2Bk_f2p1so3mnTgA@mail.gmail.com> <53BFCBF4.2090104@att.net> <CAC=ypSULmXU2HBpG2gf2J=9_o-sLccECud%2Be9KUg6-ppz7phww@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <kappei84@gmail.com>: > 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: <Sony> on motherboard >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_ec0: <Embedded Controller: GPE >> > 0x17, ECDT> port 0x62,0x66 on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: cpu0: <ACPI CPU> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: cpu1: <ACPI CPU> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: cpu2: <ACPI CPU> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: cpu3: <ACPI CPU> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: hpet0: <High Precision Event Timer> >> > iomem 0xfed00000-0xfed003ff on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: atrtc0: <AT realtime clock> port >> > 0x70-0x77 irq 8 on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: attimer0: <AT timer> 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: <ACPI Host-PCI bridge> port >> > 0xcf8-0xcff on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: battery0: <ACPI Control Method >> Battery> >> > on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_acad0: <AC Adapter> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_lid0: <Control Method Lid >> Switch> >> > on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_button0: <Power Button> on >> acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_tz0: <Thermal Zone> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_tz1: <Thermal Zone> on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: atkbdc0: <Keyboard controller >> (i8042)> >> > port 0x60,0x64 irq 1 on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_sony0: <Sony notebook >> controller> >> > on acpi0 >> > Jul 11 07:30:47 Von-Neumann kernel: acpi_sony0: PID 0 >> > Jul 11 07:37:54 Von-Neumann kernel: acpi0: <Sony> on motherboard >> > Jul 11 07:37:54 Von-Neumann kernel: acpi_ec0: <Embedded Controller: GPE >> > 0x17, ECDT> port 0x62,0x66 on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: cpu0: <ACPI CPU> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: cpu1: <ACPI CPU> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: cpu2: <ACPI CPU> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: cpu3: <ACPI CPU> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: hpet0: <High Precision Event Timer> >> > iomem 0xfed00000-0xfed003ff on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: atrtc0: <AT realtime clock> port >> > 0x70-0x77 irq 8 on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: attimer0: <AT timer> 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: <ACPI Host-PCI bridge> port >> > 0xcf8-0xcff on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: battery0: <ACPI Control Method >> Battery> >> > on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: acpi_acad0: <AC Adapter> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: acpi_lid0: <Control Method Lid >> Switch> >> > on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: acpi_button0: <Power Button> on >> acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: acpi_tz0: <Thermal Zone> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: acpi_tz1: <Thermal Zone> on acpi0 >> > Jul 11 07:37:54 Von-Neumann kernel: atkbdc0: <Keyboard controller >> (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" >> > >> >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC=ypSV36Dk_3a30OeCxmowqnM5iqcJkM%2B4qKgsOTNTEzmztSQ>