[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2.2.17 upgrade

On Mon, 28 Aug 2000, Dale L . Morris wrote:
> I installed the 2.2.17 kernel over 2.2.16 using the make-kpkg
> option. I'm having a problem getting lilo to boot the 2.2.17 kernel,
> if I 'cd /' then run '/sbin/lilo' the machine boots up without any drivers
> for eth0 or sound. If I run 'lilo -L' from / it boots up the old 2.2.16
> kernel. The only way I can boot into 2.2.17 is to use the boot floppy
> I made. I know this is simple, but what do I need to do to map lilo to
> 2.2.17?
> thanks
> -- 
> "Know thyself.."
> -- 
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null

Odd. It should've run lilo for you and backed up the old kernel. When you did
dpkg -i kernel-image-2.2.xx<version>.deb did it run lilo? Didn't it also copy
the modules into /lib/modules/2.2.17? I had no problems whatsoever using
make-kpkg. Did you configure the proper modules for the new kernel? You have
to enable module support, too. I need a little more information from you.
What output do you get when running make-kpkg?

Did you install the Debain package that it created? Sounds like you may have
skipped that.

Daniel E. Baumann
E-mail: baumannd@msoe.edu (preferred)
        baumannd@obfuscation.penguinpowered.com (caution: dynamic DNS 
																								service, may bounce)

Web location: 	http://www.msoe.edu/~baumannd

"Life would be so much easier if we could just look at the source code." 

      -- Dave Olson

Reply to: