MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Originally posted by xavierh ........fixed the apcupsd problem. The issue was that the usb device path change on this new version, therefore it was nto detecting it properly and the service could not start because of that....
Can you post here how you fixed this? I have the same problem with the USB device not being detected; it was working just fine under Mdk 9.2.
And if you have time to explain how you got lm_sensors to work, that's the other issue I'm trying to solve with no success right now! Again, they were pretty easy to get working under 9.2 . Now I get this message:
Code:
For 2.6 kernels, make sure you have mounted sysfs and done
'modprobe i2c_sensor'!
make sure that you have the specific motherboard model that you are using, kernel version, lm_sensors version and they will put you on the right track...
Thanks very much! I'll get going on this stuff either tonight or tomorrow. Spent all day trying to get things right and about out of my mind...
(Edit three minutes later) Got apcupsd fixed and working! If you're ever in Kansas City, I owe you a dinner or two! I'll try the lm_sensors tomorrow. Not nearly so important.
Originally posted by jonr Thanks very much! I'll get going on this stuff either tonight or tomorrow. Spent all day trying to get things right and about out of my mind...
(Edit three minutes later) Got apcupsd fixed and working! If you're ever in Kansas City, I owe you a dinner or two! I'll try the lm_sensors tomorrow. Not nearly so important.
Glad to help amigo.... let us know how it goes with the sensors....
Originally posted by xavierh Glad to help amigo.... let us know how it goes with the sensors....
I got the sensors apparently sensing, but their results don't show up in gkrellm, even in the version for Mdk 10.1 that I replaced my older version with. The only thing that came up missing in checking out the sensors was the max6650 module that reads the fan speed. I have no idea how to supply that. But the temperatures don't show in gkrellm, either. Under 9.2, I had the CPU temperature, the ambient temperature inside the computer case, and the speed of the fan mounted on the CPU all showing pretty accurately. Now there's nothing and the sensors settings are grayed out in the gkrellm configuration, as though sensors weren't working.
Originally posted by jonr I got the sensors apparently sensing, but their results don't show up in gkrellm, even in the version for Mdk 10.1 that I replaced my older version with. The only thing that came up missing in checking out the sensors was the max6650 module that reads the fan speed. I have no idea how to supply that. But the temperatures don't show in gkrellm, either. Under 9.2, I had the CPU temperature, the ambient temperature inside the computer case, and the speed of the fan mounted on the CPU all showing pretty accurately. Now there's nothing and the sensors settings are grayed out in the gkrellm configuration, as though sensors weren't working.
when you open a console and issues teh sensors command, what does it do? are the results accurate? if thats the case, then the issue is in gkrellm. open gkrellm configuration and go the sensors area.each fan, temperature and voltage area have 3 columns in gkrellm: sensor, enable and label. the sensor column will have the name of he sensor that will correspond to what lm_sesors detected. does it match?
Originally posted by xavierh when you open a console and issues teh sensors command, what does it do? are the results accurate? if thats the case, then the issue is in gkrellm. open gkrellm configuration and go the sensors area.each fan, temperature and voltage area have 3 columns in gkrellm: sensor, enable and label. the sensor column will have the name of he sensor that will correspond to what lm_sesors detected. does it match?
Here's what issuing the "sensors" command results in; I don't see any actual sensed data here:
Code:
[root@bodhisattva home.jon.backup]# sensors
eeprom-i2c-0-52
Adapter: SMBus Via Pro adapter at 0400
Memory type: SDR SDRAM DIMM
Memory size (MB): 128
eeprom-i2c-0-51
Adapter: SMBus Via Pro adapter at 0400
Memory type: SDR SDRAM DIMM
Memory size (MB): 128
eeprom-i2c-0-50
Adapter: SMBus Via Pro adapter at 0400
Memory type: SDR SDRAM DIMM
Memory size (MB): 128
The table in the "sensors" area of the gkrellm configuration just shows:
Temperatures
Fans
Voltages
and nothing else; the other two columns are empty and the adjustment areas are grayed out.
In other words, just the way it looks on an installation without any lm_sensors.
I followed these instructions obtained by running sensors-detect:
Code:
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe max6650
modprobe eeprom
modprobe via686a
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
(I added the last part to /etc/rc.sysinit.)
And when I rebooted, I got "No sensors found!" (with the exclamation mark).
Running "sensors" after rebooting got the same "No sensors found!"
Seems strange, or maybe not. I'm over my head. I never had to go through these maneuvers to get them working with 9.2--I know the 2.6 kernel makes it all different.
Originally posted by jonr Update on lm_sensors installation challenge:
I followed these instructions obtained by running sensors-detect:
Code:
To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-viapro
modprobe i2c-isa
# I2C chip drivers
modprobe max6650
modprobe eeprom
modprobe via686a
# sleep 2 # optional
/usr/local/bin/sensors -s # recommended
#----cut here----
(I added the last part to /etc/rc.sysinit.)
And when I rebooted, I got "No sensors found!" (with the exclamation mark).
Running "sensors" after rebooting got the same "No sensors found!"
Seems strange, or maybe not. I'm over my head. I never had to go through these maneuvers to get them working with 9.2--I know the 2.6 kernel makes it all different.
Computer still functions, though...
As the late Ray Charles would say: lets take it from the top.......
what motherboard you got? The reason i ask is that it is very important, for lm_sensors (at least on 10.1 since I di not have those issues in previous versions). to only load the modules that are necessary. I have also found that that once to do a modprobe to load a particular module it will stay there "per secula seculorum" (for ever an ever!!!) no matter how many reboots you do afterwards.
my suggestiong would be do first form the console (under root) an lsmod, paying close attention to the modules tha you described before. if they are loaded (which they will be), then do an modprobe -u [modulename] and unload all those modules.
form what I can se you need to unload the following modules: max6650, eeprom, via686a, i2c-viapro, i2c-isa, i2c-dev (the last one with "sort of" disable lm_sensors.
After you unload them, then do a sensors-detect, again checling which sensors are actually being detected and hopefully it will work this timew (I know I had to do that after I upgraded to 10.1 from 10.0. Hopefully this will work for you too....
if not, then use thatsite and open a ticket with them. They answered me in less that 24 hours amigo....
Originally posted by xavierh ... good luck and let us know how it goes...
Still no sensors found last time I rebooted after removing those modules. However, I
didn't take those lines out of sysinit.rc first. I've now removed them and next time I
boot I'll see what happens. (I also removed the modules with modprobe -r again.
By the way, though sensors-detect finds MAX6650 with a "confidence 4" for max6650
module, modprobe doesn't like either spelling, or other variants I tried, and keeps
saying "FATAL" not found. Oh, well.
You spent a lot of time trying to help me. Thanks! I've got a few other things to do,
believe it or not, but I'll keep experimenting and see if I can get the sensors to work
eventually. If not, it's not too important; I just like to keep an eye on the temperature
of the CPU, mainly.
If you do the upgrasde from kde 3.2 to kde 3.3 you will need to change switch to kde menus before doing the upgrade. After the upgrade menudrake does not work and you need to use kde menu editor to edit the menus. to do this, create a folder called .menu in your home directory and inside it you need to create a file whose named should correspond the the one inside the kde-menu shell script....
If somebody has any questions on this please let me know...
[QUOTE]Originally posted by opjose
[B]That makes sense as Mandrake hasn't switched over to 3.3 yet.
When you refer to the "download sidebar" are you talking about the graphic that appears on the menu? file:/home/alvaro/Desktop/snapshot1.png[IMG]file:/home/alvaro/Desktop/snapshot1.png[/IMG]
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.