Hide Forgot
Description of problem: The error message I am seeing with Fedora 13 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 13 64 bit DVD. Version-Release number of selected component (if applicable): Steps to Reproduce: 1. Load x88_64 fedora 13 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.
Created attachment 479730 [details] sosreport report file Here is an sos report from an installed machine if that is helpful.
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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
Same problem with F15, albeit on different hardware (still Dell, though). Adding a mem= argument fixed it. Hardware details: http://www.smolts.org/client/show/pub_56e87ac6-19bb-4390-a9e6-a673dc32532b
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.
Please reread comment #3 where I said I'm experiencing this on F15. I'd update the version number on this but myself, but I don't have the appropriate permissions to do so. Similarly, I don't seem to be able to reopen this bug.
only the original reporter can reopen closed bugs. I'll reopen it. can you attach a dmesg from an affected system ?
Yes, but not immediately. It's my work box, and I need to get some work done, so I've rebooted back into F13 for now (F15 is unusable for me out of the box, for many reasons -- at least the memory mishap has a trivial workaround)
Looking at Gary's dmesg, two things jump out at me.. 1. The resulting e820 map doesn't look any different, which makes me wonder if this is just some quirk of the bootloader. 2. The booted system looks like it booted without the mem= arg ? If this bug only happens at install time, that would probably indicate a syslinux bug as opposed to a kernel or grub bug.
Yes. It only failed at install time. Post install it boots fine.
Created attachment 510255 [details] dmesg Yep, confirmed that normal booting with grub doesn´t require the extra mem= parameter. It´s only necessary at install time.
I have some RHEL 6 machines actually in production in a lab that have this same problem. (think fedora 13/14) They used PXE to install. I had to add the mem= argument to get these working in the PXE menu environment. So perhaps its not limited to syslinux ? Or perhaps PXE boot environment uses syslinux? Once installed they boot fine.
Reassigning to syslinux.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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