Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hello again, I am writing you all from my Windows box so you know this is not a good sign. Anyway I have just install Suse Linux, OpenSuse 10.0 to be exact and I am having a rather frustrating time with the kernel installation progress. I have kernel experience as I have been compling my own on various systems for a year now yet it seems to be with Suse I am having the worst time with. Now because Suse is using an initialram disk I need to have a initrd image file in order for me to boot. I have used this method in Fedora quite often. What happens is, after many times searching with google and LinuxQuestions I enter the following command.
mkinitrd -k vmlinuz-22.214.171.124 -i initrd-126.96.36.199
and this makes the initrd file in the present working directory. I then issue the command to send the file to boot everything goes well. Now I adjust my grub menu accordingly and upon boot up I get this error
error 15: file not found
I have gone over grub for typos etc. and have found none. Is there another means I should make my initrd image? Thanks again I would really love to get on my Linux machine again.
Help me understand something here. You have a number of different SuSE entries. How many entirely different SuSE installations do you have? Two?
In one case you are starting from first drive, second partition and going to the path /boot/file_here. In another case you are starting from first drive, third partition and going to the path /boot/file_here.
This will not work if you have only one SuSE installation.
For some reason or another SuSe added entries to the Menu list. It has 3 entries and one failsafe mode. That is correct. The entry that is going to the 3 partition is for safe mode. Any idea on what I to do from here?
Alright I just figured her out, this is my first time seriously sitting down with Suse so there are a few things that I have to watch out for, I went through the YAST configure utility where I send the options to my kernel and my initial RAM image. From there I had to tweak a few things manual to direct it to where my root partition was, which I had forgot to add previous thus making my kernel not boot. Thanks for all your help i appreciate it.