Hide Forgot
Description of problem: The error message I am seeing with Fedora 14 install DVD is: (lots of dots) Not enough memory to load specified image. giving mem=4294967296 as a kernel argument works around the problem. (pressing "tab" to give addition args) I have 4 GB memory installed in this PC. This is a problem on the DELL Optiplex 740 workstation with fedora 14 64 bit DVD. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Load x88_64 fedora 14 DVD 2. Boot machine 3. Select install Actual results: Installation hangs. Expected results: Should install without needing mem= argument. Additional info: Seemes to be similar to bugzilla bug 538911 in fedora 12 and bug 589303 in RHEL 6 and bug 678819 in Fedora 13.
Created attachment 479732 [details] sosreport report file Here is an sos report from an installed machine if that is helpful.
There isn't anything we can do about the F14 install at this point, as we don't respin the install isos. Does this still happen on the F16 Alpha install?
Yes. Error in Fedora 16 alpha is: (x86_64 DVD) Not enough memory to load specified image. Either with "Install/upgrade" or "Use basic video driver" options at first menu. Adding mem=4gb to kernel arguments by pressing "tab" works around the issue. Shall I open bugs for Fedora 15 and Fedora 16? Both distros have this same issue as well as RHEL 6.
(In reply to comment #3) > Yes. Error in Fedora 16 alpha is: (x86_64 DVD) > > Not enough memory to load specified image. > > Either with "Install/upgrade" or "Use basic video driver" options at first > menu. > > Adding > > mem=4gb > > to kernel arguments by pressing "tab" works around the issue. > > Shall I open bugs for Fedora 15 and Fedora 16? Both distros have this same > issue as well as RHEL 6. No, we'll just move this to f16.
Looking at the dmesg in the sosreport tarball, it looks like that kernel didn't need the mem= line to boot. I'm suspecting this is a syslinux bug if it's only affecting the install media.
Yes. This only occurs at install time with the DVD media or via PXE boot. Post install the kernel boots just fine without needing to add a mem= line within grub.
*** Bug 575330 has been marked as a duplicate of this bug. ***
I had posted a bug (https://bugzilla.redhat.com/show_bug.cgi?id=575330). The work-around was to give mem= option to the installer kernel. However, I am happy to report that the release DVD or Live CD (both x86_64) no longer require this work-around. I have 5GB RAM on the Dell Optiplex 740 and now have a working install of Fedora 16 x86_64.
I am still hitting this with the release Live CD (6G of ram), and I can confirm mem=5120m makes it work. It's also a Dell machine, XPS.
The problem is that some Dell machines put memory holes low in memory for some unknown reason: [ 0.000000] BIOS-e820: 0000000001e00000 - 0000000001f00040 (reserved) This confuses Syslinux which ends up thinking the machine only has 30 MiB of memory. Using linux.c32 works around this problem. linux.c32 is basically a standalone version of the kernel loader from Syslinux 5, which can deal with braindead memory maps like this.
In other words, instead of: label blah linux vmlinuz-foo append bar ... do ... label blah com32 linux.c32 append vmlinuz-foo bar
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.