Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369
Rep:
RAM allocation
Yesterday I upgrade my RAM from 2 GB to 4GB and my BIOS
Looking into my BIOS hardware spec it says total RAM 4096 MB
Appropriate 640 MB
Available 3456 MB
According to the shop where I buy my computer it is because graphic card
being a Nvidia Gforce 6200 turbo cash allocated in advance that amount of RAM.
My question is this true or not ?
Looking in My computer in opensuse it is says Total RAM 3.3 GB caches 253,9 MB available 2.9 GB
So he seems to wright about the preallocation , but still is this true ?
And if so why ?
My MOBO ASUS P5LD-X/I333
Thanks in advance
This is a common problem: only being able to access 3.3GB of 4.0GB of RAM when using a 32 bit kernel. What you need to do to get access to the rest is to install a PAE enabled kernel. I don't know what it's called on your distros, but it might be called bigmem or something like that. If you have a 64 bit CPU, you could always load the 64 bit version of your OS.
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369
Original Poster
Rep:
Quote:
Originally Posted by Quakeboy02
This is a common problem: only being able to access 3.3GB of 4.0GB of RAM when using a 32 bit kernel. What you need to do to get access to the rest is to install a PAE enabled kernel. I don't know what it's called on your distros, but it might be called bigmem or something like that. If you have a 64 bit CPU, you could always load the 64 bit version of your OS.
I refer in my original post to opensuse 64 bits version
I refer in my original post to opensuse 64 bits version
I guess I missed that, as I don't know anything about Suse numbering. You might also go into the BIOS and reduce the video memory size to the lowest possible value. Linux will normally take it back and use it for the video card, but include it in memory totals.
Ok, I actually do not see where you said you were using the 64bit version of suse, you did say 64bit cpu. You can run the 32bit version of suse on a 64bit cpu, which is why we are making a point of this. If you post the results of "uname -a " it will clear up any doubts.
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369
Original Poster
Rep:
Quote:
Originally Posted by lazlow
Ok, I actually do not see where you said you were using the 64bit version of suse, you did say 64bit cpu. You can run the 32bit version of suse on a 64bit cpu, which is why we are making a point of this. If you post the results of "uname -a " it will clear up any doubts.
The answer is Linux-XR4p 2.6.27.7.9-default # 1SMP V2008-12-04 +100
I686 I686 I386GNULinux
Which takes us right back to what Quake said in Post #4. Here is what a 64bit reports back:
Quote:
[fred@localhost ~]$ uname -a
Linux localhost.localdomain 2.6.23.15-137.fc8 #1 SMP Sun Feb 10 17:03:13 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
Personally I consider using the PAE/Bigmen solution to be a hack. It converts the register from 32bit to 36bit(?,never can remember) in software, which is by its very nature slower. Not all applications will behave well using PAE either. On the other hand switching to 64bit (on most distros) requires a complete fresh install. I guess I would consider just living without the .8gig until you are ready to update, it will not cause any issues.
Distribution: Mandriva 2009 X86_64 suse 11.3 X86_64 Centos X86_64 Debian X86_64 Linux MInt 86_64 OS X
Posts: 2,369
Original Poster
Rep:
Well I did a total fresh install with X686 , but the total amount of RAM is still 3.3 GB and the free RAM memory even drops down a bit because X686 use more as a cashes.
So it seems to me that my retailer was correct when he said that difference in the BIOS between the 4 GB and the available of 3.3 GB is caused by the fact that it is preallocated by my Graphic card who used a turbo cashes .
Well I did a total fresh install with X686 , but the total amount of RAM is still 3.3 GB and the free RAM memory even drops down a bit because X686 use more as a cashes.
So it seems to me that my retailer was correct when he said that difference in the BIOS between the 4 GB and the available of 3.3 GB is caused by the fact that it is preallocated by my Graphic card who used a turbo cashes .
Um, why did you install 686 still again and expect a different result? As has already been said, you need to either go with a 64-bit install or a bigmem 686 install.
Yeah, you need to download a new iso and select the AMD64 (or x86_64) version this time. Just reinstalling your 32 bit system is not going to make any difference at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.