update-grub writes in wrong settings for example memmap=54M\$970M

[sdowney717]

Binary package hint: grub2

I have a memory module that memtest86 says the last 54MB is bad.
total memory is 1024mb.
So, using memmap you can tell the kernel to ignore and not use a specified memory range.
In my case memap=54M\$970, so the kernel wont use starting from 970MB the next 54Mb's.

since it is bash script, you have to escape the $.??
you want the linux kernel line after splash, in /boot/grub/grub.cfg to have appended on the end, memmap=54M\$970 but
when you edit the /etc/default/grub file to add in a kernel parameter memmap=54M\$970, grub-update
writes in memmap=54M$\970 which wont work.

I dont know if my syntax for escaping the '$' is correct but if it is, then this is a bug.

this is my line in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash memmap=54M\$970"

and running update-grub yields

linux /boot/vmlinuz-2.6.31-14-generic-pae root=UUID=4923760a-6e34-4678-b0ab-d06b151a2998 ro single memmap=54M$\970

The '$' and '\' are reversed. That means i will have to hand edit the grub.cfg file everytime a new kernel comes thru or update-grub is run

ProblemType: Bug
Architecture: i386
Date: Sat Nov 28 14:08:09 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: grub2 (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: grub2
Uname: Linux 2.6.31-14-generic i686

[sdowney717 (sdowney717)]

a couple of references about memmap usage
http://ubuntuforums.org/showthread.php?t=860631

http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-03/msg05303.html

[sdowney717 (sdowney717)]

ok, i got it with using this

54M\\\$970M

yields this

54M\$970M

[Bryan Quigley (bryanquigley)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

This was reported against a very old release so I'm going to close it. If you still have the issue please reopen.