From: [email protected]

Package: lm-sensors
Version: 2.8.7-2
Severity: grave
Justification: renders package unusable

I'm trying to get working lm-sensors on debian:

dubrava:/home/mantas# apt-get install lm-sensors

[...]

Setting up lm-sensors (2.8.7-2) ...

Gtk-WARNING **: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog

Creating config file /etc/sensors.conf with new version
cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.


As I don't know what is sysfs (procfs is mountend automatically on my
system by discover) and didn't got any debconf prompts about mounting
sysfs, so I did 'modprobe i2c_sensor' and then did:

dubrava:/home/mantas# /etc/init.d/lm-sensors restart
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

It seems same shit again :(

Then I've read in /usr/share/doc/lm-sensors/README.Debian this:

2.6 kernels

Once you have your kernel properly configured, you need to probe for the sensors available on your system. You can use the sensors-detect program to
do this.

Hehe, if it's so simple, why don't offer debconf prompt for user about this?

OK, then I started sensors-detect program pressed Enter several times and
got this info in terminal:

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

#----cut here----
# I2C adapter drivers
i2c-isa
# I2C chip drivers
w83627hf
#----cut here----

Then, run /etc/init.d/module-init-tools


To make the sensors modules behave correctly, add these lines to /etc/modprobe.d/local and run update-modules:

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


I copied info into /etc/modules, then copied another part into /etc/modprobe.d/local and then acidently searched /etc/modprobe.d/aliases
and found, that the same alias is in /etc/modprobe.d/aliases already !!!

One more bug :( Also I think it's not hard to make script, which adds needed lines automatically, why user should manually to do this ?

OK. It seems all things, which I've found in documentation are done, so I
tried to start lm-sensors again:

dubrava:/home/mantas# /etc/init.d/lm-sensors start
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

Again the same shit :( For sure I did lsmod:

dubrava:/var/cache/apt/archives# lsmod |grep i2c
i2c_sensor 2944 1 w83627hf
i2c_isa 1920 0
i2c_core 23364 3 w83627hf,i2c_sensor,i2c_isa

So, I searched /usr/share/doc/lm-sensors/ for info how to mount sysfs, but after 2 hours searching local and web documentation found no info and
decided to report a bug.

So,
- why sensors-detect isn't started automatically (after debconf prompt)
about this ?
- why output of sensors-detect isn't copied to /etc/modules automatically ?
- why sysfs isn't mounted in /etc/init.d/lm-sensors or in some other place
automatically ?

It seems lm-sensors will be usable for simple users only, when these problems will be solved (not even advanced users can't get lmsensors working :( )

Thanks for maintaining and good luck :)

-- System Information:
Debian Release: 3.1
Architecture: i386
Kernel: Linux dubrava.homelinux.org 2.6.5-1-k7 #2 Fri Apr 30 20:46:35 EST 2004 i686
Locale: LANG=lt_LT, LC_CTYPE=lt_LT

Versions of packages lm-sensors depends on:
ii debconf [debconf-2.0] 1.3.20 Debian configuration management sy ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an ii libsensors3 2.8.7-2 Library to read temperature/voltag ii makedev 2.3.1-58 Creates device files in /dev.
ii perl 5.8.4-2 Larry Wall's Practical Extraction ii ucf 0.33 Update Configuration File: preserv

-- debconf information:
lm-sensors/negatives:



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

clone 266227
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 26627 minor
thanks

[ For the initscripts maintainer, in short the problem is that
/sys is not mounted at boot time in a system using a 2.6 kernel. ]


On Tue, Aug 17, 2004 at 07:01:16AM +0300, Mantas Kriaučiūnas wrote:

Package: lm-sensors
Version: 2.8.7-2
Severity: grave
Justification: renders package unusable

I'm trying to get working lm-sensors on debian:

dubrava:/home/mantas# apt-get install lm-sensors

[...]

Setting up lm-sensors (2.8.7-2) ...

Gtk-WARNING **: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog

Creating config file /etc/sensors.conf with new version
cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

As I don't know what is sysfs (procfs is mountend automatically on my
system by discover) and didn't got any debconf prompts about mounting
sysfs, so I did 'modprobe i2c_sensor' and then did:

sysfs should be mounted on a 2.6 kernel. It is the jobs of initscripts,
and it is surprising that it is not mounted at boot time.

dubrava:/home/mantas# /etc/init.d/lm-sensors restart
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

It seems same shit again :(

Then I've read in /usr/share/doc/lm-sensors/README.Debian this:

2.6 kernels

Once you have your kernel properly configured, you need to probe for the sensors available on your system. You can use the sensors-detect program to do this.

Hehe, if it's so simple, why don't offer debconf prompt for user about this?

Simply because the Debian Policy forbids to do that. Moreover, the "Once
you have your kernel properly configured" is important there, it means
that need to have the drivers built as modules or built into the kernel.
And it could a lot more complicated with 2.4 kernels than with 2.6
kernels.

OK, then I started sensors-detect program pressed Enter several times and
got this info in terminal:

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

#----cut here----
# I2C adapter drivers
i2c-isa
# I2C chip drivers
w83627hf
#----cut here----

Then, run /etc/init.d/module-init-tools

To make the sensors modules behave correctly, add these lines to /etc/modprobe.d/local and run update-modules:

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

I copied info into /etc/modules, then copied another part into /etc/modprobe.d/local and then acidently searched /etc/modprobe.d/aliases
and found, that the same alias is in /etc/modprobe.d/aliases already !!!

You're right, that alias is already present for 2.6 kernels.
And for 2.4 kernels, the alias is automatically added by the package.

One more bug :( Also I think it's not hard to make script, which adds needed lines automatically, why user should manually to do this ?

Because some users prefer to build the driver in hard in their kernel,
some others prefers to load them manually, and moreover, they maybe more
than one module possible for the same device.

[...]

So,
- why sensors-detect isn't started automatically (after debconf prompt) about this ?

Explained before. However, I'll add a debconf note to explain how to
configure the kernel modules, though it is already explained in /usr/share/doc/lm-sensors/README.Debian.

- why output of sensors-detect isn't copied to /etc/modules automatically ?

Explained before. It's better to let the users decide, and copy/paste is
not a very difficult thing.

- why sysfs isn't mounted in /etc/init.d/lm-sensors or in some other place
automatically ?

As said, it is not the job of lm-sensors. I have reassigned a copy of
this bug to initscripts.

It seems lm-sensors will be usable for simple users only, when these problems will be solved (not even advanced users can't get lmsensors working :( )

I don't want to feed the troll, but I know a lot people that can be
defined as "simple users" using lm-sensors. Without the problem of sysfs
(which I repeat doesn't come from lm-sensors), you would have configured
it easilly.

Bye,
Aurélien

--
.''`. Aurelien Jarno GPG: 1024D/F1BCDB73
: :' : Debian GNU/Linux developer | Electrical Engineer
`. `' [email protected] | [email protected]
`- people.debian.org/~aurel32 | www.aurel32.net


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)

From: [email protected]

On Tue, 17 Aug 2004 19:37:32, Aurelien Jarno wrote:

clone 266227
reassign -1 initscripts
retitle -1 /sys not mounted at boot on a 2.6 kernel
retitle 266227 Should explain how to configure
severity 26627 minor
thanks

[ For the initscripts maintainer, in short the problem is that
/sys is not mounted at boot time in a system using a 2.6 kernel. ]

Cannot reproduce. I've installed the latest sysvinit packages
on systems with 2.4 and 2.6 kernels and have never seen the
problem. In fact, initscripts tries really hard to mount /sys.

Is there any way to reproduce this? If not, it's a local problem
aka "customization" on the reporters' system.

Wait a minute .. is the reporter using the latest glibc and
a sysvinit package from woody, perhaps? glibc (libc6) used
to mount /sys, but doesn't do that anymore - if lm-sensors
wants /sys available, it needs to depend on sysvinit (>= 2.86-1).

If so please assign this bug back to lm-sensors.

Please depend on sysvinit, not initscripts! Sysvinit will pull
in initscripts automatically, which is preferable for a smooth
woody -> sarge upgrade.

On Tue, Aug 17, 2004 at 07:01:16AM +0300, Mantas Kriaučiūnas wrote:

Package: lm-sensors
Version: 2.8.7-2
Severity: grave
Justification: renders package unusable

I'm trying to get working lm-sensors on debian:

dubrava:/home/mantas# apt-get install lm-sensors

[...]

Setting up lm-sensors (2.8.7-2) ...

Gtk-WARNING **: cannot open display:
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog

Creating config file /etc/sensors.conf with new version
cp -f /usr/share/lm-sensors/sensors.conf.eg /etc/sensors.conf
cp -f /usr/share/lm-sensors/sensors.conf.eg /var/lib/ucf/cache/:etc:sensors.conf
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

As I don't know what is sysfs (procfs is mountend automatically on my system by discover) and didn't got any debconf prompts about mounting sysfs, so I did 'modprobe i2c_sensor' and then did:

sysfs should be mounted on a 2.6 kernel. It is the jobs of initscripts,
and it is surprising that it is not mounted at boot time.

dubrava:/home/mantas# /etc/init.d/lm-sensors restart
Setting sensors limits:Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
Can't access procfs/sysfs file
Unable to find i2c bus information;
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
For older kernels, make sure you have done 'modprobe i2c-proc'!
done.

It seems same shit again :(

Then I've read in /usr/share/doc/lm-sensors/README.Debian this:

2.6 kernels

Once you have your kernel properly configured, you need to probe for the sensors available on your system. You can use the sensors-detect program to do this.

Hehe, if it's so simple, why don't offer debconf prompt for user about this?

Simply because the Debian Policy forbids to do that. Moreover, the "Once
you have your kernel properly configured" is important there, it means
that need to have the drivers built as modules or built into the kernel.
And it could a lot more complicated with 2.4 kernels than with 2.6
kernels.

OK, then I started sensors-detect program pressed Enter several times and got this info in terminal:

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

#----cut here----
# I2C adapter drivers
i2c-isa
# I2C chip drivers
w83627hf
#----cut here----

Then, run /etc/init.d/module-init-tools

To make the sensors modules behave correctly, add these lines to /etc/modprobe.d/local and run update-modules:

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

I copied info into /etc/modules, then copied another part into /etc/modprobe.d/local and then acidently searched /etc/modprobe.d/aliases and found, that the same alias is in /etc/modprobe.d/aliases already !!!

You're right, that alias is already present for 2.6 kernels.
And for 2.4 kernels, the alias is automatically added by the package.

One more bug :( Also I think it's not hard to make script, which adds needed
lines automatically, why user should manually to do this ?

Because some users prefer to build the driver in hard in their kernel,
some others prefers to load them manually, and moreover, they maybe more
than one module possible for the same device.

[...]

So,
- why sensors-detect isn't started automatically (after debconf prompt) about this ?

Explained before. However, I'll add a debconf note to explain how to configure the kernel modules, though it is already explained in /usr/share/doc/lm-sensors/README.Debian.

- why output of sensors-detect isn't copied to /etc/modules automatically ?

Explained before. It's better to let the users decide, and copy/paste is
not a very difficult thing.

- why sysfs isn't mounted in /etc/init.d/lm-sensors or in some other place
automatically ?

As said, it is not the job of lm-sensors. I have reassigned a copy of
this bug to initscripts.

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)