Booting with intel-wireless

Trying to install Arch on a netbook. Used unetbootin to create a liveusb. How do I boot with this parameter?
"For intel wireless drivers you need to boot with the intel-wireless boot parameter"

schen wrote:Try it without the intel-wireless boot parameter. If if still works, continue on. Also, only a few hours passed before you bumped this thread. Please try to be more patient.
Right, sorry.
Anyway, I got it to boot with that, but now I've realized that's not what I needed, I have an Atheros card.
Thing is, I can't get it to work during the setup.
These are outputs of some commands:
>lspci | grep -i net
01:00.0 Ethernet controller: Marvell Technology Group Ltd. Uknown device 4380 (rev 10)
02:00.0 Network controller: Atheros Communications, Inc. Unknown device 002a (rev 01)
>iwconfig
lo no wireless extensions
iwconfig and ifconfig of wlan and ath 0 through 3 say they don't exist. What am I to do?

Similar Messages

T60 does not boot with Intel T7600G CPU

I replaced my Intel Core Duo T2400 with Intel Core 2 Duo T7600G CPU in ThinkPad T60(1951-CTO) laptop. However, laptop does not boot with Intel Core 2 Duo T7600G CPU. It doesn't even complete the POST: https://db.tt/8UL8FlE0 As seen in the video, I plugged in the power adapter at 0:02 and pressed the power button at 0:06. One can hear a little click made by optical device. If I press the power button again at 0:16, this click does not happen. BIOS version is 2.27. I have reset the BIOS settings by disconnecting the CMOS battery, but this didn't help. Once I replace the T7600G with my old T2400 then I'm able to boot the laptop.
Any ideas what might cause such behavior? Shouldn't there be beep codes in case of CPU issues? What else to try?

TuuS wrote:
600X wrote:
Since you came from a T2400, does your T60 even have a Rev. 3 motherboard? If it does not, then no Core 2 Duo will work, only Core Duo's.
I don't claim to be the top authority on T60 motherboards, but I believe any will use a Core 2 T7600, 7400, 7200 if the firmware is updated.
My own experience mirrors what TuuS has stated. I have yet to see a T60/p from any walk of life with a recent BIOS that will bark at a proper Core 2 Duo CPU.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

Installing Arch with intel wireless (iwlwifi-3945)

i have tried various times in the past few weeks to install arch with minimal success. The only time i was able to actually set up a system that would allow me to get to a gui and use the internet was when i had an install of Archie Linux (Live CD) that i had to chroot with kubuntu to add wireless support. Needless to say i preferred a cleaner install (especially after having to manually rename the folders, etc. for the repository changes).
Anyways when arch is loading it makes mention of needing to append the boot image to include intel-wireless. i was wondering what exactly was involved in doing that. Because after trying to just install the package ifconfig does not show my wlan device. Any help is appreciated. let me know if more info is needed.

pl2lnce wrote:
i have tried various times in the past few weeks to install arch with minimal success. The only time i was able to actually set up a system that would allow me to get to a gui and use the internet was when i had an install of Archie Linux (Live CD) that i had to chroot with kubuntu to add wireless support. Needless to say i preferred a cleaner install (especially after having to manually rename the folders, etc. for the repository changes).
Anyways when arch is loading it makes mention of needing to append the boot image to include intel-wireless. i was wondering what exactly was involved in doing that. Because after trying to just install the package ifconfig does not show my wlan device. Any help is appreciated. let me know if more info is needed.
I have Arch with iwl3945 drivers running here just fine. No tweaks to the cpio image needed.
I have never heard of this either... You need both the drivers and the firmware. Check dmesg if everything is okay. Ifconfig -a should show a wlan0 device, if not, something went wrong.
broch wrote:I have HP dv5000t (dualcore) with the same card. Never had any problems with intel 3945. However I am using ipw3945 instead of iwl3945 as the later is still early beta and far from stability, performance of ipw.
Since 1.1.0 stability is just fine. Throughput is still a problem though. I get like 2.8 MBps with earlier versions, and the 1.1.21 one can hit it too, but mostly it's around 1 MBps . I prefer that to yet another proprietary package though. It's not every day I transfer a few GB to my wired server .
Last edited by B (2007-11-15 18:12:18)

PXE Boot With intel Based IMAC

Hello,
I am trying to boot my IMAC from the network with PXE Boot with no success.
I found some documents (very little) about how to boot mac from network using diffrent mac with app called netboot, but i assume that because my imac is intel based it should be able to boot from PXE.
Are there any documents information you could point me to ?
Thanks.

U.S. websites for those companies don't show those models on their product lists or at support. If your iMac recognizes your printer, don't worry about the driver, it's there.

Pc laptops Compatible with Intel Wireless Display (WiDi)

I am perplexed and am in need of information/understanding/a reality check.
I recently bought a Lenovo Z570 laptop that was explicitly advertised as supporting Intel Wireless Display (WiDi). I also bought a Belkin Screencast adaptor.
The computer arrived and there was the WiDi shortcut on the desktop. I plugged the Screencast adaptor to my tv through an HDMI cable and set the tv to the correct channel for the input. Great so far!
Per Intel's list of updates (http://www.intel.com/support/wireless/wtech/iwd/sb/CS-033375.htm), I went through and updated the wireless driver and then the Graphics driver. When I tried to update the Intel Wireless Display software, the process was aborted. And my screencast said that the monitor display could not be sent to tv.
After a lot of searching, I realized that my i5-2450M processor does not appear on Intel's list of compatible processors. System requirements can be found at http://www.intel.com/support/wireless/wtech/iwd/sb/CS-031059.htm which says that the processor must be:
ONE of the following:
Intel® Core™ i7: 640M; 660LM; 640LM; 620LM; 620M; 610E; 690UM; 680UM; 660UM; 640UM; 620UM; 660UE; 2710QE; 2820QM; 2720QM; 2635QM; 2630QM; 2657M; 2649M; 2629M; 2620M; 2617M; 2540M; 2520M; 2510E; 2640LM; 2620LM; 2630UM; 2610UM; 2530UM; 2920XM
Intel® Core™ i5: 580M; 560M; 540M; 520M; 480M; 460M; 450M; 430M; 580UM; 560UM; 540UM; 520UM; 470UM; 430UM; 2540M; 2520M; 2410M; 2537M
Intel® Core™ i3: 390M; 380M; 370M; 350M; 330M; 330E; 2310M
Strange, but at that point I was just angry that the store and/or Lenovo had made a whopping mistake. After all, the WiDi shortcut and program was on my laptop; there has to be a reason for that, right?
After a lot of searching, I haven't come up with any answers, only more questions. Here on Best Buy, I searched for pc laptops that support WiDi. A list of 36 or 37 machines came up as qualifying. However, in going through them one by one, only a handful have processors that appear on Intel's list for the System Requirements.
I am very confused. Is Intel's list out of date? But if that's so, why didn't my attempt to update and use the software work? Are bestbuy and costco and multiple laptop makers mistaken when they say a machine is capable of supporting Wireless Display? What the heck is going on? Can anyone help me figure this out?
The Lenovo is on it's way back, but I need a new laptop as my old one is literally falling apart. A new one with WiDi would be extremely useful for a disabled family member. I'm also stuck with the Screencast I bought now too. Beyond all that, I'm really curious what is going on. Am I just stupid or befuddled or . . .is there something I'm missing? Any help would be so, so appreciated. Thank you.

The notebook does fully support WiDi but for some unknown reason, yours simply did not work. The CPU specs from Intel list WiDi as a capability of the CPU and the notebook has the appropriate hardware. I couldn't say why it didn't work but Lenovo does not advertise WiDi as a function of that model on their website so something is obviously off.

ISCSI boot with Intel NICs added to windows 2008 r2 routing table causes non iscsi traffic to attempt default routes on iscsi networks

I have a server with Intel 82576 Gigabit Dual Port Nics. I have configured them to use iSCSI boot the primary looks to 10.0.0.1/24 and the secondary looks to 10.0.1.1/24. The target is configured correctly. Everything boots as expected.
I have added the MPIO feature and configured MPIO for the iscsi initiator as per: http://blogs.technet.com/b/migreene/archive/2009/08/29/3277914.aspx.
My issue is that the iSCSI networks show up in the routing table like so:
I did not configure a default route in the Intel setup utility:
I tried to explicitly remove the 0.0.0.0 entry and leave blank, with no change. As you can see with the above routing table traffic attempts to travel over these routes:
C:\Users\Administrator>ping google.com
Pinging google.com [209.85.145.99] with 32 bytes of data:
Reply from 10.0.0.201: Destination host unreachable.
Reply from 10.0.1.201: Destination host unreachable.
Reply from 209.85.145.99: bytes=32 time=23ms TTL=51
Reply from 209.85.145.99: bytes=32 time=22ms TTL=51
Ping statistics for 209.85.145.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
A ping to the outside world first attempts on 10.0.0.x/24 network, then on 10.0.1.x/24 network and then finally on the network the traffic should go over. I don't want my iSCSI traffic to ever show up with a default route. How do I get rid of it?
route delete 0.0.0.0 mask 0.0.0.0 "on-link" results in: The route deletion failed: The parameter is incorrect.
route delete 0.0.0.0 mask 0.0.0.0 on-link results in: The route deletion failed: The parameter is incorrect.
route delete 0.0.0.0 deletes all default routes, then I have to add back in the "valid default route" of 192.168.100.6.
I would like to not have to do a route delete though.

So I've sort of given up on fixing the gateway assignment in the route for iSCSI boot. I configured a DHCP server to give out the information required by iSCSI boot and configured the network cards to use DHCP for their configuration. I insured
that my DHCP server gave out no default gateway entry. However, I still got the undesired routes in the routing table. This makes me assume that there isn't a "fix" for it, only the workaround.
Here is the script I run on each iSCSI Boot initiator (you would obviously change the ip number to suit your environment):
@Echo off
Rem fixes iscsi route problem as shown below:
Rem IPv4 Route Table
REM ===========================================================================
REM Active Routes:
REM Network Destination Netmask Gateway Interface Metric
REM 0.0.0.0 0.0.0.0 On-link 10.0.0.200 10255
REM 0.0.0.0 0.0.0.0 On-link 10.0.1.200 266
REM 0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.98 266
REM The top 2 lines are on the iscsi interface and traffic tries to go out it
REM We need to delete the routes, so we'll just delete all gateway routes and
REM add back in the one we care about.
route delete 0.0.0.0 >c:\iscsibootroutefix.log
route -p add 0.0.0.0 mask 0.0.0.0 192.168.100.6 >>c:\iscsibootroutefix.log
After running it I get:
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.100.6 192.168.100.98 11
10.0.0.0 255.255.255.0 On-link 10.0.0.200 10255
10.0.0.1 255.255.255.255 On-link 10.0.0.200 10255
10.0.0.200 255.255.255.255 On-link 10.0.0.200 10255
Then I added a task in “task scheduler” of "administrative tools" that ran as the user “system” “when the computer starts” that runs this script.

Problems connecting on Wireless 802.11n with my T61 with Intel Wireless AGN

Hi, I live in Thailand and have a similar problem as others with my Intel Wireless AGN connection as others. I have a D-Link Model DSL-2740B Rangebooster N ADSL2/2+ Modem Router. It is supposed to support 802.11n draft wireless connections of up to a maximum of 270 MBPS versus 54 MBPS for 802-11G wireless. Of course, I don't expect it to reach the maximum transfer speed, particularly here in Thaiand, however I would expect it to produce results better than the 54 MBPS rate for 802-11G. I first tried it on my ThinkPad T61 which incorporates Intel® Wireless WiFi Link 4965AGN. When connected, it shows a speed of 54MBPS (802-11G) instead of higher wireless 802-11n speeds. I've upgraded my router to the latest firmware and have tried different configurations with no improvement in performance. One think I have noted is that when I make an on-line configuration change to my router configuration then select "apply", immediately my ThinkPad rate changes to 150 MBPS momentarily then my connection is lost (to be expected as the router changes are being implemented), followed by reconnection of wireless signal only to return at 54 MBPS again. I also have an older ThinkPad model without built-in wireless capability so I purchased a Belkin wireless 802.11n USB adapter to connect to my router. Again, the maximum connection is at 54 MBPS. When I repeat configuration changes to my router as I did above, my ThinkPad connection momentarily changes to only 1 MBPS instead of 150 MBPS as in my other T61 ThinkPad then reverts back to 54 MBPS once the configuration changes have been completed. Has anyone successfully used wireless 802.11n successfully at the higher transfer rates (above 54 MBPS)? Is it possible that my TOT Goldcyber connection speed is artificially limited? I notice that my rated speed for my desktop computer connected to my same D-Link DSL-2740B only indicates a rated speed of 100 MBPS. I use Vista Home Premium 64-bit on my destop, Vista Home Premium 32-bit on my ThinkPad T61, but us Windows XP Professional on my older ThinkPad. I feel that my problem is either with my ADSL carrier (TOT) or compatibility with my D-Link DSL-2740B Modem Router and my ThinkPad T61 internal wireless card and/or Belkin wireless n USB adapter. IT-City is letting me swap out the Belkin USB for the D-Link Rangebooster n DWA-140 USB adapter next week when they restock. The only other think that I can think of is that wireless n just doesn't work in Thailand and that maybe I should just stick with wireless G and go with a higher powered wireless USB model such as the business rated EmGenius EUB 362 EXT. Has anyone used this model and had good success with it; I've heard that it is a long range model and has the capability of reaching 108 MBPS through some sort of magic? Looking forward to reading your replies and possible solution.
Pattayadavid

Hi!
Intel Wi-Fi cards support full 802.11n speed of 300 Mb/s working at 5 GHz range only. Your D-Link DSL-2740B works only in 2.4 GHz range. So to get 300 Mb/s you have to get another wi-fi router that supports 802.11n in both 2.4 and 5 GHz, for instance Lynksys WRT610N or Apple Airport Extreme or whatever.

Dell Studio Laptop with Intel Core i5 S15Z with Intel Wireless Display issues (WIDI) (pkg deal)

i bought this laptop in Jan,2010 . Due to some h/w issue BB replace it in April. When i tested my wireless display capability using the the Intel Wireless Display option i got a message "Intel My Wifi Technology not enabled. Restart the computer and try again." i have restarted my laptop several times. Also in the icon tray when i keep the mouse pointer on top of Intel My Wifi Technology it gives a message "Adapter not found". Please help.
I took the laptop to Geek squad in BB and they told me that they need to put the laptop to factory defualt and troubleshoot the issue that why the wireless adapter is not enabled.
Any suggestion as i don't want to go through this madness of backing up the data and restoring again. This will be my 3rd time . Any other alternatives .
Anybody using the above system with Netgear push2tv . Can you share the output of device manager as i like to see what wireless device you are seeing as i am suspecting this laptop may not have one but then sice i see the s/w available i am confused ?

Almost every time we see a WIDI display issue, it is because the user is trying to use it too far away from the t.v.. It has a very short distance and when out of range, shows an adapter not found error. Playing with it, we found that over 15 ft it adapter wouldn't connect at all, and the closer the better as far as connectivity.
Crystal
Superuser
Forum Guidelines | Terms & Conditions | Community Guidelines | What is a Superuser?
*Remember to mark your questions solved and click the star to give kudos to show your thanks!*
While I used to be a Best Buy Employee, I no longer have any affiliation with Best Buy.
My opinions do not in any way shape or form represent Best Buy's Official decisions.

Senforce 3.2 conflicts with Intel Wireless drivers

Hi, the company I work for is running Senforce 3.2 (the old name for Endpoint Security). It is conflicting with the Intel Wireless drivers in a batch of new laptops (both trying to start/stop the drivers at same time).
Would like to know if anyone has seen similar behaviour, or what a possible solution might be.
Many thanks.

simonbarron,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

[SOLVED] Authentication with AP on 3.6.* with Intel Wireless adapter

Edit 06/2014: Solved ages ago via 3.10+
Kernels tested: 3.6.2-1, 3.6.3-1, 3.6.4-1.
After the latest kernel upgrade my wireless can't authenticate with my AP, wicd-gtk hangs on "authenticating" and then says "bad password".
lspci -vnn | grep -i net
02:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] [8086:0083]
A snip from /var/log/messages showing errors at boot. The last messages just repeat continuously.
Oct 16 14:52:44 localhost kernel: [ 9.337732] iwlwifi 0000:02:00.0: loaded firmware version 39.31.5.1 build 3513
8
Oct 16 14:52:44 localhost kernel: [ 10.079892] iwldvm: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
Oct 16 14:52:44 localhost kernel: [ 10.079898] iwldvm: Copyright(c) 2003-2012 Intel Corporation
Oct 16 14:52:44 localhost kernel: [ 10.079930] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
Oct 16 14:52:44 localhost kernel: [ 10.079933] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
Oct 16 14:52:44 localhost kernel: [ 10.079935] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
Oct 16 14:52:44 localhost kernel: [ 10.079937] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE disabled
Oct 16 14:52:44 localhost kernel: [ 10.079938] iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_P2P disabled
Oct 16 14:52:44 localhost kernel: [ 10.079941] iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Wireless-N 100
0 BGN, REV=0x6C
Oct 16 14:52:44 localhost kernel: [ 10.080008] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:52:44 localhost kernel: [ 10.087424] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
Oct 16 14:52:44 localhost kernel: [ 10.100826] iwlwifi 0000:02:00.0: device EEPROM VER=0x15d, CALIB=0x6
Oct 16 14:52:44 localhost kernel: [ 10.100828] iwlwifi 0000:02:00.0: Device SKU: 0x50
Oct 16 14:52:44 localhost kernel: [ 10.100830] iwlwifi 0000:02:00.0: Valid Tx ant: 0x1, Valid Rx ant: 0x3
Oct 16 14:52:44 localhost kernel: [ 15.821575] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:52:44 localhost kernel: [ 15.829048] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:52:44 localhost kernel: [ 15.879478] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:52:44 localhost kernel: [ 15.886902] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:52:44 localhost acpid: starting up with netlink and the input layer
Oct 16 14:52:44 localhost acpid: 4 rules loaded
Oct 16 14:52:44 localhost acpid: waiting for events: event logging is off
Oct 16 14:52:53 localhost kernel: [ 25.219799] jme 0000:04:00.5: eth0: Link is down
Oct 16 14:52:53 localhost acpid: client connected from 600[0:10]
Oct 16 14:52:53 localhost acpid: 1 client rule loaded
Oct 16 14:52:56 localhost kernel: [ 28.035738] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:52:56 localhost kernel: [ 28.043276] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:52:56 localhost kernel: [ 28.268085] jme 0000:04:00.5: eth0: Link is down
Oct 16 14:52:56 localhost kernel: [ 28.309378] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:52:56 localhost kernel: [ 28.316816] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:52:59 localhost kernel: [ 31.543667] wlan0: authenticate with 84:c9:b2:b8:cb:f0
Oct 16 14:53:01 localhost kernel: [ 33.551368] wlan0: failed to insert STA entry for the AP (error -5)
Oct 16 14:53:01 localhost kernel: [ 33.551710] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:01 localhost kernel: [ 33.551758] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:01 localhost kernel: [ 33.559158] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:03 localhost kernel: [ 35.603895] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:03 localhost kernel: [ 35.603953] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:03 localhost kernel: [ 35.611394] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:05 localhost kernel: [ 37.656025] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:05 localhost kernel: [ 37.656093] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:06 localhost kernel: [ 37.663560] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:08 localhost kernel: [ 39.708223] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:08 localhost kernel: [ 39.708277] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:08 localhost kernel: [ 39.715713] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:10 localhost kernel: [ 41.760384] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:10 localhost kernel: [ 41.760415] ------------[ cut here ]------------
Oct 16 14:53:10 localhost kernel: [ 41.760424] WARNING: at drivers/net/wireless/iwlwifi/dvm/../iwl-trans.h:607 iwlagn_mac_flush+0x1c2/0x1e0 [iwldvm]()
Oct 16 14:53:10 localhost kernel: [ 41.760425] Hardware name: K52F
Oct 16 14:53:10 localhost kernel: [ 41.760432] iwl_trans_wait_tx_queue_empty bad state = 0
Oct 16 14:53:10 localhost kernel: [ 41.760435] Modules linked in: reiserfs arc4 iwldvm mac80211 uvcvideo jme iwlwifi videobuf2_vmalloc videobuf2_memops videobuf2_core videodev joydev snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_intel snd_hda_codec acpi_cpufreq snd_pcm snd_page_alloc snd_hwdep snd_timer snd jmb38x_ms serio_raw media sdhci_pci asus_laptop iTCO_wdt iTCO_vendor_support cfg80211 mperf sdhci mei intel_ips lpc_ich mmc_core i2c_i801 mii soundcore microcode kvm_intel psmouse memstick input_polldev evdev processor kvm ac thermal battery sparse_keymap coretemp crc32c_intel rfkill tun loop ext4 crc16 jbd2 mbcache sr_mod sd_mod cdrom ahci libahci libata scsi_mod ehci_hcd usbcore usb_common i915 video button i2c_algo_bit intel_agp intel_gtt drm_kms_helper drm agpgart i2c_core
Oct 16 14:53:10 localhost kernel: [ 41.760539] Pid: 658, comm: wpa_supplicant Not tainted 3.6.2-1-ARCH #1
Oct 16 14:53:10 localhost kernel: [ 41.760542] Call Trace:
Oct 16 14:53:10 localhost kernel: [ 41.760554] [<c0139f22>] warn_slowpath_common+0x72/0xa0
Oct 16 14:53:10 localhost kernel: [ 41.760565] [<fa8e4922>] ? iwlagn_mac_flush+0x1c2/0x1e0 [iwldvm]
Oct 16 14:53:10 localhost kernel: [ 41.760574] [<fa8e4922>] ? iwlagn_mac_flush+0x1c2/0x1e0 [iwldvm]
Oct 16 14:53:10 localhost kernel: [ 41.760579] [<c0139ff3>] warn_slowpath_fmt+0x33/0x40
Oct 16 14:53:10 localhost kernel: [ 41.760588] [<fa8e4922>] iwlagn_mac_flush+0x1c2/0x1e0 [iwldvm]
Oct 16 14:53:10 localhost kernel: [ 41.760608] [<fa840803>] __ieee80211_recalc_idle+0x1f3/0x2d0 [mac80211]
Oct 16 14:53:10 localhost kernel: [ 41.760626] [<fa84112a>] ieee80211_recalc_idle+0x2a/0x50 [mac80211]
Oct 16 14:53:10 localhost kernel: [ 41.760642] [<fa83942e>] __ieee80211_start_scan+0xfe/0x510 [mac80211]
Oct 16 14:53:10 localhost kernel: [ 41.760659] [<fa83a37e>] ieee80211_request_scan+0x2e/0x50 [mac80211]
Oct 16 14:53:10 localhost kernel: [ 41.760677] [<fa846f29>] ieee80211_scan+0x69/0x80 [mac80211]
Oct 16 14:53:10 localhost kernel: [ 41.760693] [<f9864178>] cfg80211_wext_siwscan+0x248/0x2e0 [cfg80211]
Oct 16 14:53:10 localhost kernel: [ 41.760700] [<c02294ed>] ? __kmalloc+0x12d/0x160
Oct 16 14:53:10 localhost kernel: [ 41.760713] [<f9863f30>] ? cfg80211_find_vendor_ie+0xc0/0xc0 [cfg80211]
Oct 16 14:53:10 localhost kernel: [ 41.760722] [<c04ad214>] ioctl_standard_call+0x2d4/0x3c0
Oct 16 14:53:10 localhost kernel: [ 41.760729] [<c04d0fc3>] ? schedule+0x23/0x60
Oct 16 14:53:10 localhost kernel: [ 41.760741] [<f9863f30>] ? cfg80211_find_vendor_ie+0xc0/0xc0 [cfg80211]
Oct 16 14:53:10 localhost kernel: [ 41.760748] [<c04ad4fd>] wext_handle_ioctl+0x1fd/0x230
Oct 16 14:53:10 localhost kernel: [ 41.760760] [<f9863f30>] ? cfg80211_find_vendor_ie+0xc0/0xc0 [cfg80211]
Oct 16 14:53:10 localhost kernel: [ 41.760768] [<c03f8cc3>] dev_ioctl+0xb3/0x4e0
Oct 16 14:53:10 localhost kernel: [ 41.760776] [<c03e3f4d>] ? sys_sendto+0xfd/0x140
Oct 16 14:53:10 localhost kernel: [ 41.760784] [<c03e2025>] sock_ioctl+0x85/0x260
Oct 16 14:53:10 localhost kernel: [ 41.760790] [<c03e1fa0>] ? sock_fasync+0x90/0x90
Oct 16 14:53:10 localhost kernel: [ 41.760796] [<c0243eca>] do_vfs_ioctl+0x7a/0x570
Oct 16 14:53:10 localhost kernel: [ 41.760804] [<c02f70e1>] ? copy_to_user+0x31/0x50
Oct 16 14:53:10 localhost kernel: [ 41.760813] [<c01855b7>] ? getnstimeofday+0x47/0x130
Oct 16 14:53:10 localhost kernel: [ 41.760819] [<c0244428>] sys_ioctl+0x68/0x80
Oct 16 14:53:10 localhost kernel: [ 41.760826] [<c04d7e1f>] sysenter_do_call+0x12/0x28
Oct 16 14:53:10 localhost kernel: [ 41.760830] ---[ end trace 004dc83771a21a26 ]---
Oct 16 14:53:10 localhost kernel: [ 41.760841] iwlwifi 0000:02:00.0: Request scan called when driver not ready.
Oct 16 14:53:10 localhost kernel: [ 41.760938] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:10 localhost kernel: [ 41.768376] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:12 localhost kernel: [ 43.825863] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:12 localhost kernel: [ 43.825917] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:12 localhost kernel: [ 43.833397] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:14 localhost kernel: [ 45.881485] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:14 localhost kernel: [ 45.881488] iwlwifi 0000:02:00.0: Request scan called when driver not ready.
Oct 16 14:53:14 localhost kernel: [ 45.881593] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
Oct 16 14:53:14 localhost kernel: [ 45.889068] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
Oct 16 14:53:16 localhost kernel: [ 47.940286] ieee80211 phy0: Hardware restart was requested
Oct 16 14:53:16 localhost kernel: [ 47.940344] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
dmesg output (this repeats also)
[ 81.793548] iwlwifi 0000:02:00.0: Loaded firmware version: 39.31.5.1 build 35138
[ 81.796181] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[ 81.798709] iwlwifi 0000:02:00.0: Status: 0x0000204C, count: 5
[ 81.801253] iwlwifi 0000:02:00.0: 0x00000005 | SYSASSERT
[ 81.803780] iwlwifi 0000:02:00.0: 0x0001E404 | uPc
[ 81.806261] iwlwifi 0000:02:00.0: 0x0001E3E8 | branchlink1
[ 81.808719] iwlwifi 0000:02:00.0: 0x0001E3E8 | branchlink2
[ 81.811080] iwlwifi 0000:02:00.0: 0x00000826 | interruptlink1
[ 81.813361] iwlwifi 0000:02:00.0: 0x00000000 | interruptlink2
[ 81.815543] iwlwifi 0000:02:00.0: 0x0000020D | data1
[ 81.817643] iwlwifi 0000:02:00.0: 0x00000009 | data2
[ 81.819695] iwlwifi 0000:02:00.0: 0x0000020D | line
[ 81.821702] iwlwifi 0000:02:00.0: 0x000186E0 | beacon time
[ 81.823683] iwlwifi 0000:02:00.0: 0x00000920 | tsf low
[ 81.825611] iwlwifi 0000:02:00.0: 0x00000000 | tsf hi
[ 81.827480] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[ 81.829333] iwlwifi 0000:02:00.0: 0x0000BE04 | time gp2
[ 81.831170] iwlwifi 0000:02:00.0: 0x00000000 | time gp3
[ 81.833008] iwlwifi 0000:02:00.0: 0x0001271F | uCode version
[ 81.834856] iwlwifi 0000:02:00.0: 0x0000006C | hw version
[ 81.836706] iwlwifi 0000:02:00.0: 0x00C8330C | board version
[ 81.838560] iwlwifi 0000:02:00.0: 0x04150010 | hcmd
[ 81.840401] iwlwifi 0000:02:00.0: 0x00022080 | isr0
[ 81.842231] iwlwifi 0000:02:00.0: 0x00000000 | isr1
[ 81.844048] iwlwifi 0000:02:00.0: 0x00000002 | isr2
[ 81.845845] iwlwifi 0000:02:00.0: 0x0040D440 | isr3
[ 81.847639] iwlwifi 0000:02:00.0: 0x00200080 | isr4
[ 81.849426] iwlwifi 0000:02:00.0: 0x01000002 | isr_pref
[ 81.851216] iwlwifi 0000:02:00.0: 0x000114DA | wait_event
[ 81.853015] iwlwifi 0000:02:00.0: 0x00000000 | l2p_control
[ 81.854816] iwlwifi 0000:02:00.0: 0x00000000 | l2p_duration
[ 81.856637] iwlwifi 0000:02:00.0: 0x00000000 | l2p_mhvalid
[ 81.858438] iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
[ 81.860230] iwlwifi 0000:02:00.0: 0x00000005 | lmpm_pmg_sel
[ 81.862012] iwlwifi 0000:02:00.0: 0x10021644 | timestamp
[ 81.863786] iwlwifi 0000:02:00.0: 0x00001020 | flow_handler
[ 81.865622] iwlwifi 0000:02:00.0: Start IWL Event Log Dump: display last 20 entries
[ 81.867473] iwlwifi 0000:02:00.0: EVT_LOGT:0000047246:0x0000000f:0484
[ 81.869314] iwlwifi 0000:02:00.0: EVT_LOGT:0000047256:0x00000010:0484
[ 81.871100] iwlwifi 0000:02:00.0: EVT_LOGT:0000047269:0x00000015:0484
[ 81.872853] iwlwifi 0000:02:00.0: EVT_LOGT:0000047280:0x00000016:0484
[ 81.874572] iwlwifi 0000:02:00.0: EVT_LOGT:0000047290:0x00000017:0484
[ 81.876261] iwlwifi 0000:02:00.0: EVT_LOGT:0000047301:0x00000018:0484
[ 81.877917] iwlwifi 0000:02:00.0: EVT_LOGT:0000047306:0x00000019:0484
[ 81.879530] iwlwifi 0000:02:00.0: EVT_LOGT:0000047312:0x000001c9:1108
[ 81.881116] iwlwifi 0000:02:00.0: EVT_LOGT:0000047313:0x00000024:1108
[ 81.882667] iwlwifi 0000:02:00.0: EVT_LOGT:0000047313:0x00000001:1108
[ 81.884192] iwlwifi 0000:02:00.0: EVT_LOGT:0000047314:0x00000033:1108
[ 81.885679] iwlwifi 0000:02:00.0: EVT_LOGT:0000047319:0x0002000d:0464
[ 81.887129] iwlwifi 0000:02:00.0: EVT_LOGT:0000047320:0x0000000d:0462
[ 81.888553] iwlwifi 0000:02:00.0: EVT_LOGT:0000047339:0x00002806:1062
[ 81.889959] iwlwifi 0000:02:00.0: EVT_LOGT:0000047343:0x02020202:1074
[ 81.891368] iwlwifi 0000:02:00.0: EVT_LOGT:0000048434:0x00000325:1074
[ 81.892767] iwlwifi 0000:02:00.0: EVT_LOGT:0000048483:0x000001a4:0602
[ 81.894182] iwlwifi 0000:02:00.0: EVT_LOGT:0000048638:0x04150010:0401
[ 81.895595] iwlwifi 0000:02:00.0: EVT_LOGT:0000048640:0x0000000d:0451
[ 81.897017] iwlwifi 0000:02:00.0: EVT_LOGT:0000048646:0x00000000:0125
[ 83.703038] iwlwifi 0000:02:00.0: Error sending REPLY_RXON: time out after 2000ms.
[ 83.704232] iwlwifi 0000:02:00.0: Current CMD queue read_ptr 21 write_ptr 22
[ 83.705636] iwlwifi 0000:02:00.0: Error clearing ASSOC_MSK on BSS (-110)
[ 83.707703] ieee80211 phy0: Hardware restart was requested
[ 83.707758] iwlwifi 0000:02:00.0: L1 Disabled; Enabling L0S
[ 83.715263] iwlwifi 0000:02:00.0: Radio type=0x0-0x0-0x3
[ 83.779279] iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x2000000.
[ 83.780573] iwlwifi 0000:02:00.0: CSR values:
[ 83.782128] iwlwifi 0000:02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[ 83.783982] iwlwifi 0000:02:00.0: CSR_HW_IF_CONFIG_REG: 0X00c8330c
[ 83.785851] iwlwifi 0000:02:00.0: CSR_INT_COALESCING: 0X00000040
[ 83.787730] iwlwifi 0000:02:00.0: CSR_INT: 0X00000000
[ 83.789610] iwlwifi 0000:02:00.0: CSR_INT_MASK: 0X00000000
[ 83.791486] iwlwifi 0000:02:00.0: CSR_FH_INT_STATUS: 0X00000000
[ 83.793353] iwlwifi 0000:02:00.0: CSR_GPIO_IN: 0X00000000
[ 83.795234] iwlwifi 0000:02:00.0: CSR_RESET: 0X00000000
[ 83.797121] iwlwifi 0000:02:00.0: CSR_GP_CNTRL: 0X080403c5
[ 83.799023] iwlwifi 0000:02:00.0: CSR_HW_REV: 0X0000006c
[ 83.800936] iwlwifi 0000:02:00.0: CSR_EEPROM_REG: 0X00001885
[ 83.802860] iwlwifi 0000:02:00.0: CSR_EEPROM_GP: 0X90000001
[ 83.804785] iwlwifi 0000:02:00.0: CSR_OTP_GP_REG: 0X00010001
[ 83.806720] iwlwifi 0000:02:00.0: CSR_GIO_REG: 0X00080044
[ 83.808653] iwlwifi 0000:02:00.0: CSR_GP_UCODE_REG: 0X00000010
[ 83.810592] iwlwifi 0000:02:00.0: CSR_GP_DRIVER_REG: 0X00000000
[ 83.812535] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP1: 0X00000000
[ 83.814490] iwlwifi 0000:02:00.0: CSR_UCODE_DRV_GP2: 0X00000000
[ 83.816425] iwlwifi 0000:02:00.0: CSR_LED_REG: 0X00000078
[ 83.818360] iwlwifi 0000:02:00.0: CSR_DRAM_INT_TBL_REG: 0X88032ccf
[ 83.820300] iwlwifi 0000:02:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
[ 83.822206] iwlwifi 0000:02:00.0: CSR_ANA_PLL_CFG: 0X00880300
[ 83.824092] iwlwifi 0000:02:00.0: CSR_HW_REV_WA_REG: 0X0001001a
[ 83.825997] iwlwifi 0000:02:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0000
[ 83.827923] iwlwifi 0000:02:00.0: FH register values:
[ 83.829885] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X032d5a00
[ 83.831941] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X0032dbd0
[ 83.834023] iwlwifi 0000:02:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000010
[ 83.836138] iwlwifi 0000:02:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80811104
[ 83.838284] iwlwifi 0000:02:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
[ 83.840464] iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
[ 83.842674] iwlwifi 0000:02:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[ 83.844919] iwlwifi 0000:02:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
[ 83.847190] iwlwifi 0000:02:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
Any ideas?
Edit: changed thread title
Last edited by Minsc (2014-06-19 01:06:15)

d41f3a76dbc185paulinchenk wrote:
Not for me :-(
I have an Intel(R) Centrino(R) Advanced-N 6205 AGN and the only way get it connecting to my WPA2-AES network was downgrading to linux 3.5. But because I have optimus graphics, this means I can no longer use bumblebee, as it depends on 3.6.
Anyone got a hint for a workaround to get both working?
Thanks
Does the 11n_disable workaround work for you?
Just upgraded to 3.6.5, I still have the problem on Centrino Wireless 100 N, with some differences: now it seems to authenticate but with very low speeds and the connection isn't stable. I haven't found out much more, I'll try to get more information during the week. Right now I still use the 11n disabled.
Last edited by pulce (2012-11-04 18:06:38)

Hangs on boot with Logitech wireless keyboard

I am running Windows 7 on a Thinkpad W510 and just bought a Logitech S520 wireless keyboard and mouse.
When I try to boot, the system hangs at the Thinkpad splash screen.
I updated the BIOS to the latest version but it had no effect. I also changed the boot sequence so that USB boot was after HD boot.
This had no effect and the system still hangs on boot.
If I remove the USB receiver the system boots fine and I can then insert the USB receiver and everything works propely.
Is there anything that I am missing? This just doesn't make sense.
Thanks for any further suggestions.

I have the newer port replicator (issued July ?? 2010) and it is always plugged in to USB 2 port. From the port replicator I go to a powered USB hub. In the later I have the transmitter for my Logitech mouse. I have never tried the Logitech transmitter directly in my laptop so can indicate whether that would hang my system and at least right now I'm not interesting in trying it.

Intel wireless display - widi

How do I install/activate the intel widi on my Toshiba Satellite P845t-S4310. The operating system is windows 8
Thanks Carroll

Satellite P845t-S4310
Intel Wireless Display
I've never implemented WiDi, Carroll. I'm just referencing what I read.
Unless your TV has it built-in, you need a PUSH2TV adapter.
How to Connect Laptop to TV with Intel® Wireless Display (WiDi)
-Jerry

Intel wireless chipset clients random Citrix disconnects

Currently using intel 5100 & 6200 client cards on multiple driver versions. WiSM is 7.0.116. APs are 1250 and 1260 series. Citrix is setup to send server-side keepalives for session reliability. Randomly, several times a day the client will get disconnected from the Citrix application session but maintain connectivity to the AP and other applications continue to work. Traces show the server-side keepalive reach the controller but are delayed from controller to client by 5-6 seconds. Just enough time for the Citrix server to timeout and tear down to session. Additional testing shows the delay most likely occurs somewhere from controller to AP. It occurs on multiple controllers on multiple campuses.
We have Dell/Broadcom clients that don't experience the problem. The only commonality seems to be the Intel cards. Any ideas? CCX? I know Intel has a special relationship with Cisco regarding CCX and have developed features not available on other cards. Tried disabling power save and other CCX features but hasn't solved the issue. Any ideas are appreciated on this very strange problem.
Thanks!
Sent from Cisco Technical Support iPhone App

Update to this issue. I've found the 5 second delay actually is occurring on the AP. Packets traverse normally through the entire network but randomly delayed at the AP. TAC is looking at it but no cause found yet. Also verified this seems to occur only with Intel wireless chipsets. Others (Broadcom etc.) don't experience the problem.
Sent from Cisco Technical Support iPhone App

How do i adapt Satellite A660 PSAW9A-02T00F for Intel Wireless Display

How do i adapt my A660 -PSAW9A-02T00F laptop for Intel Wireless Display (WIDI)?
So I can use the new Push2TV Netgear adapter?
*when apparently my model doesn't support it!
Sooooooooooooo not happy.
Surely there must be away to "adapt" the model I have so that it does support it?*
From the Toshiba FAQ section:
How do I connect and use my Intel Wireless Display?
+Please note: The Intel Wireless Display is only supported on the Toshiba Satellite E200/006.
For full product information you may go here. (mind you there's no link to go anywhere)+
Link to FAQ: http://www.mytoshiba.com.au/support/item/411
My computer is not very old yet.... Here I am :(
Please... someone tell me there's a FIX for this!
Cheers
Jodes
Message was edited by: JodieR

Hi
To be honest I never tried to connect my notebook to TV with Intel Wireless Display but I found some informations on Intel page:
http://www.intel.de/content/www/de/de/architecture-and-technology/intel-wireless-display.html
here is a nice HowTo movie created by Intel:
http://communities.intel.com/community/tech/intel_widi
But requirements are:
Core CPU i7-620M, i5-540M, i5-520M, i5-430M, i3-350M and i5-330M
Furthermore you need Intel-HM57-, -HM55-, -QM57- or -QS57- chipset
And preinsatlled Windows 7.
Should check this with your notebook!

W701 Won't boot with USB dongle attached

W701 with current BIOS (6KET46WW v1.12) will hang if there is a USB dongle for a Microsoft Explorer Mouse USB dongle in the upper left USB (2.0) socket on boot. Works fine if you put the USB dongle in the lower USB/eSata socket. Note that the upper socket on this 2541-W1Z is NOT a USB 3.0 port (silver, not blue). Course I don't want to put it in that socket since I like to use that for eSata... Apparently the same problem exists in the W5XX laptops as well, but I don't see a post discussing the issue on the W701.

Have you seen the thread
Hangs on boot with Logitech wireless keyboard
Yours may be a similar problem.
I'm about to get a W701 in a day or 2 and will be in the same situation. I'll check it out and report back when I can.
ThinkPad W701 25002LG, i7 2Ghz,FX 3800M, 4Gb,16GB, SSD 320GB, DVDRW, RGB WUXGA, Wacom, Col Sensor, Fingerprint reader, Mini Dock

Booting with intel-wireless

Similar Messages

Maybe you are looking for