PCMech Forums - View Single Post

shafe1 · 07-11-2000, 08:41 AM

After X crashes, I have to log in as root and run fsck on each "/" "/home" and "/programs" I made the files systems when I first set up the system. after I clean these, I can usually login again (to X or console as a regular user) after this is done. Some times the crash creates a core file some times it doesn't (at least that I could find) it seems to create one if it crashes while some one is logged on and not when it dumps X during logout. I'm fairly sure its not the card because after the screen goes blank it will come back on when you move the mouse, but llike I said after that it may lose X with just a click of the mouse on the desktop or when I'm logging out.
The storage device is just running off the standard IDE port on the motherboard. The Video card worked fine in Windoze. The fact that the timing of these incidences (after the system has blanked the screen, I usually don't have the problems if the user is continaully on the system and then shutdown)is what pointed me toward screen saver or APM (which I first turned off in the BIOS, and then When I read the error in .xsession-errors about xset I read the man pages on it).
I've even tried to have x logged out to the login screen and switched over to the console screen during times when the system wasn't going to be used for a while (didn't help.. it was just a thought). I know with a UNIX based system I should rarely have to shutdown the computer, but I have to do it everyday. About core files, I hadn't really checked how big they were, but I remember from working with UNIX that there didn't seem to be a lot of useful (for amdins and normal users) info in them... they were more for programmers if I remember right. But I can look into it. I just figured with how things were happening (and since I know it has caused problems in the past, and I really don't need or want it) turning off the APMD features was an obvious place to start trying to resolve this problem.
All in all I still prefer Linux to Windoze, I haven't had one General protection fault in ages, and the crashes from clicking the mouse on something are few (It mostly crashes... the screen goes black or gray and the cursor sits in the upper left corner blinking) when I'm logging out. Just the family is getting tired of having to wait until I get there to clean it so they can use the computer. :-) My desire for the time being is to get this system running the way it should, then when I get my family a new computer (hopefully they'll love Linux by then) I can do all the playing and configuring that I want to on this old system. I just want to get a stable OS, working properly. If it takes shutting down some of the nice to have extras, then that's what I'll do. BTW, EX, Can you think of anything else that may be causing this besides a faulty video card or the an APM incompatiblity? Should I try using frame buffers and standard VGA for the monitor, and then running the virtual desktops at 800X600 even though I set the deafult to 640X480? I've looked in books and can't seem to find a reference for this type of problem.
Thanks again,
Me!

PS.
I boot to runlevel 5 and have xstart automatically. I'm trying to keep startup as simple as possible for my family, so they don't have to worry about starting X, they can just turn on the computer and go log-in to a graphical environment. Afterall, they're used to having Windoze. Waht can I say it was a Windows world for a long while
:-(
[This message has been edited by shafe1 (edited 07-11-2000).]

[This message has been edited by shafe1 (edited 07-11-2000).]

[This message has been edited by shafe1 (edited 07-11-2000).]

07-11-2000, 08:41 AM	#7
shafe1 Member (6 bit) Join Date: Apr 2000 Location: Florida Posts: 58	After X crashes, I have to log in as root and run fsck on each "/" "/home" and "/programs" I made the files systems when I first set up the system. after I clean these, I can usually login again (to X or console as a regular user) after this is done. Some times the crash creates a core file some times it doesn't (at least that I could find) it seems to create one if it crashes while some one is logged on and not when it dumps X during logout. I'm fairly sure its not the card because after the screen goes blank it will come back on when you move the mouse, but llike I said after that it may lose X with just a click of the mouse on the desktop or when I'm logging out. The storage device is just running off the standard IDE port on the motherboard. The Video card worked fine in Windoze. The fact that the timing of these incidences (after the system has blanked the screen, I usually don't have the problems if the user is continaully on the system and then shutdown)is what pointed me toward screen saver or APM (which I first turned off in the BIOS, and then When I read the error in .xsession-errors about xset I read the man pages on it). I've even tried to have x logged out to the login screen and switched over to the console screen during times when the system wasn't going to be used for a while (didn't help.. it was just a thought). I know with a UNIX based system I should rarely have to shutdown the computer, but I have to do it everyday. About core files, I hadn't really checked how big they were, but I remember from working with UNIX that there didn't seem to be a lot of useful (for amdins and normal users) info in them... they were more for programmers if I remember right. But I can look into it. I just figured with how things were happening (and since I know it has caused problems in the past, and I really don't need or want it) turning off the APMD features was an obvious place to start trying to resolve this problem. All in all I still prefer Linux to Windoze, I haven't had one General protection fault in ages, and the crashes from clicking the mouse on something are few (It mostly crashes... the screen goes black or gray and the cursor sits in the upper left corner blinking) when I'm logging out. Just the family is getting tired of having to wait until I get there to clean it so they can use the computer. :-) My desire for the time being is to get this system running the way it should, then when I get my family a new computer (hopefully they'll love Linux by then) I can do all the playing and configuring that I want to on this old system. I just want to get a stable OS, working properly. If it takes shutting down some of the nice to have extras, then that's what I'll do. BTW, EX, Can you think of anything else that may be causing this besides a faulty video card or the an APM incompatiblity? Should I try using frame buffers and standard VGA for the monitor, and then running the virtual desktops at 800X600 even though I set the deafult to 640X480? I've looked in books and can't seem to find a reference for this type of problem. Thanks again, Me! PS. I boot to runlevel 5 and have xstart automatically. I'm trying to keep startup as simple as possible for my family, so they don't have to worry about starting X, they can just turn on the computer and go log-in to a graphical environment. Afterall, they're used to having Windoze. Waht can I say it was a Windows world for a long while :-( [This message has been edited by shafe1 (edited 07-11-2000).] [This message has been edited by shafe1 (edited 07-11-2000).] [This message has been edited by shafe1 (edited 07-11-2000).]