removed apmd but it still seems to be there
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am using acpi in place of apm because it allows me to press the power button to shutdown the computer. I can easily accidentally press the power button, so it is good to have it go through the shutdown sequence or even do nothing instead of powering down without performing the shutdown actions, which could possibly corrupt my filesystem. Well, here's the deal. I turned acpi on in the boot loader and removed apmd, but the system is still trying to use apm. I tried removing powermgmt-base, but doing so would remove the entire gnome system. What can I do to fix this problem? PRINCE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAZvWGAl2SNUPt1I8RAqT5AJ9OWLc1A3zMf0pHUCNxa2n9dIwtkACfdzLb 6Gbc6J8C0yTKC1TS+K8GmLA= =/aga -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removed apmd but it still seems to be there
Hello Lorenzo Prince ([EMAIL PROTECTED]) wrote: I am using acpi in place of apm because it allows me to press the power button to shutdown the computer. I can easily accidentally press the power button, so it is good to have it go through the shutdown sequence or even do nothing instead of powering down without performing the shutdown actions, which could possibly corrupt my filesystem. Well, here's the deal. I turned acpi on in the boot loader and removed apmd, but the system is still trying to use apm. I tried removing powermgmt-base, but doing so would remove the entire gnome system. What can I do to fix this problem? What exactly does still trying to use apm mean? Does it try to use the apm driver instead of the acpi driver? Did you compile apm support as a module, or into the kernel? Did you try the apm=off boot parameter? Did you rerun lilo after changing the config file? best regards Andreas Janssen -- Andreas Janssen [EMAIL PROTECTED] PGP-Key-ID: 0xDC801674 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removed apmd but it still seems to be there
I am using acpi in place of apm because it allows me to press the power button to shutdown the computer. I can easily accidentally press the power button, so it is good to have it go through the shutdown sequence or even do nothing instead of powering down without performing the shutdown actions, which could possibly corrupt my filesystem. Well, here's the deal. I turned acpi on in the boot loader and removed apmd, but the system is still trying to use apm. I tried removing powermgmt-base, but doing so would remove the entire gnome system. What can I do to fix this problem? How did you remove apm? (precise commands please). How do you know that the system is still trying to use apm? Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removed apmd but it still seems to be there
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Andreas Janssen: # What exactly does still trying to use apm mean? Well, I am guessing that's what it's doing when it prints to the console and dmesg the following error message: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) apm: overridden by ACPI. It also prints a fatal error to the console saying that when it is trying to insert the apm module that there is no such device. But that isn't sent to dmesg. I apologize. I guess I should have clarified what is happening a little better. # Does it try to use the apm driver instead of the acpi driver? Not exactly. It seems to keep trying to load the apm driver even though the acpi driver is already loaded. # Did you compile apm support as a module, or into the kernel? I am currently running a stock 2.6.4 kernel which has apm compiled as a module. # Did you try the apm=off boot parameter? Yes. No luck. Same thing happens. # Did you rerun lilo after changing the config file? I actually decided to try grub, so I didn't have to run anything after changing the config file. PRINCE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAZxynAl2SNUPt1I8RAi+OAJ9mGQVpUsegyBr+OOUOtul4bN/9pQCcCd26 n11HokQeEhf14XWwDHdT5zc= =w/Wn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removed apmd but it still seems to be there
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Alexis Huxley: # How did you remove apm? (precise commands please). apt-get --purge remove apmd # How do you know that the system is still trying to use apm? apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) apm: overridden by ACPI. sent to /var/log/messages and dmesg command. The same lines are printed to the console along with a fatal error inserting /lib/modules/2.6.4-1/.../apm.ko no such device message. The last message isn't sent to /var/log/messages or dmesg. PRINCE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAZyTZAl2SNUPt1I8RAspIAJ9wJFErcMHrONarKKqJgZCONVnXSACgiqKY iHXhzd1kAUyNy6Y1GAjAi+M= =ZUBW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removed apmd but it still seems to be there
hi, i can't seem to find your previous mails on the list page, and i had deleted them from my account, so ... did you remove the apm packages? u have removed the apm argument from lilo, and since you have built it in as a module, is it still there in /etc/modutils (i'm not sure how this would make a difference if apm is removed, but its worth a shot?) hth. On Sun, 28 Mar 2004, Lorenzo Prince wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Andreas Janssen: # What exactly does still trying to use apm mean? Well, I am guessing that's what it's doing when it prints to the console and dmesg the following error message: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac) apm: overridden by ACPI. It also prints a fatal error to the console saying that when it is trying to insert the apm module that there is no such device. But that isn't sent to dmesg. I apologize. I guess I should have clarified what is happening a little better. # Does it try to use the apm driver instead of the acpi driver? Not exactly. It seems to keep trying to load the apm driver even though the acpi driver is already loaded. # Did you compile apm support as a module, or into the kernel? I am currently running a stock 2.6.4 kernel which has apm compiled as a module. # Did you try the apm=off boot parameter? Yes. No luck. Same thing happens. # Did you rerun lilo after changing the config file? I actually decided to try grub, so I didn't have to run anything after changing the config file. PRINCE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAZxynAl2SNUPt1I8RAi+OAJ9mGQVpUsegyBr+OOUOtul4bN/9pQCcCd26 n11HokQeEhf14XWwDHdT5zc= =w/Wn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] rajesh menon at http://www.cs.nyu.edu/~prm225/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: removed apmd but it still seems to be there
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thus spake Rajesh Menon: # did you remove the apm packages? u have removed the apm argument from # lilo, and since you have built it in as a module, is it still there in # /etc/modutils (i'm not sure how this would make a difference if apm is # removed, but its worth a shot?) I have removed the apmd package and there never was an apm boot parameter, so I added apm=off to my boot parameters. I just tried removing /etc/modutils/apm and I will see how that goes, although like you, I don't see how that could be causing the problem if a) acpi is enabled and b) apm is explicitly disabled. PRINCE -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAZ0ljAl2SNUPt1I8RAqlKAJ9GXWBGcWZNG+lOPNQlyuv6qVUjiACfdJyT UsuBkLKfED2aonOagiumABM= =ZLtR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
