2.6.37 Kernel and ACPI
I have a custom built 2.6.37 kernel where I have most of my devices compiled into the kernel. The only modules are related to nouveau (in case I want to go back to proprietary nvidia) and sound drivers. Everything seems to be running fine. However, in /proc/acpi, I'm missing a number of entries, such as thermal_zone/, dsdt, etc. I do have ac_adapter/, battery/, button/, event, processor/, and wakeup.
I've gone through what I think is a VERY detailed review of my kernel config, and I can't find where I've missed something ACPI related. Here is my kernel config with the ACPI section. Code:
|
The layout of /proc/acpi varies depending upon your hardware.
For instance here (Lenovo Thinkpad T61 6457-4XG): Code:
bash-4.1$ ls -1 /proc/acpi/ Code:
bash-4.1$ find /proc/acpi -name "thermal*" |
I should have mentioned that I get all of the standard ACPI items in /proc/acpi when running the stock Slackware generic or huge kernels.
|
It's very possible that /proc/acpi layout varies depending upon the kernel version.
Anyhow what gives 'find /proc/acpi/ -name "thermal*"'? Also, knowing which hardware you have could help. |
Under 2.6.37, nothing comes back from the find command. Under 2.6.35.11 (Slackware generic), it's /proc/acpi/thermal_zone.
Here is the results of the output of lspci: Code:
|
My hardware is very similar to yours, maybe but the processor type:
Code:
bash-4.1# uname -mpi Also you could have a look in /sys/ For instance: Code:
bash-4.1# find /sys/ -name "thermal*" |
I can get most of the ACPI info from the sysfs, so I don't know why it's not showing up in /proc. Thanks for posting your config file, but I'm not able to really pinpoint what the main difference is.
|
If the info is available in /sys and userland programs are set up to get it from there, there is no need to put it in /proc in addition.
If I understand well, /sys could fully replace /proc some day. Does you CPU get over heated, or is the fan triggered when temperature becomes too high? That is the question, practically speaking ;) |
I don't think anything is getting overheated, and I think the fans are working correctly. You are correct, that is my real question and concern. I know that /proc is pretty much deprecated, but there are a number of programs that look there first, like conky. Right now, I've got conky looking in /sys for things like the temperature, but I still have this nagging feeling that if /proc is not being populated correctly, something is misconfigured somewhere.
|
I use conky as well and had to change my .conkyrc after some kernel upgrades to keep up with moving layouts in /proc and/or /sys.
This is a recurrent integration problem: when you change a component of the system, more often than never there is a change in some interface which you have to keep up with in changing some other components as well. My guess is that the Slackware team is kept busy with that ;) |
The same here with 2.6.38-rc4 kernel:
Code:
|
All times are GMT -5. The time now is 01:40 AM. |