Messages in this thread | | | Date | Fri, 24 Sep 1999 01:55:34 -0700 | From | "H. Peter Anvin" <> | Subject | Re: syslinux-1.43 bug [and possible PATCH] |
| |
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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |