Kernel Update : vmlinuz-2.6.6 : no such file or directory
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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!
Distribution: home: slackware 11 and work: SLES 9 on zseries
Posts: 13
Rep:
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.
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
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"
Distribution: SlackWare 10.1+, FreeBSD 4.4-5.2, Amiga 1.3,2.1,3.1, Windors XP Pro (makes a fair answering machine)
Posts: 287
Rep:
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.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.