Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Based on some suggestions I've found, I've tried adding mem=10G and mem=8G to the kernel boot parameters with no luck.
I've also tried CentOS 5.1 with the same results.
There also don't appear to be any options in the BIOS that allow me to tweak my memory settings, but the system itself *appears* to recognize the full 8GB.
Does anyone have any ideas as to what I should try next? Any input is greatly appreciated.
IIUC, your motherboard has integrated graphics. That takes a chunk of your main memory. It's hard to believe it takes that big a chunk.
I downloaded the manual for your motherboard (I'm trying to select a motherboard for a new Linux system myself, so I'm downloading a lot of motherboard manuals). I was surprised that manual gives no hint how you manage the amount of memory used by the integrated graphics.
The Asus motherboard I recently purchased for my son's Windows XP system at least gives a method of managing that. It fails to explain what the BIOS choices really mean and how they interact with Windows Driver choices, but at least there is a hint. It seems to have the ability to take up to a GB of ram for integrated graphics if you want to. I can't imagine why you would want to, and that certainly isn't the default, and you seem to be losing even more than a GB. So, I may be barking up the wrong tree.
Also, I've seen BIOS choices in many motherboard manuals for controling the size of the hole they put in the address space (I think near the end of the first 4GB). I never understood that issue (what it is for, how it interacts with Windows or Linux, etc.) and I don't seen any discussion of it in your Motherboard manual.
Lenard: No worries on the arch mismatch, but FWIW, I was originally running Centos 4.6 x86 with kernel-smp and it recognized the same (6.7GB) amount of RAM. I rebuilt the system as x86_64 to try and remedy the problem with no luck.
johnsfine: Hrm, I've got this motherboard in multiple systems and none of them have onboard video. I'm using a 512MB PCI-e video card in them. The only thing I can think of that *might* give me any memory management options in the BIOS would be a BIOS update but I don't know if a) any updates exist and b) if any updates will render my board(s) useless. (BIOS updates and I have a rotten history so I usually use them as a last resort)
I'm aware of the fact that there can be a memory-management "gap" where up to 2GB of the initial 4GB of memory can be reserved. That's why I was trying to attempt the mem=10GB boot option. I found the suggestion here:
I'd love to figure this out, because RAM issue asside, the system screams. I've got one running (5) VMware-Server virtual machines & it stays around 80-85% idle with very minimal CPU I/O wait states (having a 3ware PCI-e 9660 helps).
I think the 7602176k to 8388608K drop is probably due to the video sharing thing. The 6627648k to 7602176k drop is another issue. You might try playing around with the bios hole setting to see if that will effect anything. The other guess would be to go over to the Centos forum and see if they have any ideas.
Edit: I could not find the 9660 on 3wares site. Are you sure that is the correct model #? It could be that this card is taking up the memory before the OS even sees it.
Atlastc, I followed that link about the memory-management "gap" (because I want to set up a similar system myself soon) but I didn't understand it. If you find any clearer explanation, please report it back to this thread.
Lazlow, I'm pretty sure the 7602176k represents physical ram plus swap file, so it should be ignored for this discussion. I think the ram size is 6627648.
Lazlow: The 9660 was a typo - I meant 9650 (http://www.3ware.com/products/serial_ata2-9650.asp). The 3ware 9650 has 256MB of onboard DDR2 memory used for write-caching which really helps performance. I've got an (8) port 9650 in a different motherboard that doesn't have these RAM issues.
Unfortunately my BIOS is very basic and doesn't have anything geared towards messing around with memory (that I can find). There's an entire screen dedicated to overclocking (and I could overclock the RAM config), but again, the BIOS *seems* to be reporting the full 8GB.
Johnsfine: The best I could come up with on the memory mapping is this:
As I understand it, your motherboard (or OS, I guess) can reserve portions of RAM for various functions, thus leaving less for normal system operations. I think the poster from my previous link was trying to show ways of tricking the kernel into handling memory differently(?)
I've cross-posted this into the CentOS 4 hardware forums, but they're kind of quiet & I've received no responses:
I just went over to take another look at the system/BIOS to gather more info. The motherboard version is 1.0 and the running BIOS is "F4". If you look at this link:
You'll see that they're currently at BIOS revision "F12" and at "F5" they list "Improve DDR2 compatibility"...
So I'm wondering if a BIOS update would a) potentially address this issue and b) give me more options to tweak memory settings...
I also scoured through the BIOS again - there are absolutely no onboard video options (there is no actual onboard video port). The only "tweaking" options are under the "MB Intelligent Tweaker" section, but it mainly deals with CPU/RAM voltage and clock speed...
I'm not so sure I want to try a BIOS update because I don't have any spares of this particular model. I'll have to ponder this one.
Distribution: Debian, Ubuntu, CentOS; in days past Fedora, Solaris, SunOS, 4.2BSD, 4.3BSD, SVR4, AIX, HP-UX
Posts: 101
Rep:
I have very similar problems with a very similar setup. My board is rev2 of the GA-M57SLI-S4, the OS is Fedora 8 (x86_64), and I have 4GB (i.e. 4x1) of memory. The BIOS recognizes all 4GB, but free and the system monitor report only ~3.2GB.
I posted a question to FedoraForum on this subject, and I responded to the thread on the CentOS forums as well. There is also another similar thread here at LinuxQuestions.
For those interested, this board has no onboard video.
This system was upgraded from 2GB (i.e. 2x1) to 4GB (4x1). When I first booted into the BIOS after adding the other two 1GB sticks, the BIOS only reported ~3.2GB. After I reset the CMOS and rebooted into the BIOS, it reported all 4GB. Fedora still only sees ~3.2, however.
Distribution: Debian, Ubuntu, CentOS; in days past Fedora, Solaris, SunOS, 4.2BSD, 4.3BSD, SVR4, AIX, HP-UX
Posts: 101
Rep:
Quote:
Originally Posted by lazlow
Ordinary
Are you running 32bit or 64bit?
Lazlow, thanks for your interest. As I stated, I am running Fedora 8 x86_64. I guess that it may not be obvious that's the 64 bit version.
Actually, I think I have managed to fix my problem. I think it was a buggy and lying BIOS. Sometimes it would show 4095MB extended memory and sometimes 3327MB depending on its mood. That was BIOS FE for the Gigabyte GA-M57SLI-S4 rev2 (to which I had upgraded for its virtualization support). Updating to BIOS FFC (published 4 Jan 2008) seems to have fixed my memory access problem, and now I can see all of my new memory. Maybe this info will help someone else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.