[SOLVED] Building 2.6.34-rc1 kernel on current (BOB's way) ...... LILO ran automatically?

damgar · 03-13-2010, 07:06 PM

I'm confused by this. I have built maybe 20 kernels with Slack over the last 6 months. I always follow BOB's how-to. This time, building 2.6.34-rc1 on an as-of-today-current system (minus the kernels, as I build my own) something weird happened when I did

Code:

make modules install

Code:

root@i7:/usr/src/linux# make modules install
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  Building modules, stage 2.
  MODPOST 1890 modules
WARNING: modpost: Found 11 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
sh /usr/src/linux-2.6.34-rc1/arch/x86/boot/install.sh 2.6.34-rc1DAMAN arch/x86/boot/bzImage \
                System.map "/boot"
Warning: LBA32 addressing assumed
Added huge
Added generic
Added Daman
Added custom
Added 2.6.33 *
Added LFS_BUILD
Fatal: open /mnt/damanLFS/boot/LFS: No such file or directory
make[1]: *** [install] Error 1
make: *** [install] Error 2

What just happened?

botnet · 03-13-2010, 07:40 PM

pretty sure its make modules_install

at least thats what i always do, then copy the bzImage over, and run lilo manually

running 2.6.34-rc1 on -current with no problems

damgar · 03-13-2010, 07:50 PM

Ah yes I did leave out the "-". Just when you think you have something down......... <corrects typo and hides his embarassment>

allend · 03-14-2010, 07:36 AM

LOL - Join the club! Been there, done that.

linus72 · 03-14-2010, 07:41 AM

gnashley · 03-14-2010, 02:14 PM

Yeah, you don't want to be running 'make install'...