Reword the "Can't access /proc file" error message so that

Linux 2.6 users don't get confused. Update the FAQ accordingly.


git-svn-id: http://lm-sensors.org/svn/lm-sensors/trunk@2208 7894878c-1315-0410-8ee3-d5d059ff63e0
This commit is contained in:
Jean Delvare committed 2004-01-09 21:09:58 +00:00
1 parent a456f4a784
commit 28c6adc439
2 files changed
+3 -3

No files matched your search

+2 -2
View File
@@ -555,7 +555,7 @@ to work.
* Section 4.17:: Bad readings from particular chips
* Section 4.18:: How do I configure two chips (LM87) differently?
* Section 4.19:: Dmesg says @samp{Upgrade BIOS}! I don't want to!
* Section 4.20:: Sensors says @samp{Can't access @file{/proc} file}
* Section 4.20:: Sensors says @samp{Can't access procfs/sysfs file}
* Section 4.21:: Sensors says @samp{No sensors found!}
* Section 4.22:: Sensors output is not correct!
* Section 4.23:: What is at I2C address XXX?
@@ -977,7 +977,7 @@ is the I/O address. You must select an address that is not in use.
@node Section 4.20, Section 4.21, Section 4.19, Problems
@section Sensors says @samp{Can't access @file{/proc} file}
@section Sensors says @samp{Can't access procfs/sysfs file}
@itemize
@item (release 2.6.0 and later) Did you @command{modprobe i2c-proc}? Check @command{lsmod}.
+1 -1
View File
@@ -34,7 +34,7 @@ static const char *errorlist[] =
/* SENSORS_ERR_WILDCARDS */ "Wildcard found in chip name",
/* SENSORS_ERR_NO_ENTRY */ "No such feature known",
/* SENSORS_ERR_ACCESS */ "Can't read or write",
/* SENSORS_ERR_PROC */ "Can't access /proc file",
/* SENSORS_ERR_PROC */ "Can't access procfs/sysfs file",
/* SENSORS_ERR_DIV_ZERO */ "Divide by zero",
/* SENSORS_ERR_CHIP_NAME */ "Can't parse chip name",
/* SENSORS_ERR_BUS_NAME */ "Can't parse bus name",