Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I am trying to install the new 2.6.4 kernel. (Yes, I'm new to Linux and probably should not be trying this)
I am down the the /sbin/mkinitrd /boot/initrd-2.6.4.img 2.6.4 part and it gives me the message:
linux:/usr/src/linux # /sbin/mkinitrd /boot/initrd-2.6.4.img 2.6.4
/boot/initrd-2.6.4.img/var/tmp is not a directory
Yes, I see that this was addressed earlier, but it was never answered fully. I'm hoping someone has had more luck since.
Also, when it comes to the next part of configuring grub.config file, do I put in everything from title and end where it says, (Note ? If so, then also, do I put in the LABEL area what it said root=.....which according to my file......='s root (hd1,1) Does this mean I put in the () as well?
Originally posted by andzerger this is how i do the sketchy stuff with my kernel..
edit the /boot/grub/grub.conf (or) /etc/grub.conf file
copy the entry for suse to the line below it, and change the name of the kernel to the one thats
not going to overwrite your old one, (/kernelname in grub.conf is /boot/kernelname from the / dir)
delete the line that says (initrd /imagename) and add a few words to the kernel line (initrd=noinitrd) ..
now when you reboot youll see two kernels in grub (as if you had windows and linux on the machine) and you can pick which one to go to.. im sure youll understand much better when you look at the grub.conf file
this works for lilo too in case you use that, i just dont know what lilo looks like anymore
This is what is in my /etc/grub.conf file. I don't understand what you are saying to change, and how.
your distro must be waay different, maybe you have something in /boot/grub.conf or /boot/grub/grub.conf that makes a little more sense, im sorry i wont be around for a while, someone else will walk you through, or maybe google can help (very specific keyword phrases usually turn up forums like this one)
Distribution: RHEL, Ubuntu, Solaris 11, NetBSD, OpenBSD
Posts: 225
Rep:
Quote:
Originally posted by Morbid A quick question....(I hope)
I am trying to install the new 2.6.4 kernel. (Yes, I'm new to Linux and probably should not be trying this)
I am down the the /sbin/mkinitrd /boot/initrd-2.6.4.img 2.6.4 part and it gives me the message:
linux:/usr/src/linux # /sbin/mkinitrd /boot/initrd-2.6.4.img 2.6.4
/boot/initrd-2.6.4.img/var/tmp is not a directory
Yes, I see that this was addressed earlier, but it was never answered fully. I'm hoping someone has had more luck since.
Also, when it comes to the next part of configuring grub.config file, do I put in everything from title and end where it says, (Note ? If so, then also, do I put in the LABEL area what it said root=.....which according to my file......='s root (hd1,1) Does this mean I put in the () as well?
Hi Morbid,
were you able to solve this problem?? I haven't been able to compile a new initrd file - still haven't tried to reboot, but thought I would try and get it sorted anyway as I (hopefully) will have an SCSI raid array soon and will definitely need the initrd file then!
No, I didn't get it to work. I thought I had everything set correctly and tried rebooting and wound up with a blank screen. I'm going to re-install again later this week. I've searched for quite some time looking for the answer. When I find it I'll post it. Good luck!
Distribution: RHEL, Ubuntu, Solaris 11, NetBSD, OpenBSD
Posts: 225
Rep:
hmmm there seems to be a bit of a coincidence here....we're bothing using SuSE9.0 and appear to be the only ones who have had this problem...
Well I guess there's not a lot else to do, but did you try recompiling your kernel morbid with everything you need to boot included, because I'm told - and I think it says this earlier in the thread - you shouldn't need the initrd image at all then?
I think I'm going to try Slackware...the CDs have been tempting me all week....
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Please ignore if inappropriate SteveK1979 and Morbid.
SuSE used to require loads of SuSE-specific patches in earlier versions of their distro. Simply loading down the sources from Kernel.org would leave you with a broken compilate, even when it went through the compiler without complaint. Did you check on their site whether you got everything necessary from them (i.e. their patches and readmes)?
Perhaps this will help. I did a search on SUSE and came up with this. No, I have not read it. (Foolish of me, I know) but, I am about to go to bed after freshly installing SUSE again. (This due to my failure to properly compile it to 2.6....yet AGAIN!) I'm tired...wife's cranky.....I'm going to bed! Night all!
I'd just like to say thank you so much to all the patient people here who help newbies like me. Especially to DrOzz who started this thread. I've been running Madrake 9.2 for about a month now and can finally compile a kernel with some realibility now thanks to this thread and this awesome forum resource.
Hi. Read the whole message thread but have a question with regards using old config. I am using Mandrake 9.2 which does not either contain the kernel source or include on the discs. of course no current .config file exists. i downloaded kernel 2.4.22 which is what i am running and according to instructions earlier in this thread ran "make oldconfig" to create a .config file with my currentt config. It prompted for NEW settings/features but seemed to create a default .config. this had the incorrect network card & audio selected and did not have ext3 fs which i am using since first set up.
Am i doing something wrong, miss something written here earlier or is this an issue specific to Mandrake? Would be a lot easier to start with the current config. Also in learning kernel configuration it would be easier to see what by default is needed even if i need to run "make xconfig" starting from scratch.
well its kinda hard to say what you need by default per se, as all machines
are different (for the most part) ...
for instance, my board has an onboard raid controller, which i would
need to compile into my kernel to have it work ...
thats one of many examples, but what i am trying to get across is that for
example if i gave you my config you would be compiling my config
for my chipset on my board, my NIC, my raid, etc, etc .. and your machine may not have this stuff ...
a generic basic config just has the general stuff that will give you a
successful boot and maybe only some of your things will work, and if
your lucky everything will ...
so the best thing you can do is identify the hardware you have, and just
recompile your kernel from scratch and just compile what you need, and
its also i guess we can say good practice to compile in stuff that you
think you may use in the future ...
so in conclusion my personal opinion is that i think its pointless to
do a make oldconfig on a default kernel that was package with your distro.
it makes more sense to do an oldconfig if you previously compiled and
you have the kernel set up already how you want it ..
thats how i look at it anyways ..
Thanks for the reply. There are a number of items that i am not sure of. My thought was that my own current (old) config would give me at least the starting point on what i need. Guess one of the things is to go through an entire .config and learn what each does.
As to my question on creating a .config with my current/original/default kernel settings (using make oldconfig) can you tell me what i did wrong or need to do differently to do this?
Thanks...
Suse needs a different syntax for their mkinit it appears. I did a lot more digging around the 'net and managed to find someone who, like us, has struggled to get 2.6.4 compiled. Thankfully he's done it before and figured out the syntax.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.