Bug#542898: grub-pc: install finds kernel command line properly, but doesn't write it to /etc/default/grub

2012-12-30 Thread Corey Hickey

On 2012-12-29 09:08, Martin Naughton wrote:

Hello Corey,
  Do you have the file that is produced missing the line?
You say both files below are missing the line. When you do the work around
does it write this missing line to the files below?

/etc/default/grub
/boot/grub/grub.cfg


Thanks for looking into that. I'm not sure the bug is still relevant 
after so much time has passed, but I'll see if I can reproduce it and 
provide sample files when I have a chance (should be some time early 
this week).


-Corey


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#542898: grub-pc: install finds kernel command line properly, but doesn't write it to /etc/default/grub

2012-12-29 Thread Martin Naughton
including Corey email address



On Sat, Dec 29, 2012 at 5:08 PM, Martin Naughton blades2...@gmail.comwrote:

 Hello Corey,
  Do you have the file that is produced missing the line?
 You say both files below are missing the line. When you do the work
 around does it write this missing line to the files below?

 /etc/default/grub
 /boot/grub/grub.cfg

 A bit more information might help

 --
 Regards
 Martin Naughton




-- 
Regards
Martin Naughton


Bug#542898: grub-pc: install finds kernel command line properly, but doesn't write it to /etc/default/grub

2009-08-21 Thread Corey Hickey
Package: grub-pc
Version: 1.96+20090808-1
Severity: normal

Hello,

I like the transition from grub-legacy to grub2 so far, except for one
detail that I have been unable to troubleshoot yet. When I install the
grub-pc package, I get prompted:

The following Linux command line was extracted from the `kopt'
parameter in GRUB Legacy's menu.lst. Please verify that it is correct,
and modify it if necessary.

The command line shown was correctly parsed from menu.lst, so I leave
it alone. The installation scripts then go on to generate
/etc/default/grub and /boot/grub/grub.cfg, but the kernel command line
seems to get ignored. In /etc/default/grub, a line is generated:

GRUB_CMDLINE_LINUX_DEFAULT=quiet

That quiet option then gets propagated on to /boot/grub/grub.cfg. If
I change the GRUB_CMDLINE_LINUX_DEFAULT option manually and run
update-grub2, that works ok.

I thought it would be good to report this in case it happens to other
people. My grub-legacy menu.lst should be attached. I can reproduce the
problem right now by running:

# apt-get --purge remove grub-pc
# rm /boot/grub/core.img
# apt-get install grub-pc

Thanks,
Corey

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/disk/by-uuid/036c4ae3-4272-410d-91ef-0bb0b9dddcc0 / reiserfs rw,relatime 0 0
/dev/hda1 /mnt/freedos vfat 
rw,relatime,fmask=0022,dmask=,allow_utime=0022,codepage=cp437,iocharset=iso8859-1
 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/device.map
(hd0)   /dev/hda
*** END /boot/grub/device.map

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
set timeout=5
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output.gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, Linux 2.6.30.5 {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.30.5 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro  quiet
initrd  /boot/initrd.img-2.6.30.5
}
menuentry Debian GNU/Linux, Linux 2.6.30.5 (recovery mode) {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.30.5 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro single 
initrd  /boot/initrd.img-2.6.30.5
}
menuentry Debian GNU/Linux, Linux 2.6.28.7 {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.28.7 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro  quiet
initrd  /boot/initrd.img-2.6.28.7
}
menuentry Debian GNU/Linux, Linux 2.6.28.7 (recovery mode) {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.28.7 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro single 
initrd  /boot/initrd.img-2.6.28.7
}
menuentry Debian GNU/Linux, Linux 2.6.28 {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.28 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro  quiet
initrd  /boot/initrd.img-2.6.28
}
menuentry Debian GNU/Linux, Linux 2.6.28 (recovery mode) {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.28 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro single 
initrd  /boot/initrd.img-2.6.28
}
menuentry Debian GNU/Linux, Linux 2.6.26.3 {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.26.3 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro  quiet
initrd  /boot/initrd.img-2.6.26.3
}
menuentry Debian GNU/Linux, Linux 2.6.26.3 (recovery mode) {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux   /boot/vmlinuz-2.6.26.3 
root=UUID=036c4ae3-4272-410d-91ef-0bb0b9dddcc0 ro single 
initrd  /boot/initrd.img-2.6.26.3
}
menuentry Debian GNU/Linux, Linux 2.6.24.2 {
set root=(hd0,6)
search --no-floppy --fs-uuid --set 036c4ae3-4272-410d-91ef-0bb0b9dddcc0
linux