Re: apm support
Mark Santcroos wrote: On Sat, Sep 07, 2002 at 07:29:10PM +0200, John Angelmo wrote: I'm trying to get some apm support on my laptop. I have device apm in my kernelconf and apm_enable=YES in rc.conf but when I run apm I get: [ ... ] what could I be missing? That's a good question! What gives you the idea something is wrong here? I will guess, which may save some turnaround time for the messages, that it's these specific line items: Battery status: unknown Remaining battery time: unknown Battery 0: Battery status: unknown Remaining battery time: 0:00:00 APM Capabilities: unknown -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: apm support
Battery status: unknown Remaining battery time: unknown Battery 0: Battery status: unknown Remaining battery time: 0:00:00 APM Capabilities: unknown What does: 'sysctl -a hw.acpi' show? And what does the 'apm' command show when you unplug your AC? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: apm support
On Mon, 9 Sep 2002 10:56:07 +0200 Mark Santcroos [EMAIL PROTECTED] wrote: Battery status: unknown Remaining battery time: unknown Battery 0: Battery status: unknown Remaining battery time: 0:00:00 APM Capabilities: unknown What does: 'sysctl -a hw.acpi' show? sysctl -a 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.acline: 1 hw.acpi.battery.life: 98 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 And what does the 'apm' command show when you unplug your AC? Plugged out and then plugged in right after that: -bash-2.05b$ apm APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: charging Remaining battery life: invalid value (0x) Remaining battery time: unknown Number of batteries: 1 Battery 0: Battery status: not present APM Capabilities: unknown -bash-2.05b$ apm APM version: 1.2 APM Managment: Enabled AC Line status: on-line Battery status: high Remaining battery life: 92% Remaining battery time: 3:03:00 Number of batteries: 1 Battery 0: Battery status: high Remaining battery life: 92% Remaining battery time: 3:03:00 APM Capabilities: unknown -bash-2.05b$ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: apm support
On Mon, Sep 09, 2002 at 11:15:43AM +0200, John Angelmo wrote: Battery status: unknown Remaining battery time: unknown Battery 0: Battery status: unknown Remaining battery time: 0:00:00 These were all zero because you were plugged in, as you showed the values were showed when you were unplugged. APM Capabilities: unknown This is explained by the fact that you run ACPI. Afaik it's either ACPI or APM that your laptop has. Yours has ACPI. The reason that you can still use the 'apm' command is that the ACPI driver 'emulates' the behaviour of /dev/apm, but the information is not actually coming from apm. (Can you remove device apm from your kernel to ack this?) What laptop do you have btw? And how is the suspending/resuming working? Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: apm support
Mark Santcroos wrote: On Mon, Sep 09, 2002 at 11:15:43AM +0200, John Angelmo wrote: Battery status: unknown Remaining battery time: unknown Battery 0: Battery status: unknown Remaining battery time: 0:00:00 These were all zero because you were plugged in, as you showed the values were showed when you were unplugged. APM Capabilities: unknown This is explained by the fact that you run ACPI. Afaik it's either ACPI or APM that your laptop has. Yours has ACPI. The reason that you can still use the 'apm' command is that the ACPI driver 'emulates' the behaviour of /dev/apm, but the information is not actually coming from apm. (Can you remove device apm from your kernel to ack this?) What laptop do you have btw? http://www.fujitsu-siemens.com/rl/products/notebooks/professional/lifebook/lifebookc/lifebookc.html But with an older Celeron 800Mhz And how is the suspending/resuming working? Great in Windows, not at all in FreeBSD, well the screen goes blank but not black, (no power off to the screen) after 15 minutes. /John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: apm support
On Mon, 9 Sep 2002, Mark Santcroos wrote: On Mon, Sep 09, 2002 at 11:15:43AM +0200, John Angelmo wrote: Battery status: unknown Remaining battery time: unknown Battery 0: Battery status: unknown Remaining battery time: 0:00:00 These were all zero because you were plugged in, as you showed the values were showed when you were unplugged. APM Capabilities: unknown This is explained by the fact that you run ACPI. Afaik it's either ACPI or APM that your laptop has. Yours has ACPI. Got a question about this... I have a IBM ThinkPad 770Z and I think it's APM when it was running the pre-load Win98 but with WinME and 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 This is what my sysctl hw.acpi output looks like. Originally, all the hw.acpi.thermal.tz*.active were -1 so I changed it to 1 but it still didn't turn the fans on. root@bigbang [6:27pm][~] 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.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: 3180 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: 3130 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: 3090 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: 3050 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: 3037 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.thermal.tz5.temperature: 3060 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: 49 hw.acpi.battery.time: -1 hw.acpi.battery.state: 4 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 The reason that you can still use the 'apm' command is that the ACPI driver 'emulates' the behaviour of /dev/apm, but the information is not actually coming from apm. (Can you remove device apm from your kernel to ack this?) What laptop do you have btw? And how is the suspending/resuming working? Mark Cheers, Vince - [EMAIL PROTECTED] - 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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ACPI support (was Re: apm support)
[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. to disable sleep state transition by lid switch: hw.acpi.lid_switch_state=NONE APM BIOS is completely disabled when acpi(4) is enabled. The acpi(4) just emulates limited functions of APM by using acpi functions. 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 Note that hw.acpi.thermal.tz0.active=1 is worng because it is not bool value, and 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. 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ACPI support (was Re: apm support)
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: [EMAIL PROTECTED]:/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
