Andrei Popescu wrote:
On Fri, Feb 29, 2008 at 07:18:41AM +0000, andy wrote:
[...]
with a fix from the manufacturers. The other alternative seems to be
the mem=xxx option passed to the kernel. If I use the latter approach,
is this something that I can develop a script to do automatically at
boot (for example, to run it as part of the GRUB parameters), or is it
something that I would have to do manually?
$ grep kopt /boot/grub/menu.lst
## If you want special options for specific kernels use kopt_x_y_z
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=/dev/hda2 ro vga=791
# xenkopt=console=tty0
Regards,
Andrei
Thanks for this Andrei. How would I tweak this to enable my kernel to
recognise and utilise the additional RAM? Looking through the file, the
relevant section appears to be this commented part:
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
The instructions are to not uncomment the section, but just to edit. So
would my edit be to add
memtest86=true or memtest=false
or would I simply add the line to menu.lst between the two markers that
reads:
mem=2097152M #2GB RAM
The latter is what I understand from bootparam(7), but I'd like to
confirm before I commit.
Thanks
A
--
"If they can get you asking the wrong questions, they don't have to worry about the
answers." - Thomas Pynchon, "Gravity's Rainbow"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
