Int. WiFi and 3G

English Network/Internet
#1

My WiFi has started to play-up.
I can sometimes connect, but it only lasts for a short time, other times I can’t connect at all. I have noticed that the KDE WiFi widget will have the red “slashed” circle symbol and every couple of seconds flash to the red X symbol.
I have uninstalled the plasmoid and installed the networkmanager, but I can still only connect very rarely. I’m also having trouble with my 3G modem, but that might be a different problem.
The only thing I can that happened between working wifi and not is a kernel security patch. But, with my track record, it could have been me.
I have also tried connecting with the traditional method, but that’s not connecting either for some reason.
/sbin/lspci -n

06:00.0 Network controller: Intel Corporation WiFi Link 5100
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

06:00.0 0280: 8086:4232
07:00.0 0200: 10ec:8168 (rev 02)

dmesg | less

  9.761448] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d
    9.761453] iwlagn: Copyright(c) 2003-2010 Intel Corporation
    9.761613] iwlagn 0000:06:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    9.761652] iwlagn 0000:06:00.0: setting latency timer to 64
    9.761786] iwlagn 0000:06:00.0: Detected Intel(R) WiFi Link 5100 AGN, REV=0x54
    9.790427] iwlagn 0000:06:00.0: device EEPROM VER=0x11f, CALIB=0x4
    9.790454] iwlagn 0000:06:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    9.790643] iwlagn 0000:06:00.0: irq 51 for MSI/MSI-X
   10.136539] iwlagn 0000:06:00.0: loaded firmware version 8.24.2.12

  102.824196] wlan0: authenticate with c6:64:c7:a7:0b:e9 (try 1)
  102.826586] wlan0: authenticated
  102.826638] wlan0: associate with c6:64:c7:a7:0b:e9 (try 1)
  102.829061] wlan0: RX AssocResp from c6:64:c7:a7:0b:e9 (capab=0x431 status=0 aid=1)
  102.829065] wlan0: associated

  391.712054] iwlagn 0000:06:00.0: Microcode SW error detected.  Restarting 0x92000000.
  391.712058] iwlagn 0000:06:00.0: Loaded firmware version: 8.24.2.12
  391.712077] iwlagn 0000:06:00.0: Start IWL Error Log Dump:
  391.712080] iwlagn 0000:06:00.0: Status: 0x000312E4, count: 5
  391.712254] iwlagn 0000:06:00.0: Desc                                  Time       data1      data2      line
  391.712258] iwlagn 0000:06:00.0: NMI_INTERRUPT_WDG            (0x0004) 0323706277 0x00000002 0x02030000 294
  391.712260] iwlagn 0000:06:00.0: pc      blink1  blink2  ilink1  ilink2  hcmd
  391.712263] iwlagn 0000:06:00.0: 0x006E4 0x005AA 0x006E8 0x008B2 0x022CA 0x223001C
  391.712266] iwlagn 0000:06:00.0: CSR values:
  391.712268] iwlagn 0000:06:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
  391.712294] iwlagn 0000:06:00.0:        CSR_HW_IF_CONFIG_REG: 0X00480303
  391.712306] iwlagn 0000:06:00.0:          CSR_INT_COALESCING: 0X0000ff40
  391.712317] iwlagn 0000:06:00.0:                     CSR_INT: 0X80000000
  391.712328] iwlagn 0000:06:00.0:                CSR_INT_MASK: 0X00000000
  391.712339] iwlagn 0000:06:00.0:           CSR_FH_INT_STATUS: 0X40010000
  391.712350] iwlagn 0000:06:00.0:                 CSR_GPIO_IN: 0X00000000
  391.712360] iwlagn 0000:06:00.0:                   CSR_RESET: 0X00000000
  391.712370] iwlagn 0000:06:00.0:                CSR_GP_CNTRL: 0X080403c5
  391.712382] iwlagn 0000:06:00.0:                  CSR_HW_REV: 0X00000054
  391.712393] iwlagn 0000:06:00.0:              CSR_EEPROM_REG: 0X00000000
  391.712404] iwlagn 0000:06:00.0:               CSR_EEPROM_GP: 0X90000004
  391.712416] iwlagn 0000:06:00.0:              CSR_OTP_GP_REG: 0X00060000
  391.712426] iwlagn 0000:06:00.0:                 CSR_GIO_REG: 0X00080042
  391.712438] iwlagn 0000:06:00.0:            CSR_GP_UCODE_REG: 0X0000a7b3
  391.712449] iwlagn 0000:06:00.0:           CSR_GP_DRIVER_REG: 0X00000000
  391.712461] iwlagn 0000:06:00.0:           CSR_UCODE_DRV_GP1: 0X00000000
  391.712472] iwlagn 0000:06:00.0:           CSR_UCODE_DRV_GP2: 0X00000000
  391.712483] iwlagn 0000:06:00.0:                 CSR_LED_REG: 0X00000058
  391.712495] iwlagn 0000:06:00.0:        CSR_DRAM_INT_TBL_REG: 0X8813715e
  391.712506] iwlagn 0000:06:00.0:        CSR_GIO_CHICKEN_BITS: 0X27800200
  391.712518] iwlagn 0000:06:00.0:             CSR_ANA_PLL_CFG: 0X00880300
  391.712529] iwlagn 0000:06:00.0:           CSR_HW_REV_WA_REG: 0X0001001a
  391.712540] iwlagn 0000:06:00.0:        CSR_DBG_HPET_MEM_REG: 0Xffff0000
  391.712542] iwlagn 0000:06:00.0: FH register values:
  391.712576] iwlagn 0000:06:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X13730600
  391.712604] iwlagn 0000:06:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X01344ff0
  391.712626] iwlagn 0000:06:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X00000080
  391.712648] iwlagn 0000:06:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
  391.712670] iwlagn 0000:06:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
  391.712703] iwlagn 0000:06:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
  391.712730] iwlagn 0000:06:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
  391.712757] iwlagn 0000:06:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0001
  391.712779] iwlagn 0000:06:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000
  391.712848] iwlagn 0000:06:00.0: Start IWL Event Log Dump: display last 20 entries
  391.712875] iwlagn 0000:06:00.0: EVT_LOGT:0363574045:0x00000000:1352
  391.712893] iwlagn 0000:06:00.0: EVT_LOGT:0363574046:0x00000002:1353
  391.712912] iwlagn 0000:06:00.0: EVT_LOGT:0363574093:0x000000d4:0322
  391.712936] iwlagn 0000:06:00.0: EVT_LOGT:0363574122:0x00656a5f:0310
  391.712954] iwlagn 0000:06:00.0: EVT_LOGT:0363583760:0x0000010f:0106
  391.712973] iwlagn 0000:06:00.0: EVT_LOGT:0363583761:0x00000000:0302
  391.712986] iwlagn 0000:06:00.0: EVT_LOGT:0363583794:0x00000000:1350
  391.713005] iwlagn 0000:06:00.0: EVT_LOGT:0363583795:0x00000000:1351
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363583795:0x00000000:1352
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363583795:0x00000002:1353
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584010:0x000000d4:0322
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584040:0x00656a5f:0310
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584214:0x0000010f:0106
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584215:0x00000000:0302
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584249:0x00000000:1350
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584250:0x00000000:1351
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584250:0x00000000:1352
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363584250:0x00000002:1353
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363784206:0x000000d7:0123
  391.713007] iwlagn 0000:06:00.0: EVT_LOGT:0363784214:0x00000000:0125
  391.713284] iwlagn 0000:06:00.0: Command POWER_TABLE_CMD failed: FW Error
  391.713288] iwlagn 0000:06:00.0: set power fail, ret = -5

 1004.029682] wlan0: deauthenticating from c6:64:c7:a7:0b:e9 by local choice (reason=3)

 1004.029682] wlan0: deauthenticating from c6:64:c7:a7:0b:e9 by local choice (reason=3)
 1004.039179] cfg80211: Calling CRDA to update world regulatory domain
 1004.043576] bridge-wlan0: disabling the bridge
 1004.046036] bridge-wlan0: down
 1004.046044] bridge-wlan0: detached
 1004.046111] /dev/vmnet: open called by PID 1752 (vmnet-bridge)
 1004.046121] /dev/vmnet: hub 0 does not exist, allocating memory.
 1004.046141] /dev/vmnet: port on hub 0 successfully opened
 1004.046152] bridge-wlan0: device is wireless, enabling SMAC
 1004.046155] bridge-wlan0: up
 1004.046160] bridge-wlan0: attached

 1005.989694] bridge-wlan0: disabling the bridge
 1005.992286] bridge-wlan0: down
 1005.992295] bridge-wlan0: detached
 1066.977743] wlan0: authenticate with c6:64:c7:a7:0b:e9 (try 1)
 1066.980262] wlan0: authenticated
 1066.980300] wlan0: associate with c6:64:c7:a7:0b:e9 (try 1)
 1066.982815] wlan0: RX AssocResp from c6:64:c7:a7:0b:e9 (capab=0x431 status=0 aid=1)
 1066.982820] wlan0: associated
 1067.987691] bridge-wlan0: device is wireless, enabling SMAC
 1067.987695] bridge-wlan0: up
 1067.987698] bridge-wlan0: attached
 1492.978402] wlan0: deauthenticating from c6:64:c7:a7:0b:e9 by local choice (reason=3)

 1493.000600] bridge-wlan0: disabling the bridge
 1493.003033] bridge-wlan0: down
 1493.003041] bridge-wlan0: detached
 1493.003180] /dev/vmnet: open called by PID 1752 (vmnet-bridge)
 1493.003190] /dev/vmnet: hub 0 does not exist, allocating memory.
 1493.003210] /dev/vmnet: port on hub 0 successfully opened
 1493.003219] bridge-wlan0: device is wireless, enabling SMAC
 1493.003223] bridge-wlan0: up
 1493.003228] bridge-wlan0: attached
 1494.863173] bridge-wlan0: disabling the bridge
 1494.866855] bridge-wlan0: down
 1494.866863] bridge-wlan0: detached
 1786.382623] ADDRCONF(NETDEV_UP): wlan0: link is not ready
 1852.292209] iwlagn 0000:06:00.0: RF_KILL bit toggled to disable radio.
 1852.293485] iwlagn 0000:06:00.0: Not sending command - RF KILL
 1852.293490] iwlagn 0000:06:00.0: Error sending REPLY_RXON_TIMING: enqueue_hcmd failed: -5
 1852.293493] iwlagn 0000:06:00.0: Error setting RXON timing!
 1852.303023] iwlagn 0000:06:00.0: Not sending command - RF KILL
 1852.303028] iwlagn 0000:06:00.0: Error sending REPLY_RXON_TIMING: enqueue_hcmd failed: -5
 1852.303030] iwlagn 0000:06:00.0: Error setting RXON timing!
 1854.633230] iwlagn 0000:06:00.0: RF_KILL bit toggled to enable radio.

/usr/sbin/iwconfig

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:off/any  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
vmnet1    no wireless extensions.

vmnet8    no wireless extensions.

Is this any help?
Thanks

#2

You should report that microcode error on the mailing list
linux-wireless@vger.kernel.org. I know that the Intel group has recently
published new firmware, but I have no Intel devices and do not keep up with the
details.

#3

Ok I will do that. What other info should I give them?
Can I just email them the above information?

#4

On 05/04/2011 03:36 PM, asarge wrote:
>
> Ok I will do that. What other info should I give them?
> Can I just email them the above information?

The stuff in your first posting plus the output of uname -r. They won’t know
that you are using openSUSE so they need to know the kernel version. I am
assuming that your driver is the standard one, not one from compat-wireless.

#5

Could it be that the
Intel® WiFi Link 5100
devices have all the same numeric ID
8086:4232
(apart from the subsystems)
but that there are although technical differences
(especially if it comes to 802.11 Draft-N)?

See:

Products Available
…]
512AN_MMW (supports 802.11a/b/g/Draft-N1 in a PCIe Mini Card form factor)
512AG_MMW (supports 802.11a/b/g in a PCIe Mini Card form factor)
512AN_HMW (supports 802.11a/b/g/Draft-N1 in in a PCIe Half Mini Card form factor)
512AG_HMW (supports 802.11a/b/g in in a PCIe Half Mini Card form factor)

and

Subsystems
…]
8086 1201 WiFi Link 5100 AGN
8086 1204 WiFi Link 5100 AGN
8086 1205 WiFi Link 5100 BGN
8086 1206 WiFi Link 5100 ABG
8086 1216
8086 1221 WiFi Link 5100 AGN
8086 1224 WiFi Link 5100 AGN
8086 1225 WiFi Link 5100 BGN
8086 1226 WiFi Link 5100 ABG
8086 1301 WiFi Link 5100 AGN
8086 1304 WiFi Link 5100 AGN
8086 1305 WiFi Link 5100 BGN
8086 1306 WiFi Link 5100 ABG
8086 1321 WiFi Link 5100 AGN
8086 1324 WiFi Link 5100 AGN
8086 1325 WiFi Link 5100 BGN
8086 1326 WiFi Link 5100 ABG

If so it may make sense to add to the bugreport also data that includes also the ID of the subsystem like according paragraph of the output of

/sbin/lspci -nnk

or of

/sbin/lspci -nnk | grep -A2 -i net

?

Just my amateurish guessing…

Regards
Martin
(pistazienfresser)

#6

I am using the standard drivers as far as I know.
Its odd that it can sometimes work for a short amount of time. Last night I had the best run out of it for a few days. It conneced for about 15min. Then I was unable to connect again.
Are we leaning towards the kernel update or excessive user headspace (me) being the problem?

#7

I am using the standard drivers as far as I know.
Its odd that it can sometimes work for a short amount of time. Last night I had the best run out of it for a few days. It conneced for about 15min. Then I was unable to connect again.
Are we leaning towards the kernel update or excessive user headspace (me) being the problem?