LinuxQuestions.org - [SOLVED] linux 3.1 problem with my wireless card (Intel iw 5100)

- Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)

- - linux 3.1 problem with my wireless card (Intel iw 5100) (https://www.linuxquestions.org/questions/linux-kernel-70/linux-3-1-problem-with-my-wireless-card-intel-iw-5100-a-911448/)

linux 3.1 problem with my wireless card (Intel iw 5100)

I tried to build linux 3.1 on two slackware boxes.
Everything worked ok with the fujitsu laptop that has the 3945 (Intel) card.
But I got a problem with the hp laptop with the wireless Intel 5100.

Code:

cat /etc/slackware-version

Slackware 13.37.0

Below are the results of the command (on the same machine---hp intel 5100)

Code:

dmesg | grep -i iw

After I booted with the newly built kernel 3.1:

Code:

[  12.011875] iwlagn 0000:03:00.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11

[  12.020766] iwlagn 0000:03:00.0: setting latency timer to 64

[  12.020786] iwlagn 0000:03:00.0: pci_resource_len = 0x00002000

[  12.029585] iwlagn 0000:03:00.0: pci_resource_base = f9310000

[  12.038131] iwlagn 0000:03:00.0: HW Revision ID = 0x0

[  12.046427] iwlagn 0000:03:00.0: pci_enable_msi failed

[  12.047666] iwlagn 0000:03:00.0: PCI INT A disabled

[  12.063757] iwlagn: probe of 0000:03:00.0 failed with error -1

With my current kernel (2.6.39.1):

Code:

[  11.738450] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:

[  11.746983] iwlagn: Copyright(c) 2003-2010 Intel Corporation

[  11.755513] iwlagn 0000:03:00.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11

[  11.763934] iwlagn 0000:03:00.0: setting latency timer to 64

[  11.763960] iwlagn 0000:03:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54

[  11.794422] iwlagn 0000:03:00.0: device EEPROM VER=0x11f, CALIB=0x4

[  11.802673] iwlagn 0000:03:00.0: Device SKU: 0Xb

[  11.811999] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels

[  13.125595] iwlagn 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692

[  13.159028] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'

[  344.744824] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 76:d9:ac:11:16:86 tid = 0

[ 1888.334146] iwlagn 0000:03:00.0: Stopping AGG while state not ON or starting

[ 2103.857526] iwlagn 0000:03:00.0: Aggregation not enabled for tid 0 because load = 6

[ 2107.288417] iwlagn 0000:03:00.0: iwlagn_tx_agg_start on ra = 76:d9:ac:11:16:86 tid = 0

I checked the version of the firmware. Looks up to date.
Of course I built the kernel by using

Code:

make oldconfig

...

So far I have no clue. Any idea, anybody?

Thanks

linux-3.0.4+wireless wifi ok

I just built linux-3.0.4 and rebooted on it.
No problem, the card works fine

Code:

# dmesg | grep -i iw

[  10.603787] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:

[  10.612247] iwlagn: Copyright(c) 2003-2011 Intel Corporation

[  10.657903] iwlagn 0000:03:00.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11

[  10.666776] iwlagn 0000:03:00.0: setting latency timer to 64

[  10.732045] iwlagn 0000:03:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54

[  10.795129] iwlagn 0000:03:00.0: device EEPROM VER=0x11f, CALIB=0x4

[  10.803757] iwlagn 0000:03:00.0: Device SKU: 0Xb

[  10.812680] iwlagn 0000:03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels

[  12.487625] iwlagn 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692

[  12.498653] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'

Same problem with linux-3.1 and iwlagn (wifi link 1000). Got it to work after enabling CONFIG_PCI_MSI.

Quote:

Originally Posted by j-kidd (Post 4515681)

Same problem with linux-3.1 and iwlagn (wifi link 1000). Got it to work after enabling CONFIG_PCI_MSI.

???

Code:

$ grep -c CONFIG_PCI_MSI config-3.1.0 

0

Anyway, it works okay with linux-3.0.8 the latest stable kernel.

Quote:

Originally Posted by vonbiber:4516319

Anyway, it works okay with linux-3.0.8 the latest stable kernel.

Is the kernel from slackware repos or from kernel.org ?
Because.as far as i know 3.1 is the latest stable now.

Quote:

Originally Posted by hen770 (Post 4517008)

Is the kernel from slackware repos or from kernel.org ?
Because.as far as i know 3.1 is the latest stable now.

http://www.kernel.org/

says the latest stable is 3.08

That's where I got it

Had the same problem with an Intel 5100 on Slackware64 13.37 - confirming that setting CONFIG_PCI_MSI fixed it for me, thanks :)

Quote:

Originally Posted by vonbiber (Post 4516319)

???

Code:

$ grep -c CONFIG_PCI_MSI config-3.1.0 

0

It wasn't in my .config either, but I enabled it from the menu. "Bus options (PCI etc.) --> Message Signaled Interrupts (MSI and MSI-X)"

Sometimes the settings at the .config are diefferent from what you see in the menus.
@CTM - what kernel are using?

I got bit by this when upgrading my wife's laptop from 2.6.38 to 3.1.0 today (this was on Gentoo). I believe it's due to choosing to enable th new IOMMU options during "make oldconfig". I ended going back into "make menuconfig" and correcting it by choosing PCI_MSI as recommended above and that fixed my issue.

Quote:

Originally Posted by CTM (Post 4518669)

setting CONFIG_PCI_MSI fixed it for me, thanks :)

It wasn't in my .config either, but I enabled it from the menu. "Bus options (PCI etc.) --> Message Signaled Interrupts (MSI and MSI-X)"

I didn't see it.
Here's a screenshot of my menuconfig:
http://www.mypicx.com/11112011/menuconfig-3.1/

ok, yesterday I did the following.
Building linux-3.1.1

Code:

make oldconfig

I didn't see where 'CONFIG_ARCH_SUPPORTS_MSI' is in the menuconfig but I did
see it in the .config file. I enabled it:

Code:

sed -i 's?# CONFIG_ARCH_SUPPORTS_MSI is not set?CONFIG_ARCH_SUPPORTS_MSI=y?' .config

Then I ran menuconfig and enabled the following

Code:

Processor type and features -->[*] Local APIC support on uniprocessors[*] IO-APIC support on uniprocessors

Code:

Bus options (PCI, etc.) -->[*] Message Signaled Interrupts (MSI and MSI-X)

(yes, this time it did appear)

I built and installed this kernel and rebooted and this time everything worked fine.

Thanks for the info on MSI. I wouldn't have known where to look.