FedoraThis forum is for the discussion of the Fedora Project.
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.
I'm trying to compile my own kernel for Fedora 7 - which is going very well. Speed increases etc, but whenever I do I loose my wireless.
I've traced it back to both the stock kernel and also the src.rpm kernel from Fedora (!) is missing this module, so I'm having to go get it and build it.
My main question is this: do I need to grab it from anywhere special?
The main site (ipw3945.sourceforge.net) requires a daemon - which I don't like the idea of - not to mention a quick browse of google says the iwl module is using the new wireless stack in the kernel, making the daemon unnecessary.
Sorry if this seems trivial, but I'm just starting to play around with the kernel, and would like any tips in that area too.. Is there a collected fedora module set about?
Do I need to make any special settings for Fedora?
Is it wise for me to jump ahead and use the 126.96.36.199 - rather then sticking to the older 2.6.21 (I think I remember hearing Redhat back-port improvements, not sure if that's done in Fedora too)?
when you do a make menu config there is the 3945 driver under
network -> wireless on the new kernels if I remember correctly. I may not but I think that is where it is. It may require another driver in the kernel as well before it will show up. Make sure you put a 'm' next to it to get it to compile as a module if that is what you want. A 'y' will make it be compiled directly into the kernel.
Also, from what I've read and my own experiences the driver in the kernels (atleast the ones that are out atm) have problems with the 3945 card and are very hit or miss. Plus I don't know if you can enable monitor mode within the kernel driver. My recomendation would be to stay with compiling the driver yourself and moving the .ko file into the modules section after your kernel is compiled. This way you will have full control. I hope this helps in someway and I just moved back to fedora 7 so i haven't checked the kernels yet.
Also, a good starting point would be to take the lastest kernel in the repos and move the .config file over to your new kernel. Then do a make oldconfig (i think is the command) which should set just about everything up for you like it is in the old kernel, including the 3945 driver. After that you can do a make menuconfig and go in and tweak it like you'd like and remove all the crap you don't want.
If the make oldconfig doesn't enable the 3945 driver you might be looking for a kernel patch for it.
Let me know if you need any help.
Last edited by nomb; 09-04-2007 at 09:28 AM.
Reason: after thought