I apologize if thos has been asked a million times already. It also seems like basic general linux knowledge but i dont know it so im asking.

Im currently trying my hand at setting up a webserver with a dell optiplex 740 using an amd athlon x2 64 2.5ghz processor and 2 gigs ddr2 667 ram. No addutional grfx carss just the built invideo stuff. I have been running into problems all weekend. First was actually getting a good iso. Then a reliable image burn. I think i have those two issues sorted. Im installing on a new hdd so this isnt a dual boot.

My problem is with a good iso and image burn to dvd i hang on install with a message stating not enough memory for specified image/kernel/version (i cant remember exactly but its a common problem i find in other threads). Then im given a boot: prompt.

So ive determined my issue at this point i think. From ehat im reading is that dell puts a memory hole early in ram and the install thinks it doesnt havr enough ram because it has no addresses mapped beyond the hole. At least thats my understanding.

The solition i read is to use mem=##### to modify or add to the grub file manually how much memory to use...

Thats my understanding thus far but i cant figure out the syntax and exact location to use mem=####. Do i type that in at the boot: ? If so in what syntax? Ive read that i should hit tab after the error then use the mem=####.

Could someone explain the process in detail and any sytax i may be missing and anything else i should know? When i simply type say mem=2048 at the boot: prompt. It tells me it cant recognize the kernel so i assume that isnt right. I may also not be entering e memory amount correctly.

Thats it as far as i can deduct.

Ive tried a few versions of fedora all x86 64 as i think thats the right one for my system.

That will actually be a kernel boot parameter, when you first boot you'll get the menu with installation options and from there you should be able to press [TAB] to edit options.

Ah ok i will try that when i get home.

Edit: After writing the message below, I used google to find the issue, probably what the OP found:
https://bugzilla.redhat.com/show_bug.cgi?id=678820
That does make it sound like mem= is a correct work around.


Where did you read that?
That doesn't sound very plausible.
Even if it is correct, I'm pretty sure correct syntax for mem= still wouldn't help any.
Linux can use memory with big holes. But I don't know whether there is some restriction in loading the kernel across a hole. One one not normally expect a hole in ram after the first MB and before enough contiguous ram to load a kernel.

Do you have any version of Linux that will boot up? Maybe 32 bit Linux is best for this.
With any Linux that boots up try the following command and post the results:
That should give you the BIOS memory map showing which ram the BIOS tells Linux is usable vs. reserved or missing.

I figured it out. Now ive got fedora installed and running.

Not sure where i read about the memory hole but i did have to use mem= to get it working. I just wasnt aware of when and how to de it. Pressed tab abd entered mem=1024M at the promt and it installed.

Thanks for the help if i fond where i read about the memory hole ill post it.

Edit: yeah thats exactly what I read through that link. comment 10.

Posted the results of the command you said to run.

[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
[ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000001e00000 (usable)
[ 0.000000] BIOS-e820: 0000000001e00000 - 0000000001e80040 (reserved)
[ 0.000000] BIOS-e820: 0000000001e80040 - 000000007bed0000 (usable)
[ 0.000000] BIOS-e820: 000000007bed0000 - 000000007bed3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007bed3000 - 000000007bee0000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007bee0000 - 000000007bf00000 (reserved)
[ 0.000000] BIOS-e820: 000000007c000000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] Aperture pointing to e820 RAM. Ignoring.


Thats the result in the booted fedora I have installed