MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've been using Mandrake 10.1 now without any problems for almost 6 months. Now, it has started randomly shutting itself down. I get a message on the screen saying 'Power saving enabled' and then the system shuts down. I've tried disabling acpid, and turning off acpi in the kernel (booting with acpi=off in lilo.conf), with no luck.
I googled for the problem and the closest I found was a bad video card, but the video card is on the motherboard, so I got a new video card, put it in, and disabled the onboard video card, but the problem remains. Sometimes, the system will only stay up for a few minutes before shutting down, barely long enough to do anything.
I'm a very seasoned linux user with about 7 years of linux experience, but this problem is baffling me. If anyone has any ideas, I'd appreciate it.
I'm not sure if this helps, but if I leave the computer off for a while (like overnight), it will stay up for a little longer (10-20 minutes) before shutting down, but after the problem starts, it will only stay up for a minute or two. Could it be an overheating problem? If so what could I do to fix it? I've visually checked the fans and they are spining, but I can't tell if they are spining fast enough.
System specs: AMD Athlon XP, Asus A7S266-VM/U2 motherboard, 512MB.
I would appreciate any ideas, but I want to be sure it's not a software problem before I try and get new hardware.
- check /var/log/messages
- try to install the sensors "package" and "gkrellm" and watch temperature
- keep a root window open and try "dmesg | tail -n 50 | tee /tmp/messages.out" when system shuts down
Ya, heat sensors will preemptively kill a machine. Check you heatsinks and fans for dust/wear. Bad connections to fans will freak it out too, so check the connections for oxidation/etc.
A quick check for this funtion is to boot you machine, with the case open, and pull the cpu fan cord, you should see a warning, and the machine will power down after 2-3 secs. (sounds scary, I know, but no harm done if it's unpluged for only a few secs)
Thanks for the info. So I installed the sensors package and it has four temperatures:
Temp: 88C (Max 90C) This fluxuates, and sometimes hits 90C
MBTemp: 64C (Max 40C)
CPUTemp: 36C (Max 45C)
Temp3: 21C (Max 45C)
I'm not sure if the labels are correct or not. So if the processor (or MB) is running too hot, I should just have to add some more fans or will it mean that the processor or motherboard is faulty? I'm also getting the following alarms in the /var/log/messages from sensord:
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: VCore 1: +1.65 V (min = +1.42 V, max = +1.57 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: VCore 2: +1.60 V (min = +2.40 V, max = +2.61 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: +3.3V: +5.60 V (min = +3.14 V, max = +3.46 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: +12V: +7.17 V (min = +11.39 V, max = +12.61 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: -12V: -16.32 V (min = -12.63 V, max = -11.41 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: -5V: -10.25 V (min = -5.26 V, max = -4.77 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: Stdby: +0.00 V (min = +4.76 V, max = +5.24 V) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: fan2: 0 RPM (min = 2657 RPM, div = 2) [ALARM]
May 11 21:30:02 pcp09740815pcs sensord: Sensor alarm: Chip it87-isa-0290: fan3: 0 RPM (min = 2657 RPM, div = 2) [ALARM]
You MB sensor is prolly under your cpu.
(sounds dirty, or you cpu is aging and running hot)
I would try in this order:
clean all dust, ect
Remove hardware you don't use (dialup modem, ect)
new (good+ quality) heatsink + fan for cpu
The logs look like the program isn't working well with your mobo, some of the obviously wrong data points can be ignored, but see if there's anything you can do to drop those voltages (did someone try to overclock your machine?)