From: "H. Peter Anvin" <hpa@transmeta.com>
To: Neil Conway <nconway.list@UKAEA.ORG.UK>
Cc: Kanoj Sarcar <kanoj@google.engr.sgi.com>,
syslinux@linux.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.rutgers.edu
Subject: Re: syslinux-1.43 bug [and possible PATCH]
Date: Fri, 24 Sep 1999 01:55:34 -0700 [thread overview]
Message-ID: <37EB3C86.F17CC25A@transmeta.com> (raw)
In-Reply-To: <99Sep24.094756bst.66313@gateway.ukaea.org.uk>
Neil Conway wrote:
>
> > Have other people run into this problem and worked around it some
> > other way? (One way would be to specify mem= at the boot: prompt
> > from syslinux. Yet another way seems to be to specify mem= in
> > the syslinux.cfg file. Changing HIGHMEM_MAX seems to be the cleanest,
> > although I am not sure whether this will impact the capability of
> > syslinux to install other os'es).
>
> I don't think "mem=" would help at all but I could be wrong.
>
It works; both SYSLINUX and the kernel with honour it.
> My "easy" fix was to pull out a DIMM from each of our machines, leaving
> 3x256 :-) Not elegant, but fast!
As already said, get SYSLINUX 1.44 or later...
-hpa
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-09-24 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-23 21:09 Kanoj Sarcar
1999-09-23 21:30 ` Matt Wilson
1999-09-23 21:55 ` H. Peter Anvin
1999-09-24 8:48 ` Neil Conway
1999-09-24 8:55 ` H. Peter Anvin [this message]
1999-09-24 9:43 ` Neil Conway
1999-09-24 16:30 ` Stephen C. Tweedie
1999-09-24 9:04 Javan Dempsey
1999-09-24 10:05 Javan Dempsey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37EB3C86.F17CC25A@transmeta.com \
--to=hpa@transmeta.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=nconway.list@UKAEA.ORG.UK \
--cc=syslinux@linux.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox