[syslinux] Syslinux Mem= greater than 4096M
Geert Stappers
stappers at stappers.nl
Sat Feb 4 00:13:15 PST 2012
On Sat, Feb 04, 2012 at 12:00:31AM -0600, Kevin Sullivan wrote:
> On Fri, Feb 3, 2012 at 10:33 PM, Gene Cumm wrote:
> > On Fri, Feb 3, 2012 at 22:48, Kevin Sullivan wrote:
> > >
> > > I have several boot options, but here is one example:
> > >
> > > LABEL less
> > > MENU LABEL Up to 64 GB System RAM
> > > KERNEL /boot/vmlinuz-3.1.10-b1
> > > APPEND pci=nommconf vga=773 mem=256M initrd=/boot/initrd-3.1.10-b1.img
> > >
> > > This boots a Linux kernel that can only "see" 256 MB. If I set mem=4097
> > > or greater, I get the error message.
> >
> > Same error with 'mem=4352M' ? mem should be interpreted by the core
> > for load alignments by the Syslinux core.
>
> Gene,
>
> Interesting. It does not show the error with mem=4352M. However, the
> kernel is only showing about 3.3 GB total RAM after it boots. I do not
> understand the concept that you mention of "mem should be interpreted by
> the core for load alignments by the Syslinux core. Could you give insight
> into how you picked this number and/or how I can select safer larger
> numbers? For my particular situation, I probably only need to reach the
> mem=8192M range. As an FYI, mem=4095M only gives me 3.0 GB free, so your
> answer is already proving helpful.
Interresting question.
I see in the 4352M 1 GB + 3.3 GB wonder why the 1 GB is gone.
If it was 1 MB, I would say "the 80286 high mem stuff that I never understood" :-)
Groeten
Geert Stappers
--
> And is there a policy on top-posting vs. bottom-posting?
Yes.
More information about the Syslinux
mailing list