SlackwareThis Forum is for the discussion of Slackware 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.
I have 12.2 installed and have been doing some things with the init scripts. (Note: everything is in it's own "sandbox" so the system is unaffected)
If I leave the system on all night when I come back to it in the morning the network is down, eth0. Then I try to do anything and the system locks up, it's KDE 3.5. This looks like a memory leak to me. Has anybody else seen this kind of behavior? If so what did you find and how did you fix it?
I remember having more less similar problem with USB modem (it would disconnect after some time) and a no-name main board. I had to switch to a different mobo and everything was working fine after that.
If you use dhcpcd and are modifying rc.inet1, then you probably should add '-R' to dhcpcd so it does not overwrite /etc/resolv.conf, but I doubt anything in rc.inet1 can normally halt the system... that sounds like something from a different script.
Well I found the problem. I ran memtest and came up with a few errors. I the began the process of pulling one stick at a time ( it has 4 gigs in it) and tried to run memtest again. Now it won't boot, beep or anything else. I have learned, if the info I read was correct, that the memory controller is internal to the amd athlon x2 939 socket cpu. If that is true I have no way of telling if the problem is in the cpu or in the mother board. Because of that I just can't buy another Mb and swap all my stuff into it.
What a major pain... Now it's new mother board and cpu time. And because the system I was using is two years old the memory is obsolete also. Well at least I can still spot a memory problem, even if it wasn't a leak.
You should first use good ground techniques, either with a grounding wrist strip or at least placing yourself at the the same potential level as the system by maintaining contact with the equipment.
I would shut the power off to the system and unplug the system. Clean the card edge for the memory using strips of new clean 20# paper with denatured alcohol. Swipe in one direction with folded wet paper for the edge, a new piece for each swipe. You can use a credit card to clean the connector if that is needed by folding the paper over the end of the credit card. But first you should use dry air to blow the connector out. In the USA it can be purchased at most computer/office supply houses, even Walmart has it. Then replace the card without touching the card edge.
BTW, don't use a eraser to clean/buffer the card edge. You are doing more harm then good.
I would then run 'memtest86' for a number of passes, possibly over night. If you get errors then you have a problem. Replace the bad stick. If the memory is used with bad data/address problems then you will getting nothing but nightmares!
I would not rely on the memory test performed by the 'POST'. 'memtest86' performs several pattern tests that will exercise the cells. There are better test but 'memtest has become a standard plus it's free.
You should first use good ground techniques, either with a grounding wrist strip or at least placing yourself at the the same potential level as the system by maintaining contact with the equipment.
I would shut the power off to the system and unplug the system. Clean the card edge for the memory using strips of new clean 20# paper with denatured alcohol. Swipe in one direction with folded wet paper for the edge, a new piece for each swipe. You can use a credit card to clean the connector if that is needed by folding the paper over the end of the credit card. But first you should use dry air to blow the connector out. In the USA it can be purchased at most computer/office supply houses, even Walmart has it. Then replace the card without touching the card edge.
BTW, don't use a eraser to clean/buffer the card edge. You are doing more harm then good.
I would then run 'memtest86' for a number of passes, possibly over night. If you get errors then you have a problem. Replace the bad stick. If the memory is used with bad data/address problems then you will getting nothing but nightmares!
I would not rely on the memory test performed by the 'POST'. 'memtest86' performs several pattern tests that will exercise the cells. There are better test but 'memtest has become a standard plus it's free.
Oh it gets worse. I pulled one stick. (The manual is good at showing how the sticks should be instaled if using less then four.) And guess what it wouldn't boot, beep or anything. I then did some research and found that the memory controller is in the cpu. So I'm basically F___ed. I have no way to tell if the problem is in the cpu or in the mother board. The MB is a machspeed that came with a lifetime warranty. Yea right. It seems nobody is getting machspeed to honor the warranty.
I have been going over newegg and tiger direct looking for a good mb combo. I think the next one will be a quad core. Don't ask me why maybe for the same reasons people climb mountains, Because they are there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.