Ticket #2187 (closed defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Can't access procfs/sysfs file - Kernel interface access error

Reported by: szabo.marton@… Owned by: somebody
Priority: major Milestone:
Component: misc Version: 2.10.1
Keywords: sysfs procfs Cc:

Description

Hi, when I type "sensors" or "sensors -s", I get the following error:

Can't access procfs/sysfs file Kernel interface access error For 2.6 kernels, make sure you have mounted sysfs and libsenors was compiled with sysfs support!

I am using kernel 2.4.27-2-386, and have followed all instructions regarding kernel 2.4 in INSTALL file.

Thanks in advance!

Change History

Changed 6 years ago by khali

  • cc szabo.marton@… removed
  • resolution set to fixed
  • status changed from new to closed
  • component changed from hardware to misc
  • reporter changed from ticket to szabo.marton@…

The error message is a bit confusing but typically this simply means that no hardware monitoring chip was found on your system. You may need to load some missing kernel driver, or maybe your system simply doesn't have sensors. sensors-detect should tell you if you have sensors or not. As you did not give enough details on your hardware, I can't help you further.

Changed 6 years ago by ticket

  • status changed from closed to reopened
  • resolution fixed deleted

I had the same error message last week with Fedora 2.6.20 kernel (SBS Technologies/VR9 embedded processor board), after googling and reading the source code for awhile, I found out that I need to turn on SYSFS_SUPPORT = 1 in the Makefile(lm_sensors-2.10.4). Now "sensors" is working great on both LM83 and LM75 sensor chip. Please make sure that you modify /etc/modprobe.conf and /etc/rc.local as suggested when running sensors-detect script.

Thaison Dao

Changed 6 years ago by khali

  • status changed from reopened to closed
  • resolution set to fixed

This second problem is completely unrelated with the original bug (2.6 kernel vs 2.4 kernel, different version of lm-sensors...) Please do not reopen old tickets for unrelated problems, open new tickets instead!

Anyway, I've found some issues in the kernel version detection code, which may explain your problem. It's fixed in SVN now.

Note: See TracTickets for help on using tickets.