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?

that one exaclty, the one that goes kde 3.2 download next to all the entries in the menus and read from the bottom up

Re: Update......
 

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:
...when I try to do "sensors detect."

Thanks!

APCUPSD
here is my apcupsd .conf file
UPSCABLE usb
UPSTYPE usb
DEVICE /dev/hiddev0
LOCKFILE /var/lock
UPSCLASS standalone
UPSMODE disable

the line DEVICE /DEV/HIDDEV0 is very important....on previous versions this line looked something like this:

DEVICE /dev/usb/hiddev0

lm_sensors
Since I do not know your setup (hardware, version of mdk, etc) go here:
http://secure.netroedge.com/~lm78/support.html

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... :eek:

(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.

no problem
 

Glad to help amigo.... let us know how it goes with the sensors....

Opjose any idea how to fix the banner?

Re: no problem
 

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.

Re: Re: no problem
 

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?

Opjose, any idea on that banner and how to change t?

Re: Re: Re: no problem
 

Here's what issuing the "sensors" command results in; I don't see any actual sensed data here:

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.

Update on lm_sensors installation challenge:

I followed these instructions obtained by running sensors-detect:

(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... :cool:

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....

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.

menudrake vs kde menu
 

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...

this is the one that I'm talking about
 

[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]