Belkin Components F5D7050 Wireless G USB Adapter

English Network/Internet
1

Following sticky Thread: Getting Your Wireless to Work - Everything seems okay through step VI, getting an IP address through DHCP. It appears that authorization is failing. Results from steps in sticky:

Note: This is a new installation of openSUSE on fresh (formatted) workstation

Step II What device?
Hardware info from YAST - Wireless LAN\USB2.0 WLAN (wlan0)\Kernel Driver: zd1211rw
lsusb reports “Bus 001 Device 002: ID 050d:705c Belkin Components F5D7050 Wireless G Adapter v4000 [Zydas ZD1211B]”

Step III External firmware?
I downloaded the b43 packages, installed as normal and used etc/SysConfig editor to add b43 to modules loaded on boot.
dmesg|grep firmware
22.468807] zd1211rw 1-3:1.0: firmware version 4725
Ran the following check from another thread
rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

Step IV Making connection
/usr/sbin/iwlist scan
lo Interface doesn’t support scanning.

eth0 Interface doesn’t support scanning.

wlan0 Scan completed :
Cell 01 - Address: 00:19:E4:21:B2:11
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=40/100 Signal level=40/100
Encryption key:on
ESSID:“2WIRE250”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000007b5208ce
Extra: Last beacon: 364ms ago
IE: Unknown: 00083257495245323530
IE: Unknown: 010882848B0C12961824
IE: Unknown: 030106
IE: Unknown: 0706555320010B1B
IE: Unknown: 2A0100
IE: Unknown: 32043048606C

Step V Encryption
/usr/sbin/iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:“2WIRE250”
Mode:Managed Frequency:2.437 GHz Access Point: 00:19:E4:21:B2:11
Bit Rate=1 Mb/s Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:“hex value was listed here”
Power Management:off
Link Quality=40/100 Signal level=40/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:1 Missed beacon:0

Step VI Association and authentication
iwconfig shown above
At this point KNetwork Manager will report “Setting Network Address”, this evidently times out after a short time and the Secrets for 2WIRE250 popup returns on the desktop.

Additional info:
/sbin/route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0

cat /etc/sysconfig/network/ifcfg-wlan0
BOOTPROTO=‘dhcp4’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=‘USB2.0 WLAN’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘hotplug’
USERCONTROL=‘yes’
WIRELESS_AP=’’
WIRELESS_AP_SCANMODE=‘1’
WIRELESS_AUTH_MODE=‘open’
WIRELESS_BITRATE=‘auto’
WIRELESS_CA_CERT=’’
WIRELESS_CHANNEL=’’
WIRELESS_CLIENT_CERT=’’
WIRELESS_CLIENT_KEY=’’
WIRELESS_CLIENT_KEY_PASSWORD=’’
WIRELESS_DEFAULT_KEY=‘0’
WIRELESS_EAP_AUTH=’’
WIRELESS_EAP_MODE=’’
WIRELESS_ESSID=‘2WIRE250’
WIRELESS_FREQUENCY=’’
WIRELESS_KEY=’’
WIRELESS_KEY_0=‘h:“decimal value was listed here (not hex)”’
WIRELESS_KEY_1=’’
WIRELESS_KEY_2=’’
WIRELESS_KEY_3=’’
WIRELESS_KEY_LENGTH=‘128’
WIRELESS_MODE=‘Managed’
WIRELESS_NICK=’’
WIRELESS_NWID=’’
WIRELESS_PEAP_VERSION=’’
WIRELESS_POWER=‘yes’
WIRELESS_WPA_ANONID=’’
WIRELESS_WPA_IDENTITY=’’
WIRELESS_WPA_PASSWORD=’’
WIRELESS_WPA_PSK=’’

2

On 03/27/2011 01:36 AM, fuscop wrote:
>
> Following sticky Thread: Getting Your Wireless to Work - Everything
> seems okay through step VI, getting an IP address through DHCP. It
> appears that authorization is failing. Results from steps in sticky:
>
> Note: This is a new installation of openSUSE on fresh (formatted)
> workstation
>
> Step II What device?
> Hardware info from YAST - Wireless LAN\USB2.0 WLAN (wlan0)\Kernel
> Driver: zd1211rw
> lsusb reports “Bus 001 Device 002: ID 050d:705c Belkin Components
> F5D7050 Wireless G Adapter v4000 [Zydas ZD1211B]”
>
> Step III External firmware?
> I downloaded the b43 packages, installed as normal and used
> etc/SysConfig editor to add b43 to modules loaded on boot.
> dmesg|grep firmware

What made you think that you needed Broadcom firmware? Belkin != Broadcom. That
step will not hurt, but it was not necessary.

> 22.468807] zd1211rw 1-3:1.0: firmware version 4725
> Ran the following check from another thread
> rfkill list all
> 0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>
> Step IV Making connection
> /usr/sbin/iwlist scan
> lo Interface doesn’t support scanning.
>
> eth0 Interface doesn’t support scanning.
>
> wlan0 Scan completed :
> Cell 01 - Address: 00:19:E4:21:B2:11
> Channel:6
> Frequency:2.437 GHz (Channel 6)
> Quality=40/100 Signal level=40/100
> Encryption key:on
> ESSID:“2WIRE250”
> Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
> 11 Mb/s; 12 Mb/s; 18 Mb/s
> Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
> Mode:Master
> Extra:tsf=000000007b5208ce
> Extra: Last beacon: 364ms ago
> IE: Unknown: 00083257495245323530
> IE: Unknown: 010882848B0C12961824
> IE: Unknown: 030106
> IE: Unknown: 0706555320010B1B
> IE: Unknown: 2A0100
> IE: Unknown: 32043048606C
>
> Step V Encryption
> /usr/sbin/iwconfig
> lo no wireless extensions.
>
> eth0 no wireless extensions.
>
> wlan0 IEEE 802.11bg ESSID:“2WIRE250”
> Mode:Managed Frequency:2.437 GHz Access Point:
> 00:19:E4:21:B2:11
> Bit Rate=1 Mb/s Tx-Power=27 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:“hex value was listed here”
> Power Management:off
> Link Quality=40/100 Signal level=40/100
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:1 Missed beacon:0

It appears that the device did associate and authenticate. Check the dmesg
output to be certain.

>
> Step VI Association and authentication
> iwconfig shown above
> At this point KNetwork Manager will report “Setting Network Address”,
> this evidently times out after a short time and the Secrets for 2WIRE250
> popup returns on the desktop.
>
> Additional info:
> /sbin/route -n
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 1 0 0
> eth0
> 0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0
> eth0

The routing table indicates that the wired connection was active. When correct,
the last entry would be wlan0, not eth0.

The other place to check is /var/log/NetworkManager. It should list why the
connection does not complete.

3

What made you think that you needed Broadcom firmware? Belkin != Broadcom. That
step will not hurt, but it was not necessary.

Agreed, I confused this wireless with another. I went ahead and removed the packages and the etc/Sysconfig editor setting.

It appears that the device did associate and authenticate. Check the dmesg
output to be certain.

Agree again, dmesg shows both to be successful.
5.176929] usb 1-3: New USB device found, idVendor=050d, idProduct=705c
5.176934] usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=0
5.176938] usb 1-3: Product: USB2.0 WLAN
5.176940] usb 1-3: Manufacturer: Belkin

213.597275] wlan0: authenticate with 00:19:e4:21:b2:11 (try 1)
213.599422] wlan0: authenticated
213.630406] wlan0: associate with 00:19:e4:21:b2:11 (try 1)
213.632883] wlan0: RX AssocResp from 00:19:e4:21:b2:11 (capab=0x431 status=0 aid=2)
213.632888] wlan0: associated
213.633646] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
213.633708] cfg80211: Calling CRDA for country: US
213.648912] cfg80211: Regulatory domain changed to country: US
213.648917] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
213.648921] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
213.648924] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
213.648927] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
213.648931] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
213.648934] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
213.648937] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

The routing table indicates that the wired connection was active. When correct,
the last entry would be wlan0, not eth0.
Routing table empty with wlan0 only active showed no entries.

The other place to check is /var/log/NetworkManager. It should list why the
connection does not complete.
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): new Ethernet device (driver: ‘e100’ ifindex: 2)
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): now managed
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): device state change: 1 → 2 (reason 2)
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): bringing up device.
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): preparing device.
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (eth0): deactivating device (reason: 2).
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> modem-manager is now available
Mar 27 14:23:30 seagull NetworkManager[1324]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> Trying to start the supplicant…
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (wlan0): supplicant manager state: down → idle
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (wlan0): device state change: 2 → 3 (reason 0)
Mar 27 14:23:30 seagull nm-dispatcher.action: Script ‘/etc/NetworkManager/dispatcher.d/netcontrol_services’ exited with error status 127.
Mar 27 14:23:30 seagull NetworkManager[1324]: <info> (wlan0): supplicant interface state: starting → ready
Mar 27 14:23:31 seagull NetworkManager[1324]: <error> [1301253811.86572] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name ‘org.freedesktop.NetworkManagerUserSettings’: no such name
Mar 27 14:23:31 seagull NetworkManager[1324]: <error> [1301253811.87784] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name ‘org.freedesktop.NetworkManagerUserSettings’: no such name
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) starting connection ‘2WIRE250’
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> (wlan0): device state change: 3 → 4 (reason 0)
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> (wlan0): device state change: 4 → 5 (reason 0)
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0/wireless): access point ‘2WIRE250’ has security, but secrets are required.
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> (wlan0): device state change: 5 → 6 (reason 0)
Mar 27 14:23:34 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 27 14:25:29 seagull NetworkManager[1324]: <warn> Failed to update connection secrets: 1 802-1x
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> (wlan0): device state change: 6 → 4 (reason 0)
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> (wlan0): device state change: 4 → 5 (reason 0)
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0/wireless): connection ‘2WIRE250’ has security, and secrets exist. No new secrets needed.
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘ssid’ value ‘2WIRE250’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘scan_ssid’ value ‘1’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘key_mgmt’ value ‘NONE’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘wep_key0’ value ‘<omitted>’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘wep_key1’ value ‘<omitted>’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘wep_key2’ value ‘<omitted>’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘wep_key3’ value ‘<omitted>’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: added ‘wep_tx_keyidx’ value ‘0’
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> Config: set interface ap_scan to 1
Mar 27 14:25:29 seagull NetworkManager[1324]: <info> (wlan0): supplicant connection state: inactive → scanning
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> (wlan0): supplicant connection state: scanning → associating
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> (wlan0): supplicant connection state: associating → associated
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> (wlan0): supplicant connection state: associated → completed
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network ‘2WIRE250’.
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started…
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> (wlan0): device state change: 5 → 7 (reason 0)
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> dhclient started with pid 4322
Mar 27 14:25:30 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Mar 27 14:25:31 seagull NetworkManager[1324]: <info> (wlan0): DHCPv4 state changed nbi → preinit
Mar 27 14:26:16 seagull NetworkManager[1324]: <warn> (wlan0): DHCPv4 request timed out.
Mar 27 14:26:16 seagull NetworkManager[1324]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 4322
Mar 27 14:26:16 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled…
Mar 27 14:26:16 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started…
Mar 27 14:26:16 seagull NetworkManager[1324]: <warn> Activation (wlan0/wireless): could not get IP configuration for connection ‘2WIRE250’.
Mar 27 14:26:16 seagull NetworkManager[1324]: <info> (wlan0): device state change: 7 → 6 (reason 0)
Mar 27 14:26:16 seagull NetworkManager[1324]: <info> Activation (wlan0/wireless): asking for new secrets
Mar 27 14:26:16 seagull NetworkManager[1324]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete

I understand that it is timing out waiting for IP address. I will troubleshoot that issue, if you have any suggestions on that front I would be grateful. Seems like something relatively simple may be wrong. I have other systems connecting to the router without issue (both ethernet and wireless).

4

With wlan0 only active:
sudo /sbin/route add default gw 192.168.1.254 fails with response SIOCADDRT: No such process

5

On 03/30/2011 03:36 PM, fuscop wrote:
>
> With wlan0 only active:
> sudo /sbin/route add default gw 192.168.1.254 fails with response
> SIOCADDRT: No such process

What do ‘/sbin/route -n’ and ‘/sbin/ifconfig wlan0’ show just before you try the
add command?

6

/sbin/route -n shows the default headings with no entries underneath.

/sbin/ifconfig wlan0

wlan0 Link encap:Ethernet HWaddr 00:22:75:77:7C:E7
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes: 0 (0.0 b) TX bytes: 3690 (3.8 kb)

Looks like it’s talking but either not listening, receiving or processing the info. I’m leaving for work but will check back during the night for any suggestions. Thank you very much for your assistance with this.

7

On 03/30/2011 05:06 PM, fuscop wrote:
>
> lwfinger;2314975 Wrote:
>> On 03/30/2011 03:36 PM, fuscop wrote:
>>>
>>> With wlan0 only active:
>>> sudo /sbin/route add default gw 192.168.1.254 fails with response
>>> SIOCADDRT: No such process
>>
>> What do ‘/sbin/route -n’ and ‘/sbin/ifconfig wlan0’ show just before
>> you try the
>> add command?
>
> /sbin/route -n shows the default headings with no entries underneath.
>
> /sbin/ifconfig wlan0
>
> wlan0 Link encap:Ethernet HWaddr 00:22:75:77:7C:E7
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes: 0 (0.0 b) TX bytes: 3690 (3.8 kb)
>
> Looks like it’s talking but either not listening, receiving or
> processing the info. I’m leaving for work but will check back during the
> night for any suggestions. Thank you very much for your assistance with
> this.

As you do not yet have an IP assigned, the route command cannot assign one. Your
failure is further upstream. In a previous posting, it appeared that the
wireless had associated and authenticated. Does the dmesg output confirm that?

8

Here is the (hopefully) relevant output of dmesg, immediately after cold start with wlan0 only active, login to KWallet, and Network Manager going through steps up to failing to obtain an IP address and then displaying the popup for secrets. In other words, after it fails to get an IP address through DHCP:

0.127863] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
0.128335] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
0.129759] TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
0.130684] TCP: Hash tables configured (established 131072 bind 65536)
0.130690] TCP reno registered
0.130703] UDP hash table entries: 512 (order: 2, 16384 bytes)
0.130736] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
0.131013] NET: Registered protocol family 1

2.629937] TCP cubic registered
2.629983] NET: Registered protocol family 10
2.630383] lo: Disabled Privacy Extensions
2.630634] Registering the dns_resolver key type

5.197668] usb 1-3: New USB device found, idVendor=050d, idProduct=705c
5.197674] usb 1-3: New USB device strings: Mfr=16, Product=32, SerialNumber=0
5.197678] usb 1-3: Product: USB2.0 WLAN
5.197680] usb 1-3: Manufacturer: Belkin

8.571874] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
8.571879] e100: Copyright(c) 1999-2006 Intel Corporation
8.571952] e100 0000:02:08.0: PCI INT A -&gt; GSI 20 (level, low) -&gt; IRQ 20
8.595471] e100 0000:02:08.0: PME# disabled
8.596100] e100 0000:02:08.0: eth0: addr 0xff9fe000, irq 20, MAC addr 00:0c:f1:b6:e6:ab

21.992928] zd1211rw 1-3:1.0: firmware version 4725
22.035938] zd1211rw 1-3:1.0: zd1211b chip 050d:705c v4810 high 00-22-75 AL2230_RF pa0 g–NS
22.038672] cfg80211: Calling CRDA for country: US
22.057953] ADDRCONF(NETDEV_UP): wlan0: link is not ready
22.079300] cfg80211: Regulatory domain changed to country: US
22.079306] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
22.079310] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
22.079314] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
22.079317] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
22.079320] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
22.079324] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
22.079327] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
22.098091] ADDRCONF(NETDEV_UP): eth0: link is not ready
22.226351] NET: Registered protocol family 17

68.456279] wlan0: authenticate with 00:19:e4:21:b2:11 (try 1)
68.457896] wlan0: authenticated
68.489704] wlan0: associate with 00:19:e4:21:b2:11 (try 1)
68.494179] wlan0: RX AssocResp from 00:19:e4:21:b2:11 (capab=0x431 status=0 aid=1)
68.494184] wlan0: associated
68.494989] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
68.495081] cfg80211: Calling CRDA for country: US
68.569209] cfg80211: Regulatory domain changed to country: US
68.569215] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
68.569218] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
68.569222] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
68.569225] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
68.569228] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
68.569231] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
68.569235] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)

9

On 03/31/2011 04:06 PM, fuscop wrote:
>
> lwfinger;2315045 Wrote:
>> On 03/30/2011 05:06 PM, fuscop wrote:
>>>
>>> lwfinger;2314975 Wrote:
>>>> On 03/30/2011 03:36 PM, fuscop wrote:
>>>>>
>>>>> With wlan0 only active:
>>>>> sudo /sbin/route add default gw 192.168.1.254 fails with response
>>>>> SIOCADDRT: No such process
>>>>
>>>> What do ‘/sbin/route -n’ and ‘/sbin/ifconfig wlan0’ show just before
>>>> you try the
>>>> add command?
>>>
>>> /sbin/route -n shows the default headings with no entries underneath.
>>>
>>> /sbin/ifconfig wlan0
>>>
>>> wlan0 Link encap:Ethernet HWaddr 00:22:75:77:7C:E7
>>> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
>>> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>> TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
>>> collisions:0 txqueuelen:1000
>>> RX bytes: 0 (0.0 b) TX bytes: 3690 (3.8 kb)
>>>
>>> Looks like it’s talking but either not listening, receiving or
>>> processing the info. I’m leaving for work but will check back during
>> the
>>> night for any suggestions. Thank you very much for your assistance
>> with
>>> this.
>>
>> As you do not yet have an IP assigned, the route command cannot assign
>> one. Your
>> failure is further upstream. In a previous posting, it appeared that
>> the
>> wireless had associated and authenticated. Does the dmesg output
>> confirm that?
>
> Here is the (hopefully) relevant output of dmesg, immediately after
> cold start with wlan0 only active, login to KWallet, and Network Manager
> going through steps up to failing to obtain an IP address and then
> displaying the popup for secrets. In other words, after it fails to get
> an IP address through DHCP:
>
> 0.127863] IP route cache hash table entries: 32768 (order: 5,
> 131072 bytes)
> 0.128335] TCP established hash table entries: 131072 (order: 8,
> 1048576 bytes)
> 0.129759] TCP bind hash table entries: 65536 (order: 7, 524288
> bytes)
> 0.130684] TCP: Hash tables configured (established 131072 bind
> 65536)
> 0.130690] TCP reno registered
> 0.130703] UDP hash table entries: 512 (order: 2, 16384 bytes)
> 0.130736] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
> 0.131013] NET: Registered protocol family 1
>
> 2.629937] TCP cubic registered
> 2.629983] NET: Registered protocol family 10
> 2.630383] lo: Disabled Privacy Extensions
> 2.630634] Registering the dns_resolver key type
>
> 5.197668] usb 1-3: New USB device found, idVendor=050d,
> idProduct=705c
> 5.197674] usb 1-3: New USB device strings: Mfr=16, Product=32,
> SerialNumber=0
> 5.197678] usb 1-3: Product: USB2.0 WLAN
> 5.197680] usb 1-3: Manufacturer: Belkin
>
> 8.571874] e100: Intel(R) PRO/100 Network Driver, 3.5.24-k2-NAPI
> 8.571879] e100: Copyright(c) 1999-2006 Intel Corporation
> 8.571952] e100 0000:02:08.0: PCI INT A → GSI 20 (level, low) →
> IRQ 20
> 8.595471] e100 0000:02:08.0: PME# disabled
> 8.596100] e100 0000:02:08.0: eth0: addr 0xff9fe000, irq 20, MAC
> addr 00:0c:f1:b6:e6:ab
>
> 21.992928] zd1211rw 1-3:1.0: firmware version 4725
> 22.035938] zd1211rw 1-3:1.0: zd1211b chip 050d:705c v4810 high
> 00-22-75 AL2230_RF pa0 g–NS
> 22.038672] cfg80211: Calling CRDA for country: US
> 22.057953] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> 22.079300] cfg80211: Regulatory domain changed to country: US
> 22.079306] (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
> 22.079310] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi,
> 2700 mBm)
> 22.079314] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi,
> 1700 mBm)
> 22.079317] (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> 22.079320] (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> 22.079324] (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi,
> 2000 mBm)
> 22.079327] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi,
> 3000 mBm)
> 22.098091] ADDRCONF(NETDEV_UP): eth0: link is not ready
> 22.226351] NET: Registered protocol family 17
>
> 68.456279] wlan0: authenticate with 00:19:e4:21:b2:11 (try 1)
> 68.457896] wlan0: authenticated
> 68.489704] wlan0: associate with 00:19:e4:21:b2:11 (try 1)
> 68.494179] wlan0: RX AssocResp from 00:19:e4:21:b2:11 (capab=0x431
> status=0 aid=1)
> 68.494184] wlan0: associated

It does associate and authenticate. The dmesg output does not contain any info
regarding DHCP. That would be in /var/log/messages or /var/log/NetworkManager.

10

<It does associate and authenticate. The dmesg output does not contain any info
regarding DHCP. That would be in /var/log/messages or /var/log/NetworkManager.>

I’ve looked through the following, if there telling me what’s wrong I’m not recognizing it:

/var/log/messages
Apr 1 14:54:00 seagull dhclient: Internet Systems Consortium DHCP Client 4.2.0-P2
Apr 1 14:54:00 seagull dhclient: Copyright 2004-2010 Internet Systems Consortium.
Apr 1 14:54:00 seagull dhclient: All rights reserved.
Apr 1 14:54:00 seagull dhclient: For info, please visit https://www.isc.org/software/dhcp/
Apr 1 14:54:00 seagull dhclient:
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> (wlan0): DHCPv4 state changed nbi → preinit
Apr 1 14:54:00 seagull dhclient: Listening on LPF/wlan0/00:22:75:77:7c:e7
Apr 1 14:54:00 seagull dhclient: Sending on LPF/wlan0/00:22:75:77:7c:e7
Apr 1 14:54:00 seagull dhclient: Sending on Socket/fallback
Apr 1 14:54:04 seagull dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Apr 1 14:54:09 seagull dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Apr 1 14:54:14 seagull dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Apr 1 14:54:24 seagull dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
Apr 1 14:54:35 seagull dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
Apr 1 14:54:46 seagull NetworkManager[1357]: <warn> (wlan0): DHCPv4 request timed out.
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 4277
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled…
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started…
Apr 1 14:54:46 seagull NetworkManager[1357]: <warn> Activation (wlan0/wireless): could not get IP configuration for connection ‘2WIRE250’.
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> (wlan0): device state change: 7 → 6 (reason 0)
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0/wireless): asking for new secrets
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.

/var/log/NetworkManager
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> NetworkManager (version 0.8.2) is starting…
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> Read config file /etc/NetworkManager/nm-system-settings.conf
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> VPN: loaded org.freedesktop.NetworkManager.pptp
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> VPN: loaded org.freedesktop.NetworkManager.vpnc
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> VPN: loaded org.freedesktop.NetworkManager.openvpn
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> trying to start the modem manager…
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> monitoring kernel firmware directory ‘/lib/firmware’.
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list.
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Apr 1 14:51:06 seagull NetworkManager[1357]: keyfile: parsing Auto eth0 …
Apr 1 14:51:06 seagull NetworkManager[1357]: keyfile: read connection ‘Auto eth0’
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> found WiFi radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/ieee80211/phy0/rfkill0) (driver <unknown>)
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> WiFi enabled by radio killswitch; enabled by state file
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> WWAN enabled by radio killswitch; enabled by state file
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> WiMAX enabled by radio killswitch; enabled by state file
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> Networking is enabled by state file
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): new 802.11 WiFi device (driver: ‘zd1211rw’ ifindex: 3)
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): now managed
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): device state change: 1 → 2 (reason 2)
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): bringing up device.
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): preparing device.
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): deactivating device (reason: 2).
Apr 1 14:51:06 seagull NetworkManager[1357]: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE’ failed
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): carrier is OFF
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): new Ethernet device (driver: ‘e100’ ifindex: 2)
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/1
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): now managed
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): device state change: 1 → 2 (reason 2)
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): bringing up device.
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): preparing device.
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (eth0): deactivating device (reason: 2).
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> modem-manager is now available
Apr 1 14:51:06 seagull NetworkManager[1357]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> Trying to start the supplicant…
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): supplicant manager state: down → idle
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): device state change: 2 → 3 (reason 0)
Apr 1 14:51:06 seagull NetworkManager[1357]: <info> (wlan0): supplicant interface state: starting → ready
Apr 1 14:51:06 seagull NetworkManager[1357]: <error> [1301687466.922220] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name ‘org.freedesktop.NetworkManagerUserSettings’: no such name
Apr 1 14:51:06 seagull NetworkManager[1357]: <error> [1301687466.923433] [nm-manager.c:1368] user_proxy_init(): could not init user settings proxy: (3) Could not get owner of name ‘org.freedesktop.NetworkManagerUserSettings’: no such name
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) starting connection ‘2WIRE250’
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> (wlan0): device state change: 3 → 4 (reason 0)
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> (wlan0): device state change: 4 → 5 (reason 0)
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0/wireless): access point ‘2WIRE250’ has security, but secrets are required.
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> (wlan0): device state change: 5 → 6 (reason 0)
Apr 1 14:51:11 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 1 14:53:59 seagull NetworkManager[1357]: <warn> Failed to update connection secrets: 1 802-1x
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled…
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started…
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> (wlan0): device state change: 6 → 4 (reason 0)
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled…
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting…
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> (wlan0): device state change: 4 → 5 (reason 0)
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0/wireless): connection ‘2WIRE250’ has security, and secrets exist. No new secrets needed.
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘ssid’ value ‘2WIRE250’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘scan_ssid’ value ‘1’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘key_mgmt’ value ‘NONE’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘wep_key0’ value ‘<omitted>’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘wep_key1’ value ‘<omitted>’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘wep_key2’ value ‘<omitted>’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘wep_key3’ value ‘<omitted>’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: added ‘wep_tx_keyidx’ value ‘0’
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> Config: set interface ap_scan to 1
Apr 1 14:53:59 seagull NetworkManager[1357]: <info> (wlan0): supplicant connection state: inactive → scanning
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> (wlan0): supplicant connection state: scanning → associating
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> (wlan0): supplicant connection state: associating → associated
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> (wlan0): supplicant connection state: associated → completed
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network ‘2WIRE250’.
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started…
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> (wlan0): device state change: 5 → 7 (reason 0)
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> dhclient started with pid 4277
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Apr 1 14:54:00 seagull NetworkManager[1357]: <info> (wlan0): DHCPv4 state changed nbi → preinit
Apr 1 14:54:46 seagull NetworkManager[1357]: <warn> (wlan0): DHCPv4 request timed out.
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 4277
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) scheduled…
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) started…
Apr 1 14:54:46 seagull NetworkManager[1357]: <warn> Activation (wlan0/wireless): could not get IP configuration for connection ‘2WIRE250’.
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> (wlan0): device state change: 7 → 6 (reason 0)
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0/wireless): asking for new secrets
Apr 1 14:54:46 seagull NetworkManager[1357]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Timeout) complete.

11

After some consideration, I went with my original urge and reinstalled 11.4 with LXDE as the desktop. As I expected, the wireless setup was quick and painless. I would have preferred KDE as I am much more familiar with it, but LXDE is getting to be my go-to desktop where wireless is concerned. I’ve had it work where Gnome, KDE and XFCE (sometimes) all failed. I’ll put up with its growing pains as a trade-off for connectivity, and continue to use KDE on my wired workstation. Not gonna hurt to be familiar with both. Thanks for your help.

12

I was reading through another thread “wireless realtek card not working” which discussed the reasons for inclusion/exclusion of certain random drivers and software from distributions. Does this also exist within different desktops under the same distribution (such as openSUSE 11.4). Just wondering why LXDE would work without issue, while KDE consistently hung on DHCP IP assignment. As stated in my previous post, I have LXDE up and running so no big problem at this time. Just curious as to the reason for the difference, from what I can tell the driver was from the same repository.

13

On 04/03/2011 11:36 PM, fuscop wrote:
>
> I was reading through another thread “wireless realtek card not
> working” which discussed the reasons for inclusion/exclusion of certain
> random drivers and software from distributions. Does this also exist
> within different desktops under the same distribution (such as openSUSE
> 11.4). Just wondering why LXDE would work without issue, while KDE
> consistently hung on DHCP IP assignment. As stated in my previous post,
> I have LXDE up and running so no big problem at this time. Just curious
> as to the reason for the difference, from what I can tell the driver was
> from the same repository.

No. Drivers are part of the kernel. The connection helpers are all user programs.

I don’t know what caused your problem with DHCP under KDE. I always use KDE and
have never had the problem.