WiFi detects networks but will not connect properly (Wifi Link 5300) - Page 3

bbfuller · #31 5th August 2009, 09:54 AM

Hello Mikademus

Have you considered blacklisting the 'iwlagn' module and trying with ndiswrapper?

No guarantees it would work of course, I've never seen anyone try it with a 5300.

However, if it did work then it would at least keep you going while the 'iwlagn' driver is improved. I remember when I first had a broadcom 4318 having to do that until eventually the b43 driver matured.

Post back if you want to talk about it, I've all sorts of notes for ndiswrapper here.

Fil · #32 7th August 2009, 12:03 AM

Hi,
I have been following the thread as I am trying FC 11 Live on my TP X61s, Intel 4965 wireless card and could not get wireless connection: same symptoms as Mikademus, Network Manager kept asking to connect with a password window.
Also tried to configure with System/Administration/Network + System/Administration/Services to no avail.
Just booted again with Live disc and did the following: System/Administration/SELinux Management, "Status" - System default enforcing mode set to "Disabled", Current enforcing mode set to "Permissive". After, set Network Manager with the wireless network settings: SSID, encryption + password. Still it had my network name (SSID) grayed out and I could not connect.
Finally, as last try, I connected to the router via ethernet cable (no problems since the begining) and changed in the wireless settings of the router the broadcasting of the network name (SSID) from disabled to enabled. From there on, Network Manager could list my network from grayed out to highlighted and wireless works without problems.
It is still a bug in NM that should be corrected, as it should be able to connect to hidden wireless networks, as other (Live) distros do, but maybe you can give this a try and see if it works, keep it posted and good luck!

Mikademus · #33 10th August 2009, 09:14 AM

bbfuller, thank you for your offer! Since I am learning as I go I'd love to look at your notes! If that's one way to circumvent the problem it might be of help to others, too (if it works).

bbfuller · #34 10th August 2009, 07:30 PM

Hello Mikademus

Here are the notes for using ndiswrapper:

Quote:

Ndiswrapper, as it's name implies is a way of wrapping some Linux code around a windows driver to make it work in Linux.

Ndiswrapper will not work with Windows Vista drivers. It is also not happy with every version of a driver for every chipset. If the one that came with your card doesn't work it may be necessary to experiment with other manufacturers drivers that were made for the particular chipset.

The parts of the windows driver file that you are looking for are the .inf file and the matching .sys file.

For instance in my case when I used ndiswrapper for my broadcom card, there was a 'bcmwl5.inf' file in the driver along with a bcmwl5.sys. Other manufacturers will use different file names.

Acquire full root rights with:

Code:

su -

That's a space and a minus sign after the su. It gives full root rights over the machine, not just over your own environment which is what you get with plain su.

If you haven't already, install the rpmfusion repositories:

Code:

rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm http://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-stable.noarch.rpm

Install ndiswrapper:

Code:

yum install kmod-ndiswrapper

should bring in the three relevant packages.

Then set up and configure ndiswrapper with:

Code:

ndiswrapper -i <path to your windows driver file>.inf

should install the driver,

Code:

ndiswrapper -l

if it is going to work should return "driver present" and "hardware present"

Code:

modprobe ndiswrapper

should load the driver into the kernel, but probably only until you reboot.

If you are lucky now and NetworkManager is running then after a short while it 'may' begin reporting wireless networks. NetworkManager is the preferred method of connecting to wireless networks with Fedora and should be located on the top Gnome Panel to the right in the notification area.

If it works, or indeed if it doesn't you will also need to run:

Code:

ndiswrapper -ma

The one proviso for those is that they require a working Internet connection to the machine.

There are supplemental notes for if you need to do it without Internet.

Post back if you want those, or indeed if you have any questions or problems.

Bert Rolston · #35 14th August 2009, 11:54 PM

Hi all,

I just upgraded my Latitude D600 from F9 to F11 by doing a fresh install.
ALL of my hardware worked well under F9 including wireless.
I encountered the same problem with wireless connecting then immediately disconnecting after the upgrade.
Remember, the same hardware WORKED with F9 on my network.

lspci identified my card as
Intel Corporation PRO/Wireless 2915ABG [Calexico2] Network Connection (rev 05)

I read through this thread and tried some of the simple fixes.
Then I recalled having a similar problem with a PCMCIA card when I had F7 on another laptop.

Here's what worked for me.
I disabled the NETPLUGD and WPASUPPLICANT services through SYSTEM -> SERVICES control panel.
Simply stop each service and then disable them.

Since then my wireless connection has been rock solid.

Hope this helps someone.

Cheers,
Bert

Mikademus · #36 23rd August 2009, 12:08 AM

Quote:

Originally Posted by Bert Rolston

I disabled the NETPLUGD and WPASUPPLICANT services through SYSTEM -> SERVICES control panel. Simply stop each service and then disable them.

Thanks for the advice! I'm on KDE so I assume the counterpart to system-->services is the serviceconf application. I do not have a netplugd service (or at least can't find it) and wpa_supplicant is disabled, but it seems to make no difference.

I will try bbfuller's ndiswrapper advice next.

Mikademus · #37 5th September 2009, 07:40 PM

I am now surfing wireless. And I have neither used ndiswrapper or messed around with WAP_SUPPLICANT. What I did was rather to remove the KDE4 NetworkManager plasma applet and install GNOME's counterpart, so rather than a KDE4 gizmo I have an icon in the tray. And it works.

I hesitate to place blame at KDE's steps, but it seems to be an interaction effect. Or it could perhaps be that there was another NetworkManager conflicting in the background, in which case it might still be a Fedora bug.

In either case, I'll keep my fingers crossed that this will keep working, and that it will help someone else.

Thanks everyone that has replied in this thread. I hope I have provided enough information that someone more skilled than me in Linux will be able to figure out what's amiss and fix what needs to be fixed!

**AdamW** · #38 8th September 2009, 08:17 PM

I'm not sure I actually knew you were using KDE's native networkmanager widget. I don't think that's the default, it should default to using GNOME's; this is intentional, because the KDE version was known to be fairly broken until very recently (a better version is in Rawhide now). So that definitely makes sense.

Mikademus · #39 9th September 2009, 05:22 PM

Well, what I did was install Fedora from the DVD, and then add the KDE package, that is, I did not install from the KDE4 LiveCD. I might have added the KDE Network Manager manually, I can't remember if it was installed by default or not. If I did, it was a move that would made perfect sense to me at the time, since there were no warnings about using it, and it was named "KDE Network Manager" or something in the repos.

Perhaps this might deserve an article of its own in the Fedora solutions site?

**AdamW** · #40 9th September 2009, 09:55 PM

In harsh practical terms, I haven't run across anyone else who had the same problem. My personal rule of thumb is not to bother documenting anything until at least two people hit it, so I won't do it.

Be cool if someone else wanted to, though.

zez3 · #41 24th September 2009, 08:11 PM

Quote:

Originally Posted by AdamW

In harsh practical terms, I haven't run across anyone else who had the same problem. My personal rule of thumb is not to bother documenting anything until at least two people hit it, so I won't do it.

Be cool if someone else wanted to, though.

Until now.
As my case is somehow also different because I have or want a network 802.1N only and not g or b. With those working perfectly.
I have a 5300 intel iwlagn wifi adapter on a new dell E6400 with fc11 and obvious the problem with the password requested more times and not connecting after. I have no solution to this yet.
I have tried all that was tested here plus the new fc12 rawhide live usb and nothing.
I have to try the mandriva 2009.1 again just to be sure because my first attempt running usb live did not worked, after loading a black screen pause....
I don't really what to use the emulating win drivers. I was hopping that the linux community is always a pioneer in such new speed standards and that wireless is also included somewhere there but it seems that it's not the case here.
I need to say that I have done some more tests with a 802.1N usb card from belkin with chipset and linux driver rt2870 and with that all works fine. Also on other distro's sometime it's working some not or perhaps I did not try enough. It seems to me that the problem in my case is more related to the driver iwlagn or firmware loading from that driver.

Quote:

modinfo iwlagn
filename: /lib/modules/2.6.30.5-43.fc11.i586/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
alias: iwl4965
license: GPL
author: Copyright(c) 2003-2009 Intel Corporation <ilw@linux.intel.com>
version: 1.3.27kds
description: Intel(R) Wireless WiFi Link AGN driver for Linux
firmware: iwlwifi-4965-2.ucode
firmware: iwlwifi-5150-2.ucode
firmware: iwlwifi-5000-2.ucode this firmware is loaded in my case but not helping
firmware: iwlwifi-6050-2.ucode
firmware: iwlwifi-6000-2.ucode
srcversion: 998B55AC59559D89E8152BF

Hopefully now that the N standard has been officially approved all manufactures will have to align to the same specifications and provide "good" drivers compatible also inter-producers not only between the same line of products from the same vendor as I have discovered the hard way.

glubbdrubb · #42 20th October 2009, 03:17 PM

Have you tried WICD? It is a partial replacement to Network Manager (it lacks certain PPP functionalaty). Obviosly it won't solve a driver issue but it does not have many of the strange bugs NM suffers from.

zez3 · #43 21st October 2009, 11:20 AM

Quote:

Originally Posted by glubbdrubb

Have you tried WICD? It is a partial replacement to Network Manager (it lacks certain PPP functionalaty). Obviosly it won't solve a driver issue but it does not have many of the strange bugs NM suffers from.

As I said already the network manager works, in my case, quite perfect with other non-N wifi networks. I think NM is not the problem here.

zez3 · #44 27th October 2009, 11:11 AM

Hi,
after a fresh install from usb stick and some updates now the wireless N network works.
the main difference is that I now use a older kernel version see bellow

Quote:

modinfo iwlagn
filename: /lib/modules/2.6.29.4-167.fc11.i586/kernel/drivers/net/wireless/iwlwifi/iwlagn.ko
alias: iwl4965
license: GPL
author: Copyright(c) 2003-2008 Intel Corporation <ilw@linux.intel.com>
version: 1.3.27kds
description: Intel(R) Wireless WiFi Link AGN driver for Linux
firmware: iwlwifi-4965-2.ucode
firmware: iwlwifi-5150-1.ucode
firmware: iwlwifi-5000-1.ucode

dklovedoctor · #45 12th December 2011, 07:42 PM

check command ipcs
in my case I had lost of shared memory allocated