LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 01-14-2006, 09:33 PM   #1
-=TRA=-
LQ Newbie
 
Registered: Jan 2006
Posts: 10

Rep: Reputation: 0
Fan noise problems...


I have an MSI 865 Mega; It's a "living room" computer, and the only computer my wife would accept (since it looks more or less like a stereo) by the TV.

When I used Windows, it was noicefree - even on boot the first time without any drivers.

On Linux, the FAN is on "critical" mode - ALLWAYS...

I have lm_sensors - but I can't make it "allright"... Any suggestions?

Thanks.

Quote:
Last login: Sat Jan 14 06:22:13 2006 from gw2.tonyrene.no
[tra@80 ~]$ cd /proc/acpi/thermal_zone/THRM/
[tra@80 THRM]$ cat cooling_mode
<setting not supported>
cooling mode: critical
[tra@80 THRM]$ cat temperature
temperature: 34 C
[tra@80 THRM]$ cat state
state: ok
[tra@80 THRM]$ sensors
tda9887-i2c-1-43
Adapter: cx88[0]

MT2050-i2c-1-61
Adapter: cx88[0]


Quote:

[root@80 ~]# cd /proc/acpi/fan
[root@80 fan]# ls -al
totalt 0
dr-xr-xr-x 3 root root 0 jan 15 04:25 .
dr-xr-xr-x 11 root root 0 jan 15 04:20 ..
dr-xr-xr-x 2 root root 0 jan 15 04:25 FAN
[root@80 fan]# cd FAN/
[root@80 FAN]# ls
state
[root@80 FAN]# cat state
status: on
[root@80 FAN]# exit
logout
[tra@80 ~]$ exit
logout
Quote:

[tra@80 ~]$ su -
Password:
[root@80 ~]# sensors-detect

This program will help you determine which I2C/SMBus modules you need to
load to use lm_sensors most effectively. You need to have i2c and
lm_sensors installed before running this program.
Also, you need to be `root', or at least have access to the /dev/i2c-*
files, for most things.
If you have patched your kernel and have some drivers built in, you can
safely answer NO if asked to load some modules. In this case, things may
seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all
questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
You do not need any special privileges for this.
Do you want to probe now? (YES/no): y
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 00:1f.3: Intel 82801EB ICH5
Probe succesfully concluded.

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is not loaded. Do you want to load it now? (YES/no): y
Module loaded succesfully.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: cx88[0]
Do you want to scan it? (YES/no/selectively): y
Client at address 0x43 can not be probed - unload all client drivers first!
Client at address 0x50 can not be probed - unload all client drivers first!
Client found at address 0x60
Client at address 0x61 can not be probed - unload all client drivers first!

Next adapter: SMBus I801 adapter at 0500
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x08
Client found at address 0x2d
Probing for `Myson MTP008'... Failed!
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `National Semiconductor LM85 or LM96000'... Failed!
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... Failed!
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'... Failed!
Probing for `National Semiconductor LM87'... Failed!
Probing for `National Semiconductor LM93'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83783S'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Winbond W83L784R/AR'... Failed!
Probing for `Winbond W83L785R'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x00'... Failed!
Probing for `Genesys Logic GL518SM Revision 0x80'... Failed!
Probing for `Genesys Logic GL520SM'... Failed!
Probing for `Genesys Logic GL525SM'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1026'... Failed!
Probing for `Analog Devices ADM1025'... Failed!
Probing for `Philips NE1619'... Failed!
Probing for `Analog Devices ADM1024'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `Analog Devices ADM1030'... Failed!
Probing for `Analog Devices ADM1031'... Failed!
Probing for `Analog Devices ADM1022'... Failed!
Probing for `Texas Instruments THMC50'... Failed!
Probing for `VIA VT1211 (I2C)'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
Probing for `ALi M5879'... Failed!
Client found at address 0x2f
Probing for `National Semiconductor LM78'... Failed!
Probing for `National Semiconductor LM78-J'... Failed!
Probing for `National Semiconductor LM79'... Failed!
Probing for `National Semiconductor LM80'... Failed!
Probing for `Winbond W83781D'... Failed!
Probing for `Winbond W83782D'... Failed!
Probing for `Winbond W83791D'... Failed!
Probing for `Winbond W83792D'... Failed!
Probing for `Winbond W83791SD'... Failed!
Probing for `Winbond W83627HF'... Failed!
Probing for `Winbond W83627EHF'... Failed!
Probing for `Asus AS99127F (rev.1)'... Failed!
Probing for `Asus AS99127F (rev.2)'... Failed!
Probing for `Asus ASB100 Bach'... Failed!
Probing for `Analog Devices ADM9240'... Failed!
Probing for `Dallas Semiconductor DS1780'... Failed!
Probing for `National Semiconductor LM81'... Failed!
Probing for `Analog Devices ADM1029'... Failed!
Probing for `ITE IT8712F'... Failed!
Probing for `ITE IT8705F / SiS 950'... Failed!
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'... Failed!
Client at address 0x50 can not be probed - unload all client drivers first!
Client found at address 0x68
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no): y
Probing for `National Semiconductor LM78'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM78-J'
Trying address 0x0290... Failed!
Probing for `National Semiconductor LM79'
Trying address 0x0290... Failed!
Probing for `Winbond W83781D'
Trying address 0x0290... Failed!
Probing for `Winbond W83782D'
Trying address 0x0290... Failed!
Probing for `Winbond W83627HF'
Trying address 0x0290... Failed!
Probing for `Winbond W83627EHF'
Trying address 0x0290... Failed!
Probing for `Winbond W83697HF'
Trying address 0x0290... Failed!
Probing for `Silicon Integrated Systems SIS5595'
Trying general detect... Failed!
Probing for `VIA Technologies VT82C686 Integrated Sensors'
Trying general detect... Failed!
Probing for `VIA Technologies VT8231 Integrated Sensors'
Trying general detect... Failed!
Probing for `ITE IT8712F'
Trying address 0x0290... Failed!
Probing for `ITE IT8705F / SiS 950'
Trying address 0x0290... Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0... Failed!
Probing for `IPMI BMC SMIC'
Trying address 0x0ca8... Failed!

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (0x6001)
Probing for `ITE 8705F Super IO Sensors'
Failed! (0x6001)
Probing for `ITE 8712F Super IO Sensors'
Failed! (0x6001)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87360 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87363 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87364 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87365 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87365 Super IO Voltage Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87365 Super IO Thermal Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87366 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87366 Super IO Voltage Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87366 Super IO Thermal Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87372 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87373 Super IO Fan Sensors'
Failed! (0x60)
Probing for `Nat. Semi. PC87591 Super IO'
Failed! (0x60)
Probing for `Nat. Semi. PC87371 Super IO'
Failed! (0x60)
Probing for `Nat. Semi. PC97371 Super IO'
Failed! (0x60)
Probing for `Nat. Semi. PC8739x Super IO'
Failed! (0x60)
Probing for `Nat. Semi. PC8741x Super IO'
Failed! (0x60)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (0x60)
Probing for `SMSC 47M10x/13x Super IO Fan Sensors'
Failed! (0x60)
Probing for `SMSC 47M14x Super IO Fan Sensors'
Failed! (0x60)
Probing for `SMSC 47M15x/192 Super IO Fan Sensors'
Success... found at address 0x0800
Probing for `SMSC 47S42x Super IO Fan Sensors'
Failed! (0x60)
Probing for `SMSC 47S45x Super IO Fan Sensors'
Failed! (0x60)
Probing for `SMSC 47M172 Super IO'
Failed! (0x60)
Probing for `SMSC LPC47B397-NC Super IO'
Failed! (0x60)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)

Do you want to scan for secondary Super I/O sensors? (YES/no): y
Probing for `ITE 8702F Super IO Sensors'
Failed! (skipping family)
Probing for `Nat. Semi. PC87351 Super IO Fan Sensors'
Failed! (skipping family)
Probing for `SMSC 47B27x Super IO Fan Sensors'
Failed! (skipping family)
Probing for `VT1211 Super IO Sensors'
Failed! (skipping family)
Probing for `Winbond W83627EHF Super IO Sensors'
Failed! (skipping family)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `to-be-written' (should be inserted):
Detects correctly:
* ISA bus address 0x0800 (Busdriver `i2c-isa')
Chip `SMSC 47M15x/192 Super IO Fan Sensors' (confidence: 9)


I will now generate the commands needed to load the I2C modules.
Sometimes, a chip is available both through the ISA bus and an I2C bus.
ISA bus access is faster, but you need to load an additional driver module
for it. If you have the choice, do you want to use the ISA bus or the
I2C/SMBus (ISA/smbus)? ISA

To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# I2C adapter drivers
modprobe i2c-isa
# I2C chip drivers
# no driver for SMSC 47M15x/192 Super IO Fan Sensors yet
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

WARNING! If you have some things built into your kernel, the list above
will contain too many modules. Skip the appropriate ones! You really should
try these commands right now to make sure everything is working properly.
Monitoring programs won't work until it's done.

Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/init.d/lm_sensors
for initialization at boot time.
 
Old 01-15-2006, 01:54 AM   #2
carl0ski
Member
 
Registered: Sep 2004
Location: Melbourne, Victoria Australia
Distribution: Support those that support you :)
Posts: 872
Blog Entries: 12

Rep: Reputation: 30
echo šactiveš>/proc/acpi/thermal_zone/THRM/cooling_mode

cat /proc/acpi/thermal_zone/THRM/cooling_mode

should show active
 
Old 01-16-2006, 12:33 PM   #3
-=TRA=-
LQ Newbie
 
Registered: Jan 2006
Posts: 10

Original Poster
Rep: Reputation: 0
Thanks. I'll try this.

-=TRA=-
 
Old 01-17-2006, 12:12 PM   #4
-=TRA=-
LQ Newbie
 
Registered: Jan 2006
Posts: 10

Original Poster
Rep: Reputation: 0
But it didn't...

Quote:
[tra@80 ~]$ su -
Password:
[root@80 ~]# echo active > /proc/acpi/thermal_zone/THRM/cooling_mode
[root@80 ~]# cat /proc/acpi/thermal_zone/THRM/cooling_mode
<setting not supported>
cooling mode: critical
[root@80 ~]#
Help still appreciated.

Thanks for the help so far.

-=TRA=-
 
Old 01-18-2006, 05:42 AM   #5
carl0ski
Member
 
Registered: Sep 2004
Location: Melbourne, Victoria Australia
Distribution: Support those that support you :)
Posts: 872
Blog Entries: 12

Rep: Reputation: 30
Quote:
Originally Posted by -=TRA=-
But it didn't...



Help still appreciated.

Thanks for the help so far.

-=TRA=-

sorry you forgot the quotes on active

[tra@80 ~]$ su -
Password:
[root@80 ~]# echo "active" > /proc/acpi/thermal_zone/THRM/cooling_mode



the options for cooling mode are supposed to be

critical
active
passive

can also be numbers
2
1
0


im not sure if passive turns the fan completely off

[root@80 ~]# echo "1" > /proc/acpi/thermal_zone/THRM/cooling_mode

Last edited by carl0ski; 01-18-2006 at 05:47 AM.
 
Old 01-18-2006, 05:54 AM   #6
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
What distribution are you using? That can make a difference in the approach to any system tuning and configuration task. For instance my SuSE 9.2 doesn't have the /proc/acpi/thermal_zone directory mentioned by carl0ski. If you were using SuSE then you would approach any system configuration task by using their YaST software. In SuSE you can also edit numerous configuration files in the /etc/sysconfig directory. These kinds of things are often specific to each distribution.
 
Old 01-22-2006, 02:55 PM   #7
-=TRA=-
LQ Newbie
 
Registered: Jan 2006
Posts: 10

Original Poster
Rep: Reputation: 0
I tried both with and without...

Still everything is logged, I can see the speed of the fan, the state - everything - and it's correct. I just can't change it.

I run Fedora Core 4

Logs are in "quotes", so it should be possible to see all paths, and that they exist.

I can manipulate the temp. for critical, but whatever I do, that's all I get to change (also shown in the log).


Thanks.

-=TRA=-

Quote:
[root@tra-msi THRM]# uname -r
2.6.11-1.1369_FC4
Quote:
[root@tra-msi THRM]# echo -n "100:0:90:80:65" > /proc/acpi/thermal_zone/THRM/trip_points
[root@tra-msi THRM]# cat trip_points
critical (S5): 100 C
[root@tra-msi THRM]# echo -n "79:0:90:80:65" > /proc/acpi/thermal_zone/THRM/trip_points
[root@tra-msi THRM]# cat trip_points
critical (S5): 79 C


Quote:
[tra@tra-msi ~]$ su -
Password:
[root@tra-msi ~]# cd /proc/acpi/thermal_zone/THRM/
[root@tra-msi THRM]# ls
cooling_mode polling_frequency state temperature trip_points
[root@tra-msi THRM]# cat cooling_mode
<setting not supported>
cooling mode: critical
[root@tra-msi THRM]# cat polling_frequency
<polling disabled>
[root@tra-msi THRM]# cat state
state: ok
[root@tra-msi THRM]# cat temperature
temperature: 28 C
[root@tra-msi THRM]# cat trip_points
critical (S5): 79 C
[root@tra-msi THRM]# echo "active" > /proc/acpi/thermal_zone/THRM/cooling_mode
[root@tra-msi THRM]# cat cooling_mode
<setting not supported>
cooling mode: critical
[root@tra-msi THRM]# echo "passive" > /proc/acpi/thermal_zone/THRM/cooling_mode
[root@tra-msi THRM]# cat cooling_mode
<setting not supported>
cooling mode: critical
[root@tra-msi THRM]# echo "2" > /proc/acpi/thermal_zone/THRM/cooling_mode
[root@tra-msi THRM]# cat cooling_mode
<setting not supported>
cooling mode: critical
[root@tra-msi THRM]# echo "1" > /proc/acpi/thermal_zone/THRM/cooling_mode
[root@tra-msi THRM]# cat cooling_mode
<setting not supported>
cooling mode: critical
[root@tra-msi THRM]# echo "0" > /proc/acpi/thermal_zone/THRM/cooling_mode
[root@tra-msi THRM]# cat cooling_mode
<setting not supported>
cooling mode: critical
[root@tra-msi THRM]#

Last edited by -=TRA=-; 01-22-2006 at 03:11 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
ACPI Problem? - Fan Noise das111 Linux - Newbie 2 06-28-2005 09:56 AM
Inspiron 8600 Fan noise. siggiae Slackware 3 05-24-2005 04:18 AM
Power supply fan and noise cjae Linux - Hardware 3 05-15-2005 11:37 PM
Bootup fan noise really loud string Linux - Hardware 2 11-24-2004 09:59 AM
Screen goes blank and fan noise reduces..press a button and back to normal? ginda Linux - Laptop and Netbook 1 03-31-2004 07:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 03:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration