On Thursday 08 January 2004 18:03, Glenn A Diehl wrote:
[Trying again - something broke my signature by refromating MIME headers]
Anyway, this isn't a very good fix, but it does shed light on the
problem. Is there a correct way of making grub VMALLOC_RESERVE aware?
Use the value from the
On Thursday 08 January 2004 18:03, Glenn A Diehl wrote:
Anyway, this isn't a very good fix, but it does shed light on the
problem. Is there a correct way of making grub VMALLOC_RESERVE aware?
Use the value from the kernel header, patch attached.
--
Member AFFS, WYLUG, SWP (UK), ANL, Leeds
On Thursday 08 January 2004 19:03, Glenn A Diehl wrote:
I found that if I change VMALLOC_RESERVE in
/usr/src/linux/include/asm/page.h from:
#define VMALLOC_RESERVE (12820)
to:
#define VMALLOC_RESERVE (25620)
Why do you need such a change?
Anyway, this is an issue on Linux rather
Hello.
I have run into an interesting problem with grub 0.93. This occurs with
the Linux 2.4.23 kernel from kernel.org running on an i386 platform with
SCSI disks and 2GB of memory.
I found that if I change VMALLOC_RESERVE in
/usr/src/linux/include/asm/page.h from:
#define VMALLOC_RESERVE
