Hi Having some trouble with adding an kernel and booting it i put the kernel image i built in /boot and i added the lines in lilo.conf and then ran lilo and it said it added it but when i boot the computer up it doesnt show in the list to be able to pick that image to boot up as i try from the text mode to boot it and said no such image am i missing adding something somewhere thanks for any info on how to add this this kernel was built from an linux source i d/l from kernel.org it isnt an suse rpm one thanks BOB
Bob B wrote:
Having some trouble with adding an kernel and booting it i put the kernel image i built in /boot and i added the lines in lilo.conf and then ran lilo and it said it added it but when i boot the computer up it doesnt show in the list to be able to pick that image to boot up as i try from the text mode to boot it and said no such image am i missing adding something somewhere thanks for any info on how to add this this kernel was built from an linux source i d/l from kernel.org it isnt an suse rpm one
You may have overwritten an existing image, or you forgot to label it. What did you copy to /boot, what is the entry in lilo.conf for it? You should have copied /usr/src/linux/arch/i386/boot/bzImage to something like /boot/vmlinuz-2.4.17 and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
Hi Well i have most of what you have there except the last two lines as in my other entries that was make when i install suse it didnt have anything in opitional when i type lilo it saids it added it but when i look in menu of what is avail to boot that is listed no it didnt overwrite the kernel i have the main /vmlinuz is there also the vmlinuz.suse is there also the mem test thingie i will try adding the last two lines! as i never had this trouble other then here thanks On Sat, 1 Dec 2001, zentara wrote:
Bob B wrote:
Having some trouble with adding an kernel and booting it i put the kernel image i built in /boot and i added the lines in lilo.conf and then ran lilo and it said it added it but when i boot the computer up it doesnt show in the list to be able to pick that image to boot up as i try from the text mode to boot it and said no such image am i missing adding something somewhere thanks for any info on how to add this this kernel was built from an linux source i d/l from kernel.org it isnt an suse rpm one
You may have overwritten an existing image, or you forgot to label it.
What did you copy to /boot, what is the entry in lilo.conf for it? You should have copied /usr/src/linux/arch/i386/boot/bzImage to something like /boot/vmlinuz-2.4.17
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
i add that line initrd = /boot/kernel version and it doesnt know about it no such file or dir! On Sat, 1 Dec 2001, Bob B wrote:
Hi Well i have most of what you have there except the last two lines as in my other entries that was make when i install suse it didnt have anything in opitional when i type lilo it saids it added it but when i look in menu of what is avail to boot that is listed no it didnt overwrite the kernel i have the main /vmlinuz is there also the vmlinuz.suse is there also the mem test thingie i will try adding the last two lines! as i never had this trouble other then here thanks
On Sat, 1 Dec 2001, zentara wrote:
Bob B wrote:
Having some trouble with adding an kernel and booting it i put the kernel image i built in /boot and i added the lines in lilo.conf and then ran lilo and it said it added it but when i boot the computer up it doesnt show in the list to be able to pick that image to boot up as i try from the text mode to boot it and said no such image am i missing adding something somewhere thanks for any info on how to add this this kernel was built from an linux source i d/l from kernel.org it isnt an suse rpm one
You may have overwritten an existing image, or you forgot to label it.
What did you copy to /boot, what is the entry in lilo.conf for it? You should have copied /usr/src/linux/arch/i386/boot/bzImage to something like /boot/vmlinuz-2.4.17
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Bob B wrote:
i add that line initrd = /boot/kernel version and it doesnt know about it no such file or dir!
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
Well, like I said, you may not need it, and it won't be there if you didn't create it. The new kernels are becoming modular, so you may as well learn about initrd, even if you don't need it for your particular kernel. Because all stock distributions are coming with it. The "restricted" line just makes you give the global password when you try to boot single, or otherwise hack the system, like with boot: linux init=/bin/sh You should post the dir listing of /boot, and the section of lilo.conf that is related to your kernel.
well it wont take or do anything with those last two lines there must be another way or easilier way to have this show in list of kernel that you can boot and have it boot within major overhaul thanks again! On Sat, 1 Dec 2001, zentara wrote:
Bob B wrote:
i add that line initrd = /boot/kernel version and it doesnt know about it no such file or dir!
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
Well, like I said, you may not need it, and it won't be there if you didn't create it. The new kernels are becoming modular, so you may as well learn about initrd, even if you don't need it for your particular kernel. Because all stock distributions are coming with it.
The "restricted" line just makes you give the global password when you try to boot single, or otherwise hack the system, like with boot: linux init=/bin/sh
You should post the dir listing of /boot, and the section of lilo.conf that is related to your kernel.
Also when i run lilo it saids it has added like ADDED l-17 but no show in list so i just dont know! to bad it is this hard now to get it to go maybe time to go back to slack ! thanks On Sat, 1 Dec 2001, zentara wrote:
Bob B wrote:
i add that line initrd = /boot/kernel version and it doesnt know about it no such file or dir!
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
Well, like I said, you may not need it, and it won't be there if you didn't create it. The new kernels are becoming modular, so you may as well learn about initrd, even if you don't need it for your particular kernel. Because all stock distributions are coming with it.
The "restricted" line just makes you give the global password when you try to boot single, or otherwise hack the system, like with boot: linux init=/bin/sh
You should post the dir listing of /boot, and the section of lilo.conf that is related to your kernel.
Bob B wrote:
Hi Well i have most of what you have there except the last two lines as in my other entries that was make when i install suse it didnt have
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
CAREFUL... make sure you actually make the initrd that I've named. The initrd is used to load the modules you need at boot time. If you compiled your kernel, so that you need no special modules loaded at boottime, then you do not need an initrd. Read man mk_initrd and make sure you have the right modules listed in your /etc/rc.config file.
i install the modules etc the thing is it wont show in the list of choices to boot and i just dont know why like in slackware you ad the image to /boot add an few lines and it works this is what i am doing here and it doesnt work thanks On Sat, 1 Dec 2001, zentara wrote:
Bob B wrote:
Hi Well i have most of what you have there except the last two lines as in my other entries that was make when i install suse it didnt have
and you should have an entry in lilo.conf like: image = /boot/vmlinuz-2.4.17 label = l-17 root = /dev/hda3 initrd = /boot/initrd-2.4.17 restricted
CAREFUL... make sure you actually make the initrd that I've named. The initrd is used to load the modules you need at boot time. If you compiled your kernel, so that you need no special modules loaded at boottime, then you do not need an initrd.
Read man mk_initrd and make sure you have the right modules listed in your /etc/rc.config file.
participants (2)
-
Bob B
-
zentara