No sensor detected?

wenever i would start i workout i would select a playlist and it would never work it would say "no sensor detected"
help??

Laxmax: Your sensor might be asleep....check out this link
http://docs.info.apple.com/article.html?artnum=303934#faq5

Similar Messages

Kinect Evolution - "No Sensor Detected"

Just downloaded the recently released Kinect Evolution app from the Windows Store. When I launch it, it tells me "No Sensor Detected". Any other Kinect 2 app (for instance, K2 Studio) works fine.
Yes, I am running the official 1409 SDK release.

Check the app permissions/privacy settings of you system. You may have allowed the app camera/microphone, but your PC Settings/Privacy/WebCam and/or Microphone setting may be off globally.
Windows store applications has policies on accessing the camera/microphone that desktop apps do not get exposed to.
Carmine Sirignano - MSFT

Sensors-detect changes monitor settings.

I was trying to get sensors working, so i ran the command $ sudo sensors-detect. While it was running the "Safe" probes, my monitor flickered a few times and when it settled, the image was slightly off. I'm not sure what exactly is wrong, but it's slightly fuzzier and slightly lighter. when I run the command again, it seems to switch back and forth between two states, both of which are slightly different than it was before. It happens during this probe:
Next adapter: i915 gmbus panel (i2c-2)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x4f
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6642'... No
Probing for `Texas Instruments TMP421'... No
Probing for `Texas Instruments TMP422'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Any help would be greatly appreciated. Also, it seems to be a hardware issue, because it's changed for other operating systems as well. The computer in question is a laptop, so manually changing color levels is out of the question as far as I know.
Edit:
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 650M] (rev ff)
Last edited by FugitivePlatypus (2012-09-28 22:44:33)

FugitivePlatypus wrote:So I was doing some research on i2c, and i ran the command $ sudo i2cdump 2 0x4f, after running $ sudo modprobe i2c-dev, which while it was dumping the registry values faded through different settings on my monitor. Restricting the dump to $ sudo i2cdump -r 0x60-0x91 2 0x4f left the monitor in (as far as I can tell) the condition it was in originally. This is not persistent, however, and resets for different operating systems/reboots of arch.
i2c was what I was trying to remember.
i2c-tools i2c tools that used to be part of lm-sensors.
Last edited by nomorewindows (2012-10-04 18:00:30)

Two VI merging (a Temperature PID and Light sensor detecting) plz help

Hi,
my goal is to get the data from the light sensing detectors and also to control the Temperature too.
So I designed a VI named Light detecting "sensor and data storage.vi" but the problem was temperature controlling.
as in this VI I can not set the temperature which I want.
So I made another VI named "temperature control PID.vi", and now I can control the temperature through the thermocouple.
But again the problem is that I can not run Both the VIs at the same time.
and when I try to run both the VIs at same time, the following error appears,
and I think, it is because that both the VIs has the settings for same thermocouple and can not acquire the data (teperature) at the same time.
So I want to remove the thermocouple settings from the "Light detecting sensor and data storage.vi" and want to put the " temperature control PID.vi" into it.
I am uploading both the VIs, If anyone can solve it, His work will be appreciated.
Attachments:
Light detecting sensor and data storage.vi ‏190 KB
temperature control PID.vi ‏140 KB

Hi,
I mean to say that from the first VI, i m getting the signals from detectors and it also shows me the temperature. but from this VI, I can not set the temperature of the heater.
thats why I made another VI <the second one in attached files> by which I can control the temperature.
but both the VIs are not working simultaneously.
so plz delete the temperature settings from the first VI and put the second VI into it.
thanks.

No sensor detected, battery is not low,not sleeping

sensor is linked but it's not able to detect it? tapped it...nothing

So the sensor had worked before it did this? or not?
If the sensor is linked then it should have been detected by the ipod with the sensor plugged in to the dock connector below.ARe you saying that the portion in the shoe is not being detected or the portion that connects to the ipod?
If its the sensor in the shoe then it might not be on. I know it took me a few tris before my ipod detected the shoe sensor. THe shoe sensor is tricky on determining if its on or off. Tapping it wont do you need to press the on/off button for a few seconds to turn it on. Nor does the shoe sensor go to sleep. If you keep it on even hen its not in use its on. How long have you had the sensor? Because it (battery) does have a limited run time.
GFF

New Nike+ sensor detection problem

Bought my first Nike+ yesterday, did succeed to link the sensor. Did go for a walk to test it, didn’t get any contact. Of and on with the shoe tapping pressing the button and at last contact when holding the sensor in my hand moving it around, put it in the shoe start walking and it looked good but then it after a while the voice asked if I wanted to resume the training, did that a couple of times. Then I stopped the "training" and it had registered 10 meter.
Didn’t succeed to get more contact with the sensor.
Did go to the store today and got it replaced with a new kit. Tested it right away by plug in the receiver and move around the package with the sensor, linked the sensor and got one training activated. Then when home I got problem to connect the sensor, tried several times walking around then tapped and move around the sensor in my hand and got contact, even succeed to get contact with the sensor in the shoe.
I have a old Nano ver 1, the Nano battery is not new but it still hold for several hours music.
My suspicion is that it is old Nike+ kits, didn’t seems to be a big seller in the sports shop where I bought it. I'll guess these battery’s age and get weaker if they have been on the shelf in the store for a year or so.
As I understand it the low battery indicator is based on usage/training time, so if the battery is poor when you buy the sensor there will be no indication before it dies.
It had helped if one could get the date when the sensor was produced by the serial number.
I must say I’m disappointed so far to have to spend all this time trying to make it work.
And BTW why is the excellent stopwatch function with laps separated from the Nike+ thing, as I get it there is no lap function with Nike+.
Going out for a run now to see if it still works, knock on wood.

Well after some disconnecting and connecting of the receiver did I manage to get some action from the sensor, but then it died after 940 meter.
Nike+ have had it’s chance with me I give up and make a run for a refund.

Unable to detect a thermal sensor: lm_sensors and ACPI

HP Pavilion ze5600 laptop, latest Arch kernel, ran sensors-detect and this is the result:
Sorry, no sensors were detected.
This is relatively common on laptops, where thermal management is
handled by ACPI rather than the OS.
I tried "sudo modprobe thermal" and although successful there is no thermal entry in /proc/acpi . I also tried adding "acpi_enforce_resources=lax" to kernel boot line without success. I also attempted to insert the i2c-dev module before running sensors-detect, without success.
As I have not tried any other OS on this laptop I am unsure whether it does actually have a sensor but googling around others seem to have been successful. Any suggestions on how to proceed would be most welcome.

I'd love to see this thread solved as my Dell XPS L1502 has the same situation. A sensors-detect brings the same module as you but the sensors outputs temperatures for just 2 cores for an i5 should be listed, which are about 50°C (normal?).
acpitz-virtual-0
Adapter: Virtual device
temp1: +54.0°C (crit = +100.0°C)
temp2: +54.0°C (crit = +100.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +55.0°C (high = +86.0°C, crit = +100.0°C)
Core 0: +54.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +49.0°C (high = +86.0°C, crit = +100.0°C)
The pwmconfig returns an error "no pwm-capable sensor modules installed".
Thanks for everyone contributing to this thread.
Last edited by nunobaba (2011-10-14 16:08:32)

Hard drive upgrade on 13" MBP sudden motion sensor compatibility

Hello,
I'm planning on upgrading the hard drive in my 13" MBP (aluminium unibody) and I've read a lot of posts regarding the sudden motion sensor conflicts with OS X 10.6.2. I'd like to know if the Western Digital 500GB Scorpio Blue here (http://www.dabs.com/products/western-digital-500gb-scorpio-blue-5400rpm-sata-300 -8mb-58P6.html) would suffer from the conflict (I'm not sure if "Shock Guard" = sudden motion sensor). I don't know if its a simple yes/no or whether its drive / mac specific.
If it would be a problem does anyone have a suggestion for a guaranteed compatible 500Gb hard drive (5400 rpm is fine)?
Any thoughts are much appreciated, thanks for your help!

Western Digital Lists their drive features as:
* IntelliSeek™ - IntelliSeek technology calculates optimum seek speeds to lower power consumption, noise and vibration.
* SecurePark™ - WD's SecurePark technology parks the recording heads off the disk surface during spin up, spin down and when the drive is off. This ensures the recording head never touches the disk surface resulting in improved long term reliability due to less head wear, and improved shock tolerance.
* ShockGuard™ - WD's ShockGuard technology protects the drive mechanics and platter surfaces from shocks during shipping and handling and in daily operation.
* Free-fall Sensor - As an added layer of protection, if the drive (or the system it's in) is dropped while in use, WD's free-fall sensor detects that the drive is falling and, in less than 200 milliseconds, parks the head off the disks to help prevent damage and data loss.
* WhisperDrive™ - WD's exclusive WhisperDrive technology combines state-of-the-art seeking algorithms that result in one of the quietest 2.5-inch drives on the market.
The Free Fall Sensor is the equivalent of the Sudden Motion Sensor. Looking at the specs for the drive you linked to... they list the following features:
Shock Guard, WhisperDrive, SecurePark
As they do not list Free Fall Sensor, I'm guessing this model does not have one so it should not conflict with the internal Sudden Motion Sensor in your MacBook.

Trouble building kernel module for sensor support

Hi, I'm new here but have been using Arch for a while. Recently, I decided to install Arch on an old laptop (Toshiba A70) and have managed to work out most of the kinks to where it runs nicely. Unfortunately, ACPI support is spotty and the /sys/class/thermal directory gives me only cooling_device0. I installed the lm-sensors package and ran sensors-detect, which yielded no results. Although the laptop runs smoothly otherwise, I would like to know the CPU's temp so that I would be able to set up a fan control scheme and CPU scaling (so far it's stuck at the lowest frequency, and that's kind of a big deal for me since the laptop runs on an archaic mobile P4 chip).
Sorry for the story but I felt some context was necessary. I did manage to find a kernel module that would connect those sensors to ACPI for me (http://sourceforge.net/projects/omnibook/), however I'm having trouble building it on the latest kernel. Here is the output from running make:
make -C /lib/modules/3.16.1-1-ARCH/build SUBDIRS=/root/omnibook-2.20070211 modules
make[1]: Entering directory '/usr/lib/modules/3.16.1-1-ARCH/build'
CC [M] /root/omnibook-2.20070211/init.o
In file included from /root/omnibook-2.20070211/init.c:26:0:
/root/omnibook-2.20070211/laptop.h:25:3: warning: initialization from incompatible pointer type
.callback = dmi_matched,
^
/root/omnibook-2.20070211/laptop.h:25:3: warning: (near initialization for ‘omnibook_ids[0].callback’)
/root/omnibook-2.20070211/laptop.h:34:3: warning: initialization from incompatible pointer type
.callback = dmi_matched,
^
/root/omnibook-2.20070211/laptop.h:34:3: warning: (near initialization for ‘omnibook_ids[1].callback’)
/root/omnibook-2.20070211/laptop.h:43:3: warning: initialization from incompatible pointer type
.callback = dmi_matched,
^
// I left out most of the 'incompatible pointer type' warnings since they repeat for a while.
^
/root/omnibook-2.20070211/laptop.h:1001:3: warning: (near initialization for ‘omnibook_ids[108].callback’)
/root/omnibook-2.20070211/init.c: In function ‘dmi_matched’:
/root/omnibook-2.20070211/init.c:141:16: warning: assignment discards ‘const’ qualifier from pointer target type
laptop_model = dmi_get_system_info(DMI_PRODUCT_VERSION);
^
/root/omnibook-2.20070211/init.c: In function ‘omnibook_init’:
/root/omnibook-2.20070211/init.c:281:3: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration]
proc_entry = create_proc_entry(feature->name, pmode, omnibook_proc_root);
^
/root/omnibook-2.20070211/init.c:281:14: warning: assignment makes pointer from integer without a cast
proc_entry = create_proc_entry(feature->name, pmode, omnibook_proc_root);
^
/root/omnibook-2.20070211/init.c:290:13: error: dereferencing pointer to incomplete type
proc_entry->data = feature;
^
/root/omnibook-2.20070211/init.c:291:13: error: dereferencing pointer to incomplete type
proc_entry->read_proc = &procfile_read_dispatch;
^
/root/omnibook-2.20070211/init.c:293:14: error: dereferencing pointer to incomplete type
proc_entry->write_proc = &procfile_write_dispatch;
^
/root/omnibook-2.20070211/init.c:294:13: error: dereferencing pointer to incomplete type
proc_entry->owner = THIS_MODULE;
^
cc1: some warnings being treated as errors
scripts/Makefile.build:257: recipe for target '/root/omnibook-2.20070211/init.o' failed
make[2]: *** [/root/omnibook-2.20070211/init.o] Error 1
Makefile:1333: recipe for target '_module_/root/omnibook-2.20070211' failed
make[1]: *** [_module_/root/omnibook-2.20070211] Error 2
make[1]: Leaving directory '/usr/lib/modules/3.16.1-1-ARCH/build'
Makefile:88: recipe for target 'omnibook.ko' failed
make: *** [omnibook.ko] Error 2
I have honestly no idea what to make of any of this and would really appreciate any help towards a solution. Thanks for reading

Welcome to Arch Linux
That looks like it is a 2.6 kernel module
http://sourceforge.net/p/omnibook/bugs/58/
Did you try either of these AUR offerings?
ewaller$@$odin ~ 1001 %packer -Ss omnibook
aur/omnibook-git 20110911-9 (7)
Kernel module for HP OmniBook,Pavilion,Toshiba and Compal ACL00 laptops
aur/omnibook-svn-zen 268-1 (1)
Kernel module for HP OmniBook, Pavilion, Toshiba and Compal ACL00 laptops
ewaller$@$odin ~ 1002 %
Last edited by ewaller (2014-08-23 23:33:53)

Coretemp sensors wrong on Atom 330

I have a small problem with the sensors settings. The coretemp is displayed as a value around 0 degrees. that cannot be right, can it?
sensors-detect detected coretemp. smsc47ma en smsc47m192 as modules.
output from sensors:
coretemp-isa-0000
Adapter: ISA adapter
Core 0: -3.0Â°C (crit = +90.0Â°C)
coretemp-isa-0001
Adapter: ISA adapter
Core 1: +1.0Â°C (crit = +90.0Â°C)
uname -pm
x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz

Known bug - https://bbs.archlinux.org/viewtopic.php?id=79331
https://github.com/graysky2/configs/blo … sors3.conf

Detect attack man in the middle with IDS/IPS

Hi,
I have aip-ssm 20, IPS Version 7.0(6)E4
The ID signature 7101, 7102, 7104 and 7105 is used for detecting attack arp poison.
The sensor works as IDS in promiscuous mode. All traffic is fordwared to sensor.
I have made attack man in the middle with cain & abel but sensor doesn't send alarm. I attach image with signatures.
Why don't sensor detect attack? The network is in zone inside.
Can anybody help me, please?

Did you check if SSM is getting those packets by running "packet display .." command on the sensing interface. In SSM the ARP packets would not be forwarded by ASA to the SSM.
thx
Madhu

How to test anomaly detection in IPS6 ?

Hi!
Does anybody have experience with AD in IPS6? I tried to test it today with 3 nmap sessions each scanning 100 different IPs. I saw the Sig 13003-0 (single scanner) fired:
signature: description=AD - External TCP Scanner id=13003 version=S262
alertDetails: . adExtraData: numDestIps=150; currentThreshold=150; destPort=80
The scanner threshold was indeed set to 150:
S1# sh ad-knowledge-base vs0 thresholds current
External Zone
TCP Services
Default
Scanner Threshold
User Configuration = 150
Threshold Histogram - User Configuration
Low = 10
Medium = 3
High = 1
UDP Services
This is ok. The problem is that the Sig 13003-1 (warm) didn't fire, however the number of scanned IPs was very high:
S1# sh statistics anomaly-detection vs0
Statistics for Virtual Sensor vs0
Attack in progress
Detection - ON
Learning - OFF
Next KB rotation at 10:00:00 MSK Fri Dec 28 2007
Internal Zone
TCP Protocol
UDP Protocol
Other Protocol
External Zone
TCP Protocol
Service 80
Source IP: 10.0.1.1 Num Dest IP: 280
Questions:
- what does Low/Medium/High exactly mean in threshold histogram?
- how does the sensor detect worms? When the Sig 13003-1 fires? What sequence of events should happen?
- how can I test it?

The sensor constantly watches for scanners on each port.
There are 3 categories of scanners:
Low scanners - scanners that are only scanning a low number of hosts.
Medium scanners - scanners that are scanning a medium number of hosts
High scanners - scanners that are scanning a high number of hosts
NOTE: I can't remember for sure how many hosts must be scanned for it to be a "Low" number of hosts, or "Medium" or "High". But it may be something like 5 hosts scanned is a "Low" scanner, 20 for Medium and 100 for High. Once again I am not sure of those numbers.
Also be aware that the number of hosts scanned is not the Total numner of hosts scanned, but is instead the number of hosts scanned THAT did not respond.
If you connect to 100 web servers and all web servers respond then it does not count that as a scan. If you try to connect to 100 web servers and 92 respond, then for the 8 that don't respond you would be categorized as a Low scanner.
But just because a scanner is counted in a category does not mean an alert will be generated.
There are 2 types of alerts (subsig 0 alerts, and subsig 1 alerts)
Subsig 0 alerts are for a scanner that is scanning enough hosts that you want an alert for it even when no worm has been declared.
This is the "scanner Threshold / User Configuration = 150" that you see in the "show ad-knowledge-base vs0 thresholds current" output.
If a scanner scans more than 150 hosts then a specific alert is generated even though no worm has been declared.
Any scanners scanning less than 150 hosts are still categorized but do not have alerts generated for them when no worm has been declared.
The subsig 1 alerts are for when a Worm has been declared.
Here is how a worm gets declared:
The Thesholds for Low, Medium, and High that you see in "show ad-knowledge-base vs0 thresholds current" is the number of active scanners in each category that are allowed to normally be seen on your network (this is the number of scanners that will be seen on your network even when there are no worms).
A worm gets declared when the number of scanners in any one of the 3 catgeories goes above the threshold for that category.
Let's take for example Medium=3 as the threshold for port 21. And let's assume it takes a scan of 20 hosts to be categorized as a Medium scanner.
This means normally you could have up to 3 scanners on your network where each scanner is scanning 20 or more non-responding hosts on port 21.
(Maybe these are 3 network administrators periodically checking to see which machines have port 21 open)
Suddenly you have 5 scanners that start scanning on port 21 and each of the 5 winds up with 20 or more non-responding hosts.
That 5 has broken the threshold of 3, and a worm is declared. Now any Medium Category scanner on port 21 will begin being declared a scanner under a worm condition (subsig 1).
So for your testing.
Instead of running a scan of 100 hosts from just one machine, I would recommend you scan the same 100 hosts from 2 or 3 machines (NOTE: Only need to scan a single port across those 100 hosts).
Scanning 100 hosts should get them categorized as High scanners. And having 3 High Scanners should push it over the threshold of 1.
BUT keep in mind that it needs to be 100 hosts not responding on the scanned port.
Then you will also want to try it with fewer hosts being scanned (like say 25), but with say 5 machines running nmap doing the scanning.

How to process the analog output of hall-effect sensors to determine gear RPM.

Hi,
I am using a hall effect sensor to determine the rpm of my shaft. Attached to my shaft is a spur gear, and the sensor detects when the gear teeth passes it.
The attached pdf shows the "idle" state when there is no ferrous target detected. And when a ferrous target (my gear tooth) is detected, a horizontal like is displayed.
I am using the NI-9229 device connecting my hall effect sensor to my PC.
I would like to know how I can process this signal so as to determine the rpm of my shaft in real-time.
Thanks and appreciate the assistance.
Regards,
ST
Attachments:
Hall_effect_sensing.pdf ‏218 KB

Hi, check this one out:
https://decibel.ni.com/content/thread/13337
Br,
/Roger

Sensors aren't working

I don't know if this is the place for such a post,but when i run "sensors",I get the following output :
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
and when i run sensors-detect,it does detect my hardware,but nothing changes when I run sensors again

this is it :
[root@mahmoud ~]# sensors-detect
# sensors-detect revision 5729 (2009-06-02 15:51:29 +0200)
# System: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H
This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD K10 thermal sensors... Success!
(driver `to-be-written')
Intel Core family thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal and voltage sensors... No
Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... Yes
Found `ITE IT8718F Super IO Sensors' Success!
(address 0x228, driver `it87')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Trying family `ITE'... No
Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): y
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No
Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600 SMBus
Module i2c-dev loaded successfully.
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `it87':
* ISA bus, address 0x228
Chip `ITE IT8718F Super IO Sensors' (confidence: 9)
Driver `to-be-written':
* Chip `AMD K10 thermal sensors' (confidence: 9)
Note: there is no driver for AMD K10 thermal sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no): y
Copy prog/init/lm_sensors.init to /etc/rc.d/lm_sensors
for initialization at boot time.
You should now start the lm_sensors service to load the required
kernel modules.
Unloading i2c-dev... OK
[root@mahmoud ~]# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
[root@mahmoud ~]#

Lm sensors not getting info from intel board

Greetings,
I am having the same issue that was posted here in 2008 but i can't seem to find a resolution:
http://www.spinics.net/lists/lm-sensors/msg21829.html
does anyone know how to get the intel dp35dp to work with lmsensors?
thanks!
Adam

the mobo is a dp35dp and the suspected chipset is ICH9 internal, but when i manually loaded the i2c-i801 module it didn't work.
[edit]
I also tried it87 but got the following error:
sudo insmod it87.ko
Error: could not insert module it87.ko: No such device
[/edit]
[edit2]
so i ran sensors-detect again and realized i missed this before:
Found `Nuvoton WPCD377I Super IO'
(no hardware monitoring capabilities)
google isn't very helpful for this error (partially because i'm not 100% sure what to look for
[/edit2]
Last edited by adambot (2012-08-22 22:41:21)

No sensor detected?

Similar Messages

Maybe you are looking for