APM still at it(Not Resolved
Hi, Last night i posted message asking on help to aviod my system shutdown by it self. Well put statement suggested in lilo.con in the appriate localtion suggested but jut know the system in question just power off again for no good reason. I am running SuSe 7.1 Kernel 2.4.13 Mantel RPM. 512 MB RAM 10 GB (ReiserFS / ext2 /boot) Matorx Millimum 2 MB (It's work machine ) D-Link 538 TX+ 10/100 MB What noticed this occurs when memory drop below 350 MB the system shutdown when i am going in to X/Gnome. What i find strange is i am running RH 7.1 + Kernel 2.4.13 Kernel.org with exact same MB/RAM/HD/NIC etc.. and all it well with it. I have had this problems since kernel 2.4.0 . I have checked RAM with memtest and it check out i have switched ram from RH 7.1 Box with this one done memory test as well it check out but still occurs. I have always love SuSe but seriously thinking of calling it quit's with this distro. I never any problems with other distro/kernels acting like this. Any ideas :) Alex :)
You may want to fix your clock...you're stuck in last century--Jan 1 1998. * SuSe Mailling List subscriber (suse@linuxnews.dyndns.org) [011106 15:55]:
I am running SuSe 7.1 Kernel 2.4.13 Mantel RPM.
Your are running a test kernel...you shouldn't be surprised if your machine bursts into flames.
What i find strange is i am running RH 7.1 + Kernel 2.4.13 Kernel.org with exact same MB/RAM/HD/NIC etc.. and all it well with it.
Then run the vanilla 2.4.13.
I have always love SuSe but seriously thinking of calling it quit's with this distro. I never any problems with other distro/kernels acting like this.
I assume you've already shutoff APM (in the BIOS) and turned off any hardware monitoring that your BIOS may do? You've already demostrated that a plain vanilla kernel (and a 2.2) doesn't have this problem, thereby ruling out bad hardware, power supply, and overheating? Just b/c this hardware used to work fine with another distribution or OS doesn't mean a fan hasn't died or the power supply isn't about to fail. -- -ckm
Happens everytime the system shutdown by itself Christopher Mahmood wrote:
You may want to fix your clock...you're stuck in last century--Jan 1 1998.
* SuSe Mailling List subscriber (suse@linuxnews.dyndns.org) [011106 15:55]:
I am running SuSe 7.1 Kernel 2.4.13 Mantel RPM.
Your are running a test kernel...you shouldn't be surprised if your machine bursts into flames.
What i find strange is i am running RH 7.1 + Kernel 2.4.13 Kernel.org with exact same MB/RAM/HD/NIC etc.. and all it well with it.
Then run the vanilla 2.4.13.
I have always love SuSe but seriously thinking of calling it quit's with this distro. I never any problems with other distro/kernels acting like this.
I assume you've already shutoff APM (in the BIOS) and turned off any hardware monitoring that your BIOS may do? You've already demostrated that a plain vanilla kernel (and a 2.2) doesn't have this problem, thereby ruling out bad hardware, power supply, and overheating? Just b/c this hardware used to work fine with another distribution or OS doesn't mean a fan hasn't died or the power supply isn't about to fail.
--
-ckm
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
I am fully aware that i should expect issues with test kernel but i have had issues official kernel release's also. I do not assume will not have issues form distro to an other but i have never had an issues this annoying that's. If wanted to use vanilla kernel i would bother with SuSe kernel would i? Yes APM is off in the bios I have tried many thing swicthing power supply case etc... I have tried all can think. And for while i was sure the problem was gone but i was wrong. I also put a news cmos batt just incase my cmos batt was going bad. I am just fustrated with this. This first SuSe distro give me such problems my experience with SuSe is always being great so far (Since SuSe 5.2) Alex :) Christopher Mahmood wrote:
You may want to fix your clock...you're stuck in last century--Jan 1 1998.
* SuSe Mailling List subscriber (suse@linuxnews.dyndns.org) [011106 15:55]:
I am running SuSe 7.1 Kernel 2.4.13 Mantel RPM.
Your are running a test kernel...you shouldn't be surprised if your machine bursts into flames.
What i find strange is i am running RH 7.1 + Kernel 2.4.13 Kernel.org with exact same MB/RAM/HD/NIC etc.. and all it well with it.
Then run the vanilla 2.4.13.
I have always love SuSe but seriously thinking of calling it quit's with this distro. I never any problems with other distro/kernels acting like this.
I assume you've already shutoff APM (in the BIOS) and turned off any hardware monitoring that your BIOS may do? You've already demostrated that a plain vanilla kernel (and a 2.2) doesn't have this problem, thereby ruling out bad hardware, power supply, and overheating? Just b/c this hardware used to work fine with another distribution or OS doesn't mean a fan hasn't died or the power supply isn't about to fail.
--
-ckm
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
SuSe Mailling List subscriber wrote:
Last night i posted message asking on help to aviod my system shutdown by it self. Well put statement suggested in lilo.con in the appriate localtion suggested but jut know the system in question just power off again for no good reason.
I am running SuSe 7.1 Kernel 2.4.13 Mantel RPM. 512 MB RAM 10 GB (ReiserFS / ext2 /boot) Matorx Millimum 2 MB (It's work machine ) D-Link 538 TX+ 10/100 MB
Does your BIOS monitor the processor temp? Does it have a way to shutdown your system if your processor gets above a certain temp? This is what I suspect. This is independent of APM, and is actually a good thing because otherwise you may cook your processor. Make sure your processor fan(s?) turns smoothly, if it doesn't, it may be stopping and then your machine shuts down.
What noticed this occurs when memory drop below 350 MB the system shutdown when i am going in to X/Gnome.
Is this reproducable? If not, I suspect this was just coincidence.
What i find strange is i am running RH 7.1 + Kernel 2.4.13 Kernel.org with exact same MB/RAM/HD/NIC etc.. and all it well with it.
Are you saying this same machine, or another machine with the same parts?
I have had this problems since kernel 2.4.0 .
I just replaced a motherboard because both CPU fans had stopped, and the processor apparently blew at least 2 capacitors on the board. I should have had it shutdown if the temp reached a certain point.
I have checked RAM with memtest and it check out i have switched ram from RH 7.1 Box with this one done memory test as well it check out but still occurs.
It is probably NOT ram then. I doubt it is the kernel either, otherwise many others would have experienced this problem. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871 "We can stand affliction better than we can prosperity, for in prosperity we forget God." --Dwight Lyman Moody
Yes Cpu temp are monitored but the system as no option shut it's self off should it over-heat. And my cpu temp never go over 35 c.(Red ORB cooler (Not over clocking)) Alex :) "Joe & Sesil Morris (NTM)" wrote:
SuSe Mailling List subscriber wrote:
Last night i posted message asking on help to aviod my system shutdown by it self. Well put statement suggested in lilo.con in the appriate localtion suggested but jut know the system in question just power off again for no good reason.
I am running SuSe 7.1 Kernel 2.4.13 Mantel RPM. 512 MB RAM 10 GB (ReiserFS / ext2 /boot) Matorx Millimum 2 MB (It's work machine ) D-Link 538 TX+ 10/100 MB
Does your BIOS monitor the processor temp? Does it have a way to shutdown your system if your processor gets above a certain temp? This is what I suspect. This is independent of APM, and is actually a good thing because otherwise you may cook your processor. Make sure your processor fan(s?) turns smoothly, if it doesn't, it may be stopping and then your machine shuts down.
What noticed this occurs when memory drop below 350 MB the system shutdown when i am going in to X/Gnome.
Is this reproducable? If not, I suspect this was just coincidence.
What i find strange is i am running RH 7.1 + Kernel 2.4.13 Kernel.org with exact same MB/RAM/HD/NIC etc.. and all it well with it.
Are you saying this same machine, or another machine with the same parts?
I have had this problems since kernel 2.4.0 .
I just replaced a motherboard because both CPU fans had stopped, and the processor apparently blew at least 2 capacitors on the board. I should have had it shutdown if the temp reached a certain point.
I have checked RAM with memtest and it check out i have switched ram from RH 7.1 Box with this one done memory test as well it check out but still occurs.
It is probably NOT ram then. I doubt it is the kernel either, otherwise many others would have experienced this problem.
-- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871 "We can stand affliction better than we can prosperity, for in prosperity we forget God." --Dwight Lyman Moody
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
participants (3)
-
Christopher Mahmood -
Joe & Sesil Morris (NTM) -
SuSe Mailling List subscriber