liloconfig refuses to add a linux partition and install lilo
Dear Slackers,
I am running Slackware64-14.2. I just upgraded the kernel and wanted to update also the lilo boot screen from the default lilo one with a red background to the Slackware black background. I chose the expert menu, but upon selecting the "Add Linux bootable partiton" option nothing happened, no menu appeared that offered linux partitions to add. So I had to run lilo using my old lilo.conf file. As a result, I am still with the default lilo boot screen. Do you have an idea why liloconfig refuses to add a Linux partition and install lilo? I tried renaming the existing lilo.conf, but it did not help, so the existence of a previous lilo.conf file is not the problem. Any suggestions will be appreciated. Best regards, Martin |
Why not just edit lilo.conf by hand? The line you need to change is the one saying menu-scheme. lilo.conf has its own man page which tells you what you need to change.
|
Yes, changing by hand certainly works, but I am just curios about the behaviour if liloconfig. It seems to me that it only works for a fresh installation, but does not allow modifying the lilo on an existing installation.
|
Quote:
|
Just tested liloconfig on my newly installed 14.2 and it works. In the expert mode, it won't let me select Linux first. I have to select Begin and go through all options before I can select Linux to add any partition to boot.
|
@sse007: I tried this several times, starting from Begin in the expert option. When Begin finishes, it refuses to prompt partition selection
|
Hello,
Quote:
-- SeB |
Didn't have any problems with liloconfig on Slackware64 14.2.
Even with /boot on other partition. Did exactly what is in previous post to get Slackware booting. Also added Windows. |
No problem with liloconfig here. Choose expert mode and then you have to start at the top of the next page and work each item until you have entered data from beginning to end.
If you don't fill in lilo headers you won't be able to choose any partitions |
No, after Begin upon selecting Linux, liloconfig returns to Begin. With the simple liloconfig option at the end it complains:
Code:
Fatal: No images have been defined Probably I have to issue some LVM commands before running liloconfig, so that the LVM /root partition is recognised by liloconfig? |
A member's sig from a Puppy Linux Forum I belong to comes to mind.
"I have found, in trying to help people, that the things they do not tell you, are usually the clue to solving the problem" |
Sure, the only problem is that the problem is still unsolved.
|
Maybe this will help
http://www.slackware.com/~alien/arch...README_LVM.TXT Quote:
|
@colorpurple21859: Thank you for the suggestion. I am familiar with this document, but it is directed toward first installation of LVM.
I guess the Slackware installer issues some commands in the background that make the LVM partitions visible to liloconfig. Unfortunately am unaware which these commands are. And the error that occurs when I try the simple option of liloconfig Code:
Fatal: No images have been defined |
if you want to try it using the installer., select partitions but do not format, skip the software installation and go directly to the config section and follow the document,
|
All times are GMT -5. The time now is 12:37 PM. |