DebianThis forum is for the discussion of Debian Linux.
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.
Hello all, I am a very fresh newbie to Linux, and have reached the very scary conclusion that I should recompile. I have a few questions.
I have kernel 2.6.8.something or other (Debian 3.1, sarge), and I was wondering if I should download a later one like 2.6.13? Or if I have to download one at all to recompile? If these questions seem dumb, it's probably because I'm still dumb with Linux! Not that I'm trying to make excuses for myself or anything . . .
I also run my Debian on a laptop, and I would like to be able to "hibernate" as booting takes longer than Windows did! I downloaded software suspend 2, but apparently have to compile it into the kernel along with ACPI or APM (or something like that). I am clueless as to how to do this. And "compile" and "recompile" are still very scary words in my Linux vocabulary. Yup, I guess I'm that green. I think I should really know how to do this though, and I can't make head or tail of many of the instructions I have come across.
Somewhat unrelated question, but why does "Starting MTA:" take so long during the boot?
Okay, I got as far as "make-kpkg" in the case of which my computer tells me "command not found". So, I'm a little stuck there.
I accidentally entered "make" by itself once and it started doing something which took a lot of CPU and a long time, but it ended with a bunch of errors and never did make any file. Is 'make-kpgk' a standard thing in Debian? Cause it's not in mine!
Could this have anything to do with it telling me that it won't compile cleanly when I patched it with the Software Suspend 2 patch? Rats, and I really wanted to be able to hibernate.
Well I guess this will have to wait as it's time for church. l
Thank you, that did help.
I successfully compiled my first kernel in Sarge (220.127.116.11), but now it stopped detecting my network PC card on my laptop (Netgear, PCMCIA, 16bit, 100mbps, “FA411”). I did disable the ISA support in the kernel, as well as most SCSI and perhaps a few PCI. I'm almost positive I did not undo anything having to do with PC card or PCMCIA. I even compiled a second time and enabled more PCMCIA and network/ethernet stuff. Still no luck. What did I do wrong?
2. Using a Debian kernel is OK. Have a recent kernel image installed, or use the one which came with the distribution (binary, not source)
3. Copy the configuration which came with your kernel to /usr/src/linux/.config (note the dot in front of config). Run make menuconfig, look around in the config program, save your new configuration. Don't change anything in the config or your source!
4. Compile the kernel according to the directions in the manual, and install the new image.
5. Try to boot from the new image, and make sure everything works as before.
If you work like this, you start from a safe point where you know that you are compiling the kernel in the correct way. Otherwise, you are trying to solve 3 problems (patching, compiling, finding the errors) at the same time. That's impossible.
I have installed many different machines which required patches, including laptops, and I always started this way. Just to make sure that the _standard_ unpatched kernel compiled and installed correctly.
Some notes on swsuspend2: It doesn't patch correctly on all kernels. Debian kernels are even more difficult. You'd might have to use a pristine kernel. Refer to the manual how to do that. Scrap making initrd, you don't need it. Using intitrd in swsusp2 is complicated.
2.6.13 didn't work on my laptop, I stuck with 2.6.12.
WARNING: Debian uses initrd as a standard. As soon as you don't use it, you get a kenrel panic because the IDE drivers are not compiled in. Make sure you add IDE drivers to the kernel in make menuconfig, and NOT as a module. This is a config file for 2.6.12 on my laptop
Thanks, I will read through that ASAP. The thing is, I really didn't change much in the configuration (I could probably find everything I changed). When I boot the kernel, I get the message "cardmgr[I forget what number is here, would that help?]:no sockets found!" That is the only bug in the whole system as far as I can tell. It would be nice if I only had to recompile once instead of twice or more, but hey, what use is being a newbie without a little "experience"?
I will gladly accept a short-cut to fixing this, however, if anyone has experienced a similar problem.
Okay, I finally got around to recompiling again. I loaded the old configuration file (from 2.6.8), and didn't change anything except to remove 3Dlabs, which was causing an error in compilation. It took nearly three hours to compile since I didn't remove anything.
But NOW I get the message (on boot up) saying that it "failed to load pcmcia_core". What now? Is it a problem with the 18.104.22.168 kernel itself?