I have F8 installed on a new Lenovo T61p with a 4965 wireless. I have
the following odd behaviour. There are 3 AP's in on the same network -
in fact no others are within scan range.


It seemed to be working fine - and associating with the nearest AP
(100% signal).


Suddenly after a reboot - (new kernel etc) - it refuses to connect to
the AP 12 inches from the laptop and insists on picking a second AP
which has very weak signal.


modprobe -r iwl4965 and re-initing the interface (via ifup/ifdown
using correct configs in /etc/sysconfig/network-scripts/

ifcfg-wlan0

No go.

However this black magic appears to work.

a) modprobe -r iwl4965
b) iwconfig wlan0 channel 11 # This is channel of
close AP

This spins and will not connect.

c) kill above.
d) modprobe -r iwl4965
e) turn off the radio kill switch and then turn it back on - this is
located on front of laptop.


f) ifup wlan0

Now - it picks up the AP next to the laptop ...

Are there some intel driver issues perhaps ???

thanks

gene


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Mon, May 05, 2008 at 08:19:56PM -0400, Mail Lists wrote:

> Are there some intel driver issues perhaps ???

The wireless support in Fedora kernels is very close to upstream.
This is often beneficial but sometimes unfortunate. For several
weeks, users of the iwl3945 and iwl4965 devices have been in the
latter category. :-(

You may wish to try the latest available F8 kernel in Fedora. It has
some recent fixes that have improved the situation for a number of
iwl3945 and iwl4965 users (but not all of them):

http://koji.fedoraproject.org/koji/buildinfo?buildID=47941

Hth!

John
--
John W. Linville
linville@redhat.com

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

John W. Linville <linville <at> redhat.com> writes:

> You may wish to try the latest available F8 kernel in Fedora. It has
> some recent fixes that have improved the situation for a number of
> iwl3945 and iwl4965 users (but not all of them):
>
> http://koji.fedoraproject.org/koji/buildinfo?buildID=47941

Hi John

That will certainly be worth a shot for the OP but do you know if there is an
associated kmod-nvidia rpm to match it yet (in livna devel?)



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On 2008-05-06 20:58, Mike wrote:

John W. Linville <linville <at> redhat.com> writes:


You may wish to try the latest available F8 kernel in Fedora. It has
some recent fixes that have improved the situation for a number of
iwl3945 and iwl4965 users (but not all of them):

http://koji.fedoraproject.org/koji/buildinfo?buildID=47941


Hi John

That will certainly be worth a shot for the OP but do you know if there is an
associated kmod-nvidia rpm to match it yet (in livna devel?)





I have a different problem with the iwl4965 wireless driver: on the
2.6.24.5-85.fc8.x86_64 kernel it doesn't seem to send out any packets
when trying to get an IP address, so initializing the WiFi interface
fails. The latest available F8 kernel from the above link
(2.6.24.6-90.fc8.x86_64) doesn't change that. It worked fine in the
previous kernel (2.6.24.4-64.fc8.x86_64) so that's the one I'm using.


I tested this on another system using tcpdump on the wireless interface.
With the -85 kernel there were no packets visible, but with the -64
kernel there were.


I'm on a Dell Inspiron 1720 with Intel PRO/Wireless 4965 AG or AGN.

To answer the question in the message I'm actually replying to, I have
no idea, but with the freshrpms.net version of the driver you wouldn't
have that problem since it uses DKMS to compile the driver at boot time
when it hadn't already.


--
Sjoerd Mullender

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

John W. Linville wrote:

On Mon, May 05, 2008 at 08:19:56PM -0400, Mail Lists wrote:



Are there some intel driver issues perhaps ???



The wireless support in Fedora kernels is very close to upstream.
This is often beneficial but sometimes unfortunate. For several
weeks, users of the iwl3945 and iwl4965 devices have been in the
latter category. :-(

You may wish to try the latest available F8 kernel in Fedora. It has
some recent fixes that have improved the situation for a number of
iwl3945 and iwl4965 users (but not all of them):

http://koji.fedoraproject.org/koji/buildinfo?buildID=47941

Hth!

John

Thanks for feedback. I have also discovered part of the black magic
recipe requires me to do 2 more things.


1) kill and turn off avahi-dameon service.

2) kill off something called nm-applet - i cannot find where this is
started (as the logged in kde user not root). It is not visible
anywhere on the KDE task bar so not sure how to shut off - but a
killall seems to work for now.

Then the various aditional cauldren stirring outlined earlier have
worked a total of 2 times now!


Best - and looking forward to fixes!!

Thanks again,

gene/

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, 2008-05-06 at 20:15 -0400, Mail Lists wrote:
> 1) kill and turn off avahi-dameon service.

If you never need it, then leave the service turned off.

chkconfig avavahi-dameon off

> 2) kill off something called nm-applet - i cannot find where this is
> started (as the logged in kde user not root). It is not visible
> anywhere on the KDE task bar so not sure how to shut off - but a
> killall seems to work for now.

It shows you an interface to the NetworkManager. If you don't use
network manager, you can turn that service off and the nm-applet will
not bother you.

chkconfig NetworkManager off

If you do use the NetworkManager, and you just don't want to be bothered
with the applet, the program will be launched from your desktop session
preferences (the exact name of which I cannot remember for KDE).

--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Thank you for suggestions.

Tim wrote:


If you never need it, then leave the service turned off.

chkconfig avavahi-dameon off


Yes I had done that after stopping it.

2) kill off something called nm-applet - i cannot find where this is
started (as the logged in kde user not root). It is not visible
anywhere on the KDE task bar so not sure how to shut off - but a
killall seems to work for now.



It shows you an interface to the NetworkManager. If you don't use
network manager, you can turn that service off and the nm-applet will
not bother you.

chkconfig NetworkManager off

Well - neither NetworkManager nor NetworkManagerDispatecher
service were ever running. I have found them to be not useful (yet) for
my environment (changes between wireless and wired with static).


nm-applet was started by kde - and runs as the logged in user -
it did not show in system tray or anywhere else far as I can tell but
magically starts each time I login.


--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2008-05-07 at 07:23 -0400, Mail Lists wrote:
> neither NetworkManager nor NetworkManagerDispatecher service were ever
> running. I have found them to be not useful (yet) for my environment
> (changes between wireless and wired with static).
>
> nm-applet was started by kde - and runs as the logged in user -
> it did not show in system tray or anywhere else far as I can tell but
> magically starts each time I login.

Even if the applet was started, without the NetworkManager service
running, it should do nothing. But you still should be able to stop it
starting, at all, if you want to.

It's yonks since I've used KDE, but you'd have to look through your KDE
preferences to find programs started during your login session. In
Gnome, we have a "gnome-sessions-properties" preference, but I suspect
that KDE uses its own.

If you can't find this yourself, I'd suggest starting a new thread about
how to control programs started when you login to a KDE session. You
might catch the attention of a KDE user who's not watching a wireless
LAN thread.

--
(This computer runs FC7, my others run FC4, FC5 & FC6, all using Gnome
in case that's important to the thread.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Tue, 2008-05-06 at 20:15 -0400, Mail Lists wrote:
> John W. Linville wrote:
> > On Mon, May 05, 2008 at 08:19:56PM -0400, Mail Lists wrote:
> >
> >
> >> Are there some intel driver issues perhaps ???
> >>
> >
> > The wireless support in Fedora kernels is very close to upstream.
> > This is often beneficial but sometimes unfortunate. For several
> > weeks, users of the iwl3945 and iwl4965 devices have been in the
> > latter category. :-(
> >
> > You may wish to try the latest available F8 kernel in Fedora. It has
> > some recent fixes that have improved the situation for a number of
> > iwl3945 and iwl4965 users (but not all of them):
> >
> > http://koji.fedoraproject.org/koji/buildinfo?buildID=47941
> >
> > Hth!
> >
> > John
> >
> Thanks for feedback. I have also discovered part of the black magic
> recipe requires me to do 2 more things.
>
> 1) kill and turn off avahi-dameon service.
>
> 2) kill off something called nm-applet - i cannot find where this is
> started (as the logged in kde user not root). It is not visible
> anywhere on the KDE task bar so not sure how to shut off - but a
> killall seems to work for now.
nm-applet is started by the running of NetworkMamager. However it is not
designed for kde. There one uses I believe knetworkmanager,
>
> Then the various aditional cauldren stirring outlined earlier have
> worked a total of 2 times now!
>
> Best - and looking forward to fixes!!
>
> Thanks again,
>
> gene/
>
--
================================================== =====================
Building translators is good clean fun. -- T. Cheatham
================================================== =====================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Wed, 2008-05-07 at 08:12 -0500, Aaron Konstam wrote:
> >
> > 2) kill off something called nm-applet - i cannot find where this
> is
> > started (as the logged in kde user not root). It is not visible
> > anywhere on the KDE task bar so not sure how to shut off -
> but a
> > killall seems to work for now.
> nm-applet is started by the running of NetworkMamager. However it is
> not
> designed for kde. There one uses I believe knetworkmanager,
No I am wrong. nm-applet runs as the user. I am now not sure what causes
it to run.
--
================================================== =====================
Schshschshchsch. -- The Gorn, "Arena", stardate 3046.2
================================================== =====================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list