why does my 9.2 freeze every 20ish minutes?
 

Hello. I have recently installed 9.2 and am finding it freezes all the time.
It duel boots with xp (which runs ok), and i just ran a diag disk overnight
to see if the memory was duff - but no joy.

here is my hardware
seagate 120 sata hdd
512 ram
abit 7nfs mb
ati 9200 video card
adsl speedtouch
cdrom and dvd

maybe the video drivers??

I like mandrake - but this is going to drive me back to wibdows if it carrys on

cheers, ever hopefull

rossco

ok. now given up. impossible to use with the "freezes". did a complete reinstall and then made no changes but they are still there. will hang on to version 10 finishes beta unless anyone can heko.

cheers,

ross

It sound like a hardware issue. Probably a memory with a bad sector. I've seen this a few time we just replaced it and the problem went away.

is linux (and mandrake) more fussy than windows - the diag disk didn't pick up a problem, but the memort is my thought also

cheers

Which version of windows?

windows xp pro - i can happly run it for a week without crashing.

cheers,

ross

If memory serves me right Linux uses the most upper part of memory and grows down as it uses it. All Windows platforms use the lower parts of memory and grows up as it uses it. You may be just not using that section of memory in windows that linux is using. Normally Linux is a lot more forgiving with bad hardware than Windows. Case In point my firewall and file server has a defective dircectx part of the cpu. Windows will not load at all. I have MDK9.1 running since May2003 without a hiccup. If I were using Windows only I would have thrown out the process and bought new. Instead my server runs fine.. Try installing any windows os with a bad parraly port (You gonna use a network printer and wont use the parallel port) can't be done windows wont install. but Linux will

A whole week? Wow, that's gotta be some kind of record for Windows. Sombody call the Guiness Book people. LOL, JK.

Your profile says you run RedHat, why the switch to Mandrake? Anyway, a quick google search shows a ton of people have probs with Linux and your mobo, which I think is an Abit NF7-S, since 7nfs doesn't seem to exist. Some of them are even using the 2.6 kernel, so waiting for MDK 10 might not do you much good. In any case, a few seem to have fixed their probs with kernel params to disable features. Here's a random sampling of google results, I'm sure you're capable of finding the rest on your own:

http://lkml.org/lkml/2003/12/22/94
http://www.ussg.iu.edu/hypermail/lin...12.0/1241.html
http://www.linuxquestions.org/questi...003/09/2/91641

thanks guys. sorry for the mistakes - i was in a hurry to get the post out before it crashed. i'm going to look at the posts , and perhaps pull one of the ram chips out to see which one of the two is giving me the yips...

try

http://www.systemday.com/Softwares/d...bleshooter.exe

or

http://www.simmtester.com/software_u...DocMem1_45.exe

to test your memory. i recommend Troubleshooter's extended memory test, but the other program seems to work just fine.

try leaving memtest on all night from you linux side. You can boot right to memtest with some distro boot disks.

I had a problem like this, which I thought was related to my video card (also ATI), but I later found that my memory would not work correctly n dual channel mode. It took about 5 passes throug memtest before a problem showed up.

Are there anykind of thos checks but only for harddrives?? I have a similar problem but i think it could be the harddrive.

Also, thos are .exe's. They won't work on linux (i dont have WINE) right?

-jay

yeah those .exe's are for windows. i recommended them cause rosscopeeko said he had winxp. to check hard drive integrity in linux, type fsck or check out:

http://yhslug.tux.org/docs/hdtest.htm

Try power save settings. WinXP is immune to computer trying to cut the power, but not Linux. Symtoms of that are usually lost network connection (ppp and pppoe) and frozen X server.

greetings. I hope everyone is having a good doy - I am! My system has been 24 hours and counting and there is no sign off a crash in sight!

Crito, I followed your second link as a starter and disabled the cpu disconnect in bios and whey hay!! bingo - no more crashes (as yet). cheers crito, and all the rest for there suggestions.
ps. the comment of my windows box being up for a week my have been a little exageration!