From: "Ryan Bowman" <[EMAIL PROTECTED]> > dmesg apm gives this. I don't know what a lot of it means. . . . > ACPI: have wakeup address 0xc0001000 . . . > ACPI: RSDP (v000 DELL ) @ 0x000fde50 > ACPI: RSDT (v001 DELL CPi R 10194.02065) @ 0x000fde64 > ACPI: FADT (v001 DELL CPi R 10194.02065) @ 0x000fde90 > ACPI: DSDT (v001 INT430 SYSFexxx 00000.04097) @ 0x00000000 > ACPI: BIOS passes blacklist . . . > ps, ACPI is not enabled in the kernel, since before when I had both enabled apm didn't work. > Thanks, Ryan
You would have gotten the same thing with "dmesg" not "dmesg apm", see "man dmesg" for more info. Basically dmesg is what is flashing by when linux is starting up, it lists the hardware that your running kernel is finding or not finding. As you can see, it is riddled with references to ACPI, so you've gone wrong somewhere trying to /not/ compile in ACPI support for your kernel. Whichever loads first APM or ACPI will inhibit the other from loading. Like Byron said, you could disable ACPI, but the question must be asked, why not use ACPI instead of APM? It /seems/ like your compy supports it. ACPI is less developed in linux than APM, but will be more functional (last I checked, 8months ago). Check with your manufacurer to see which power management standard the system was meant to support; if it's newer, most likely it will be ACPI. Matt W. ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
