On 03/05/10 10:32, John Matthews wrote: > 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.
> > 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? Ahh, earlier a respondentsuggested you run the command "sudo update-grub". If you open a terminal and type "man update-grub" it will tell you a little about this file (it is just small shell script) which calls another shell script called grub-mkconfig with some parameters. If you then type "man grub-mkconfig" it mentions that this file creates a grub config file. You can actually look at the shell script if you like. To find out where it is first, type: "which grub-mkconfig" The result of which should be "/usr/sbin/grub-mkconfig" So you now open and look at the script if you want to: "less /usr/sbin/grub-mkconfig" But the whole reason for my reply was that you said: "Hi sorry its taken me so long to get back to you, I did what you said sudo update-grub and it didnt change anything on the grub, but also, Ubuntu stopped loading after the grub." Now that command rebuilds the grub config file automatically by searching for interesting kernels and creating the right entries in the grub config file: /boot/grub/grub.cfg (You can examine it by typing "less /boot/grub/grub.cfg". If you feel brave, make a copy of it (use sudo in front the commands) and then add a new entry manually that loads the new lucid kernel. You should have a file in the /boot directory called something like vmlinuz-2.6.32-21-generic with a similarly named initrd.img file. It is these which need to be loaded first. These two "key" lines in my grub.cfg: linux /boot/vmlinuz-2.6.32-21-generic root=UUID=9e126082-f552-44ce-a103-925779c31147 ro quiet splash initrd /boot/initrd.img-2.6.32-21-generic tell grub what to load. There might be several "groups" of boot options in your grub.cfg, you can, if you are careful, copy one of them and add a new one for your lucid kernel of it doesn't exist and then select that on start-up (Hold the shift key down when you power-on the PC and keep it held until you get the grub boot menu). Having said all this, it might not be the wisest advice to give you. You can break things. But if it is broken then it probably doesn't matter so much. Obviously backup all your data before hacking away! HTH Alan -- The Open Learning Centre http://www.theopenlearningcentre.com -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
