1) it has never worked before in linux, however it has worked in windows. i don't know what acpi is, so could you please explain the difference between that and apm and let me know how to tell which one i have? 3) it is not a module, and is actually compiled into the kernel. # dmesg|grep -i apm apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) my output is identical to yours except that it does not have the options line 4) the following are the most useful results (excluding /var/log/messages) from # grep -i apm /var/log/* XFree86.0.log:(II) Open APM successful boot.log:Dec 4 15:44:18 mte-lap apmd: apmd startup failed boot.log:Dec 4 17:23:03 mte-lap apmd: apmd shutdown failed dmesg:apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) ksyms.0:c036fb40 apm_info_R50db8be5 ksyms.0:c0370714 apm_battery_hook_Rd8e8130c ksyms.0:c02fed40 apm_battery_hook_sem_R0a67dd77 rpmpkgs:apmd-3.0.2-12.i386.rpm
When I ran 'service apmd start', the following lines were added to /var/log/dmesg: Dec 4 17:24:31 mte-lap kernel: general protection fault: e9d4 Dec 4 17:24:31 mte-lap kernel: sr_mod i810_audio ac97_codec soundcore radeon agpgart autofs ds yenta_socket pcmcia_core 8139too mii iptable_filter ip_tables ide-scsi scsi_mod ide-cd cdrom o Dec 4 17:24:31 mte-lap kernel: CPU:   0 Dec 4 17:24:31 mte-lap kernel: EIP:   0050:[<00003613>]   Not tainted Dec 4 17:24:31 mte-lap kernel: EFLAGS: 00010046 Dec 4 17:24:31 mte-lap kernel: Dec 4 17:24:31 mte-lap kernel: EIP is at Using_Versions [] 0x3612 (2.4.18-18.8.0) Dec 4 17:24:31 mte-lap kernel: eax: 00000282  ebx: 00000001  ecx: 00000000  edx: 00000000 Dec 4 17:24:31 mte-lap kernel: esi: c0267e65  edi: 00000014  ebp: d089be74  esp: d089be6c Dec 4 17:24:31 mte-lap kernel: ds: 0058  es: 0000  ss: 0018 Dec 4 17:24:31 mte-lap kernel: Process apmd (pid: 1808, stackpage=d089b000) Dec 4 17:24:31 mte-lap kernel: Stack: 55bf5444 0000be74 00000058 7e650282 be880050 00000001 530a0000 00000016 Dec 4 17:24:31 mte-lap kernel:       0048560f 00000000 d089befc c0114b8c 00000010 d089befc 00000282 cfa70018 Dec 4 17:24:31 mte-lap kernel:       00000018 c0120000 cfa70000 d089bf46 c0267e65 d1c58000 00001000 c0115085 Dec 4 17:24:31 mte-lap kernel: Call Trace: [<c0114b8c>] apm_bios_call [kernel] 0x4c (0xd089be98)) Dec 4 17:24:31 mte-lap kernel: [<c0120000>] request_resource [kernel] 0x0 (0xd089beb0)) Dec 4 17:24:31 mte-lap kernel: [<c0115085>] apm_get_power_status [kernel] 0x65 (0xd089bec8)) Dec 4 17:24:31 mte-lap kernel: [<c0147d32>] cp_new_stat64 [kernel] 0xb2 (0xd089bef8)) Dec 4 17:24:31 mte-lap kernel: [<c0115dab>] apm_get_info [kernel] 0x4b (0xd089bf04)) Dec 4 17:24:31 mte-lap apmd: apmd startup failed Dec 4 17:24:31 mte-lap kernel: [<c0137e1d>] __alloc_pages [kernel] 0x8d (0xd089bf1c)) Dec 4 17:24:31 mte-lap kernel: [<c012cbf6>] __vma_link [kernel] 0x56 (0xd089bf30)) Dec 4 17:24:31 mte-lap kernel: [<c01622dc>] proc_file_read [kernel] 0x1cc (0xd089bf54)) Dec 4 17:24:31 mte-lap kernel: [<c013fe93>] sys_read [kernel] 0xa3 (0xd089bf94)) Dec 4 17:24:31 mte-lap kernel: [<c0109127>] system_call [kernel] 0x33 (0xd089bfc0)) Dec 4 17:24:31 mte-lap kernel: Dec 4 17:24:31 mte-lap kernel: Dec 4 17:24:31 mte-lap kernel: Code: Bad EIP value. On Wed, 2002-12-04 at 16:31, Scott Harney wrote: > > Many questions: > 1) did it ever work before? If not are you certain your laptop > model uses APM and not the newer (and incomplete in the Linux > kernel) ACPI for these functions > 2) if it did work, have you done any upgrades recently? > particularly kernel and kernel modules > 3) is APM compiled in the kernel you're running or built in as a module > use "/usr/sbin/lsmod | grep apm" to see if there's an apm module > present. Try (as root) "modprobe -v apm" to manually attempt to load the > module if it's not there. Of course it might be in the kernel itself > use "dmesg | grep apm" to help determine that. My output looks > like this: > > [EMAIL PROTECTED] scotth # dmesg | grep apm > apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) > options: [pci] [cardbus] [apm] > > 4) Logs are your friend. check for apm messages in /var/log/syslog, > /var/log/messages, and possibly /var/log/kern.log. Redhat's logging may > be more extensive than that so you may have to dig around in /var/log > use "grep -i apm /var/log/* | less" to find potential entries. every time > you have attempted to manually start apmd may have generated > some more informative logging information that "[FAILED]" > > On Wednesday 04 December 2002 03:52 pm, [EMAIL PROTECTED] wrote: > > I have an HP Pavilion zt1260 running RedHat 8.0 with kernel-2.4.18-18.8.0 > > and apmd-3.0.2-12. Whenever APM attempts to start, it fails. I cannot > > find much information about the problem, but here is what I do have: > > > > # service apmd start > > Starting up APM daemon: [FAILED] > > > > # /etc/rc.d/init.d/apmd start > > Starting up APM daemon: [FAILED] > > > > # apmd > > Segmentation fault > > > > # cat /proc/apm > > Segmentation fault > > > > # apm > > Segmentation fault > > > > # apm --suspend > > Segmentation fault > > > > # apm --standby > > Segmentation fault > > > > If anyone could help me in any way with this problem, I would appreciate > > it. Thanks > > > > Matt Eastman > > > > _______________________________________________ > > General mailing list > > [email protected] > > http://oxygen.nocdirect.com/mailman/listinfo/general_brlug.net > > -- > Scott Harney <[EMAIL PROTECTED]> > The only thing I need to know about NT is "fdisk" > > _______________________________________________ > General mailing list > [email protected] > http://oxygen.nocdirect.com/mailman/listinfo/general_brlug.net
