If this is your first visit, be sure to
check out the FAQ. You will have to register
before you can post. To start viewing messages,
select the forum that you want to visit from the selection below.
Please do not use the CODE tag when pasting content that contains formatting (colored, bold, underline, italic, etc) Use the QUOTE tag instead.
The CODE tag displays all content as plain text, including the formatting tags, making it difficult to read.
But, in general, it can't find the kernel image, and it is looking for the kernel image in a place it expects to find the kernel image.
Looks like the kernel image is called
linux.
Maybe it expects linux to be in
/boot
(and so /boot/linux).
So, you have to go find where that kernel image is and study the directory structure containing it and then experiment by changing that directory structure until it works. It usually WILL work when you hit the right directory structure (assuming the image linux is, in fact, there). For example, you might have to create the directory /boot, then put linux an the other kernel/initrd files in boot. OR --- change the kernel statement to reflect the proper path to linux.
When you get the prompt
boot <cursor>
you might try to type some things, like
kernel /boot/linux
or
kernel /linux
and see if it goes.
EDIT: See above, starting at OR ---
An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski
Comment