Dog's breakfast redux: What I did wrong!

[Art Edwards <edwardsa@icantbelieveimdoingthis.com>]

I now understand at least part of what happened. I spent more of this 
weekend than I wanted downgrading to stable. At the end the mouse was 
still smoking crack. I am running an nvidia graphics card so I tried to 
re-install the controller from nvidia. That was when it became clear 
that I was running a custom kernel without the source tree. This 
resulted from my original rebuild (February). I could not find the 
2.6.12 kernel-source (or the linux-source, for that matter), but I had a 
(seemingly) fine kernel image. When I upgraded to testing, I'm guessing 
that grub freaked about the kernel (I really don't understand why). 
There was an unfriendly take-over by lilo that I have yet to sort out. 
However, I'm guessing that lilo only builds a default stanza for Linux 
as vmlinuz, which was a 2.4.18 kernel on my machine. I  I did build a 
2.6.15 kernel from its source tree. This allowed me to install the 
nvidia driver that, in turn, put my mouse into rehab. I haven't yet 
tried to use the 'nv' driver.

So far, I have removed lilo (as in apt-get remove) and installed grub 
(native), yet lilo still haunts the machine.

Art Edwards

Arafangion wrote:

> > > "Jon Dowland" <lists@alcopop.org> wrote in message 
> > > [🔎] 20060509145221.GC19424@alcopop.org">news:[🔎] 20060509145221.GC19424@alcopop.org...
> > >   
> > >
> > >      
> > >
> > > > With a stable install (sarge) lilo should not be installed in the first
> > > > place, let alone upgraded.
> > > >
> > > >        
> Why not?
> Lilo is more capable than grub with respect to partition formats and
> afaik, is the only way to achieve a system that entirely uses LVM.
> For all other typical uses on x86 systems, I do still prefer grub.
>
> .
>
>