Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 180344 - gentoo-sources-2.6.20-r8 - cpufreqd is creating folder /.nvclock
Summary: gentoo-sources-2.6.20-r8 - cpufreqd is creating folder /.nvclock
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-30 13:30 UTC by Georg Sahli
Modified: 2007-06-02 09:14 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Sahli 2007-05-30 13:30:31 UTC
Hello,
when I use kernel 2.6.19 with AMD64 there is no problem. 
But when I use 2.6.20-gentoo-r7 or -r8 with AMD64 I have some interresting bugs and all belongs to hwmon.

Could the folder /.nvclock be from the application nvclock, but nvclock I never did install. Inside are 2 files, "bios0.rom" and "config".

And it looks like none application is using this folder. When I delete this folder live in system I do not have any problems.
Everytime during boot this folder will be created new.

Normaly only in 2.6.20 (2.6.19 is ok) out of messages it looks this:
---
w83627hf 9191-0290: Reading VID from GPIO5
cpufreqd: apm_init                 : /proc/apm: No such file or directory
cpufreqd: parse_config_rule        : WARNING! skipping config option "ac"
cpufreqd: init_configuration       : [Rule] name "AC Rule" has no options. Discarded.
cpufreqd: parse_config_rule        : WARNING! skipping config option "ac"
cpufreqd: parse_config_rule        : WARNING! skipping config option "battery_interval"
cpufreqd: init_configuration       : [Rule] name "AC Off - Low Battery" has no options. Discarded.
cpufreqd: parse_config_rule        : WARNING! skipping config option "ac"
cpufreqd: parse_config_rule        : WARNING! skipping config option "battery_interval"
cpufreqd: init_configuration       : [Rule] name "AC Off - Medium Battery" has no options. Discarded.
cpufreqd: parse_config_rule        : WARNING! skipping config option "ac"
cpufreqd: parse_config_rule        : WARNING! skipping config option "battery_interval"
cpufreqd: init_configuration       : [Rule] name "AC Off - High Power" has no options. Discarded.
cpufreqd: parse_config_rule        : WARNING! skipping config option "acpi_temperature"
cpufreqd: parse_config_rule        : WARNING! skipping config option "battery_interval"
cpufreqd: parse_config_rule        : WARNING! skipping config option "acpi_temperature"
---

I blocked this folder with a read only tmpfs partition, and then find these entries other than normal in /var/log/messages:
---
w83627hf 9191-0290: Reading VID from GPIO5
cpufreqd: apm_init                 : /proc/apm: No such file or directory
cpufreqd[6835]: segfault at 0000000000000000 rip 00002b3dc202bbf1 rsp 00007fffe8e04260 error 4
---
^ I understand that w83627hf (=sensor) is moving the GPU-BIOS into this folder
but why and for which application? And why it disrupt APM?

---
In my standard kernel .config (2.6.19 + 2.6.20) normaly I have this entries:
CONFIG_HWMON=y
CONFIG_HWMON_VID=m

I hashed out the line with "CONFIG_HWMON_VID=m" but that did change nothing, the module is build again.

Due to I had never before installed nvclock, what the hell can do this.
Both nVidia-drivers and X do work fine without.
Comment 1 Georg Sahli 2007-05-31 13:02:00 UTC
OK, found that cpufreqd is dealing and creating libs which are called nvclock.

As I did asked in our forum, it looks like I'm the only one with such a folder direct on root-partition. I do not like it there and will replace cpufreqd with another eq.
Comment 2 Georg Sahli 2007-05-31 13:12:55 UTC
Sorry I forgot to note that I had installed stable cpufreqd in version 2.1.1 on AMD64 SMP.
Comment 3 Georg Sahli 2007-05-31 13:42:01 UTC
Problem is solved by removing cpufreqd from rc and unmerging.

With it the APM failures are gone too, they're no longer logged in messages.
Comment 4 Georg Sahli 2007-06-02 09:14:17 UTC
There are some more things solved, which I had never found. 
The monitor settings for blancking and switching the monitor off!

Every 10 minutes was the monitor blancked and in plus 10 minutes the system did switch off the monitor. The standart settings in xorg.conf were ignored, and I did not find where the config for the monitor was to set.

Silly, no howto did mention that.