I was told this was a bug after enquiring about the /etc/lilo.conf "mem"
keyword. 2.0.36 and 2.2.x kernels should, apparrently, detect all
available memory without resorting to options in the lilo.conf file.
I am in the process of installing 2.2.2, so this problem might be a moot
case for me in future (I'll send another email if I have the same problem
with 2.2.2).
Regards,
Tor Houghton.
-
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/