Dell D620-Intel 3945 + PEAP

Has anyone noticed an issue with Dell D620 Laptops using the Intel 3945 card and WinXP with regards to PEAP authenication (mschapv2)? We are migrating to a LWAPP enviroment, but current we have a large autonomous AP enviroment. We have a very mobile group of users that just received new laptops and ever since they have had random connections issues with the 3945Intel card. The laptop will go from full strengh to no strengh without even moving. At times the laptop even gets in a state where it requires a reboot in order to get authenictated. We have tried the newest Intel proset 11.1 and that doesn't seem to have resolved the issues. There is nothing in any logs to point to an issue. You can have an older laptop with an intel 2200card right next to it and not have these issues.

Ensure that you don't have 2 client connection managers enabled in your PC. For example, a Microsoft WzC and a ADU on the same pc will result in lot of connectivity issues. In such cases. disable one of these client utilities.

Similar Messages

  • WRT110 crashes with Vista SP1 and Intel 3945

    I have a WRT110 with the latest firmware 1.0.4, an a Dell XPS1330 with the Intel 3945abg wireless card and the latest drivers in Intel. When ever my laptop tries to connect the router crashes and drops all other connections with other wireless devies and wired devices. I also have another laptop running XP that works great on the wireless connection. It's same to say the problem is limited to the Vista machine and the Intel 3945 wireless card. Now sure what to do?

    I have the same problem. Took me a while to figure out that when i connected my Toshiba laptop with Vista and Intel 3945 Router and network crashed couldnot even get the router accessed on hardwired computer. Everything returns back to normal when laptop disconnected from wireless network
    Customer support was not able to help, called them twice. I solved by connecting an old wireless router to one of the ports of Linksys and connect my Vista laptop on that wireless network. That is not really a solution but if you'd like to, return the router until they can at least admit that there is a problem with compatibility, upgrading firmware on wireless adaptor did not help.
    (Mod note: Edited for guideline compliance.) 
    Message Edited by kent07 on 11-06-2008 06:33 PM

  • Intel 3945 won't work after update.

    After updating a Thinkpad T60 with the Intel 3945 wireless card I am unable to connect to wireless. Wicd's GTK front end even fails to start, but the problem is not with Wicd. Anything attempting to access the card will hang, even 'ifconfig wlan0 up' hangs and I have to kill it.
    Here is 'lsmod|grep iwl':
    iwl3945 63543 0
    iwl_legacy 45018 1 iwl3945
    mac80211 203227 2 iwl_legacy,iwl3945
    cfg80211 147716 3 mac80211,iwl_legacy,iwl3945
    Here is the relevant information from everything.log:
    Feb 22 06:48:49 t60-arch kernel: [ 4.832450] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
    Feb 22 06:48:49 t60-arch kernel: [ 4.832453] iwl3945: Copyright(c) 2003-2011 Intel Corporation
    Feb 22 06:48:49 t60-arch kernel: [ 4.832641] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    Feb 22 06:48:49 t60-arch kernel: [ 4.832657] iwl3945 0000:03:00.0: setting latency timer to 64
    Feb 22 06:48:49 t60-arch kernel: [ 4.886080] iwl3945 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
    Feb 22 06:48:49 t60-arch kernel: [ 4.886084] iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
    Feb 22 06:48:49 t60-arch kernel: [ 4.886235] iwl3945 0000:03:00.0: irq 44 for MSI/MSI-X
    Feb 22 06:48:49 t60-arch kernel: [ 4.930430] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
    Feb 22 06:53:49 t60-arch kernel: [ 311.946831] iwl3945 0000:03:00.0: iwlwifi-3945-2.ucode firmware file req failed: -2
    Feb 22 06:54:49 t60-arch kernel: [ 372.106844] iwl3945 0000:03:00.0: iwlwifi-3945-1.ucode firmware file req failed: -2
    Feb 22 06:54:49 t60-arch kernel: [ 372.106853] iwl3945 0000:03:00.0: Could not read microcode: -2
    Here is 'ls /lib/firmware/|grep 3945':
    iwlwifi-3945-2.ucode
    Here is 'rfkill list':
    0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    2: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: no
    Hard blocked: no
    Obviously it is a firmware issue, even though linux-firmware is properly installed and has been reinstalled from other sources in an attempt to get it working.
    Last edited by elliott (2012-02-22 20:10:44)

    Just updated and rebooted, but wireless still seems to be working for me (also have a T60 using iwl3945. Same modules loaded that gozes listed. Here's iwl3945 containing lines in my everything.log since the reboot
    Apr 5 17:39:46 localhost kernel: [ 6.267873] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
    Apr 5 17:39:46 localhost kernel: [ 6.267877] iwl3945: Copyright(c) 2003-2011 Intel Corporation
    Apr 5 17:39:46 localhost kernel: [ 6.268108] iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    Apr 5 17:39:46 localhost kernel: [ 6.268123] iwl3945 0000:03:00.0: setting latency timer to 64
    Apr 5 17:39:46 localhost kernel: [ 6.322986] iwl3945 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
    Apr 5 17:39:46 localhost kernel: [ 6.322991] iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
    Apr 5 17:39:46 localhost kernel: [ 6.323145] iwl3945 0000:03:00.0: irq 46 for MSI/MSI-X
    Apr 5 17:40:03 localhost kernel: [ 29.666416] iwl3945 0000:03:00.0: loaded firmware version 15.32.2.9
    I'm running the stock Arch kernel from the core repo right now and linux firmware package is 20120227-1. Let me know if there's other info I can give to try and help track down the difference.

  • Can't find wireless on Dell D620

    When I install the Oracle VM Server on a Dell D620 the kernel sees the eth0 direct attached ethernet but it does not see the eth1 wireless interface. Can I just plumb/configure/create this interface and have the kernel recognize the device or do I need to recompile the kernel to pick up this device? Are there any known issues with wireless interfaces?
    pat

    So I have two questions:1.  What is the quickest way to find out the IP addresses assigned to devices on my home network?
    2.  Is there some permanent way for me to assign the device to the network, even if the IP address changes from time to time?
    The quickest way to determine the IP address assigned to the PrintServer is to generate a diagnostic print-out.
    To do so:
    Ensure that both the PrintServer and the printer attached to the Printer port are on.
    Press the Reset button, and hold it for 2 seconds. (Note: Holding the reset button for 10 seconds will reset the PrintServer back to its factory-default configuration.)
    The test page, which lists PrintServers' current settings, will be printed.
    For networked devices, like print servers and NAS devices, you will want them to have static IP addresses just outside of the range of dynamic IP addresses the DHCP server in your router is providing. Since you have an AirPort Extreme Base Station (AEBS), you have two choices to do this:
    Use the AirPort's DHCP Reservation feature to assign a "static" IP address FROM the pool of DHCP addresses it provides to the PrintServer, or
    Use the PrintServer web-based administration interface to assign the PrintServer with a static IP address.

  • Strange behavior with Cisco AP and Intel 3945 wireles card

    Hi,
    I have an interesting problem with an Intel 3945 A/G card, and my cisco APs.
    1. Given:
    Cisco 1100 and 1200 AP running IOS 12.3.8-JEA
    Two laptop, one with Intel 2200 MPCI Card, the other with Intel 3945 MPCI Card
    Microsoft AD with IAS radius server
    a. 1 SSID with Simple EAP-TLS configuration Enterprise WPA/TKIP, no vlans, broadcast SSID. both card associate correctly and operate normally.
    b. 2 SSID, 1 with simple EAP-TLS configuration Enterprise WPA/TKIP (broadcast), and 2nd SSID Open/No encryption/No authentication (not broadcasted), both cards associate correctly and operate normally.
    c. 2 SSID, 1 with simple EAP-TLS configuration Enterprise WPA/TKIP (broadcast), and 2nd SSID WPS-PSK (not broadcasted), both cards operate normally.
    Now it gets interesting:
    c. 2 SSID, 1 with EAP-TLS/WPA Enterprise on its own VLAN 102, 2nd SSID Open/No Encryption/No authentication on a separate VLAN 105, VLAN 1 is used for admin and radius backhaul to IAS.
    If both SSID are broadcasted via mbssid guest-mode both Intel cards work as expected
    If neither SSID are broadcasted, both Intel cards work as expected
    If either SSID is broadcasted via normal guest-mode command, the Intel 2200 associates and works correctly, but the Intel 3945 refuses to assocate to the AP.
    Has anyone heard of side-effect?
    Alan

    I'm seeing a similar issue with the 3945 right now. However in my example the following is the case;
    APs are 1200 series IOS upgraded running 802.11b interfaces only. There are multiple SSIDs NONE of which are broadcasting.
    We've got a few different client types. The Cisco CB21ABG cards are fine, as are the Intel 2200 and 7920 phones. It's only the 3945 that has a problem and it's running Intel's 10.5.1.68 driver which is the latest. I'm considering downgrading it to an older driver.
    Anybody got a definate fix for this Intel card???

  • Atheros AR5001+ and Intel 3945/ABG [Golan] #2

    Hello, everyone, I am trying to connect two network cards, an Atheros AR5001X + and an Intel 3945/ABG in Ad-Hoc mode, the cards are associated (apparently) but a machine does not ping and do not surf!
    It is true that I have to use a different Broadcast for both wired and wireless?
    I follow this steps on atheros(internet):
    iwconfig ath0 mode ad-hoc essid "Wireless_Network"
    ifconfig ath0 192.168.0.10 netmask 255.255.255.0 up
    And Intel:
    iwconfig wlan0 mode ad-hoc essid "Wireless_Network"
    ifconfig wlan0 192.168.0.20 netmask 255.255.255.0 up
    My modules is ath_pci(i tested ath5k too) and iwl3945.
    And my Internet is HSDPA USB Modem(ZTE MF622).
    Thanks in advance.

    Hello, everyone, I am trying to connect two network cards, an Atheros AR5001X + and an Intel 3945/ABG in Ad-Hoc mode, the cards are associated (apparently) but a machine does not ping and do not surf!
    It is true that I have to use a different Broadcast for both wired and wireless?
    I follow this steps on atheros(internet):
    iwconfig ath0 mode ad-hoc essid "Wireless_Network"
    ifconfig ath0 192.168.0.10 netmask 255.255.255.0 up
    And Intel:
    iwconfig wlan0 mode ad-hoc essid "Wireless_Network"
    ifconfig wlan0 192.168.0.20 netmask 255.255.255.0 up
    My modules is ath_pci(i tested ath5k too) and iwl3945.
    And my Internet is HSDPA USB Modem(ZTE MF622).
    Thanks in advance.

  • Intel 3945 driver needs hotplug firmware

    I'm having some issues getting the Intel 3945 wifi adapter to become recognized by Oracle Enterprise Linux 5.5.
    It seems that the 802.11 and the driver are present however it seems to need a microcode piece as well. This is documented at:
    [http://ipw3945.sourceforge.net/|http://ipw3945.sourceforge.net/]
    Step 1 on the requirements listing is for the microcode.
    The install docs say to look at /etc/hotplug/firmware.agent file to get the directory.
    I just redid my installation and this file is still not present.
    It also lists the steps to use the kernel source to come up with the directory.
    So, make gconfig and take a look:
    Device Drivers ->
    Generic Driver Options ->
    are present, however,
    Hotplug firmware loading support
    after that is not present. I saw some options for CPU hotplugging and memory hotplugging but the install docs are calling for this option which doesn't seem to be present.
    So, what's the easiest way to get hotplugging support on this version of Linux? I've tried the Red Hat forums but everyone there says to just install the ucode to /lib/firmware and off you go.
    thanks in advance,
    alan

    http://dag.wieers.com/rpm/packages/ipw3945d/
    http://dag.wieers.com/rpm/packages/dkms-ipw3945/
    http://dag.wieers.com/rpm/packages/ipw3945-firmware/
    All of these kept giving 404 errors unless I chose the source option. Oh well. So I gave up and thought I'd just compile up the latest kernel and see if that would help.
    I checked for the hotplug option and it still isn't there so I have no clue what Intel was talking about.
    I did remember seeing another message about the ucode file having a different file name so I finally ran it down.
    All you need to do is to find the firmware file and copy it so it reads:
    /lib/firmware/iwlwifi-3945-2.ucode
    and then service network start and up she comes. I tried various permutations of strace -f trying to figure out the filename but never could come up with it. Oh well. Then it's:
    add the following to modprobe.conf
    options iwl3945 disable_hw_scan=1
    and finally:
    service NetworkManager restart
    to get the little network icon on the upper right-hand side so I can get the easy wifi access point pick list.
    Then I ran firefox and it connected to web pages.
    Thanks for effort,
    alan

  • [Solved] Setting up wifi in Dell D620

    Hello,
    I have Dell D620 laptop in witch I'm trying to set up WIFI.
    I was following by instructions in: http://wiki.archlinux.org/index.php/Dell_Latitude_D620 and http://wiki.archlinux.org/index.php/Wir … 000-series
    but after all I have error:
    SIOCSIFFLAGS: No such file or directory
    when I try to make it up with
    ifconfig wlan0 up
    but it's visible in iwconfig and ifconfig -a
    I've tried to update linux-firmware also, but it's up-to-date.
    I have autoload on in my rc.conf
    output from rfkill list:
    0: dell-wifi: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    1: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    Last edited by seraph (2010-09-02 06:03:55)

    The problem was that I followed directly instructions and didn't checked that I have other wireless driver.

  • My WLAN chokes when going too fast (Intel 3945 w/ Netgear) [SOLVED]

    I recently upgraded my Internet connection from 8/1 to 24/10 and since then I have been able to download at the highest speed without any problems, except for this one of course.
    When I'm torrenting and getting higher than 2 MB/s (yes, megabytes) speeds, the connection suddenly "chokes" and puts some sort of threshold on itself at about 150 KB/s. The threshold is not put only on the torrents, but on my entire connection to *this* computer. All of the other computers connected to the router still work fine. This problem doesn't go away unless I reconnect myself to my router. This happens only on Linux, not on Windows as far as I can tell.
    What can be the problem? I have Intel 3945 drivers and 2.6.31.
    Last edited by skorpan (2009-11-30 21:39:20)

    This is *EXACTLY* what has been happening to me; thought I was going crazy. I also have an intel iwl3945 and 2.6.31. My router is a netgear wgr614v6. When I associate from *this* computer, after a seemingly random period of time, my connection gets chocked from the normal ~1.5 mb/s to 113 kb/s. This only happens to this computer, however, it *doesn't* happen over the local network, just to the internet. I can only use my full bandwidth after re-associating with the router. I was thinking it had to be a bug in the router firmware, but this looks like too much of a coincidence now...
    what router do you use?

  • Intel 3945 roaming issues

    I have some 1242 AP's set up with Cisco Fast roaming. My 3945 clients roam fine, but after a few seconds, they lose their IP address. If I have a constant ping going, my ping will drop for about 3 seconds, then replys will go for about 4 seconds. It will continue to do this about three times until stabilizing and then it works great until roaming again. Anyone have any ideas? TAC blames Intel. Intel says to work with Dell. Dell has no clue. Any help would be appreciated.

    Hi Allan,
    Have you tried tweaking Roaming Aggressiveness in the Intel PROSet client utility? You may also want to try turning off Auto-RF just to see if it makes any difference.
    I had costumers which had problems with the ProSet Utility. We deinstlled ad used the Windows XP Wireless Zero configuration.
    The Intel Wireless NIC have actual some issues with the Cisco environment.
    Some examples from the forum:
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd73e2f
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=Security%20and%20Network%20Management&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.ee95e05
    Please check if the wireless clients you use are specified in the "Cisco Compatible Client Devices" list:
    http://www.cisco.com/web/partners/pr46/pr147/partners_pgm_partners_0900aecd800a7907.html
    The mentioned versions can be found here:
    http://www.cisco.com/warp/public/765/ccx/versions_and_features.shtml
    Best regards,
    Frank

  • Lowering resolution on Dell E6510/Intel GM45HD

    Not sure if this is the right forum... anyway, I seem to be unable to lower the resolution on my laptop screen from the default one of 1600x900 (I need to get it to 1024x768 to clone the output to a projector). Attaching an external monitor works fine, and I can choose between a range of resolutions for it. Some output from xrandr:
    $ xrandr -q
    Screen 0: minimum 320 x 200, current 1600 x 2100, maximum 8192 x 8192
    eDP1 connected 1600x900+0+1200 (normal left inverted right x axis y axis) 344mm x 194mm
    1600x900 60.0*+ 40.0
    VGA1 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 367mm x 275mm
    1600x1200 60.0*+
    1280x1024 75.0 60.0
    1152x864 75.0
    1024x768 75.1 60.0
    800x600 75.0 60.3
    640x480 75.0 60.0
    720x400 70.1
    HDMI1 disconnected (normal left inverted right x axis y axis)
    DP1 disconnected (normal left inverted right x axis y axis)
    HDMI2 disconnected (normal left inverted right x axis y axis)
    HDMI3 disconnected (normal left inverted right x axis y axis)
    DP2 disconnected (normal left inverted right x axis y axis)
    DP3 disconnected (normal left inverted right x axis y axis)
    As per Arch Wiki, I tried manually creating and adding the folowing mode:
    $ cvt 1024 768 60 -r
    # 1024x768 59.87 Hz (CVT 0.79M3-R) hsync: 47.30 kHz; pclk: 56.00 MHz
    Modeline "1024x768R" 56.00 1024 1072 1104 1184 768 771 775 790 +hsync -vsync
    However, if I try to set eDP1 to this mode, the screen just goes black. Switching to a console terminal works, and
    I can kill the X server by a keyboard shortcut. However, the screen remains black even if I try to switch back to
    the "default" mode by a shell script:
    #!/bin/bash
    xrandr --output eDP1 --mode 1024x768R
    sleep 2
    xrandr --output eDP1 --mode 1600x900
    Any ideas?
    Edit: forgot to repeat the info from the subject line: I'm running a Dell Latitude E6510 laptop, with integrated Intel GM45HD video.
    Last edited by _oggy (2012-02-28 11:36:49)

    Sorry guys, forgot to reboot my computer. *smacks head on wall twice*

  • 3945BG Intel Adapter PEAP issue

    Hi, We have few SONY laptops with this builtin adapter.. Unfortunately, these adapters do not seem to work when PEAP with WinXP, is used with Cisco APs. TAC has already disowned this issue, saying it is a Intel issue. As we are not getting much of support from our Laptop vendor, i am just curious if anyone has this issue and found any good workaround...
    If any third party supplicant can overcome this issue, please provide pointers.. We would like to evaluate before purchasing it..
    Well, fyi.. i have upgraded the latest firware on Intel.

    Checked this link the SONY only support CCX v3 that part of the PEAP may not work w/ Cisco AP.
    http://www.cisco.com/web/partners/pr46/pr147/partners_pgm_partners_0900aecd800a7907.html
    http://www.cisco.com/warp/public/765/ccx/versions_and_features.shtml
    Better check w/ SONY what is their CCX support ver., or try to use other authentication method....
    Hopes this help.

  • Wicd woes...Intel 3945...assistance requested

    I have tried to use Wicd in the past without success and now that it's coming to the [extra] repository I thought for sure it'd be working by now, but I'm not having any luck at all. It doesn't even manage my DHCP wired connection, and half the time the gui doesn't even appear when I launch it.
    As the title states, I'm running an intel wireless 3945 (iwlwifi drivers) and I've installed the wicd from [testing]
    My rc.conf:
    MODULES=(vboxdrv coretemp i8k acpi-cpufreq cpufreq_ondemand fglrx b44 mii iwl3945 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
    HOSTNAME="dublin"
    lo="lo 127.0.0.1"
    eth0="dhcp"
    wlan0="dhcp"
    INTERFACES=(lo !eth0 !wlan0)
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    DAEMONS=(syslog-ng hal cpufreq wicd network !dhcdbd !networkmanager !@netfs @alsa @crond @cups @ntpd @sensors @sshd @transmissiond)
    I've tried running it with and without the standard network daemon enabled--both have the same non-working result.
    The console output when I run the tray and try to open the gui:
    [thayer@dublin ~]$ /usr/lib/wicd/tray.py
    attempting to connect daemon...
    success
    ERROR:dbus.proxies:Introspect error on :1.3:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Traceback (most recent call last):
    File "/usr/lib/wicd/edgy.py", line 85, in set_signal_image
    config.DisableLogging()
    File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 64, in __call__
    return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 136, in __call__
    **keywords)
    File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 603, in call_blocking
    message, timeout)
    dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    attempting to connect daemon...
    success
    starting...
    refreshing...
    ERROR:dbus.proxies:Introspect error on :1.3:/org/wicd/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Traceback (most recent call last):
    File "./gui.py", line 956, in <module>
    app = appGui()
    File "./gui.py", line 695, in __init__
    self.refresh_networks(fresh=False)
    File "./gui.py", line 855, in refresh_networks
    if wired.CheckPluggedIn() or wired.GetAlwaysShowWiredInterface():
    File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 64, in __call__
    return self._proxy_method(*args, **keywords)
    File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 136, in __call__
    **keywords)
    File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 603, in call_blocking
    message, timeout)
    dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
    Traceback (most recent call last):
    File "/usr/lib/wicd/tray.py", line 7, in <module>
    import edgy
    File "/usr/lib/wicd/edgy.py", line 214, in <module>
    gtk.main()
    KeyboardInterrupt
    [thayer@dublin ~]$

    Thanks you two for the advice, I've had some limited success with your tips...
    schivmeister wrote:
    As for the gui, only one click is needed. If you double-click, it won't appear For DHCP i presume you had pulled in dhcclient/dhcpcd, but sometimes configuring the IP takes a long time? This may be a DNS issue, and I suggest you try opendns.
    But first, Network daemon should be enabled before wicd, the interfaces must not be disabled either. Also, 1.3.4 is definitely better than 1.3.1
    The funny thing is, I already use opendns at the router level.  You are correct that dhclient and dhcpcd was already installed and for the record I tried both clicking and running the gui in standalone mode.
    Reversing the order of wicd and network in the daemons array appears to be what fixed the bigger issues.  Uncommenting the interfaces might have helped too, but I'm going to try removing the wlan0 device because currently Arch hangs during boot while trying to find wlan0.
    So anyway, I rebooted with these changes and was happy to see my wireless had connected flawlessly.  However, I normally use the wired connection when I'm sitting in my office and when I tried to connect to it, it just defaults back to the wireless after a few seconds.  I created a profile as directed, so it must be something else going on.
    At any rate, I've got SOMETHING working with wicd, so thanks again...
    UPDATE1:
    I disabled (!) wlan0 from the interfaces array and Wicd still picks it up okay, so at least the network daemon doesn't hang at boot while trying to associate with wlan0.
    Last edited by thayer (2007-11-21 16:23:29)

  • Dell 1564 - Intel I5-M430 - Overheating issues, very slow performance

    Hi,
    I have a dell 1564, with an I5 M430 cpu. I have cooling issues and as a result my CPU temperature peaks close to 90~95 degree Celsius sometimes on extended full cpu usage. In such situations , I cut down my usage , and manage to bring the temperature down back to reasnoble ranges of 60~75 degrees. However often in these situations even after cooling down, my cpu performance becomes very miserable. Normal browsing which usually uses 10~15% cpu show up as taking 80~90% cpu (as per top/ and other process monitors). I ran the "N-Queens" benchmark from  hardinfo show drastically reduced performance. Post overheating the benchmark takes 35s, after a reboot it takes only 7seconds. I'm trying to track down the reason for this but can't seem to figure out what's the issue. Can someone help me out in this? I'm basically looking for a solution where I don't have to reboot every time I cross the temperature threshold just to get normal CPU performance again. Ideally if its downclocking somehow I'm hoping that it should reset back normally after temperature returns to normal ranges.
    Stuff I've tried:
    * dmesg : No new messages added during/after the overheating
    * cpu scaling : cpu frequency reported by /proc/cpuinfo are back to the normal 2.26 GHz which is my peak scaling. Also I've tried all scaling governors , and even locking the frequency to 2.26GHz , doesn't seem to bring back the performance.
    * suspending and resuming , in hopes of reseting any CPU modes. No luck, CPU still in bad performance. Only a reboot fixes it.
    Output of cat /proc/cpuinfo
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 37
    model name : Intel(R) Core(TM) i5 CPU M 430 @ 2.27GHz
    stepping : 2
    microcode : 0x9
    cpu MHz : 2267.000
    cache size : 3072 KB
    physical id : 0
    siblings : 4
    core id : 0
    cpu cores : 2
    apicid : 0
    initial apicid : 0
    fpu : yes
    fpu_exception : yes
    cpuid level : 11
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm ida arat dtherm tpr_shadow vnmi flexpriority ept vpid
    bogomips : 4523.40
    clflush size : 64
    cache_alignment : 64
    address sizes : 36 bits physical, 48 bits virtual
    power management:
    ... repeats 3 more times ...
    Any suggestions , to either fix this , or ways to track down the issue, will be much appreciated. Will be happy to provide more details , logs, or specs if required. I'm right now totally clueless as to even how to figure out what's going wrong so anything is welcome.

    The one thing that sticks out is Firefox is using an excessive amount of CPU resources.  Delete Firefox and see if there is an improvement.
    Ciao.

  • Installing tonight - Dell D830 - Intel Integrated Video/Dell Wireless

    Hi,
    I am going to install tonight and I am "ok" with linux.  I am tired of all the "one in all solutions", especially when they never work as intended..
    I wanted to ask about a couple items, and I have the guide all printed out to go.
    1.  It appears my video will be fine from what I have read, does anyone have any advice in terms of how to configure xorg.conf and at what point I add in my graphical choice?
    2.  Is KDEMOD the best option for arch?  It looks good, I tried to install Chakra today but the disk kept failing on the partitioning so I am not sure what was going on.
    3.  Wireless - it looks like I need the fwcutter firmware and have to update the drivers.  I would like to use wireless as quickly as possible after my install.  Is there a way to get that going asap or only until I have it installed and onine?
    Any other "gotcha's" about installing?
    THX!!!:D

    1.) My advice: don't bother with xf86-video-intel, go straight for xf86-video-intel-legacy. The new one just isn't worth the hassle. Plus, I've actually read that xf86-video-intel-legacy is faster (I don't know if this is true or not, though).
    2.) The best choice is whatever works best for you. You should be able to find plenty of debates on which DE is the best. Usually the arguments are KDE vs. GNOME, but Xfce often comes into the mix, and occasionally you might see mention of Enlightenment. LXDE is also worth checking out.
    Anyway, if you think KDEMOD might be what you want, go ahead and try it out! It's easy enough to replace if you decide you don't like it. When people ask me what DE to use, I usually recommend Xfce.
    3.) I'm sorry, I can't help you there. I run Arch on my desktop, so I don't use wireless. I'm not even sure what you're asking, though.
    Any other "gotcha's" about installing?
    I recommend having another computer available while you're installing, in case you're not sure what to do next, and need to ask or something.
    Good luck, and welcome to the community.

Maybe you are looking for