[SOLVED] Emergency mode in Mageia after installing Slackware

[Velans]

After installing the operating systems of the third (Slackware) encountered little trouble in Mageia. I must also say that instead of GRUB installed with Mageia 3 I uploaded Lilo from the Slackware. After installing Slackware, when I wanted to turn on the lilo Mageia, instead of the system turn on emergency mode. After a while I noticed that the fault may be on the side of Windows NTFS partition. So currently I have hidden all windows partitions in /etc/fstab. And instead of the current emergency mode (after the loading system Mageia argument init = 3) can be incorporated into the loading screen where the keyboard and mouse do not work. Before installing Slackware everything worked as it should in Mageia 3. Is it the fault of Lilo or something wrong when installing Slackware introduced or may be sufficient to fix the mouse and the keyboard?

And so I entered Mageia in lilo.conf in Slackware:

Code: Select all

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda6
label = Mageia
read-only
# Linux bootable partition config ends

I'm sorry for the mistakes, but I write with Transalator Google.

[gohlip]

Most of us here had forgotten our lilo 'skills' (if we had any in the first place ), but did you somehow lose your initrd line in your lilo entry?

[edit] - and...shouldn't it be vmlinuz-desktop instead of vmlinuz?

ps: why do we use vmlinuz-desktop/vmlinuz instead of vmlinuz/vmlinuz.old?
as though vmlinuz-desktop is opposed to vmlinuz-server?
and other distro's bootloader won't pick up *-desktop in mageia - won't that be a problem?
and when "urpme --auto-orphans" is performed, it clears all kernels except the current, and vmlinuz points to the older kernel (which was cleared) - won't that be a problem?

[jkerr82508]

[edit] - and...shouldn't it be vmlinuz-desktop instead of vmlinuz?

If "desktop" is the only kernel flavour installed, then vmlinuz and vmlinuz-desktop are identical - they are both symlinks to the most recently installed vmlinuz. Similarly with initrd.img and initrd-desktop.img

Jim

[gohlip]

If "desktop" is the only kernel flavour installed, then vmlinuz and vmlinuz-desktop are identical -

If not the only kernel, the vmlinuz-desktop is the newer and vmlinuz the older. That is my point.

---- they are both symlinks to the most recently installed vmlinuz. Similarly with initrd.img and initrd-desktop.img

And if you remove all kernels except the current (like in urpme --auto-orphans), vmlinuz points to nothing. That is my other point.

This does not affect me as I use my own (non-OS) bootloader and I have been "urpme --auto-orphans" all these while without problem (also after reboot and without updates available - don't think it's wise for example to urpme after update of say, konqueror and still on current kde).

While this does not affect me at all, I think it is prudent to name our sym-link appropriately, especially for newer users. When I start using Mageia, for example, I let my bootloader point to vmlinuz, which is of course wrong; after kernel upgrade, I still boot up to older kernel. As someone once said, we should say what we mean and mean what we say. Saying *-desktop is saying nothing.

Understand completely what you say Jim, but I am just proposing that we do not let our naming of sym-links confuse our users. We should always try to be clearer.

And cheers.

[edit] - and if you look at meny.lst example (at /boot/grub/), you'll see the sample provided as "vmlinuz"
I always uninstall grub-legacy in Mageia after installation, so I don't know if menu.lst has vmlinuz or vmlinuz-desktop, but still...it will be confusing.
And still on the subject, I think it is plain wrong to have both legacy and grub2 installed. I think it's always good to have choices, even lilo, but we shouldn't install more than 1 bootloader.
And having to go through loops to install on gpt partitions, not to mention UEFI, and using rEFInd, goodness.

Cheers again. Not criticizing, just trying to help, really.

[Velans]

I modified lilo.conf and currently looks like this:

Code: Select all

# Linux bootable partition config begins
image = /boot/vmlinuz-desktop
initrd = /boot/initrd-desktop.img
root = /dev/sda6
label = Mageia
read-only
# Linux bootable partition config ends

Then it calls:

Code: Select all

# lilo
Added Windows  *
Added Slackware
Fatal: open /boot/vmlinuz-desktop: No such file or directory

And the boot folder in Mageia looks like this:

Code: Select all

$ pwd
/media/be784fa8-0ead-403d-9356-1a2d1d3ad506/boot
$ ls
System.map                          initrd-3.8.13-desktop-1.mga3.img
System.map-3.8.13-desktop-1.mga3    initrd-3.8.13.4-desktop-1.mga3.img
System.map-3.8.13.4-desktop-1.mga3  initrd-desktop.img
boot.backup.sda                     initrd.img
config                              symvers-3.8.13-desktop-1.mga3.xz
config-3.8.13-desktop-1.mga3        symvers-3.8.13.4-desktop-1.mga3.xz
config-3.8.13.4-desktop-1.mga3      vmlinuz
dracut                              vmlinuz-3.8.13-desktop-1.mga3
gfxmenu                             vmlinuz-3.8.13.4-desktop-1.mga3
grub                                vmlinuz-desktop

After using

Code: Select all

urpme --auto-orphans

in emergancy mode in Mageia text appeared: No orphaned packages to remove.

[gohlip]

As I said earlier, I am no expert in lilo (used it before, but forgotten totally), but obviously, vmlinuz-desktop is in your /boot which your lilo says is not there or cannot open. So I can only suggest that you use the linux kernel directly, which is vmlinuz-3.8.13.4-desktop-1.mga3 and use initrd-3.8.13.4-desktop-1.mga3.img for initrd. If it boots, then "dracut -f" to redo your sym-link. I am also not sure if your dkms is set up properly which kernel 3.8 requires and may affect your booting up.

Other than that, I cannot help you further and hope others can help you if the above don't work.

Good luck.

ps: I cannot presume to ask you to try grub, so I won't.

[Velans]

Thank gohlip and jkerr82508, every helping hand is important to me. . From what I remember as possessed GRUB (first skipped installing Lilo), I had problems to add Slackware, so I thought that Lilo will go easier for me. But maybe if more I thought about the GRUB menu, can I be able to add Slackware. So if install GRUB is not complicated at which I might lose data from partitions of Mageia, I try to install GRUB. I do not have with me the DVD of Mageia 3, but I also see as a way to update Mageia 3 of the installation and thus install GRUB. But wait a bit, maybe even someone from Lilo help me .

And after the change in lilo.conf, lilo command show

Code: Select all

# lilo
Added Windows  *
Added Slackware
Fatal: open /boot/vmlinuz-3.8.13.4-desktop-1.mga3: No such file or directory

In Google I found that Lilo, reportedly reads just the vmlinuz.
Velans.

[jkerr82508]

It's been years since I last used lilo, but you could try this:

In Slackware, mount the Mageia root partition at /mnt/mageia and add it to Slackware's fstab. Then change the Mageia stanza in Slackware's lilo.conf to:

Code: Select all

image = /mnt/mageia/boot/vmlinuz
initrd = /mnt/mageia/boot/initrd.img
root = /dev/sda6
label = Mageia
read-only

Jim

[saptech]

While I have Mga 3 and Salix, a slackware based distro that also uses Lilo. It was easier for me to just add Slackware to Mageia's Grub.lst file. Lilo can be a pain.

[Velans]

It's been years since I last used lilo, but you could try this:

In Slackware, mount the Mageia root partition at /mnt/mageia and add it to Slackware's fstab. Then change the Mageia stanza in Slackware's lilo.conf to:

Code: Select all

image = /mnt/mageia/boot/vmlinuz
initrd = /mnt/mageia/boot/initrd.img
root = /dev/sda6
label = Mageia
read-only

Jim

In this way, it worked. Thank you very jkerr82508. Two heads are better than one .
Currently, the entry in lilo.conf looks like:

Code: Select all

image = /mnt/mageia/boot/vmlinuz
append = "init=3"
root = /dev/sda6
label = Mageia
read-only

And Mageia 3 runs successfully.

Best regards.
Velans.