Date: Mon, 9 Sep 2002 18:18:21 -1000 (HST) From: Vincent Poy <vince@oahu.WURLDLINK.NET> To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org> Cc: marks@ripe.net, <john@veidit.net>, <current@FreeBSD.ORG>, <acpi-jp@jp.FreeBSD.org> Subject: Re: ACPI support (was Re: apm support) Message-ID: <20020909175400.B2914-100000@oahu.WURLDLINK.NET> In-Reply-To: <20020910.113211.112630082.iwasaki@jp.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 10 Sep 2002, Mitsuru IWASAKI wrote: Hi Iwasaki-san: > [subject was changed] > > Hi, > > > WinXP, it was running under ACPI. However, with the GENERIC kernel, the > > fan doesn't seem to go on. Is there a way to disable the system from > > suspending when the lid is closed? or would adding device apm to the > > kernel and then enabling apmd and apm in rc.conf cause it to read the > > settings in the BIOS which I used the ThinkPad PS2 utility to configure > > instead? When I attempt to do a make buildworld, after about 5 minutes it > > would display the following message and then the system shuts off by > > itself shortly thereafter. > > > > Sep 9 11:01:32 exabyte kernel: acpi_tz0: WARNING - current temperature > > (97.8C) exceeds system limits > > It seems that your sysctl has wrong configuration and your kernel > maybe too old. I installed FreeBSD via ISO Image from current.FreeBSD.ORG using the original kernel that came from the installed system: FreeBSD 5.0-CURRENT-20020818-JPSNAP #0: Wed Sep 4 11:55:32 PDT 2002 Sep 4 15:04:43 bigbang kernel: vince@bigbang.DNALOGIC.NET:/usr/obj/usr/src/sys/ GENERIC I wasn't able to buildworld since the machine would shutdown due to overheating so I move the HDD to my Dell Inspiron 8200 to do the buildworld and the new kernel to the latest -current code for September 8, 2002. My /etc/sysctl.conf consists of the following which is identical to the source tree without adding anything. # $FreeBSD: src/etc/sysctl.conf,v 1.6 2001/09/26 19:35:04 dillon Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # > to disable sleep state transition by lid switch: > hw.acpi.lid_switch_state=NONE Thanks. That worked. The other problem is it seems like even when it did sleep and now, the LCD doesn't actually go off at all but just remains on when the switch is pushed even though the indicator panel went off, is there a way around this? > APM BIOS is completely disabled when acpi(4) is enabled. The acpi(4) > just emulates limited functions of APM by using acpi functions. Interesting. That was where I was confused. If apm is enabled in the kernel config and rc.conf, what would actually happen. > Cooling system control code had serious bugs, fixed at 8/27. > hw.acpi.thermal.tz0.active=-1 should be OK if you want auto-thermal > management. To force thermal zones activated: > hw.acpi.thermal.tz0.active=0 > hw.acpi.thermal.tz1.active=0 > [snip] > hw.acpi.thermal.tz5.active=0 > hw.acpi.thermal.tz6.active=0 Haven't tried it yet but this is what the September 8, 2002 -current build looks like: root@bigbang [8:58pm][/var/log] >> sysctl hw.acpi hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3240 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3647 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3702 hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz1.temperature: 3200 hw.acpi.thermal.tz1.active: -1 hw.acpi.thermal.tz1.thermal_flags: 0 hw.acpi.thermal.tz1._PSV: -1 hw.acpi.thermal.tz1._HOT: -1 hw.acpi.thermal.tz1._CRT: 3442 hw.acpi.thermal.tz1._ACx: 3402 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz2.temperature: 3150 hw.acpi.thermal.tz2.active: -1 hw.acpi.thermal.tz2.thermal_flags: 0 hw.acpi.thermal.tz2._PSV: -1 hw.acpi.thermal.tz2._HOT: -1 hw.acpi.thermal.tz2._CRT: 3372 hw.acpi.thermal.tz2._ACx: 3242 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz3.temperature: 3000 hw.acpi.thermal.tz3.active: -1 hw.acpi.thermal.tz3.thermal_flags: 0 hw.acpi.thermal.tz3._PSV: -1 hw.acpi.thermal.tz3._HOT: -1 hw.acpi.thermal.tz3._CRT: 3322 hw.acpi.thermal.tz3._ACx: 3272 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz4.temperature: 3080 hw.acpi.thermal.tz4.active: -1 hw.acpi.thermal.tz4.thermal_flags: 0 hw.acpi.thermal.tz4._PSV: -1 hw.acpi.thermal.tz4._HOT: -1 hw.acpi.thermal.tz4._CRT: 3392 hw.acpi.thermal.tz4._ACx: 3092 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz5.temperature: 3030 hw.acpi.thermal.tz5.active: -1 hw.acpi.thermal.tz5.thermal_flags: 0 hw.acpi.thermal.tz5._PSV: -1 hw.acpi.thermal.tz5._HOT: -1 hw.acpi.thermal.tz5._CRT: 3432 hw.acpi.thermal.tz5._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz6.temperature: 3000 hw.acpi.thermal.tz6.active: -1 hw.acpi.thermal.tz6.thermal_flags: 0 hw.acpi.thermal.tz6._PSV: -1 hw.acpi.thermal.tz6._HOT: -1 hw.acpi.thermal.tz6._CRT: 3432 hw.acpi.thermal.tz6._ACx: 3392 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 99 hw.acpi.battery.time: -1 hw.acpi.battery.state: 2 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 > Note that hw.acpi.thermal.tz0.active=1 is worng because it is not > bool value, and I actually got the idea for that one when you and Michael Wu were discussion about the IBM s31 issue back on July 30, 2002 where you wrote: [snip] > hw.acpi.thermal.tz0.temperature: 3442 > hw.acpi.thermal.tz0.active: 0 > hw.acpi.thermal.tz0.thermal_flags: 0 > hw.acpi.thermal.tz0._PSV: 3681 > hw.acpi.thermal.tz0._HOT: -1 > hw.acpi.thermal.tz0._CRT: 3732 > hw.acpi.thermal.tz0._ACx: 3332 3352 -1 -1 -1 -1 -1 -1 -1 -1 s31 has AC0 and AC1 level cooling. Please try; # sysctl hw.acpi.thermal.tz0.active=1 to activate AC1 level cooling by manual. but automatically switching to AC1 is not functioning. I think this is bug, I'll check later on. The actual message can be found here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=54879+0+archive/2002/freebsd-mobile/20020804.freebsd-mobile > > hw.acpi.thermal.tz0._ACx: 3632 -1 -1 -1 -1 -1 -1 -1 -1 -1 > there is no _AC1. There is only _AC0, so 0 must be specified to > hw.acpi.thermal.tz0.active to force tz0 activated. Oh okay, I think I'll leave it at -1 as long as the auto thermal management works instead of shutting down the machine :-) > ACPI for FreeBSD is still under development, the best way to obtain > the most accurate info. is check /sys/dev/acpica/*.[ch] files for now :-) > Documents at http://acpi.info/spec.htm would be helpful too. > > Of course, volunteers for development and documentation always are welcome. > > Thanks Thanks for your input. I'm still trying to figure out why I couldn't get my 3Com 3CXFEM656C Combo 10/100 Fast Ethernet + 56k Modem Cardbus card working on the IBM ThinkPad 770Z since it keeps saying xl0: watchdog timeout while the card works fine on the Dell Inspiron 8200 when I tried it. The only cards I successfully got working is the Siemens/Efficient Networks SpeedStream SS1012 and a SMC Networks SMC8036TX which both seem to be physically identical cards that runs on the dc0 driver. The NetGear FA511 and the LinkSys PCMPC200 Cardbus NICs both don't work at all. Is there a database somewhere of which models of Cardbus NIC cards actually work with -current? Since one of my friends has various Xircom's and other Cardbus cards but he has to ship one to me and it would be easier to just tell him which one I want before he sends it. Thanks. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020909175400.B2914-100000>