Leatherboard1

Fedora 8 problem fixes including wireless , wpa_supplicant, keyring

Fedora 7,8: Intel 915GM video cards work. (Just in case people are trying to look things up like I usually do to see before hand if things will work with certain systems.)

Fedora 8: WPA client.

Turn on Network manager, network dispatcher and wpa_supplicant.


(You actually should only need to turn on Network Manager and then it'll automatically call the other ones.)


If you use a WPA network. In network adminstration, turn off starting wireless at start up. It will take you awful long at boot to let the wireless fail because it doesn't have the password! It'll start by itself when it access the desktop anway. So you don't have to choose to activate it in network administration.



To fix the keyring asking for password prolem, set your keyring password the same as your login password. (Otherwise, you need to do something more complicated. But I hate complication.)



Type in command su then enter to enter administrator password. Run :yum install pam_keyring

Then gedit /etc/pam.d/gdm
My setting looks like this:

#%PAM-1.0
auth [success=done ignore=ignore default=bad] pam_selinux_permit.so
auth required pam_env.so
auth optional pam_keyring.so try_first_pass
auth include system-auth
auth optional pam_gnome_keyring.so
account required pam_nologin.so
account include system-auth
password include system-auth
session required pam_selinux.so close
session include system-auth
session required pam_loginuid.so
session optional pam_console.so
session required pam_selinux.so open
session optional pam_keyinit.so force revoke
session required pam_namespace.so
session optional pam_gnome_keyring.so auto_start
session optional pam_keyring.so

Copy the whole thing paste and save.
The next time the system restarts, it asks you something about allow applications to use keyring or not. Of course allow.

Warning: If you use a different version of Fedora or Linux, you have to be very careful with this. You might get authentication failed and will not be able to login.

For versions other than Fedora 8, you should just add these two lines :



auth optional pam_keyring.so try_first_pass
session optional pam_keyring.so


For KDE, I haven't tried out a working solution. The following may work.
The above editing definitely doesn't.

There's also some error with wpa_supplicant at startup, I didn't note down the exact message. Something like wpa_supplicant fail. /etc/wpa_supplicant.conf , dbus_bus_get file or directory doesn't exist. The fix is:


Login with administrator by typing su, enter, enter password. Go to /etc/rc5.d
There's a file named S(some number)wpa_supplicant.
The error message occurs because this service is started before network manager and other things start and get the wireless card ready. So the solution is to make wpa start later.


mv S(your number)wpa_supplicant S(some big number, use two digis because everything in my computer is 2 digit)wpa_supplicant. Then it'll start just fine.


Installing XFCE makes Fedora work much faster than KDE or GNOME. You may have the following problems:

No audio. Fix: try to check and uncheck something like "use ALSA sound driver" in audio and sound card settings. One should work for you.

Pidgin. Sometimes the software doesn't show your buddies and I haven't found any solution to that. It's a bug and we can't beat it.

If you have problems with Mplayer, see here.




Technorati : , , , ,
Del.icio.us : , , , ,




Technorati :
Del.icio.us :

33 comments:

Anonymous said...

I followed all the steps you outlined but still can not connect to a WPA access point. I can connect to open (no security) access point but when I try my WPA connection from the Network Manager it pops up a box with 2 widgets one combo box with only WPA listed and a text field for the pass phrase. When I enter it a hit submit it churns awhile then returns the same box over and over again....

Paul said...

OK, why don't you tell me your wireless card's brand and model first. If you have an intel 2200bg, it should work, I am sure we'll figure out a way to make it work.
But if it goes up to 4..., I read about many people having problems with it. Because it is relatively new, so it is not well supported.

Anonymous said...

My comment is virtually identical to "anonymous" of 11/25/2007. Prior to reading this blog I was following similar steps: I have an identical /etc/pam.d/gdm as Paul's Digital World (PDW) suggests and I moved edited /etc/rc5.d so that S12wpa_supplicant was moved to S94wpa_supplicant. My gnome keyring (what a quirky and user-unfriendly program) password and my login password are identical. I was able to successfully connect to a WPA access point (requiring a password) exactly once (prior to reading PDW's blog). Since that time I have had no luck. Whenever I attempt to connect, a window pops up asking for the password; I enter the correct password, it churns for a minute and then asks for the password again.

Paul said...

You need to tell me what your card's model is.

Anonymous said...

I'm using an Atheros 5212, version 5.3.0.35 (date: 4/5/2007). Thanks for your quick response.

Paul said...

Did you see your network card show up correctly(model and is listed as a wireless card)?

If everything shows up correct, then there's no hardware compatibility problem. We should look for problem with the password, keyring problems.

When you are asked the password, did you use the login password or the wireless network password?

Paul said...

No problem. I am just on computer and let's get your problem solved so that I can go to breakfast :).

Anonymous said...

When I run 'iwconfig' as root I get the following:

ath0 IEEE 802.11a ESSID:"JCD" Nickname:""
Mode:Managed Frequency:5.785 GHz Access Point: 00:1A:70:D1:3D:BB
Bit Rate:1 Mb/s Tx-Power:8 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=63/70 Signal level=-26 dBm Noise level=-89 dBm
Rx invalid nwid:130491 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

so I am assuming that the hardware is properly recognized. When I ask NetworkManager to connect to my WPA AP, I give it the WPA password (which happens to be 22 characters). Attempting to use my login password at the NetworkManager prompt doesn't work because my login password is apparently not long enough.

Paul said...

Oh, and go to system, administration, services. Click on wpa_supplicant to see if it's running or has error messages.
Let's try to find if there are easy solutions first.

Anonymous said...

I just verified that wpa_supplicant was running. I restarted and it did so successfully without any errors. [I really appreciate your help with this]

Paul said...

Yeah, OK, if the hardware is correctly recognized, that's a good sign. Otherwise, things'll get very complicated. Check if the wpa_supplicant is running OK. And are you able to change our wpa password. I mean mine is 10+ digits but I am just afraid that there are certain bugs that if your password's too long or anything...

Anonymous said...

Note also that NetworkManager and NetworkManagerDispatcher are both running as services at level 5.

Paul said...

Try change your password and see what you get.

Paul said...

You're welcome. I am happy to help.

Anonymous said...

I changed my password to something simple ("passw0rd"). When I enter it at the NetworkManager prompt, I clicked the "show password" button so that I could see if I was entering it correctly...all was done in vain...it still doesn't work and repeatedly asked me for the WPA password as before.

Anonymous said...

I just ran dmesg and noticed the following line:

ADDRCONF(NETDEV_UP): ath0: link is not ready

I imagine that this is related but I'm not sure what to do with the info.

Paul said...

You said you were able to connect once before applying the keyring change, do you wanna try uninstall pam_keyring and change the keyring file back to what it looked like?

Were you able to connect just once or you just tried once?

Anonymous said...

I have tried connecting umpteen times but have only been successful once. I am okay with uninstalling the keyring. After running 'yum uninstall pam_keyring' what file do I need to modify change the keyring back? /etc/pam.d/gdm?

Paul said...

OK, if it didn't quite work out before you made the keyring change then it's not keyring's problem. It might be the driver's problem. I think you should try the madwifi drivers.

http://fedoraguide.info/index.php/Fedora8#Madwifi
(Install linva repository first.)

Paul said...

Apply the changes, restart, try to connect and tell me what you get.

Paul said...

Oh, and I saw some pages on the web saying madwifi is specifically designed work for Atheros. So, give it a shot.

Anonymous said...

I already installed madwifi...prior to installing madwifi I couldn't seem to get the drivers to work so madwifi definitely moved me further along. I'll try uninstalling keyring and see where that gets me.

Thanks for your help.

Paul said...

http://www.fedoraforum.org/forum/showthread.php?
t=126266&highlight=Atheros+5212
(connect the two lines together... I wasn't able to put them in one line)

Paul said...

Try that post. That seemed like someone solving a madwifi problem.

Paul said...

Worst come to worst, you can try Ubuntu too to see if they give you the hardware support. I mean above all, they are all Linux and the most important thing is to choose a distro that supports your hardwares.

Anonymous said...

Paul: I'm sure you're off to other things (and I hope you enjoyed your breakfast). I just want to mention one more point...

I'm beginning to think that the problem is related to the gnome keyring. I uninstalled pam_keyring and then removed any keys via System -> Preferences -> System -> Keyring Manager. I rebooted and attemped to connect via the NetworkManager. Prior to asking for my WPA password it asked for my keyring password; instead of entering it I selected "deny" after which I was asked for my WPA password. Upon entering my WPA password I was in!!! The problem is that for the life of me I can't seem to reproduce this work-around.

I understand if you don't have time to respond. Thanks!

Paul said...

I did have breakfast but I'm actually preparing for GRE on my computer so I'm around :).

I just had a wild thought that maybe you should try not letting wpa_supplicant start at start up. Go to system->administration->services, choose edit all run-levels in the run-level menu and uncheck the three boxes in front of wpa_supplicant. I once saw somewhere mentioning wpa having a conflict with networkmanager and keyring both running etc.

Try this.

Paul said...

Networkmanager actually will call wpa_supplicant, but just do not start it at startup, see if letting networkmanager handle wpa_supplicant will help.

Paul said...

Oh, also, you don't need network dispatcher, disable that too. My guess is some of the things have conflicts but we're just not sure which. So, just enable networkmanager at startup, no networkdispatcher, no wpa_supplicant.

Paul said...

Oh, and go to system->administration->network, uncheck the network cards so that they won't be activated by network control but let network manager activate them (you just have to uncheck them in network and network manager will automatically start them.)

Anonymous said...

I copied and pasted your setytings thing, installed the pam_keyring, but now, my wireless does not show up on the nm_applet anymore, can't enable my wireless either... my wireless card is intel 3495 , for got to backup the settings for the "gedit /etc/pam.d/gdm" thing

Paul said...

Did you change the setting first and then installed pam_keyring or first installed pam then changed the settings. Because I suppose it should work only if you first insall pam_keyring (but I've never tried).

So do you want to try changing the setting back?

I've changed my settings but I'm sure you can post a comment here and ask anyone who sees your comment post their setting before change. If that doesn't work today, I'll be of more help probably in the evening.

Anonymous said...

brilliant guide - it worked perfectly - thanks a lot! :)