Kernel Update : vmlinuz-2.6.6 : no such file or directory
 

well i've installed a new kernel following those operations :

# rm linux | ln -s linux-2.6.6 linux
# make menuconfig
# make bzImage
# make bzdisk
# make modules
# make modules_install
# mv System.map /boot/System.map-2.6.6
# mv .config /boot/config-2.6.6
# mv /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.6.6

then update lilo.conf (no error via bash mode) but when reboot i can't see the new kernel...

then i started X and see throught the control center that the new kernel has got an error in the lilo.conf :


Boot image : /boot/vmlinuz-2.6.6
fatal : open /boot/vmlinuz-2.6.6: no such file or directory



?!?!?!?!?!?!?!?! help please!

I'll assume the file is really there.. (under /boot)

One thing that can be causing this problem is that you try to start from a different partition than where the kernel is to be found. Did you check that your lilo.conf was ok before you ran lilo?

i've cheked the lilo conf via the control center, button : check configuration , and then it say kernel 2.6.6 no such file or directory!

i've done all the steps correctly (i hope so but indee something was wrong) and now seems that with that string of the lilo .conf no kernel image is associated!

issue this command: ls /usr/src/linux-2.6.6/arch/i386/boot

this should tell you whether or not there is an actual bzImage there. if there is then just try to re copy the file (command i use is: cp /usr/src/linux-2.6.6/arch/i386/boot/bzImage /boot/vmlinuz-2.6.6). i use this instead of the mv command just because it's a personal preference.

otherwise, if the bzImage doesn't exist you'll need to recompile your kernel.

good luck!

Tips on kernel building
 

Do not just assume that all is well after a kernel build.
It is not likely that you will be able to read the several THOUSAND lines that scroll by for the kernel build... One too many errors and you have no paddle up the creek

Better build suggestion....

cd /usr/src/linux #linux is the default sym link to ANY kernel sources make it that way with ln
make mrproper #for EVERY BUILD
make clean
# if you have a config file you want to use cp it to /usr/src/linux/.config
# edit MAKEFILE find EXTRAVERSION and set a name for it...
# This keeps a working kernel intact
# or you may use the sript below BEFORE you make modules_install
if OLDCONFIG then make oldconfig
make xconfig or menuconfig # to make your changes
else if
new kernel configure
make xconfig or make menuconfig
fi
make dep
# let us build a kernel and have a readable output file

nohup make bzImage &
tail -f nohup.out # if you want to watch
if you are building a kernel below 2.6 open a new term and

nohup make modules 1>modules.out 2>modules.err

after the builds are done you can read these files with less or more or a text ed
less nohup.out #kernel build
less modules.out #mod build
less modules.err #mod errors

if all is good
make modules_install

and here is a help script but you must edit for your own box
#!/bin/sh
cd /boot
mv vmlinuz-YOURS vmlinuz-YOURS.1
mv System.map-YOURS System.map-YOURS.1
mv config-YOURS config-YOURS.1
cd /lib/modules
cp MODULES_CURRENT MODULES_CURRENT.1
cd /usr/src/linux
make modules_install
cp System.map /boot/System.map-NEW
cp .config /boot/config-NEW
cp arch/i386/boot/bzImage /boot/vmlinuz-NEW
cd /boot
rm System.map
rm config
ln -s System.map-NEW System.map
ln -s config-NEW config
echo "Edit your /etc/lilo.conf and run lilo!!!"
echo "make sure you ID the former kernel with .1 and make a new boot for the NEW one"

Doing the above will save some headaches...

Yes I build LOTS of kernels.... I have a WULF....

Is the System.map and .config necessary to be in /boot?

I have NEVER done that before. And my system is working fine. Please tell me what is it about.

YES... For more info on this subject read the kernel HOWTOs
The System.map lays out locations for the kernel it does get checked on occations...
The config file is there more as a 'safe' keeping for your current configuration.
These are linux defaults and should be used.....

alright, after copying System.map to /boot. Do I need to reinstall lilo and reboot?

if ur lilo.conf was already updated with the new link to the new kernel, just reboot, else u'll have to update it!

well ,i've made the file bzImage, that file is under /usr/src/linux-2.6.6/cd arch/i386/boot
i also copied it in this way :

# cp /usr/src/linux-2.6.6/arch/i386/boot/bzImage /boot/vmlinuz-2.6.6).

then i've to perform those 2 commands :

# make modules
# make modules_install

but from which directory ? i assume the directory is linux-2.6.6 right ?

from here i issued make modules and i got :

make[1] 'arch/i386/kernel/asm.offsets.s' is up to date
CC [M] drivers/net/dummy.mod.o
LD [M] drivers/net.dummy.ko

that's all
then make modules_install adn i got :
if [ -r System.map ]; then /sbin/depmod -ae - F System.map 2.6.6; fi

that's all.

are those commands right?

kernel successfully compilated and installed!!! :) yahooooooooooooo


but now i got another problem ! ahahahah i'm starting to love linux!!!

the NTFS hard disk are not mounted (with the old kernel they were ok).... uhmmmm i'll make a gooogleeeee

Did you compile in NTFS support with the new kernel?

uhmm i'm not sure... when i've done menuconfig i have not choose nothing.. only saved new configuration file!

trying to recompile the kernel..
but i cand find any NTFS info in the menuconfig...

:confused:

found it! i'm a dumb.