Wireless problem in Fedora13

[JD]

On 06/24/2010 11:38 PM, Thomas Taylor was caught red-handed while writing::
> On Thu, 24 Jun 2010 18:24:31 -0700
> Thomas Taylor<linxt at comcast.net>  wrote:
>
>    
>> Hi all;
>>
>> Recently installed Fedora13 and am working through problems.  I've managed to
>> solve most by lots of reading documentation and googling but am being
>> frustated with wireless not working in KDE.  It's working fine in Gnome but I
>> prefer KDE.
>>
>> I've tried both using NetworkManager and traditional (ifup) methods but can't
>> get associated with my wireless router except in Gnome.  The router (Linksys
>> WRT54G) is set to not broadcast ESSID.  I can see it with iwlist wlan0 scan
>> but only Gnome will associate with it.
>>
>> It's my understanding that both Gnome and KDE use NetworkManager but with
>> different GUIs.  If that is so, why won't both associate?
>>
>> Any comments or suggestions gladly accepted.
>>
>> Thanks, Tom
>>
>>      
> Additional information as appropriate:
>
> lspci:
>
> 08:00.0 Network controller: Intel Corporation WiFi Link 5100
> 14:00.0 FireWire (IEEE 1394): O2 Micro, Inc. Device 10f7 (rev 01)
> 14:00.1 SD Host controller: O2 Micro, Inc. Device 8120 (rev 01)
> 14:00.2 Mass storage controller: O2 Micro, Inc. Device 8130 (rev 01)
> 20:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
> Express Gigabit Ethernet controller (rev 03)
>
>
> lsmod:
>
> nf_nat                 19059  2 ipt_MASQUERADE,iptable_nat
> stp                     1887  1 bridge
> llc                     4557  2 bridge,stp
> ip6t_REJECT             4055  6
> nf_conntrack_ipv6      17513  14
> ip6table_filter         2743  1
> ip6_tables             16558  1 ip6table_filter
> ipv6                  267065  32 ip6t_REJECT,nf_conntrack_ipv6
> iwlcore               220675  1 iwlagn
> mii                     4142  1 r8169
> mac80211              196945  2 iwlagn,iwlcore
> cfg80211              117099  3 iwlagn,iwlcore,mac80211
>
> ifup wlan0
>
> Error org.freedesktop.NetworkManagerSettings.InternalError: unable to get the
> connection D-Bus path Error
> org.freedesktop.NetworkManagerSettings.InternalError: unable to get the
> connection D-Bus path Error for wireless request "Set Encode" (8B2A) : SET
> failed on device wlan0 ; Invalid argument. Determining IP information for
> wlan0... failed; no link present.  Check cable?
>
> dmesg | grep iwlagn:
>
> iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux,
> 2.6.33.3-85.fc13.x86_64-kds iwlagn: Copyright(c) 2003-2009 Intel Corporation
> iwlagn 0000:08:00.0: PCI INT A ->  GSI 17 (level, low) ->  IRQ 17
> iwlagn 0000:08:00.0: setting latency timer to 64
> iwlagn 0000:08:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54
> iwlagn 0000:08:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
>    alloc irq_desc for 33 on node -1
>    alloc kstat_irqs on node -1
> iwlagn 0000:08:00.0: irq 33 for MSI/MSI-X
> iwlagn 0000:08:00.0: firmware: requesting iwlwifi-5000-2.ucode
> iwlagn 0000:08:00.0: loaded firmware version 8.24.2.12
>
> The error message from ifup leads me to believe the problem is with a missing
> D-Bus service.  When I go to System>  Admin>  Services (in Gnome), D-Bus is not
> listed and an rpm -q for it comes up blank.  Is this something KDE should have
> installed during the Fedora installation?  If so, how do I get it?
>
> JD, adding the "-dd" didn't help since the network never gets that far in KDE.
>
> Tim, unfortunately I am unable to get to my router which is located in the
> basement and I'm handicapped and can't get down the stairs.  It was setup many
> years ago with admin access restricted to wired connection which I don't have
> up here.  Hmmm, maybe I need a 100ft patch cord!
>
> Tom
>    

I did not say -dd would make it work. It simply forces
the wpa_supplicant to issue more debug messages.
But since now you reveal that it is unable to talk to dbus,
you need to also add -u in addition to -dd
Option -u enabled dbus when NetworkManager is used.

I really have found no need for NetworkManager. I have disabled
it. Furthermore, I found that when I tried to use NetworkManager,
it was  not even reading /etc/sysconfig/wpa_supplicant for the
arguments, so, I was not able to see the debug output of wpa_supplicant,
and it did not even select the correct interface (ra0).
I suggest you get rid of NetworkManager altogether.
Disable it AND remove -u from /etc/sysconfig/wpa_supplicant,
and you will be just fine!

Cheers,

JD