DebianThis forum is for the discussion of Debian 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.
Hello friends, I compiled kernel-2.4.22, moved bzImage from /etc/src/linux-2.4.22/arch/i386/boot to /boot/bzImage added
Code:
image=/boot/bzImage
label=Linux-2.4.22
read-only
to /etc/lilo.conf after than i do /sbin/lilo, it shows me that the new Linux-2.4.22 is added to lilo than reboot the PC and ... none
the PC stuck at "LILO 2.22" and than reboot itself without any chance for me to choose which one kernel to use, load again and the same thing is repeating again and again (the PC dosn't stop to reboot)
I haven't on that PC floppy drive to make rescue diskette, please help me
have I chance to chroot the partition and to try get back old kernel in lilo.conf If I boot from the install CD (the PC is in the office, I am at home now)
next time use make-kpkg to make your kernel compilation. I was afraid of it at first, but it does a _great_ job.
Use a cd (first or any other except update) to boot the system, do a chroot and change lilo.conf, run lilo and then
(for the make-kpkg thingy)
as root
Code:
apt-get install make-kpkg
cd /your_path_to_the_kernel_source
make clean
make-kpkg clean
make-kpkg ......
cd ..
dpkg -i kernel-image-2.4.22.......deb
lilo
reboot
don't remember the params for make-kpkg as I am not in front of my box. There must be parameter about --append-to-version (as in 2.4.22-4-k7 and the version of the package).
this works as a wonder on my machine.
As a bonus you will have the configuration and the system.map files in the /boot dir, it will make new symbolic links from /vmlinuz to the new kernel, the old /vmlinuz link will be /vmlinuz.old (but you can prevent this behavior with params for the make-kpkg command), and with more params you can be asked at install time if you want boot diskette
Thanks pe2338, but I want first to compile kernel on the way that everyone compile it, than I'll try to do it by Debian way just because I use different distributions in home and work
I did it successfully (maybe) ! I have one more question
I used one old PC of mine to compile the new kernel. There I have 3Com NIC ... so when I installing woody it don't ask me about network settings, just ask me for the hostname.
So when the default (bf24) install was complete, I installed ncurses and compiled the kernel, the PC can't locate the NIC, I must type
and this is happened, every time when the PC is restarted. ifconfig showed me just the loopback
I added in /etc/network/interfaces the settings for the NIC and now everything is O.K. but ... why woody can't ask me for the network settings ? The NIC isn't new ... I inserted in the kernel module for the 3Com NICs but I think it don't load the modules :/
modify (better said add) a file in /etc/modutils and insert the aliases and all the necessary lines there (I don't remember which are they, but with a look at the other files there you will figure out)
then do a update-modules-modutils or something like that... good luck
it's strange for me, but in /etc/network/interfaces was added just loopback ... so I added and the parameters of the NIC and everything is O.K. When I restarter the PC for the first time with the new kernel I typed "modprobe 3c58x" once, and everytime that I restart the PC just ifconfig the NIC and add default gateway. Thanks pe2338
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.