thanks On Tue, 19 Dec 2000, Denzil Kelly wrote:
> Date: Tue, 19 Dec 2000 20:16:36 -0800 (PST) > From: Denzil Kelly <[EMAIL PROTECTED]> > To: dude <[EMAIL PROTECTED]>, debian-user@lists.debian.org > Cc: [EMAIL PROTECTED] > Subject: Re: Modules and kernel upgrades > > Yes, I had this problem a few weeks back. I posted a > message here and here is the fix that worked for me. > > Ah! What you have there is a gotcha in the current > Debian > kernel-building > documentation. Most dists put a .config in the linux > directory that > reflects > the options used to build the distributed kernel. > Debian doesn't. > However, > you can get it from /boot/config-2.2.17 (if you are > running Potato). > Copy > that file to /usr/src/linux/.config before running > make menuconfig or > make > xconfig. > > In your situation, I think the make-kpkg routine puts > the new config in > the > /boot dir. The old one will be available as > /boot/config-2.2.17.bak. > > --- dude <[EMAIL PROTECTED]> wrote: > > > > Hi all. im not sure where to find this information > > > > ive read some of the documetntaion > > > > the problem is that when i install and compile a new > > kernel > > and then make modules > > and > > > > make modules install > > > > everything seems to work, > > > > but when i boot up > > > > i see a lot of messages about modules not found > > > > what is going on? > > > > thanks > > > > > > > > -- > > To UNSUBSCRIBE, email to > > [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > > [EMAIL PROTECTED] > > > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Shopping - Thousands of Stores. Millions of Products. > http://shopping.yahoo.com/ >
