On 02/05/10 14:03, Alan Lord (News) wrote:
The script that "update-grub" calls - grub-mkconfig - looks for kernels
and so forth and automatically generates the config file for grub.
It*should* find any kernels in /boot so perhaps when you ran it the
relevant partition wasn't mounted?
You can also manually edit your /boot/grub/grub.cfg file and try adding
a new boot option pointing the "linux /vmlinux-XXX ..." line to the
necessary drive designation (i.e. /dev/sda2 - where the "/" root
partition of Lucid is) rather than UUID strings and try that.
At least it might give you a way of playing and testing things.
HTH
Al
Hi Alan,
thank you for the message. Unfortunately, I have no idea what you are
talking about. Tried reading that through about half dozen times, and
wouldnt even know where to start.
Can you explain a bit more?
John
--
Ubuntu User #30817
--
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/
