LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   Too Much Ram!!! need help (https://www.linuxquestions.org/questions/linux-general-1/too-much-ram-need-help-301624/)

Archalien 03-14-2005 05:25 PM

Too Much Ram!!! need help
 
Ok guys heres a newb ? for ya!

I tried installing several distros of Linux on my laptop:

FC1,2, and 3
Mandrake 10.1
Suse 9.2

All with the same problem: ultra slow!!!!
Mandrake and Suse 1 hour to boot!!!
Fedora was better at between 10-20 minutes but any time I tried updateing anything or installing new kernels the whole install got f'd up in one way or another.

With Suse 9.2 installed someone told me to remove 1 stick of ram, from 1 gig to 512, with no other modification it booted in less than 1.5 minutes!!!!!

I tried search here but could not search well enough to find a relevant thread. Can someone please point me to a resource that will help me use all of my ram!
and fix this problem. thx

SciYro 03-14-2005 05:28 PM

it might be a swap problem .. if the swap space and RAM are not aligned right, i hear things get SLOW ... i hear its supposed to be about 2X more swap space then RAM

Brian1 03-14-2005 05:48 PM

You can download memtest86+ and burn it to a floppy or cd and boot off that and let it test the memory and see if it finds any problems. Some of the test can take a while.

If you still have FC3 installed. Check in your /boot for memtest+-v1.26 If it is there then you can add it to your /boot/grub/grub.conf and boot that up. Here Is a sample of my grub.conf

Code:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,1)
#          kernel /vmlinuz-version ro root=/dev/hda8
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Fedora Core (2.6.11-rc3) Cdfs, Ntfs, Udf, Ufs, Acpi, Hermes Packet_Writing
        root (hd0,1)
        kernel /vmlinuz-2.6.11-rc3 ro root=/dev/hda8 vga=793
        initrd /initrd-2.6.11-rc3.img
title Fedora Core (2.6.11-rc3) with BootCharting On, Cdfs, Ntfs, Udf, Ufs, Acpi, Hermes Packet_Writing
        root (hd0,1)
        kernel /vmlinuz-2.6.11-rc3 ro root=/dev/hda8 vga=793 init=/sbin/bootchartd
        initrd /initrd-2.6.11-rc3.img
title Fedora Core (2.6.9-1.649)
        root (hd0,1)
        kernel /vmlinuz-2.6.9-1.649 ro root=/dev/hda8 vga=793
        initrd /initrd-2.6.9-1.649.img
title Memtest86+ (3.2)
        root (hd0,1)
        kernel /memtest86+-v3.2 ro root=/dev/hda8 vga=793
title Winblows XP Amateur
        rootnoverify (hd0,0)
        chainloader +1

I have a newer version installed but the one on default install should work fine. I mostly use this tool to run down the battery once a month.

Brian1
" Google the Linux way @ http://www.google.com/linux "

tormented_one 03-14-2005 05:53 PM

What about HiMem in the kernel? I had to activate it to get the full gig to read in my system.

Archalien 03-14-2005 06:21 PM

there is nothing wrong with tthe ram.

Its something to do with linux.
The fact that someone suggested to remove the ram and it fixed my problem means someone knows wtf is going on here.

gbhil 03-14-2005 07:27 PM

Quote:

Originally posted by Archalien
there is nothing wrong with tthe ram.

So you have probed and traced both sticks, temp tested and fill/flushed each single block to verify this?
If not, never assume the hardware is OK. But I'll agree in this case there is another reason.

Quote:

Originally posted by Archalien

Its something to do with linux.
The fact that someone suggested to remove the ram and it fixed my problem means someone knows wtf is going on here.

The problem is that you only have support for 960 megabytes of physical RAM enabled in your kernel.
Recompile your kernel with himem support or look for a pre-compiled kernel package from your distro that supports it.

Archalien 03-15-2005 11:45 AM

thankyou

Shade 03-16-2005 01:21 AM

I've never heard of having more than the supported amount of ram having adverse effects on a system.
For a while, I was running with 1 gig ram, but without himem support. Nothing slower, the machine just used only 960 of the available 1024.

I'm not sure this is the correct issue. I'd still be more prone to suspect hardware than software. Both sticks are of the same maker and speed?

--Shade

syg00 03-16-2005 02:41 AM

I'm with Shade - sounds significantly suspect to me.

Archalien 03-16-2005 06:49 PM

My ram is a matched set of High Performance/low latency-

After simply removing 1 stick of ram all speed problems have been solved, I mean it -no other modification was done!
All distros boot in under 2 minutes now!

I went into the "make menuconfig" for both kernels I have in FC3 .
Both have the himem 4GB option selected already, so I dont know what else to do????

syg00 03-16-2005 10:28 PM

You need to do some basic diagnostics.
Do both sticks (separately) work o.k. ???.
Is there a motherboard restriction on which slots the sticks must be installed in ???.

Have you run memtest as suggested above - with both sticks in.
What does dmesg show during/after one of your slow sessions ???.
Likewise /var/logs.

Personally I'm not surprised the highmem changes didn't result in any change.

J.W. 03-17-2005 02:40 AM

My 2 cents -- I agree with Shade and syg00. It's good that both sticks are identical, but if system performance goes down the drain when both are installed, my top 2 guesses would be:

1. One of the sticks is bad. If your system boots in a normal amount of time with stick "A", try seeing what happens when you remove "A" and replace it with "B". If performance is poor, then stick "B" is defective. Replace it.

2. One of your RAM slots is defective. If both "A" and "B" work correctly in slot 0, but anytime slot 0 and slot 1 are occupied the performance degrades, then your mobo is defective.

As a secondary test, and as already suggested, definitely run memtest on each stick separately (since your PC is having problems when both sticks are installed). If one of the sticks fails, then you can clearly blame that stick as the cause. If both sticks pass, but the system basically doesn't boot when both are installed, personally I'd conclude that the mobo has a problem of some sort.

In any event, that's how I'd approach the issue; others may have other/better suggestions. Good luck with it either way -- J.W.

Archalien 03-17-2005 11:47 AM

Cmon guys how many times do I have to tell you THIS IS NOT A HARDWARE PROBLEM!!!!!

The ram and motherboard are fine! Read b4 you post please.

I didnt change the himem settings, they where already set to 4gig on both kernels, so nothing was changed.

zikhermm 03-17-2005 12:19 PM

Quote:

Originally posted by Archalien
Cmon guys how many times do I have to tell you THIS IS NOT A HARDWARE PROBLEM!!!!!

The ram and motherboard are fine! Read b4 you post please.

I didnt change the himem settings, they where already set to 4gig on both kernels, so nothing was changed.


Yes, you are of course correct.
It couldn't possible be your motherboard or RAM, it MUST be Linux - an extremely stable OS that has worked for me and countless others for years exactly they way we wanted it to.

drowbot 03-17-2005 03:14 PM

I understand your frustration, but there is no need to be rude. We are reading your posts, and nothing in them states that you have done anything to rule out a problem with the RAM or motherboard. If you have run memtest and done as J.W. suggested, then please let us know so that we can provide better insight.

The people on this board are more than happy to help you, but we need to know what you have done to rule out a hardware problem, rather that you just 'shouting' at us that it is not hardware. None of us provide help for profit, or even any kind of personal benefit. We provide help out of a sense of community and shared experience. GNU/Linux is a community, and you enter that community when asking it for help. Please have some respect.

As to your problem, I also believe it may be the RAM. The fact that somebody told you to remove a stick of RAM and it fixed the problem doesn't indicate that it is an OS problem. It indicates, IMHO, that whoever suggested this course of action has suffered from a bad stick of RAM before, and suggested you start taking sticks out.


All times are GMT -5. The time now is 06:07 AM.