Re: lilo and mbr
I did reinstall lilo. When I reinstalled the kernel, I chose the option of wiping off the
old lilo.config and making a new one. I ran lilo after that. Does not help.
--- Riccardo Tortorici <riccardo.tortorici@email.it> wrote:
> You should reinstall lilo after compiling...something like that:
> make clean && make all && make modules_install && lilo
> in order to update the mbr with the new kernel image configured in
> /etc/lilo.conf.
> bye
>
> Punit Ahluwalia wrote:
> > I upgraded the kernel to 2.6.7, and successfully booted with the new kernel once.
> > However, I had to compile the kernel again, to include some additional support. I
> cannot
> > boot after compiling and installing the kernel the second time. I received a message
> > during the configuration that mbr.b was missing. I don't see it in /boot. On booting,
> > numbers start rolling on the screen as soon as BIOS transfers the control. I suspect
> I
> > have damaged the mbr. Any ideas?
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Meet the all-new My Yahoo! - Try it today!
> > http://my.yahoo.com
> >
> >
> >
>
> --
> - Riccardo Tortorici -
> Linux Registered User #365170
> Count yourself @ http://counter.li.org/ !
> Proudly Running Debian GNU/Linux "Sid" - Linux Kernel 2.6.9
> --
> HTML email can be dangerous, is not always readable, wastes bandwidth
> and is simply not necessary please don't send them to me!
> If you don't know what I'm talking about please read this:
>
> http://www.georgedillon.com/web/netiquette.shtml
>
>
>
> --
> Email.it, the professional e-mail, gratis per te: http://www.email.it/f
>
> Sponsor:
> Software per PC e non solo...scopri tutto quello che c'è da sapere!
> Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2969&d=16-11
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
Reply to: