Fedora This forum is for the discussion of the Fedora Project. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
10-13-2006, 12:59 AM
|
#1
|
LQ Newbie
Registered: Jun 2003
Location: New Orleans
Distribution: Fedora Core 5
Posts: 20
Rep:
|
Problem installing ieee80211 subsystem on a dell e1505
Trying to install the ieee80211 subsystem so that I can run my wireless card, the Intel 3945ABG. I get this error message when I do the make command:
Code:
[root@dellpenguin ieee80211-1.2.15]# make
Checking in /lib/modules/2.6.17-1.2187_FC5smp for ieee80211 components...
egrep: /lib/modules/2.6.17-1.2187_FC5smp/build//.config: No such file or directory
egrep: /lib/modules/2.6.17-1.2187_FC5smp/build//include/linux/autoconf.h: No such file or directory
make -C /lib/modules/2.6.17-1.2187_FC5smp/build M=/home/jason/ieee80211-1.2.15 modules
make[1]: Entering directory `/lib/modules/2.6.17-1.2187_FC5smp/build'
make[1]: *** No rule to make target `modules'. Stop.
make[1]: Leaving directory `/lib/modules/2.6.17-1.2187_FC5smp/build'
make: *** [modules] Error 2
[root@dellpenguin ieee80211-1.2.15]#
This is my info when I run uname:
Code:
[root@dellpenguin ieee80211-1.2.15]# uname -r
2.6.17-1.2187_FC5smp
Any help would be appriciated, thanks!
|
|
|
10-18-2006, 12:27 AM
|
#2
|
Member
Registered: Mar 2003
Location: Nevada
Distribution: Anything but Ubuntu... don't ask.
Posts: 145
Rep:
|
here is your fix...
ok I HAD the same problem but I fixed it and here is how:
first you need to connect that lovely network card(eth0) and configure your WIRED network
open terminal and switch to root. then run this command:
# yum install yumex
I know many will balk at this but hey: you bought a laptop, you want to be mobile... why the heck would you want to fiddle with config and command line on the go?!?
now before you can use yumex you need to open /etc/yum.repos.d and create a file called "atrpms.repo"
open the file (need to be root to do this) and add this:
[atrpms]
name=Fedora Core $releasever - $basearch - ATrpms
baseurl=http://dl.atrpms.net/fc$releasever-$basearch/atrpms/stable
gpgkey=http://ATrpms.net/RPM-GPG-KEY.atrpms
gpgcheck=1
save the file go back to terminal. then run (as root)
# yum update
that will start to update everything... just kill it when you see it load the atrpms repo... I know there is an easier way but this is what I did and I cant figure any other method right now...
next goto applications-system tools-Yum Extender. yumex will load and will configure itself.
once the repos have loaded go to the repo tab (by the way this will likely be the last time you use terminal... at least for now.) and check the atrpms option, then click refresh at the bottom.
after it refreshes, go to update and find the latest kernel (mine was kernel-smp 2.6.18-1.2200.fc5) check it and the corosponding devel package (kernel-smp-devel-same version) then click the add to que button on the bottom (If you already updated to this kernel you will just need the devel package. if you went past it, reboot to an older kernel, uninstall your newer one-useing that handy REMOVE button in yumex- and reupdate to the correct one. this is important!!!) next go to the INSTALL button and search for and install ipw3935- look ofr the one specifically for your kernel version, this also is important as the versions need to match!!!. check it, click add to que, and then to the que button. once in the que, simply his apply, sit back and watch the show!
once done it will install all the dependancies (includeing the daemon and the ieee80211 and crap)
after yumex is finished open terminal (I know... I lied) and type (as root)
# setup
then useing the keyboard go to system services, and on the NetworkManager hit space to mark it active. then tab to "ok" and hit enter. then exit.
you can now reboot to your shiny new kernel with wifi support!
the nifty thing here is that you will get a new connection icon by your clock, that allows you to manage your wifi connections on the fly... much like the windblows wifi manager!!!
BE WARNED!!!
I have done this and am typeing this very forum post on my wifi connection now, however I cannot get the darn daemon to run on startup. everytime I boot I have to open terminal and start it by running(as root)
# /sbin/ipw3935d
this will fix it... but this is annoying... looking for a fix for this also.
|
|
|
10-18-2006, 07:52 AM
|
#3
|
LQ Newbie
Registered: Jun 2003
Location: New Orleans
Distribution: Fedora Core 5
Posts: 20
Original Poster
Rep:
|
Yes I kept messing with it and those are actually the exact steps that I followed, thank you!
Have you been getting any problems after, it seems that if my wifi is on too long Fedora starts to lagg real bad. Like I will be typing and it will freeze and hold one key for aaaaaaaaaaaaaaaaaawhile, like that. When I do Fn + F2 it stops immediately. Any reason why? Thanks for the assistance and for taking the time to post that, I am sure that it will be helpful to others that stumbled around.
|
|
|
10-18-2006, 10:38 AM
|
#4
|
Member
Registered: Mar 2003
Location: Nevada
Distribution: Anything but Ubuntu... don't ask.
Posts: 145
Rep:
|
I was experianceing that too originally, I ended up uninstalling ipw3945 and ALL its dependancies, rebooting and then reinstalling them (simply by selecting ipw3945 only) it seemed to fix it. I think the ipw3945 daemon had a memory leak or something but I cant be sure.
quick question: did you get it to autostart on boot? if so how?!? I can t get that darn daemon to load automatically.
EDIT: nevermind, just added "/sbin/ipw3945d" to the bottom of /etc/rc.local
Last edited by IcoNyx; 10-18-2006 at 11:28 AM.
|
|
|
10-18-2006, 02:10 PM
|
#5
|
LQ Newbie
Registered: Jun 2003
Location: New Orleans
Distribution: Fedora Core 5
Posts: 20
Original Poster
Rep:
|
Quote:
Originally Posted by IcoNyx
I was experianceing that too originally, I ended up uninstalling ipw3945 and ALL its dependancies, rebooting and then reinstalling them (simply by selecting ipw3945 only) it seemed to fix it. I think the ipw3945 daemon had a memory leak or something but I cant be sure.
quick question: did you get it to autostart on boot? if so how?!? I can t get that darn daemon to load automatically.
EDIT: nevermind, just added "/sbin/ipw3945d" to the bottom of /etc/rc.local
|
Awesome, I will try that and see how it goes. Also thanks for the idea of autostarting the daemon, going to implement that also.
Thanks again!
|
|
|
All times are GMT -5. The time now is 02:58 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|