Well, there was an update and I performed it, but I don' t think that' s the prolbem. It stopped working after I installed a third OS on my HD. However, now I have only Sabayon Linux and SalixOS installed. Could kernel panic be related to the tird OS on HD?
What tool did you use to reinstall GRUB? Is it GRUB 2?
It's a while since I've used Grub but someone here will know
My guess about the kernel is just that, a guess; but since the trouble started when a new bootloader was installed, and Salix worked before, it seems likely that the bootloader is no longer configured correctly for Salix. This has happened several times to me recently during the transition from the kernel that came with Salix 13.37 to the 14.0 one, and Salix's own tools don't always get it right when multi-booting different distros with different kernel versions.
mimosa wrote:What tool did you use to reinstall GRUB? Is it GRUB 2?
It's a while since I've used Grub but someone here will know
My guess about the kernel is just that, a guess; but since the trouble started when a new bootloader was installed, and Salix worked before, it seems likely that the bootloader is no longer configured correctly for Salix. This has happened several times to me recently during the transition from the kernel that came with Salix 13.37 to the 14.0 one, and Salix's own tools don't always get it right when multi-booting different distros with different kernel versions.
Sabayon uses GRUB2. So its GRUB2 installed. Before installing the third distro everything worked fine. So i thought that reinstalling GRUB from sabayon would fix the problem but nothing changed. So the problem could be related to GRUB2 configuration?
That would be the first thing I'd investigate, yes. Depending on what tools Sabayon has, there may be some relatively straightforward way to tweak the configuration within Sabayon. Alternatively, you could use a Live linux (such as Salix 13.37 live) but as I mentioned, its rather nice GUI for Lilo may not cope well with this situation. Or if you're comfortable with the command line, you could chroot into Salix from any Live CD/USB, edit /etc/lilo.conf by hand, and install lilo as the bootloader.
I'm hoping somebody who's familiar with Grub2 will notice this thread and post some advice, though. I stopped using grub when it was still legacy.
first of all, thanks for the reply.
Ok, so I'll take a look at Salix configuration in Grub. I would like to use lilo as last resource. However thank you
If you can't figure out the correct Grub 2 boot stanza for Salix you could install Lilo to the Salix root partition and then put a chainloader entry in your Grub 2 menu.
