Steve Langasek wrote: > Bad advice. Adding kernels by hand will only make it more difficult for > update-grub to reconcile the boot stanzas the next time it runs. You > should fix this by running "sudo update-grub" instead. > > I tried running "sudo update-grub" and got the following result:
> [sudo] password for daniel: > Searching for GRUB installation directory ... found: /boot/grub > Searching for default file ... found: /boot/grub/default > Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst > Searching for splash image ... none found, skipping ... > Found kernel: /boot/vmlinuz-2.6.31.5 > Found kernel: /boot/vmlinuz-2.6.31-14-generic > Found kernel: /boot/vmlinuz-2.6.28-16-generic > Found kernel: /boot/memtest86+.bin > Updating /boot/grub/menu.lst ... done I'm a bit concerned about the line "searching for splash image ... none found, skipping ...". Is this something that needs to be corrected? Daniel -- jaunty to karmic upgrade failed to update menu.lst (update-grub missing from kernel-img.conf) https://bugs.launchpad.net/bugs/470265 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
