LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   Problems installing new RAM in SUSE 9.3 (https://www.linuxquestions.org/questions/suse-opensuse-60/problems-installing-new-ram-in-suse-9-3-a-446364/)

I'mabadger 05-19-2006 05:37 AM

Problems installing new RAM in SUSE 9.3
 
I have a Soltek SL-75KAV motherboard, which says that I can shove different bits of ram in it at the same time (3 slots) of DIMM PC133 SDRAM. So I have two slots with 256 in each, put a new 512 stick in the third and I have issues.

THe computer turns on. It does a memory test, and that identifies that there is 1 gig in there. Once we boot up SUSE however, it gets to the line:

swsusp: Suspend partion has wrong signature?

And then does not continue.
Unfortunately I can't remember much else about the error message, so what I did was search and foudn some people had problems with KPowersave. So I booted up fine without the extra ram in, disabled KPowersave, shutoff, put the RAM back in, booted up.. the same thing happened.

I don't know how to get hold of that full output, as it doesn't give me a prompt or anything and just freezes. If anyone can help that would be great. It works without the RAM, and Soltek says I can mix'n'match, and does not get past that line with the RAM.

God Bless
Jonty

jschiwal 05-19-2006 06:04 AM

When you boot up, go to the grub menu and edit the boot parameters (on the current boot). Remove the resume=/dev/hd## and substitute "noresume".

Take a look at this link. SuSE is mentioned specifically on page 47.
https://www.linux-magazine.com/issue...re_Suspend.pdf

I hope this helps. Regards.

I'mabadger 05-19-2006 07:18 AM

Many thanks. I did that and then that wasn't a problem any more. What happens now is that it doesn't get past the line

Running /etc/init.d/boot.local done

And nothing.
Beforehand, a variety of things can fail at each start up. The only consistent thing is that further up, there is always the message:

/etc/init.d/boot.rootfsk: line 30 : 2053 Segmentation fault mount -n -o remount,rw /

Where 2053 can be 2080 and then another file fails, or 2071 and a third couple fail.
Line 30 of the above file in context is:

export FSCK_MAX_INST

rc_reset

case "$1" in #this is line 30
start)
#
# fsck may need a huge amount of memory, so make sure, it is t
here.

Any ideas? Again, it boots fine without the ram, and the above happens with the added ram.

God Bless
Jonty

jschiwal 05-21-2006 02:06 AM

Try booting up once in the safe mode. Maybe the problem will resolve itself after that. I think that you need a swap partition twice the size of ram for swsusp to function properly.

I'm also wondering whether your ram is OK, or if it is the proper type.

I'mabadger 05-22-2006 05:38 AM

Many thanks. Tried memtest-86 and it failed on the second pass.

God Bless
Jonty


All times are GMT -5. The time now is 04:55 AM.