Re: sdram and linux

1998-04-02 Thread tony mollica
thanks for the info. The motherboard recognizes the memory as sdram just fine and linux starts up ok but then the problems start. Mostly, applications stop and disappear from the desktop without warning and the file system (as fsck reports) becomes corrupted. The machine never locked up and it

Re: sdram and linux

1998-04-02 Thread Dan Hugo
tony mollica wrote: > > Hi. Just looking for a little more info. > > Just installed 64megs 168 pin sdram (replacing the 64megs of the usual > type 72 pin edo stuff) in my system and it appears > to be causing file system corruption, as indicated on boot > up by fsck (attempted boot up, actually).

sdram and linux #2

1998-03-30 Thread tony mollica
Thanks for all the replies. I can appreciate the possibility of the hdd going bad, but it has been operating flawlessly before and after trying to use the sdram, but that doesn't exclude the possibility. Tried the old mem and both the .30 and .33 kernels this morning with absolutely no problems.

Re: sdram and linux

1998-03-30 Thread Michel LESPINASSE
On Mon, 30 Mar 1998, Stephen Carpenter wrote: > anyway memtest86 boots on its own anyway... quick Q: does memtest86 > work on SDRAM ? I know it doesn't work on ECC or Parity ram? I will > dfind out tonight...I am trowing 64 MB od SDRAM in my machine (nice > upgrade from 32 MB of old SIMMs) Well

Re: sdram and linux

1998-03-30 Thread Bill Leach
It sounds a lot like memory that is not fast enough (or not enough wait states). It might also be some sort of "addressing error" that does not show up in Win. Also, did you tell lilo that you have more than 64M of memory? -- best, -bill [EMAIL PROTECTED] [EMAIL PROTECTED] [EM

Re: sdram and linux

1998-03-30 Thread tko
tony mollica writes: > > Hi. Just looking for a little more info. > > Just installed 64megs 168 pin sdram (replacing the 64megs of the usual > type 72 pin edo stuff) in my system and it appears > to be causing file system corruption, as indicated on boot > up by fsck (attempted boot up, actually)

Re: sdram and linux

1998-03-30 Thread Stephen Carpenter
can you give a little more information? I recently had a simmilar problem that munged my system ...but... it wasn't ram related (tho my RAM did go bad too..for unrelated reasons) Are you runnin gbo or hamm? There is a package that was in hamm when it was unsatble...which is on my hamm CD that I bur

Re: sdram and linux

1998-03-30 Thread Markus Lechner
tony mollica wrote: > Hi. Just looking for a little more info. > > Just installed 64megs 168 pin sdram (replacing the 64megs of the usual > type 72 pin edo stuff) in my system and it appears > to be causing file system corruption, as indicated on boot > up by fsck (attempted boot up, actually). B

Re: sdram and linux

1998-03-30 Thread Ossama Othman
I've got 128MB of ECC SDRAM in my hamm box and haven't had any problems. Some people say that you should only use SDRAM that is certified to work with your motherboard. Did you set up your BIOS to use SDRAM instead of DRAM? -Ossama _

Re: sdram and linux

1998-03-30 Thread Manoj Srivastava
Hi, This may also be indicative of incipient problems with your hard drive. Back up all your data (just in case) ... manoj -- Our business is run on trust. We trust you will pay in advance. Manoj Srivastava <[EMAIL PROTECTED]> Key C72610

sdram and linux

1998-03-30 Thread tony mollica
Hi. Just looking for a little more info. Just installed 64megs 168 pin sdram (replacing the 64megs of the usual type 72 pin edo stuff) in my system and it appears to be causing file system corruption, as indicated on boot up by fsck (attempted boot up, actually). Booting from the rescue disk and