| View previous topic :: View next topic |
| Author |
Message |
phsdv
Guru
Joined: 13 Mar 2005
Posts: 372
Location: Europe
|
 Posted: Fri Oct 14, 2005 8:08 pm Post subject: [solved] No ACPI |
 |
|
I can not get ACPI working on my system. I need the fan access. Since I loaded the lm_senors the fan is always running at full speed. (before the bios took care of it??)
I have ACPI enable in the BIOS, even some 2.0 extensions. The machine is a Soltek SL-B8E-F with SMP (hypertreading enabled). Many message from APCI in dmesg but no /proc/acpi? Anyone an idea what is going on?
| Code: | dmesg (parts cut out)
Linux version 2.6.12-gentoo-r9 (root@pserver) (gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8)) #6 SMP Fri Oct
14 21:20:09 CEST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001df40000 (usable)
BIOS-e820: 000000001df40000 - 000000001df50000 (ACPI data)
BIOS-e820: 000000001df50000 - 000000001e000000 (ACPI NVS)
BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
479MB LOWMEM available.
found SMP MP-table at 000ff780
On node 0 totalpages: 122688
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 118592 pages, LIFO batch:31
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v002 ACPIAM ) @ 0x000f6d00
ACPI: XSDT (v001 A M I OEMXSDT 0x10000320 MSFT 0x00000097) @ 0x1df40100
ACPI: FADT (v003 A M I OEMFACP 0x10000320 MSFT 0x00000097) @ 0x1df40200
ACPI: MADT (v001 A M I OEMAPIC 0x10000320 MSFT 0x00000097) @ 0x1df40300
ACPI: OEMB (v001 A M I OEMBIOS 0x10000320 MSFT 0x00000097) @ 0x1df50040
ACPI: DSDT (v001 1ABOY 1ABOY000 0x00000000 INTL 0x02002026) @ 0x00000000
ACPI: PM-Timer IO Port: 0x808
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: TEMPLATE Product ID: ETEMPLATE APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 2
Allocating PCI resources starting at 1e000000 (gap: 1e000000:e1b80000)
Built 1 zonelists
Kernel command line: root=/dev/hda5 acpi=ht,force elevator=cfq
...
...
ACPI: Subsystem revision 20050309
ACPI: Interpreter disabled.
pnp: PnP ACPI: disabled |
| Code: | # ls -l /proc/acpi
ls: /proc/acpi: No such file or directory |
| Code: | # grep ACPI .config | grep -v "#"
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
CONFIG_ACPI_BLACKLIST_YEAR=0
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_PNPACPI=y
|
Last edited by phsdv on Sat Oct 15, 2005 10:47 am; edited 1 time in total |
|
| Back to top |
|
 |
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sat Oct 15, 2005 3:57 am Post subject: |
|
|
I've seen a couple things around about ACPI and lm_sensors, because mine were flaking out as well. In my case, the
chip providing the sensor functions doesn't get along well with:
I notice that the kernel is reporting PNPACPI as disabled in your dmesg, yet you have it enabled in your .config so maybe you've got the same chip as I do, or yours has a similar incompatibility. The chip I've got is the Winbond 83627EHG, and I
believe the problem also comes up with the 83627EHF. There is a patch, but it applies to the latest kernel sources, 2.6.14.
I tried backporting it by hand, and the module compiled and loaded fine, but it didn't work, so it must depend on other
changes in the newer source tree.
Thomas S. Howard |
|
| Back to top |
|
|
phsdv
Guru
Joined: 13 Mar 2005
Posts: 372
Location: Europe
|
| Posted: Sat Oct 15, 2005 10:47 am Post subject: |
|
|
| didymos wrote: | ...maybe you've got the same chip as I do, or yours has a similar incompatibility. The chip I've got is the Winbond 83627EHG, and I
believe the problem also comes up with the 83627EHF. There is a patch, but it applies to the latest kernel sources, 2.6.14. |
My machine is using the 83627thf. Almost the same. However switching off CONFIG_PNPACPI did not help.
Nevertheless I've got it running! I changed my boot parameters frominto |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sat Oct 15, 2005 11:31 pm Post subject: |
|
|
That's good. In my case, the problem wasn't as severe. I just can't access sensor info, despite the chip being detected.
Thomas S. Howard |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
