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.
The automatic module loading support can't be installed as a module. It has to be installed into the kernel. The file systems themselves can be installed as modules. If you go under the file system menu you should be able to select Y, N, or M. But I have to warn you, I have never used xconfig before so I am not sure what it looks like when something is a module vs. compiled into the kernel image.
i went back into the xconfig and searched in the file systems to find this under the Kernel automounter version 4 support:
To compile this support as a module, choose M here: the module will be
called autofs4. You will need to add "alias autofs autofs4" to your
modules configuration file.
It was selected as a module. Also, there is another Kernel automounter above it in the file system selection but this one is the 'newer' version. Should I, or can I, select both?
Also, how do i edit the modules configuration file to add the alias command(or check if its there yet)?
Originally posted by jtshaw The file systems themselves can be installed as modules.
Is this really true? I'd say that at least ext3 (or whatever file system you use on your root partition) must be compiled in to the kernel. Since the kernel modules are files in the file system you get into kind of a Catch-22 otherwise (a.k.a Kernel Panic).
I was making changes in the xconfig, saving, then rebooting into the new kernel-2.6.1 to see if it had affected any of the 'failures'...which it didn't. I'm really at a loss and am definately in the deep end of the bottomless pool...and sinking faster than an anchor.
I can't bootup into my original linux as i'm missing some lib2.so or some such thing(after booting the linux-2.6.1 kernel, i booted the original config up but got locked up during bootup...i waited for 15 min. or so(it was probing for new hardware as the 2.6.1 wasn't recognizing my mouse, sound driver, etc) while it probed. i thought it was locked so i just reset. then on the next bootup, i noticed the message indicating linux wasn't shutdown properly(paraphrased) and i chose to do a thorough scan(another paraphrase) of my drives. i auto-corrected and that's when i seemed to have lost those lib2.so file thingies.
So, i hate to say it, but i'm just going to re-install linux again lol.
thanks for all the help here as I have learned much. I'll probably be back in a few hours with more problems!! haha
Is this according to plan (to mess things up and try again until you've learned)? If it is, then I'd say that you've learned some stuff already . If it's not what you had planned and you're pissed right now , then I'll have to ask if you really need a new kernel or if you couldn't just go with the default 2.4 kernel.
We'll be here waiting for your next bunch of questions though. I will be up for a couple of hours more (it's currently 9 PM). Otherwise I assume that I'll see you around when I'm having my morning tea tomorrow
well, i didn't mess up the kernel on purpose just to learn.. i'd rather have it running correctly but hey, it was my first attempt at compiling my very own kernel.
na, im not peeved at all. it's a little frustrating but only because i'm not really sure what i did wrong to mess up my linux box where i can't even boot into it. lol. Oh well, it's all just a learning experience.
I will most likely be loading a Fedora Core1 distro onto my pc. it seems pretty cool and i know a few peeps online who use it and enjoy it as well.
but i do have one Q before i end myposting in this thread....
When i make changes in the xconfig or menuconfig or one of those.....does it affect EVERY kernel or just the one i'm currently using to edit it with? and are those changes automatic upon saving and rebooting? or do i have to compile the kernel again (completing the steps needed after this step) in order for these changes in the xconfig to take place.
The settings you enter in xconfig or menuconfig affect the compilation of the kernel that you're currently building. So it shouldn't have any effect on other kernels on the system. Nothing really changes on your system until you enter make install. Then, kernel modules are copied to your /boot directory.
Making your own kernel is not really a walk in the park (as you might have noticed ). Especially not a 2.6 kernel on a system that used to have a 2.4 kernel. Something (haven't read up on the subject yet) has changed in the module subsystem. This means that you should have updated the module-init-tools package too. Now he tells me! Sorry, I probably should have mentioned that.
My recommendation, if you want to compile your own kernel, is to start with a 2.4 kernel. To make it really simple, make a kernel with no modules at all. Make sure that you know what hardware you have and make a monolithic 2.4 kernel tailor-made for your system. I could give you some hints if you run into problems with sound card, network card and video card.
About tea. Always English Breakfast in the morning! In my experience, the best English Breakfast tea comes from Twinings. Now I've just had a cup of lovely Assam. If you were closer I had offered you a cup . There are still some crumpets left from the afternoon tea. We could have toasted them and eaten them with some butter and cheese.
hmmm, so you are suggesting i compile the same kernel that i already have? just tweaking it a bit, i s'pose eh? sounds like a grand idea.
to do that, would i have to d/l the kernel source from somewhere or is it somewhere in the files/folders?
I do know that i will be having with my sound card because I am using Onboard sound (KT 400) and hasn't worked in either linux distro that i've installed over the past few days(installing linux is fun).
thanks for the offer of crumpets and tea! It's been a long while since i've endulged in the good ol' crumpets and tea.
Download the latest 2.4 kernel from www.kernel.org (or your local mirror). It is still being maintained, so a shiny new 2.4 kernel should be "better" than the one you have (less vulnerabilities).
I'll look in to the sound card problem. But that's Linux biggest problem right now -- since it's members of the community that makes drivers, support for the latest hardware is not the best.
I take back what I said in the previous post -- VIA has drivers available for several Linux distributions: http://www.viaarena.com/?PageID=294
But still - it could be fun to try to include it yourself in the kernel (what you get from VIA is just a kernel module, I assume). I'll try to download the latest 2.4 kernel now and poke around a little in xconfig.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.