On Fri, Feb 29, 2008 at 12:14:37PM +0000, andy wrote: > 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: No, the line you need to edit is the one with 'kopt=...'. Don't uncomment it, just add the relevant parameter to the end (like I added vga=791 for my laptop). After you're done you *must* run /usr/sbin/update-grub Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein)
Attachment:
signature.asc
Description: Digital signature