Re: lilo.conf problem
From: P.T. Breuer (ptb_at_oboe.it.uc3m.es)
Date: 01/01/04
- Previous message: Michael Heiming: "Re: bake-off and ...?"
- In reply to: pc user: "Re: lilo.conf problem"
- Next in thread: pc user: "Re: lilo.conf problem"
- Reply: pc user: "Re: lilo.conf problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 01 Jan 2004 10:10:26 GMT
pc user <paul@not_a_real.edu> wrote:
> On 2004-01-01, P.T. Breuer <ptb@oboe.it.uc3m.es> wrote:
> > pc user <paul@not_a_real.edu> wrote:
> > (incomprehensible para :-( )
> Didn't like it myself but hard to explain.
When explaining something, do not use the word *IT*!
Leave spaces between ideas.
> The idea was that I had
> copied the lilo.conf and just changed the ref to /dev/hda6 as the
> boot partition,
SPACEEEEEEEEEEEE. Full stop. Whatever. Put a brake on it!
You mean "root partition", not "boot partition"?
> I thought; problem is that I had a typo for the
> "linux" image so that it was /dev/hda5, which is the swap partition.
^^^ what "it"?
SPACEEEEEEE.
Yes, correct your problem (root=/dev/hda5 instead of root=/dev/hda6) and
rerun lilo.
And you do not mean "linux image", you mean "root partition".
> linux wouldn't boot since it was the wrong boot partition.
At least. So correct your mistake. And it's "root partition".
> The 2nd image, "old-linux", had the correct boot partition, /dev/hda6.
("root partition")
> For some reason, booting "old-linux" stops at loading the net, hotplug
> and usb stuff.
Shrug. Different problem. Probably you have the wrong ethernet driver
specified. Read your modules.conf, or /etc/modules.
> >> Using rescue system under SuSE 8.1, I was able to correct the lilo.conf
> >> BUT on bootup, I get the error that VFS cannot find/boot from hda5,
> >> of course. Running lilo, the error was that lilo don't understand
> >> device "0x0106"; what is this device?
> >
> > Whatever one you pointed it at. Major 1, minor 6. /dev/ram6, I suppose.
> > Point it at something sensible instead! Why do you choose a ramdisk?
> > Are you planning on running an initrd? Why? Just keep things simple.
> Whatever or whenever did I point it at? I have no idea
You are the only one WITH an idea of what you did.
> nor how it got
> there.
Find out. Tell us when you do.
> Oh, initrd is on my desktop lilo.conf; have tried deleting it
> for the laptop and no difference in booting.
Then I think you know how it got there! You seem to have more than "no
idea".
Why are you running an initrd?
> Aha, didn't run lilo
> when initrd was deleted; will try it.
Tell us about it when you *have* done something, not before.
> Probably will delete it from
> the desktop also.
OK. But going by your track record, I wouldn't have you touch a working
lilo.conf.
> Don't know how initrd got into the lilo.conf for
> the desktop.
Then you should ask yourself who has been playing with root in your
computer! Is your porridge OK? :-)
> > Why would you need to look at google? Reading your lilo.conf is the
> > indicated course!
> Google...because there is always someone who "answers" with the phrase
> "look in google" as if google had all the answers and regardless of
> the question; it looks to me like an auto-response by some people.
It is, when you have a real problem. But you don't have a real problem
- you have a mess created by yourself. It's your invention.
> Looking at the lilo.conf doesn't help me too much as I don't know
> the details/nuances even with info or man or docs.
You don't need to know details or nuances - it's perfectly
straightforward. Check that every line makes sense - there are no
shortcuts to doing so! You go through the lines one by one.
> I had done something including "looking". The original problem is that
> lilo.conf says the boot image is located on /dev/hda5, my swap partition.
Then change it. And no, boot= is not the "boot image", but the location
of the boot sector that gets written. It should be "hda", if you plan
on writing to the MBR!
Please be exact.
If you mean "root=", that is the root partition, and should be
/dev/hda6.
> Even when changing the /dev/hda5 to /dev/hda6, the boot process still say
> that it cannot locate the boot stuff on /dev/hda5! So where did the boot
> kernel/whatever get the /dev/hda5 since it is no longer on the lilo.conf.
You forgot to run lilo - you didn't change the boot sector. How do you
expect the boot sector to read your lilo.conf? I'm puzzled!
> However, your tip about the initrd in the lilo.conf may help if running
It is not a "tip".
> lilo after deleting it and the boot process looks at /dev/hda6 for its stuff.
> I had thought that initrd was a "required" entry as it has been on every
> fresh install I've done before SuSE's change to use grub.
If you have the modules on your disk, why put them in an initrd?
But I would leave well alone if I were you!
Peter
- Previous message: Michael Heiming: "Re: bake-off and ...?"
- In reply to: pc user: "Re: lilo.conf problem"
- Next in thread: pc user: "Re: lilo.conf problem"
- Reply: pc user: "Re: lilo.conf problem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
