IPW3945 Booting Problem

[Thomas Paine]

I have my wireless mostly working on my laptop, but I have two issues left.

First off, my wpa_supplicant tries to start before my ipw3945d daemon.
I searched, but I can't seem to figure out a way to get it to start afterwards.

Second, I searched and found several posts on getting gnome to try my
login password to unlock my keyring, and I tried without success on
adding a line to my pam. My password to my keyring is the same as the
password when I login, so I'm not sure what is causing it to not use
my password.

Thanks.

[Mikkel]

Thom Paine wrote:
> I have my wireless mostly working on my laptop, but I have two issues left.
>
> First off, my wpa_supplicant tries to start before my ipw3945d daemon.
> I searched, but I can't seem to figure out a way to get it to start
> afterwards.
>
> Second, I searched and found several posts on getting gnome to try my
> login password to unlock my keyring, and I tried without success on
> adding a line to my pam. My password to my keyring is the same as the
> password when I login, so I'm not sure what is causing it to not use
> my password.
>
> Thanks.

You may want to take a look at
/usr/share/doc/initscripts-8.45.7/sysvinitfiles - it describes how
the order services are started and stopped is controlled. One thing
to keep in mind if you are going to change the order of a service,
you should run "chkconfig --del <service>" before editing the file,
and run "chkconfig --add <service>" after making the changes so that
the links get updated properly.

Mikkel

[Todd Zullinger]

Thom Paine wrote:
> I have my wireless mostly working on my laptop, but I have two
> issues left.
>
> First off, my wpa_supplicant tries to start before my ipw3945d
> daemon.  I searched, but I can't seem to figure out a way to get it
> to start afterwards.

Mikkel's reply hopefully helped you to get the startup order right.
Alternatively, you may be able to not use the wpa_supplicant service
directly if you use NetworkManager.  I have an ipw3945 in my laptop
and use NM to connect to my wireless network using WPA2.  I don't have
the wpa_supplicant service enabled.
> Second, I searched and found several posts on getting gnome to try
> my login password to unlock my keyring, and I tried without success
> on adding a line to my pam. My password to my keyring is the same as
> the password when I login, so I'm not sure what is causing it to not
> use my password.

I'm running FC6 and have pam_keyring-0.0.8-3.fc6 installed.  My
/etc/pam.d/gdm file looks like this:

#%PAM-1.0
auth       required    pam_env.so
auth       optional    pam_keyring.so try_first_pass
auth       optional    pam_ssh.so try_first_pass
auth       include     system-auth
account    required    pam_nologin.so
account    include     system-auth
password   include     system-auth
session    optional    pam_keyinit.so force revoke
session    include     system-auth
session    required    pam_loginuid.so
session    optional    pam_console.so
session    optional    pam_keyring.so
session    optional    pam_ssh.so

The two relevant lines I added are:

auth       optional    pam_keyring.so try_first_pass

and

session    optional    pam_keyring.so

I don't recall if there was anything else I needed to install or tweak
to get this working, I don't think there was.  Hopefully someone will
smack me with the clue stick if I'm forgetting anything important.

Check the list archives for pam_keyring and you will hopefully find a
few other discussions on getting this to work.  I've had it working
since FC5 and it's quite handy.

Good luck!

[Thomas Paine]

I checked my gdm and it matches, yet I still get prompted to iunput my password.

I disabled wpa_supplicant when I boot up, and that cleared up another
boot error.

I tried removing and reinstalling pam_keyring, but I still need to put
in my password.

Any more ideas?

I even reordered my gdm file the same as yours as I thought it might
be a line number thing.

Thanks.

[Kevin Cummings]

Thom Paine wrote:
> I checked my gdm and it matches, yet I still get prompted to iunput my
> password.
>
> I disabled wpa_supplicant when I boot up, and that cleared up another
> boot error.
>
> I tried removing and reinstalling pam_keyring, but I still need to put
> in my password.
>
> Any more ideas?

I don't think its possible to *not* have to input your passcode (unless
is null).  Its not your login password, its your encryption passcode.
Just because they're the same value doesn't mean that one will suffice
for the other.  Mine are different.  I have to type them in each and
every time I need to use them.  Its a PITA.  Everything I have read says
that you shouldn't use a null passcode, then your passwords can be
compromised by just breaking your login password, but I'm beginning to
wonder if the convenience isn't worth the risk, especially if you have a
sufficiently strong password to begin with.

Under my setup (done by my laptop provider), NetworkManager applet runs
when I login, and if my ethernet is *not* connected, it tries to bring
up the wireless, prompting me for my KeyRing Manager passcode.  My
problem is with NM not always connecting to my wireless network.  Its
hit or miss (mostly miss) while sometimes ending after 1 attempt, other
times prompting me for my wireless key.  I am guess that my success rate
is well less than 3%.  And it doesn't matter how my wireless AP is
configured (which protocol, or none at all).  My daughter's Windows
wireless has no problems with my wireless AP (or at least the converse
failure rate that I do B^)
> I even reordered my gdm file the same as yours as I thought it might
> be a line number thing.
>
> Thanks.

[Thomas Paine]

Maybe to clarify, I have my login password the same as my keyring
password. NM seems to be remembering my WPA key, and if my ethernet
isn't plugged in it uses my wireless and that works 100% for me. It's
jsut the nuisance of typing in my keyring password everytime I connect
to wireless.

Thanks.

[Kevin Cummings]

Thom Paine wrote:
> Maybe to clarify, I have my login password the same as my keyring
> password. NM seems to be remembering my WPA key, and if my ethernet
> isn't plugged in it uses my wireless and that works 100% for me. It's
> jsut the nuisance of typing in my keyring password everytime I connect
> to wireless.

have you tried setting your keyring passcode to nothing?

It shouldn't prompt if there isn't one....
> Thanks.

[Todd Zullinger]

Thom Paine wrote:
> Maybe to clarify, I have my login password the same as my keyring
> password. NM seems to be remembering my WPA key, and if my ethernet
> isn't plugged in it uses my wireless and that works 100% for me.
> It's jsut the nuisance of typing in my keyring password everytime I
> connect to wireless.

Maybe it's worth deleting and recreating your gnome-keyring?

I think all you need to do to delete your keyring is to remove the
file ~/.gnome2/keyrings/default.keyring.  You may need to logout and
do this from the console, I'm not sure.

There's a page on the wiki[1] that says you can change your password
in FC6 using "/usr/libexec/pam-keyring-tool -c" or
gnome-keyring-manager but neither of those work for me.

[1] http://fedoraproject.org/wiki/Tools/NetworkManager