Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi all, I was trying to compile kernel 2.4.19 a few times already, and ran into a few problems. The problems were that I'd choose the newly compiled kernel from lilo and the screen gets blank/black. I'm sure it was some module that was not setup properly in xconfig. I tried so many different settings and still got the blank screen. A buddy of mine suggested "make oldconfig", and that supposingly was to use my current configuration of which I was running from and of which was a good working config from the default slackware 8.1 installation. Well that didn't work. My theory is since I was "make mrproper" too many times, which makes it vanilla, something changed in the transistion. So when I ran "make oldconfig" it didn't really use the actual configuratin I was running off from. My question is lets say I installed Slackware 8.1, and most things were working fine but wanted to add extra hardware settings, and so i download 2.4.19, now what steps should I take to save my current good configuration I am running from? This may be a newbie question, but I'm not sure if I ran "make xconfig" from the 2.4.19 directory that it starts off with my current running config, so is it that setup already or should I save something or load a "x" file name of which I'm not sure what is called or where it is located.
I don't know too much about the subject, but i have doubts whether or not the /usr/src/linux/.config (the file xconfig and menuconfig generate) will work for the new kernel. I would run make menuconfig before make mrproper and "save configuration to another file" and use that as a backup. Again, i might just be talking out of my ass, so i'll be watching this thread to see the real answer
Thanx man, I'm such a newb too with Linux, but I'm a technogeek none the less but winblows, yeah a drone basically, that was how I was paying my bills with, but since the market is not looking so great for winblows mofos, I just had to make the swith over linux to gain momentum and get back in the game. That is why for this question I want to phase out the headaches and get it down to minimum withough problems. So yeah my situation is I want to use a new kernel but also as well recompile from a good working config which I know works, for example the kernel 2418 I'm running now, works good, but missing some device/modules settings, and so I download 2419, manually do xconfig, and lilo goes black dude, make xconfig like a thousand times to phase out possibilities, but same shit still happens, mind you also that I even ran without some of the experimental shit that is there for kicks. Also purty much went Vanilla and sometimes it would work and load lilo, but problem with that is with my crap I would like to work such as usb mass storage, sound blaster live gameport, and a few other equipment aren't included in Vanilla. Tried to use oldconfig, but it didn't seem to work off the currently good working configuration, seemed it was oldconfig'in off a previous attempt at recompile, which was also not workin for me. I know this issue sounds repetitive, but I'm not sure how I would approach or phrase this in a simplier fashion. Ok so far I have done this since to phase out more headaches, I've reformatted, installed slack 8.1, now awaiting instructions on how to handle this in a way so I can back up anything, such as configs, or whatever extra files that may make this less painful for me, and then compile off these good backed up files. Any body wanna help this bastard out? LMAO. I will give your suggestions a try adam_boz.
Anyway, the make oldconcfig, as quoted from the kernel how to:
`make oldconfig' will attempt to configure the kernel from an old configuration file; it will run through the `make config' process for you. If you haven't ever compiled a kernel before or don't have an old config file, then you probably shouldn't do this, as you will most likely want to change the default configuration.
So, you may wanna check your /boot directory for a .config file of some sort to use. Try using the "make xconfig" command and there is a button below "save and exit" that says something about load config file, try loading the config file from your /boot directory.
Glad to hear you are trying the switch from winblows. Tell us more about what you mean by the lilo screen goes black?
The last step of the make install program runs lilo, but if you haven't edited your /etc/lilo.conf file yet, as I always for get to, you will have to rerun it after editing lilo.conf to point to your new (and your old) kernel. Old and new b/c if the new one bombs, you want to be able to boot up the second.
It doesn't make sense to me that after recompiling the kernel, lilo stops working. When lilo starts, the pc still has no idea where the kernel is. It is only after lilo that a bum kernel will cause problems.
I think there must be another problem either in the lilo.conf file or else in the mbr. Running lilo should tell you something. Running lilo should tell you which partitions were added successfully.