In your long string of makes you missed one important thing: make install (assuming
you've tested
it and want to install it).
I recommend booting up with the floppy (the result of make bzdisk) and then do a
"depmod -a" to
get the module dependancies for your new kernel all sorted out. I'm sure you don't
have to reboot
to get the full benefits (anyone?) but b/c now is not the time for me to start
fighting new
battles, i would reboot (with the new floppy). Then "depmod -a" and away you go. If it
works well,
then go back to your linux install directory (where you did the "make dep clean modules
modules_install bzdisk") and do a "make install". I usually do it the other way - i
make sure i
have a boot floppy of the kernel that works, then i just install the new one and if it
*doesn't*
work then i boot up w/ my floppy and make the necessary fixes. It just works almost
every time so
that's the most efficient for me. So for *me* it goes like this:
# make dep clean modules modules_install bzdisk install
then i reboot, and then it's
# depmod -a
Possibly one more reboot and badabing, everything is working perfectly.
Hope that helps :-)
j
--- Declan Moriarty <[EMAIL PROTECTED]> wrote:
> Further to the other post. I went to build a kernel again, and had to
> install bin86, gcc, the kernel source, headers, ncurses-devel, & ncurses. I
> now vaguely recall a reinstall on this m/c with the mandrake cd acting up
> somewhat :-/. It was still left looking for some stupid dependency thing called
> libbfd.2.9.5.0.16.so, which I couldn't find. Built the kernel anyhow from
> scratch screwed up first time over the missing bin86 which rpm never mentioned
> was needed, BTW, and I forgot the <make modules_install> second time :-(.
> Sorted that, and I still have EXACTLY the same error message :-(. Before you
> ask, I renamed the /lib/modules/2.2.14 directory each time so I wouldn't have
> new modules landing on old ones. I think I know how to do a kernel.
> make xconfig then (MUCH later)
>
> make dep; make clean; male all; make modules; make modules_install; make bzImage
>
> Judging by file dates in the /boot directory, it all went in except the module
> info. vmlinuz-2.2.14-15, & System.Map are new. module-info is still from
> last August. Is this important?
>
> Have I screwed up again, or is it a hardware thing? The hardware approach would
> be to swap network cards, bring over the working kernel, which would run the
> machine, and generally try to transfer the fault some way. I could probably
> swap linux disks, as they each have a linux disk, and boot to a consoile. But I
> don't want to take these computers apart if I don't have to.
>
> BTW, is there a magic with rpm to find out what package on the cd supplies such
> a file? There's umpteen rpms there, and without querying each of them
> individually It would be nice to let something else do the work.
>
>
>
> -- Regards,
>
>
> Declan Moriarty
>
>
>
>
> Applied Researches - Ireland's Foremost Electronic Hardware Genius
>
> A Slightly Serious(TM) Company
>
> Without the optimist, the pessimist wouldn't know how happy he isn't.
>
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
