Date: Wed, 29 Mar 2017 22:59:50 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Pete Wright <pete@nomadlogic.org> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: iwm Intel 3165 Message-ID: <CAJ-Vmo=5K09J=Ur930LR9vLbauiX70CwyM=k5mZngJ=LJTObzA@mail.gmail.com> In-Reply-To: <5b648cbd-c546-aa14-f69a-d08c9973c1d2@nomadlogic.org> References: <5b648cbd-c546-aa14-f69a-d08c9973c1d2@nomadlogic.org>
next in thread | previous in thread | raw e-mail | index | archive | help
hi! Just don't load it in /boot/loader.conf . That's still buggy. -a On 29 March 2017 at 20:14, Pete Wright <pete@nomadlogic.org> wrote: > Hi there, > > I have a new laptop with the following Intel wireless chipset that seems to > be having problems getting enabled: > > iwm0@pci0:1:0:0: class=0x028000 card=0x44108086 chip=0x31658086 > rev=0x79 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Wireless 3165' > class = network > > I have the following configured in my loader.conf: > > if_iwm_load="YES" > iwm3160fw_load="YES" > iwm7260fw_load="YES" > iwm7265fw_load="YES" > iwm8000Cfw_load="YES" > > I have seen the following error on both the latest 12-CURRENT snapshot as > well as the drm-next branch that work is being done on to support newer > Intel graphics and can reproduce on both code bases. Here is what I'm > seeing in the dmesg buffer: > > iwm0: <Intel(R) Dual Band Wireless AC 3165> mem 0xd1000000-0xd1001fff at > device 0.0 on pci1 > iwm7265Dfw: root not mounted yet, no way to load image > iwm0: could not read firmware iwm7265Dfw (error 0) > iwm0: dumping device error log > iwm0: Invalid error log pointer 0x00000000 > iwm0: driver status: > iwm0: tx ring 0: qid=0 cur=0 queued=0 > iwm0: tx ring 1: qid=1 cur=0 queued=0 > iwm0: tx ring 2: qid=2 cur=0 queued=0 > iwm0: tx ring 3: qid=3 cur=0 queued=0 > uhub0: iwm0: tx ring 4: qid=4 cur=0 queued=0 > iwm0: tx ring 5: qid=5 cur=0 queued=0 > iwm0: tx ring 6: qid=6 cur=0 queued=0 > iwm0: tx ring 7: qid=7 cur=0 queued=0 > iwm0: tx ring 8: qid=8 cur=0 queued=0 > iwm0: tx ring 9: qid=9 cur=0 queued=0 > iwm0: tx ring 10: qid=10 cur=0 queued=0 > iwm0: tx ring 11: qid=11 cur=0 queued=0 > iwm0: tx ring 12: qid=12 cur=0 queued=0 > iwm0: tx ring 13: qid=13 cur=0 queued=0 > iwm0: tx ring 14: qid=14 cur=0 queued=0 > iwm0: tx ring 15: qid=15 cur=0 queued=0 > iwm0: tx ring 16: qid=16 cur=0 queued=0 > iwm0: tx ring 17: qid=17 cur=0 queued=0 > iwm0: tx ring 18: qid=18 cur=0 queued=0 > iwm0: tx ring 19: qid=19 cur=0 queued=0 > iwm0: tx ring 20: qid=20 cur=0 queued=0 > iwm0: tx ring 21: qid=21 cur=0 queued=0 > iwm0: tx ring 22: qid=22 cur=0 queued=0 > iwm0: tx ring 23: qid=23 cur=0 queued=0 > iwm0: tx ring 24: qid=24 cur=0 queued=0 > iwm0: tx ring 25: qid=25 cur=0 queued=0 > iwm0: tx ring 26: qid=26 cur=0 queued=0 > iwm0: tx ring 27: qid=27 cur=0 queued=0 > iwm0: tx ring 28: qid=28 cur=0 queued=0 > iwm0: tx ring 29: qid=29 cur=0 queued=0 > iwm0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > iwm0: rx ring: cur=0 > iwm0: 802.11 state -1 > iwm_intr: null vap > iwm0: Failed to start INIT ucode: 35 > > When i try to configure the device the netif rc script errors out stating > the device doesn't exist. > > Let me know if any additional debugging info would be helpful, and if this > is a real issue I am def willing to help test patches etc. > > Cheers! > -pete > > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=5K09J=Ur930LR9vLbauiX70CwyM=k5mZngJ=LJTObzA>