| Suse/Novell This Forum is for the discussion of Suse 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
07-04-2005, 07:34 AM
|
#1
|
|
Member
Registered: Nov 2004
Location: Scotland
Distribution: Suse 10 - Running KDE
Posts: 314
Rep:
|
Crash, Crash, Crash, Crash and You Guessed it Crash!
Hello
I am running Suse 9.2 on the KDE enviroment, I have been running it for some months with no real problems with system stability, up till a few weeks ago, my system has no started freezing up a lot, crashing and rebooting when I am in the middle of doing stuff.
So when this started happening I tried a few things, but nothing seemed to stop this from happening, so I decided to do a fresh install and wipe the hardrive, so I did this, and it seemed to be running smother, but now it has started doing it again!
Any ideas? This is driving me crazy! I need a stable system 
Im not exactly sure what to do about it, is there some way to find out what is causing this?
The only thing I have changed in the default settings of the install is the make of the monitor, as it seemed to get that wrong, and I upped the resoloution from 1024
and the colours from 16bit to 24bit, I have now set that back to the default to see if that will, help, it does seem to be running a little better now, anyone know if this will help and anything else I can do to stabilise my system?
If this keeps happening, I will have to do the unthinkable and return to windows
I really dont want to do that as I have come to like linux a lot.
Thanks 
|
|
|
|
07-04-2005, 08:25 AM
|
#2
|
|
Senior Member
Registered: Mar 2004
Location: Munich
Distribution: SuSE 12
Posts: 3,511
Rep:
|
Does your graphics card use shared memory? If this is the case I would suggest to run a memory test from your boot CD.
|
|
|
|
07-04-2005, 08:28 AM
|
#3
|
|
Member
Registered: Nov 2004
Location: Scotland
Distribution: Suse 10 - Running KDE
Posts: 314
Original Poster
Rep:
|
Quote:
Originally posted by abisko00
Does your graphics card use shared memory? If this is the case I would suggest to run a memory test from your boot CD.
|
Thanks for your reply
Im not sure exacly what you mean by shared memory (I am just quite new to all this)
How would I run a memory test?
Thanks 
|
|
|
|
07-04-2005, 08:32 AM
|
#4
|
|
Senior Member
Registered: Mar 2004
Location: Munich
Distribution: SuSE 12
Posts: 3,511
Rep:
|
Quote:
|
Im not sure exacly what you mean by shared memory (I am just quite new to all this)
|
Many cheaper and I think all onboard graphic cards use the normal RAM of your system. Better cards have their own separate memory. Since your only change was to switch to a higher color depth (and therefore higher memory usage), I guessed it may have to do with broken RAM.
To run the test, boot from your SUSE boot CD (usually CD1) and select the memory test on the grub menu.
|
|
|
|
07-04-2005, 08:37 AM
|
#5
|
|
Member
Registered: Nov 2004
Location: Scotland
Distribution: Suse 10 - Running KDE
Posts: 314
Original Poster
Rep:
|
Quote:
Originally posted by abisko00
Many cheaper and I think all onboard graphic cards use the normal RAM of your system. Better cards have their own separate memory. Since your only change was to switch to a higher color depth (and therefore higher memory usage), I guessed it may have to do with broken RAM.
To run the test, boot from your SUSE boot CD (usually CD1) and select the memory test on the grub menu.
|
Okay thanks, I will give that a go, if it is that does that mean I would have to replace the RAM?
Also, how long does the test usually take? 
|
|
|
|
07-04-2005, 09:12 AM
|
#6
|
|
Senior Member
Registered: Mar 2004
Location: Munich
Distribution: SuSE 12
Posts: 3,511
Rep:
|
Quote:
Originally posted by little_penguin
Okay thanks, I will give that a go, if it is that does that mean I would have to replace the RAM?
Also, how long does the test usually take?
|
I am not sure about the time (might take some). If the test returns errors and you have more than one module, you should try to remove a single RAM module and run the test again, to see which one is defect. I know no other solution than to replace the defect module. It may be possible to lock the defect addresses, but I have no idea how to achieve that.
|
|
|
|
07-04-2005, 09:29 AM
|
#7
|
|
Member
Registered: Oct 2003
Location: South London
Distribution: Gentoo.
Posts: 297
Rep:
|
Possibly related, but not sure:
SUSE updated xorg-x11-libs a few back, leaving me pretty much unable to use KDE - crashes, freezes etc. I just reinstalled the orginal package. I have not been able to install the patch without the same thing happening.
L
|
|
|
|
07-04-2005, 09:32 AM
|
#8
|
|
Member
Registered: Nov 2004
Location: Scotland
Distribution: Suse 10 - Running KDE
Posts: 314
Original Poster
Rep:
|
Quote:
Originally posted by abisko00
I am not sure about the time (might take some). If the test returns errors and you have more than one module, you should try to remove a single RAM module and run the test again, to see which one is defect. I know no other solution than to replace the defect module. It may be possible to lock the defect addresses, but I have no idea how to achieve that.
|
Okay thanks  I will try giving that a go.
Actually the graphic settings that I have set my computer back to is what was sujested during the original install, does this perhaps mean the problems were originally caused by mean changing this from what it was meant to be? (I made them higher than orginal)
Would misconfiguration cause a system that would be instable and crash and freeze a lot?
|
|
|
|
07-04-2005, 09:34 AM
|
#9
|
|
Member
Registered: Nov 2004
Location: Scotland
Distribution: Suse 10 - Running KDE
Posts: 314
Original Poster
Rep:
|
Quote:
Originally posted by lacerto
Possibly related, but not sure:
SUSE updated xorg-x11-libs a few back, leaving me pretty much unable to use KDE - crashes, freezes etc. I just reinstalled the orginal package. I have not been able to install the patch without the same thing happening.
L
|
Have you tried setting your graphics/motnitor setting back to the default of what they were on your original install? This seems to have made a difference for me, but whether it will last Im not sure!
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 08:16 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|