bootlader issue lilo

General talk about packaging procedures and packages.
nilguy
Posts: 2
Joined: 28. May 2013, 06:42

bootlader issue lilo

Post by nilguy » 28. May 2013, 07:21

i really faced this issue back wen i dual booted win xp n some linux os with lilo n just my new hard drive become unbootable

after trying grub based distro frm 2 yrs i just want to try slackware based os but it still uses lilo also read start up guide of salix were still lilo as bootlader is used is there any option to install grub or grub 2 instead of lilo while installing

also i tried salix in live mode n in kde info center it doesnt detect my processor n core while other mandriva/suse/fedora/debian just detects...............so is it normal to install............................

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 28. May 2013, 07:42

It should be reasonably straightforward to switch to Grub after installation.

I'm not sure about the core detection, but it shouldn't make any difference whether you're using Live or not. Have you tried any other Salix flavours on that machine? Not that that should make any difference either ...

How exactly can you tell they aren't detected?

nilguy
Posts: 2
Joined: 28. May 2013, 06:42

Re: bootlader issue lilo

Post by nilguy » 28. May 2013, 08:01

just tried slackel but same issue abot core n why not salix just provide an option to bootlader whether to use grub or lilo while installing


n wat abot mbr if i just installed lilo n then through repos grub can u just guide me how to do that in deep..................

User avatar
gapan
Salix Wizard
Posts: 5531
Joined: 6. Jun 2009, 17:40

Re: bootlader issue lilo

Post by gapan » 28. May 2013, 08:29

What do you mean it doesn't detect your processor? Of course it detects your processor, otherwise it wouldn't work at all.

And what issue did you have with lilo? And why are you sure you''ll have the same issue with the lilo in salix?
Image
Image

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 28. May 2013, 08:34

I'm afraid I haven't used Grub for some time so I can't give you reliable advice about it. But if you do install Salix, you may find Lilo meets your needs well enough without the bother of changing it. In particular, dual booting with Windows shouldn't be a problem, though you might encounter some hiccups dual booting with other distros (with a different kernel).

noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 13. Dec 2013, 16:50

Hello again,

Talking about lilo, how would I edit lilo to dual boot my old ubuntu partition,on startup lilo says "couldn't mount be cause of unsupported optional features (240)" ?
Both are ext 4.

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 13. Dec 2013, 17:02

How are you trying to reconfigure Lilo?

Try lilosetup, or failing that, liloconfig.

djemos
Salix Warrior
Posts: 1071
Joined: 29. Dec 2009, 13:45
Location: Greece

Re: bootlader issue lilo

Post by djemos » 13. Dec 2013, 19:38

noob51 wrote:Hello again,

Talking about lilo, how would I edit lilo to dual boot my old ubuntu partition,on startup lilo says "couldn't mount be cause of unsupported optional features (240)" ?
Both are ext 4.
This message has nothing to do with your boot problems. Same message here but lilo or grub boots fine.
what is your disk partitions, where your linux distro's are installed, what kernels do you have, what ubuntu version etc.
You did not provide any information so it is difficult someone to help.

noob51
Posts: 54
Joined: 22. Oct 2013, 16:56

Re: bootlader issue lilo

Post by noob51 » 13. Dec 2013, 22:59

OK,

xubuntu 12.04
boot/vmlinuz-3.2.0-54-generic

Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000d5e27

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 78065581 39031767 83 Linux
/dev/sda2 78065662 156301311 39117825 5 Extended
/dev/sda5 152258560 156301311 2021376 82 Linux swap
/dev/sda6 78065664 152258559 37096448 83 Linux (salix)

Partition table entries are not in disk order

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

User avatar
mimosa
Salix Warrior
Posts: 3101
Joined: 25. May 2010, 17:02
Contact:

Re: bootlader issue lilo

Post by mimosa » 14. Dec 2013, 03:24

Did you try lilosetup or liloconfig? If not, how have you tried to update the bootloader? In any case, what happened?

To run lilosetup from the command line, after installing it if necesary, as root, do:

Code: Select all

lilosetup.py

Post Reply