Memory question on Arch x86_64. 2x2048 MB = 3950 MB?

I have a naive memory question for some knowledgeable folks. My machine has 2x2 Gb sticks which should total to 4096. When I do a free -m under Arch, it's only showing 3950. Is the remaining 146 reserved or..?
$ free -m
total used free shared buffers cached
Mem: 3950 422 3528 0 28 157
-/+ buffers/cache: 236 3714
Swap: 2000 0 2000

Thats a really good question and the result you get is normal as far as I know.
Part of it (a small part I believe) is used by the kernel, the rest of it, and this is where things are not so clear, is reserved as an agp apperture.
As far as I could tell (I have stumbled uppon that too) the problem seems to be that some bioses don't setup everything as they should.
The thing is that some devices can only handle 32bit addresses so their address is somewhere until the 4GB mark, because the bios doesn't setup the memory remapping correctly (sometimes the user has no way set anything related to memory remapping, this seems to be the case with some desktop boards and most notebooks/laptops). This memory remapping "problem" was anticipated and there are ways to properly handle that.
For some reason unknown to me (and most people that have stumbled upon this) many bioses don't setup (or allow the setup) of proper remapping. To add to the problem the kernel seems to reserve 128MB of agp aperture by default even if you don't have an agp card, this reserved address space falls in the first 4GB of addressing space therefore stealing you some memory.
I have tried to regain those MB, I have tried to recompile the kernel with a different config and I've tried several kernel boot parameters and the only thing I could regain was 64MB if I recall correctly. I can't find now what I have added to regain those 64MB, I didn't keep that option in the kernel line, 64MB were not worth the possibility of having problems later on.
I know its a pain to have that voice in the back of your head telling you that there is some memory that is being wasted, specially if you have tried a 32bit kernel with support for 64GB of address space and got 4050 MB of usable memory, but just leave it as it is, it's not worth the time and the trouble.

Similar Messages

Automated install Arch x86_64 root-file system the "Raspberry" way..

Dear Archers,
I am currently deeply interested in installing Arch as dual boot on my
current x86_64 system.
And yes, there is plenty information regarding this subject in Arch wiki's.
However...
I would like to automate the installation the "Raspberry-Pi" -way.
Details on the "Installation tab" of:
http://archlinuxarm.org/platforms/armv6/raspberry-pi.
As you can see, the installation steps are easy to automate, in my opinion.
That's why I wrote an automation script for this purpose..
The information further suggests that there is a root-filesystem for
Arch named: 'ArchLinuxARM-rpi-latest.tar.gz.'
Unfortunately, I don't think this root system will function on x86_64 systems..
So I researched if there was a root filesystem for Arch x86_64 and found filenames like 'root-image.fs.sfs' 'core.db' 'core.img'.
But I'm unsure if these archives/images really contain a rootfilesystem similar to the ArchARm system.
Therefore my question:
Does anybody know if there is a similar root filesystem for x86_64 so I can reproduce the "rpi-way" installation for x86_64 systems?
Kind regards,
Kees Epema

You are definitely not going to be able to simply dd arch to your machine unless you create an image to do so. Even then, that image would become old and stale pretty quickly, possibly leading to problems getting the system up to date.
In my opinion, the raspberry pi way to simply dd'ing an image to an SD card is a disservice to the ArchlinuxARM users. Though seemingly the proper way to get a system running on a raspberry pi, it masks the install process and leaves the user without a clue as to what would have gone into creating the system.
Go read the beginners guide. Use a virtual machine to practice if you need. Shortcuts are not going to help you with Arch.

[SOLVED] Skype on Arch x86_64

How do I install skype on arch x86_64? I tried a lot of ways but no go I hope this is the right subforum for this post.
Last edited by obsrv (2008-09-27 09:46:18)

obsrv wrote:Yes does skype will be fully 64bit? That would be great. I imagine days when whole world would use 64bit software, and 32bit would be deprecated like now 16bit
There was, and maybe still is, a Skype dev floating around here somewhere. He said that they are working on it. But, if memory serves me well, I think that the number of people working on the Linux client may amount to only one!

Memory Question "4x1 Gig or 2x2 Gig?" what is faster?

Memory Question "*4x1 Gig or 2x2 Gig*?" what is faster?
I'm still don't know if witch to choose?
4 times 1 gigabyte Ram Memory is cheaper but if I choose for 2 times 2 GB Ram I can always beef it it later.
And is my memory faster if I'm using 4 slots with 1 gig over 2 slot with 2 gig?
I'm asking this question because I think using 4 times the memory bandwidth will be faster?
http://www.janmaartendewit.com

Hello Jan
Welcome to Apple Discussions
The iMac (Late 2009): Installing or replacing memory article and your User's Guide are pretty clear, they both say that +"You can use 2 GB or 4 GB RAM SO-DIMMs of 1066MHz DDR3 SDRAM in each slot."+ and not 1GB modules. > http://support.apple.com/kb/HT3918
To upgrade your ram you will want at least 2 more 2 or 4GB modules and add that to the current 2 x 2GB of ram. > http://eshop.macsales.com/shop/memory/iMac/DDR321.527
Dennis

Error! Build of vmblock.ko failed for: 3.12.2-1-ARCH (x86_64)

Hello,
I'm very new to the world of arch linux. I see that there are patches for this but I don't have knowledge of using them.
Help please?
sudo dkms install -m open-vm-tools -v 2013.09.16 -k $(uname -r)
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.12.2-1-ARCH VM_UNAME=3.12.2-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmblock; make VM_UNAME=3.12.2-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmci; make VM_UNAME=3.12.2-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmhgfs; make VM_UNAME=3.12.2-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmsync; make VM_UNAME=3.12.2-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vmxnet; make VM_UNAME=3.12.2-1-ARCH MODULEBUILDDIR=/var/lib/dkms/open-vm-tools/2013.09.16/build -C vsock.........
Error! Build of vmblock.ko failed for: 3.12.2-1-ARCH (x86_64)
Consult the make.log in the build directory
Last edited by diabolik (2013-12-02 15:31:57)

OK, assuming the patch posted there fixes the problem, the only problem before you is how to patch?
If that's the case, you should first download the patch content posted on the AUR page and save it with the given filename, i.e., vmblock-9.0.2-5.0.2-3.12.patch
Then put the filename in the sources field of the PKGBUILD and put the file's md5sum in the respective field of the PKGBUILD as well.
After that, run
$ makepkg -si
You might want to read the following for reference:
https://wiki.archlinux.org/index.php/PKGBUILD
https://wiki.archlinux.org/index.php/Makepkg
Last edited by x33a (2013-12-03 05:48:46)

[SOLVED] Fail to boot Arch x86_64 live CD on a HP laptop

Hey, guys, what's up?
Well, here's the thing: I bought a new laptop a couple days ago and I'm kind of having some trouble. Its a HP Pavilion dm4-1063cl (this model: http://www.notebookcheck.info/HP-Pavili … 579.0.html, just in case).
I ran some tests in Windows 7 about the architecture of the processor and it clearly seems that it can support arch x86_64 bits. However, I tried to boot Arch x86_64 by a Net Installation CD and it doesn't work. The process fail in the "Loadin UDEV events" phase, something like that. PS: the i686 image boots perfectly.
Then, I thought that was the CD I burned the reason for trouble - I did not check md5sum and stuff like that. So, I burned another dual image (with boths i686 and x86_64) and tried to run again the 64bits kernel. It did not work in the same phase.
The only response I get is a dark screen that never seems to go away. It was a panic I've never seen before with Arch Linux.
The only alternative I can think right now is trying an older version of the live image CD and see what happens, but it doesn't seem like a very good option. Any ideas?
Hope someone of you can help me. Here in Brazil, most of computers we buy come with Windows installed and we don't have quite a chance of not getting - or paying for - it. I'm sure I'll have such a trouble installing dual boot with Arch Linux, but I really miss my Arch Linux...
And, damn, I worked too hard to get a new processor. I really dont wanna use Arch i686 on a pc with x86_64 architecture, it seems like an option, but a dumb one. =p
Cheers,
Wilson.
EDIT: It turns out that tt was not a kernel panic as I thought. The kernel changed the resolution of the display during this fase, and somehow it doesent work.
The trick I used to solve this was adding "nomodeset" to the kernel line in the Live CD booting. Btw, you can do it by selecting the booting option you want in the live CD and pressing TAB. Then, you can edit the kernel line. (:
Last edited by wilsaooo (2010-12-28 06:17:41)

lamegaptop wrote:
Resurrecting this post because I may help you or someone else.
HP DM4-1265, Intel Corei5, Intel Graphics. (Two days old, windoze wiped, Arch installed)
At boot the brightness is, for some unexplained reason, set all the way down to 0 on these intel based DM4 laptops. A few simple <Fn>+<F3> turns the brightness back up.
To solve this I had to put this in rc.local -
echo 6 > /sys/class/backlight/acpi_video0/brightness
you can enter it manually to test first (as root). Try to turn your brightness up and down with it to make sure it works.
My fan ran like crazy too. HP chose to default a BIOS setting that keeps the fan running constantly. I disabled that and all is well. Fan only comes on when needed and lm_sensors shows my temps, right now, at 43C. Ambient is at 77F right now (I'm in Florida) and this kick butt Arch laptop is, in fact, on my lap.....
Don't give up man.
First of all: thanks for replying.
I installed manually the "coretemp" kernel modules and lm-sensors now give some different response. The script "sensors-detect" does not find any answer.
Looks like the temperature run in a regular level (50º-60º), which I consider a good sign. However, sometimes when I use arch for 24h+, it shuts down suddenly and does not let me boot my computer again - I believe it is a overheating problem. Happened a couple times, big no big deal.
On the other hand, in Windows 7 I have no trouble at all. The temperature goes around 40º with some daily activities. It worries me out because I used - and I do use - largely and successfully Arch i686 version in crappy notebooks with no heating at all.
I tried some tweaks in the rc.local, but none of them seemed to really work. With cpufreq, I could slow down the processors and maintain a regular temperature. Looks like I can list some of the fans speed in the /sys/ files, but much of them do not seem to have any change at all. Some of them looks like to have some "max_state" set to low values like 1, but most do have a limit like 10.
I will keep trying. If there's anything new, I'll post here
Cheers,
Wilson

Arch x86_64 won't boot, but i686 will. Live USB and HDD.

To be more succinct, what could cause 64 bit arch not to boot when 32 bit arch boots fine on a non-UEFI system that supports 64 bit, when all other variables are constant?
My first response seeing this post would be to immediately assume the noob (me) posting this doesn't know the difference between a 32 and 64 bit system. However, "ubuntu-14.04.1-desktop-amd64.iso" (latest 64 bit ubuntu iso) boots from live USB and installs without error. It also came preinstalled with Windows 7 (64 bit), so I'm relatively sure it supports x86_64.
I wrote "archlinux-2014.08.01-dual.iso" (MD5 verified) to my USB. Selecting i686 boots fine. Selecting x86_64 restarts my system, eventually sending me back to the arch live menu after it posts.
Upon recommendation by a WonderWoofy on reddit, I tried to install arch x86_64 by bootstrapping and chrooting from the 64 bit ubuntu live usb. I ended up with same problem, where attempting to load arch reboots my system immediately.
Right now, I'm assuming it's the same issue booting from the live usb (arch iso) and from the arch installation on my hard drive, since they seem identical to me. I haven't tried recreating the install for i686 to see if it works (mainly because it's late -- if it'll help I'll do it upon suggestion).
Here's the only text that shows once I attempt to boot into arch. This is from the hard drive and using syslinux (which is pointed at my root partition on sda -- I don't have a boot partition).
Loading ../vmlinuz-linux... ok
Loading ../initramfs-linux.img...ok
Probing EDD (edd=off to disable)... ok
Which doesn't look like it's messing up anywhere...
And of course I'm a noob so go easy on me x)
UPDATE: I found this thread but I'm not seeing his error message, so I'm not sure what to do.
Last edited by SirProudNoob (2014-08-13 02:54:24)

It's an Intel Core 2 Quad processor. Are there any more diagnostic commands that would be helpful? I didn't see anything else in util-linux that might help...
Here's the output for "lscpu":
ubuntu@ubuntu:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Stepping: 10
CPU MHz: 2327.537
BogoMIPS: 4655.07
L1d cache: 32K
L1i cache: 32K
L2 cache: 2048K
NUMA node0 CPU(s): 0-3

Automatically tagging arch=(x86_64) to PKGBUILDs in yaourt?

Every time I get a package from the AUR, I need to manually edit it to add the arch=('x86_64') string so I can get packages to install. Is there something magical I could to to put that string in the PKGBUILDs, as well as make me a burger? I am really hungry.

Tom's got a point - if you find a package missing x86_64 as a supported arch, and you can build and run it fine on your system, let the package maintainer know so they can add it into the PKGBUILD.
In any case, this is a bit hacky, but will probably work:
#!/bin/bash
# makepkg64.sh - add the x86_64 arch as supported, then make the package.
[ -f ./PKGBUILD ] && echo "arch=('x86_64')" >> PKGBUILD
makepkg $@
cat << EOF
Here's a juicy hamburger:
.' o '.
/ o o \
|o o o|
/'-.._o __.-'\
\ ````` /
|``--........--'`|
jgs `'----------'`
Eat it while you tell the upstream maintainer whether this package works or not.
EOF
Last edited by Cerebral (2007-09-14 12:23:19)

Get arch x86_64

When i write "arch" in the terminal, i get i386. I try to write : sudo env ARCHFLAGS="-arch=x86_64" and still after i386. How can i change the i386 architecture of my cpu to x86_64 in Mac OS X10.6.3?

Here's a reply I made some time ago about this subject.

Arch X86_64 - Logmein Plugin

Hi
Hope you can help me with this one:
I have a 64Bits arch installation, i'm tryng to use firefox and logmein, i have tried to put the plugin manually on /usr/lib/mozilla/plugins and compile from AUR that despite give me an error on the architecture, i was able to edit pkgbuild and add the line arch=("x86_64") and install it anyway...
But when i try to remote to a computer...i can't....it stuck on connect network...and then error message as disconnected....
Any ideas or someone in the same situation.
Thanks
Sniff

Sniffer wrote:
Hi
Hope you can help me with this one:
I have a 64Bits arch installation, i'm tryng to use firefox and logmein, i have tried to put the plugin manually on /usr/lib/mozilla/plugins and compile from AUR that despite give me an error on the architecture, i was able to edit pkgbuild and add the line arch=("x86_64") and install it anyway...
But when i try to remote to a computer...i can't....it stuck on connect network...and then error message as disconnected....
Any ideas or someone in the same situation.
Thanks
Sniff
Reply to myself..
This S###y plugin only works on X86. Period.

Arch x86_64 install on compaq 615

I have this funny compaq 615 laptop with amd x2 athlon 2.2 Ghz.At the time on the laptop is debian sid but im planing to install arch.
So has anyone this combination?Compaq 615 + Arch x86_64 and maybe awesome wm?
I tred to install awesome wm on my desktop but i couldn`t.It sayed that i dond have i686 proc and this is a 32bit software.

btw, during install i have installed the b43.framwarecutter. and now i foun this in aur http://aur.archlinux.org/packages.php?ID=21690
so should i download this and install?will it work?and moste important how the hell should i do this?

Arch-x86_64, X11, ati-radeon-hd3200

OK, I've got this brand new machine (amd-64 quad core, 4 gig memory) with a builtin ati radeon hd3200 graphics adapter.
I've had no joy with the 'usual' graphics drivers (ati, radeonhd, vesa) so downloaded from the ati/amd website - got version 8.7 of the 'fglrx' driver.
I am running the very latest version of archlinux-x86_64 (as of yesterday).
Running the install script just bombs out without any explanation and the driver is not found when I start up X.
The funny thing is - I had troubles with the i686 version of archlinux as well - it came back with an error but the driver was obviously installed and it all worked.
With x86_64 I'm well and truely snookered ...
Any suggestions??
Per

Oh and btw ... here's the log from the ati-install script:
[Message] Kernel Module : Trying to install a precompiled kernel module.
[Message] Kernel Module : Precompiled kernel module version mismatched.
[Message] Kernel Module : Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
assuming new VMA API since we do have kernel 2.6.x...
Assuming default VMAP API
Assuming default munmap API
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.26-ARCH/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/linux-2.6.26-ARCH'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 'KCL_GetInitKerPte':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2744: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2744: error: (Each undeclared identifier is reported only once
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2744: error: for each function it appears in.)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 'KCL_GetPte':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2782: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 'KCL_GetPageTableByVirtAddr':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2845: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 'KCL_TestAndClearPageDirtyFlag':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2972: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function 'KCL_GetDmaPhysAddr':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:3016: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: At top level:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4177: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4177: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4195: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4195: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4202: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4202: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4209: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4209: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4216: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4216: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4223: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4223: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4230: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4230: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4239: error: unknown field 'nopage' specified in initializer
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:4239: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:6768: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:6794: warning: initialization from incompatible pointer type
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.26-ARCH'
make: *** [kmod_build] Error 2
build failed with return value 2
[Error] Kernel Module : Failed to compile kernel module - please consult readme.

865pe neo2-p Memory question

HI all
Hope someone can answer me a question
I have a 865pe noe2-p mobo , i have just stuck in x 4 1 gig ddr400 mem modules
The Specs of the board state as per MSI site that this board can support 4 gig , yet my bios is only reporting 3.1 gig
Mem modules are showing as dual channel in bios
Bios version is up to date ver 3.a , as per live update
CPU intell celeron 2.53 ghz clocked up to 2.92 ghz
4 gig Kingston DDR400 mem
Nvidea 6600
sata hdd's , 500 gig and 160 gig
is there something i am missing here to enable this board to see 4 gig of mem as per the specs of the board
I am only running XP and fully understand the SW limitation ,
I do not see this as being issue with SW , this seems to stem back to the board not picking the correct amount of ram installed
Has anybody else see this ?
Is there a resolve ?
Thanks in advance
Tadkin

Quote
is there something i am missing here to enable this board to see 4 gig of mem as per the specs of the board
I am only running XP and fully understand the SW limitation ,
I do not see this as being issue with SW , this seems to stem back to the board not picking the correct amount of ram installed
The software limitation you are talking about is only one side of the coin. The memory adress decode space of the chipsets memory controller is restricted to 32bit addressing before software (operating system) ever comes into play. Part of this adress space needs to be reserved for other system devices and cannot be used for system memory addressing. No mainboard featuring an Intel 865PE Chipset was ever (or will ever) be able to fully address 4GB of system memory. This is a chipset rather than a board or BIOS limitation. It is not even a problem but a hardware restriction that was only overcome severl chipset generations later (Intel P965 and 975X to be precise).

Memory question

I have a couple of questions about memory.
1. I have Corsair TwinX XMS PC3200 2x1024mb. settings at corsair are 2.5-3-3-6 It shows up in speedfan as:
FSB-DRAM................. CPU/14
CAS# Latency............. 3.0 clocks
RAS#to CAS# Delay..... 3 clocks
Ras Precharge...............3 Clocks
Cycle Time(tras).............7 Clocks
Bank Cycle Time(trc)......10 clocks
DRAM IdleTimer.............16 clocks
I just want to run it at a better speed to get the most out of it.
2. Plus my MB supports DDR266/333/400 modules. Does that mean I can't run the 433/500/533/550?
When I started to overclock I had the DRAM set on 400 and with the OC it went to 424. with no problems. Then I had to drop it to 333 to keep OCing and got the DRAM up to 198 running stable. I had to drop the FSB so eventually the DRAM went to 184. I ran Sandra with the 424mhs setting and the 184mhz setting and the 184mhz setting was really a lot quicker...so I stayed there.
Now how can I get better speeds out of the memory? Would it be better to buy a different memory to achieve my goals?

MR,
You Stated :
1. I have Corsair TwinX XMS PC3200 2x1024mb. settings at corsair are 2.5-3-3-6 It shows up in speedfan as:
FSB-DRAM................. CPU/14
CAS# Latency............. 3.0 clocks
RAS#to CAS# Delay..... 3 clocks
Ras Precharge...............3 Clocks
Cycle Time(tras).............8 Clocks
Bank Cycle Time(trc)......12 clocks
DRAM IdleTimer.............16 clocks
I just want to run it at a better speed to get the most out of it.
The figures you posted above look more like figure you would have gotten from the memory Tab in CPU Z. Can you confirm this and also post all figures you get form the SPD Tab in CPU Z regarding your RAM. If you RAM setting are set to Auto in BIOS then the above figures are really your SPD readings that were applied by your BIOS Auto RAM setting feature. The CPU Z SPD read out will confirm this. If this is the Case then you have Corsair TwinX2048-3200 Kit (3-3-3-8) vice the TwinX2048-3200C2 (2--3-3-6*) with the asterix annotated as [* These parts support 2-3-3-6 latency on Intel platforms, and 2.5-3-3-6 latency on AMD platforms.]. Double check your product number on your RAM and pay perticular attention to letters and/or numbers after TwinX2048-3200....> Check result against listing the TwinX matched pair memory listing here http://www.corsairmemory.com/corsair/xms.html
Plus my MB supports DDR266/333/400 modules. Does that mean I can't run the 433/500/533/550?
You could likely use memory up to DDR 500 on your board if you wanted to OC and leave ram at 1:1 ratio. Higher memory would be wasted money.
Good luck,

Memory Question for G4 Cube

In accordance with recommendations on a previous question here I have ordered OS 10.4.6 from Apple to install on my Cube. The Apple rep said it would work with the 384 MB ram I now have in the computer. I think I will add more memory though and the Apple rep advised I visit <www.crucial.com> to get it as Apple no longer stocks memory for the Cube. The spec for memory in the Cube manual says to use "PC-100" synchronous DRAM (SDRAM). The crucial.com site recommended a 512MB chip that says it is "PC-133" and implies it will work, guarantied. Will it?
It will be 2 weeks at least before Apple will ship the OS 10.4.6 package as it is on backorder. I know I will have some questions on installation when I get it.
JTB

PC133 RAM is usually less expensive than PC100. The cube has 3 slots, and the max you can install is 3 x 512 megs. If all three slots are already filled, you will have to remove one of the modules and replace it with the 512 you plan to buy. I would personally stick with PC100, particularly if the modules that will remain are PC100.
I usually buy my RAM from Ramdirect. Their prices are competitive, and they have always stood behind what they sell - there is a lifetime guarantee. I will recommend them without reservation.
http://www.ramdirect.com/vcom/index.php?cPath=1723
(I have no relationship with the company, other as a satisfied customer.)
Installing the RAM is dead easy, but you might want to download a service manual.
http://cubeowner.com/manuals/cubesvc_man02.pdf

Memory question on Arch x86_64. 2x2048 MB = 3950 MB?

Similar Messages

Maybe you are looking for