Intel Centrino Wireless-N 1000 can't connect to AP
乔楚
honestqiao at gmail.com
Wed Dec 18 08:17:58 UTC 2013
Will I need to tie debug?
Not wifi, laptop use is indeed very painful
2013/12/11 Adrian Chadd <adrian at freebsd.org>
> OK, I'll see if my centrino 1xx / 1xxx units match yours and are
> problematic.
>
> Please file a PR!
>
>
> -a
>
> On 7 December 2013 05:34, 乔楚 <honestqiao at gmail.com> wrote:
> > Today ,I upgrade my freebsd from 10-beta4 to current.
> > Now, my freebsd can't connect to wireless AP. Wireless LAN strike.
> >
> > iwn0 in /var/log/message:
> > Dec 7 08:02:00 x201i kernel: iwn0: <Intel Centrino Wireless-N 1000> mem
> > 0xf2400000-0xf2401fff irq 16 at device 0.0 on pci2
> >
> > Dec 7 08:02:00 x201i kernel: iwn0: attempting to allocate 1 MSI vectors
> (1
> > supported)
> > Dec 7 08:02:00 x201i kernel: msi: routing MSI IRQ 266 to local APIC 0
> > vector 62
> > Dec 7 08:02:00 x201i kernel: iwn0: using IRQ 266 for MSI
> > Dec 7 08:02:00 x201i kernel: iwn0: MIMO 1T2R, BGS, address
> > 8c:a9:82:5a:41:58
> > Dec 7 08:02:00 x201i kernel: iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> > Dec 7 08:02:00 x201i kernel: iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> > 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
> > Dec 7 08:02:00 x201i kernel: iwn0: 1T2R
> > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz
> > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 6.5Mbps - 65Mbps
> > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz SGI
> > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 7Mbps - 72Mbps
> > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz:
> > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 13.5Mbps - 135Mbps
> > Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz SGI:
> > Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 15Mbps - 150Mbps
> > ......
> > Dec 7 08:02:00 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:16
> > Dec 7 08:02:00 x201i kernel: iwn0: iwn_intr: fatal firmware error
> > Dec 7 08:02:00 x201i kernel: firmware error log:
> > Dec 7 08:02:00 x201i kernel: error type = "SYSASSERT" (0x00000005)
> > Dec 7 08:02:00 x201i kernel: program counter = 0x00018DBC
> > Dec 7 08:02:00 x201i kernel: source line = 0x00000032
> > Dec 7 08:02:00 x201i kernel: error data = 0x0000000100000000
> > Dec 7 08:02:00 x201i kernel: branch link = 0x00018D6E00018D6E
> > Dec 7 08:02:00 x201i kernel: interrupt link = 0x0000082600000000
> > Dec 7 08:02:00 x201i kernel: time = 1538064582
> > Dec 7 08:02:00 x201i kernel: driver status:
> > Dec 7 08:02:00 x201i kernel: tx ring 0: qid=0 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 1: qid=1 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 2: qid=2 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 3: qid=3 cur=2 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 4: qid=4 cur=57 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 5: qid=5 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 6: qid=6 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 7: qid=7 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 8: qid=8 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 9: qid=9 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 10: qid=10 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 11: qid=11 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 12: qid=12 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 13: qid=13 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 14: qid=14 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 15: qid=15 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 16: qid=16 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 17: qid=17 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 18: qid=18 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: tx ring 19: qid=19 cur=0 queued=0--
> > Dec 7 08:02:00 x201i kernel: rx ring: cur=29
> > ......
> > Dec 7 08:02:01 x201i wpa_supplicant[667]: ioctl[SIOCS80211, op=103,
> val=0,
> > arg_len=128]: Device not configured
> > Dec 7 08:02:01 x201i wpa_supplicant[667]: wlan0: Failed to initiate AP
> scan
> >
> > I do not know where the problem is?
> > If necessary, I can tie debugging.
> > _______________________________________________
> > freebsd-current at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscribe at freebsd.org"
>
More information about the freebsd-current
mailing list