Oh and for collectl, this could help: (from their homepage)
How do I configure collectl to run all the time as a service?
Use the chkconfig to change collectl’s setting to ‘on’. On boot, collectl will be automatically started. To start collectl immediately, type ‘service collectl start’.
So you could try:
chkconfig collectl on
Don’t know about sm_driveio, maybe that uses lm_sensors? (see my previous post)
Last time I looked, collectl on suse was woefully out-of-date and I tend to focus more on debian boxes these days. In any event, before going too far down the road I’d suggest downloading the tarball from sourceforge, untar it and just run INSTALL. If it’s still broken let me know via the mailing list or post something on the forum.
Took a look at this.
Surprisingly to me, it wasn’t even installed.
I noticed that although it’ll run fine by default from the CLI, running as a service is not enabled by default. Although the Unit is “loaded” it won’t “enable” for me, will look at it more closely. So, your problem doesn’t appear to be related to your upgrading, there might be a Unit configuration issue (possibly even intentional).
And, of course take a look at whether more hardware is sensor-capable on my system besides CPU and GPU temp.
As for sm_driveio (related to the KDE Drive I/O widget), I don’t know what the driver is but it was packaged with the widget installation. I don’t hold out much hope for the widget to be fixed, AFAIK the author hasn’t been heard from and hasn’t updated his software in over 2 years.
The problem with collectl (without looking more deeply into it) is that although it offers to display drive I/O data, the values are empty… So, something is amiss collecting data.
Just to be clear, all collectl does for disk stats (and most others) is to report what it finds in /proc/diskstats. If they’re coming up empty, either there really is not activity or there is something wrong with the kernel! Literally every other tool I’ve ever looked at gets its disk stats from there.
You can also try running collectl with -d4. This will have it print out all values from /proc as it’s reading them. The main purpose is for me when I’m doing development but it’s also a handy way to verify what collectl is reading if you’re not sure where it’s looking.
I guess things are done differently by this community, but for future reference if someone sends me a link I can fix it in the base package so people don’t have to worry about patches. That was they can also download the latest bits from sourceforge if the suse distro gets behind.
On 2013-04-18 14:26, markseger wrote:
> wolfi323;2547978 Wrote:
>> But regarding collectl I just found this:
>> So this should be fixed soon in 12.3 as well, I guess…
> I guess things are done differently by this community, but for future
> reference if someone sends me a link I can fix it in the base package so
> people don’t have to worry about patches. That was they can also
> download the latest bits from sourceforge if the suse distro gets
Just a comment.
Most developers/packagers do not read the forums, they tend to use more
the mail list. So they will probably not read your request.
The package maintainer at openSUSE could use that information, I guess.
You could simply add it to the bugzilla - same login as in these forums.
The general policy at openSUSE is that packages do not get updated after
a release, but security bugs and important things get backported and the
original released version is patched.
On the other hand, there are many repositories besides the official
ones, and those tend instead to update the packages they provide.
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)