Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Tried using one memory stick at a time. Same problems. Also tried to induce a freeze by stressing motherboard with a nonconductive probe; nothing.
Presently I am running off the onboard video output with the GPU physically removed. Logically I can't see how reinstalling the GPU and installing the Nvidia drivers could eliminate the problem. I am open to trying it if everybody is out of other ideas.
Put the hardware back together and don't touch it again!
Next time the system "freezes," try Ctrl+Alt+F3 or some other F-key. If you are transported to a command-prompt (Ctrl+Alt+F1 should take you back ...), then you've just identified your problem ... as a software problem.
99.9% of the time, when you have an actual hardware problem, the system doesn't "freeze." It dies. (As in: "four paws up, and 'X's instead of eyes." Time to get a shovel ...)
You probably have an error in your XWindows/XOrg configuration. Or, you might have a sporadic failure in the video hardware.
Put the hardware back together and don't touch it again!
Next time the system "freezes," try Ctrl+Alt+F3 or some other F-key. If you are transported to a command-prompt (Ctrl+Alt+F1 should take you back ...), then you've just identified your problem ... as a software problem.
99.9% of the time, when you have an actual hardware problem, the system doesn't "freeze." It dies. (As in: "four paws up, and 'X's instead of eyes." Time to get a shovel ...)
You probably have an error in your XWindows/XOrg configuration. Or, you might have a sporadic failure in the video hardware.
Clicked on Firefox, screen goes to diagonal lines. Ctrl-Alt-F3 does nothing. Also tried Ctrl-Alt-F-1-thtough12.
Tried using one memory stick at a time. Same problems. Also tried to induce a freeze by stressing motherboard with a nonconductive probe; nothing.
Presently I am running off the onboard video output with the GPU physically removed. Logically I can't see how reinstalling the GPU and installing the Nvidia drivers could eliminate the problem. I am open to trying it if everybody is out of other ideas.
I saw the nouveau errors from your log output, that's why I suggested to try nvidia drivers, your onboard video has NVIDIA GeForce 7025 chipset so nvidia driver should work with it too...
Maybe there is something wrong in your Xorg conf file also (as sundialsvcs said). Freeze happens only in a X session?
I saw the nouveau errors from your log output, that's why I suggested to try nvidia drivers, your onboard video has NVIDIA GeForce 7025 chipset so nvidia driver should work with it too...
Maybe there is something wrong in your Xorg conf file also (as sundialsvcs said). Freeze happens only in a X session?
Located the NVIDIA driver for the 7025 chipset and have started installation which has become an adventure in itself. I will get back and post results later today or tomorrow.
You may need to blacklist nouveau in /etc/modprobe.d (if nvidia installer does not it automatically)
Just create a file with name like 'disable-nouveau.conf' in /etc/modprobe.d with content:
You may need to blacklist nouveau in /etc/modprobe.d (if nvidia installer does not it automatically)
Just create a file with name like 'disable-nouveau.conf' in /etc/modprobe.d with content:
Code:
blacklist nouveau
options nouveau modeset=0
Already did this. The next complaint from the NVIDIA installer program is:
The good news is that Firefox now loads and works smoothly. No freezups after a few hours of normal use.
The bad news is that upon powering up, after logging in, startx goes to a blank screen with the message:
"OUT OF RANGE
Please change your PC input signal resolution."
Ctrl-Alt-F3 takes me back to terminal mode and asks for a login. Startx now takes me to the Fluxbox desktop and all is well. I would actually like to go back to a lower resolution with text that isn't microscopic.
Normally random unpredictable behavior is RAM. But with a CPU that old that is considered missing modern architectures it could be other things. You could try running a 32 bit distro and see if the issue persists. At a minimum do not use nouveau as I had similar issues to yours last time that I did. nVidia has pretty much sabotaged that driver to favor theirs. Under the proprietary nvidia driver I didn't have random crash issues, but I did have other issues.
If you're running from storage that is attached to a usb bus, you might try using a powered usb hub. If you lose access to your storage (it's usb after all) while using your storage, that'll crash a system. And our modern usb sticks can be power hungry little things. Especially on the same hub as a webcam or networking dongle. I find SDHC cards and a reader to be more forgiving in the needy power department while having tolerable IO speeds. Just have a couple at hand and expect the medium to fail every six months +/- six months.
Perhaps nvidia-xconfig can help change your display settings. Using xrandr for non-nvidia gpus can do that too and many desktops like gnome or kde lets you change those settings in a gui.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.