* Need support for Intel new wifi module 9462NGW @ 2017-10-31 4:13 Chris Chiu 2017-10-31 7:25 ` Luca Coelho 0 siblings, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-10-31 4:13 UTC (permalink / raw) To: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi, We just have the Intel new WiFi module 9462NGW from Acer and tried to verify if it works on the latest linux kernel. Unfortunately it seems not even detected because the PCI ID seems unknown to the iwlwifi driver. Then I add the following line to drivers/net/wireless/intel/iwlwifi/pcie/drv.c iwl_hw_card_ids {IWL_PCI_DEVICE(0x31DC, 0x02A4, iwl9460_2ac_cfg)}, dmesg shows the following [ 12.994422] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9260-th-b0-jf-b0-33.ucode failed with error -2 [ 12.994442] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9260-th-b0-jf-b0-32.ucode failed with error -2 [ 12.994456] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9260-th-b0-jf-b0-31.ucode failed with error -2 [ 12.994470] iwlwifi 0000:00:0c.0: Direct firmware load for iwlwifi-9260-th-b0-jf-b0-30.ucode failed with error -2 [ 12.994473] iwlwifi 0000:00:0c.0: no suitable firmware found! [ 12.994477] iwlwifi 0000:00:0c.0: minimum version required: iwlwifi-9260-th-b0-jf-b0-30 [ 12.994479] iwlwifi 0000:00:0c.0: maximum version supported: iwlwifi-9260-th-b0-jf-b0-33 I'm not able to find these missing files in linux-firmware.git and any other possible place. What's the status of supporting this 9462NGW? Please let me know if any more information required. Thanks Chris ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-10-31 4:13 Need support for Intel new wifi module 9462NGW Chris Chiu @ 2017-10-31 7:25 ` Luca Coelho 2017-10-31 7:29 ` Chris Chiu 2017-11-06 3:22 ` Chris Chiu 0 siblings, 2 replies; 23+ messages in thread From: Luca Coelho @ 2017-10-31 7:25 UTC (permalink / raw) To: Chris Chiu, johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Tue, 2017-10-31 at 12:13 +0800, Chris Chiu wrote: > Hi, Hi Chris, > We just have the Intel new WiFi module 9462NGW from Acer and > tried > to verify if it works on the latest linux kernel. Unfortunately it > seems not even detected because the PCI ID seems unknown to the > iwlwifi driver. Then I add the following line to > drivers/net/wireless/intel/iwlwifi/pcie/drv.c > iwl_hw_card_ids > {IWL_PCI_DEVICE(0x31DC, 0x02A4, iwl9460_2ac_cfg)}, > > dmesg shows the following > > [ 12.994422] iwlwifi 0000:00:0c.0: Direct firmware load for > iwlwifi-9260-th-b0-jf-b0-33.ucode failed with error -2 > [ 12.994442] iwlwifi 0000:00:0c.0: Direct firmware load for > iwlwifi-9260-th-b0-jf-b0-32.ucode failed with error -2 > [ 12.994456] iwlwifi 0000:00:0c.0: Direct firmware load for > iwlwifi-9260-th-b0-jf-b0-31.ucode failed with error -2 > [ 12.994470] iwlwifi 0000:00:0c.0: Direct firmware load for > iwlwifi-9260-th-b0-jf-b0-30.ucode failed with error -2 > [ 12.994473] iwlwifi 0000:00:0c.0: no suitable firmware found! > [ 12.994477] iwlwifi 0000:00:0c.0: minimum version required: > iwlwifi-9260-th-b0-jf-b0-30 > [ 12.994479] iwlwifi 0000:00:0c.0: maximum version supported: > iwlwifi-9260-th-b0-jf-b0-33 > > > > I'm not able to find these missing files in linux-firmware.git and > any > other possible place. What's the status of supporting this 9462NGW? > Please let me know if any more information required. Thanks Unfortunately we have not published the firmware for this NIC yet. I'll try to get an approval to publish it today (or latest by the end of the week) and I'll let you know. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-10-31 7:25 ` Luca Coelho @ 2017-10-31 7:29 ` Chris Chiu 2017-11-06 3:22 ` Chris Chiu 1 sibling, 0 replies; 23+ messages in thread From: Chris Chiu @ 2017-10-31 7:29 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Great. Thanks. On Tue, Oct 31, 2017 at 3:25 PM, Luca Coelho <luca@coelho.fi> wrote: > On Tue, 2017-10-31 at 12:13 +0800, Chris Chiu wrote: >> Hi, > > Hi Chris, > > >> We just have the Intel new WiFi module 9462NGW from Acer and >> tried >> to verify if it works on the latest linux kernel. Unfortunately it >> seems not even detected because the PCI ID seems unknown to the >> iwlwifi driver. Then I add the following line to >> drivers/net/wireless/intel/iwlwifi/pcie/drv.c >> iwl_hw_card_ids >> {IWL_PCI_DEVICE(0x31DC, 0x02A4, iwl9460_2ac_cfg)}, >> >> dmesg shows the following >> >> [ 12.994422] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-33.ucode failed with error -2 >> [ 12.994442] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-32.ucode failed with error -2 >> [ 12.994456] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-31.ucode failed with error -2 >> [ 12.994470] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-30.ucode failed with error -2 >> [ 12.994473] iwlwifi 0000:00:0c.0: no suitable firmware found! >> [ 12.994477] iwlwifi 0000:00:0c.0: minimum version required: >> iwlwifi-9260-th-b0-jf-b0-30 >> [ 12.994479] iwlwifi 0000:00:0c.0: maximum version supported: >> iwlwifi-9260-th-b0-jf-b0-33 >> >> >> >> I'm not able to find these missing files in linux-firmware.git and >> any >> other possible place. What's the status of supporting this 9462NGW? >> Please let me know if any more information required. Thanks > > Unfortunately we have not published the firmware for this NIC yet. > I'll try to get an approval to publish it today (or latest by the end > of the week) and I'll let you know. > > -- > Cheers, > Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-10-31 7:25 ` Luca Coelho 2017-10-31 7:29 ` Chris Chiu @ 2017-11-06 3:22 ` Chris Chiu 2017-11-06 7:22 ` Luca Coelho 1 sibling, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-11-06 3:22 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Luca, Any update for the firmware approval? Chris On Tue, Oct 31, 2017 at 3:25 PM, Luca Coelho <luca@coelho.fi> wrote: > On Tue, 2017-10-31 at 12:13 +0800, Chris Chiu wrote: >> Hi, > > Hi Chris, > > >> We just have the Intel new WiFi module 9462NGW from Acer and >> tried >> to verify if it works on the latest linux kernel. Unfortunately it >> seems not even detected because the PCI ID seems unknown to the >> iwlwifi driver. Then I add the following line to >> drivers/net/wireless/intel/iwlwifi/pcie/drv.c >> iwl_hw_card_ids >> {IWL_PCI_DEVICE(0x31DC, 0x02A4, iwl9460_2ac_cfg)}, >> >> dmesg shows the following >> >> [ 12.994422] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-33.ucode failed with error -2 >> [ 12.994442] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-32.ucode failed with error -2 >> [ 12.994456] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-31.ucode failed with error -2 >> [ 12.994470] iwlwifi 0000:00:0c.0: Direct firmware load for >> iwlwifi-9260-th-b0-jf-b0-30.ucode failed with error -2 >> [ 12.994473] iwlwifi 0000:00:0c.0: no suitable firmware found! >> [ 12.994477] iwlwifi 0000:00:0c.0: minimum version required: >> iwlwifi-9260-th-b0-jf-b0-30 >> [ 12.994479] iwlwifi 0000:00:0c.0: maximum version supported: >> iwlwifi-9260-th-b0-jf-b0-33 >> >> >> >> I'm not able to find these missing files in linux-firmware.git and >> any >> other possible place. What's the status of supporting this 9462NGW? >> Please let me know if any more information required. Thanks > > Unfortunately we have not published the firmware for this NIC yet. > I'll try to get an approval to publish it today (or latest by the end > of the week) and I'll let you know. > > -- > Cheers, > Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-06 3:22 ` Chris Chiu @ 2017-11-06 7:22 ` Luca Coelho 2017-11-07 4:26 ` Chris Chiu 0 siblings, 1 reply; 23+ messages in thread From: Luca Coelho @ 2017-11-06 7:22 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Mon, 2017-11-06 at 11:22 +0800, Chris Chiu wrote: > Hi Luca, Hi Chris, > Any update for the firmware approval? Yes, I published it last Thursday. Sorry, I was in such a hurry that I forgot to tell you about it. You can find it here: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-9260-th-b0-jf-b0-33.ucode?id=f132386b542b52ade0416ecb6cb7aef426f5d175 Let me know how it goes. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-06 7:22 ` Luca Coelho @ 2017-11-07 4:26 ` Chris Chiu 2017-11-09 3:11 ` Chris Chiu 0 siblings, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-11-07 4:26 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Luca, I just tried the firmware but seems still something wrong. dmesg shows me the following [ 17.786041] Intel(R) Wireless WiFi driver for Linux [ 17.786042] Copyright(c) 2003- 2015 Intel Corporation [ 18.120052] iwlwifi 0000:00:0c.0: loaded firmware version 33.610294.0 op_mode iwlmvm [ 20.995731] iwlwifi 0000:00:0c.0: Detected Intel(R) Dual Band Wireless AC 9460, REV=0x318 [ 22.012109] iwlwifi 0000:00:0c.0: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x2339 [ 22.012115] iwlwifi 0000:00:0c.0: Failed to start INIT ucode: -110 [ 22.024100] iwlwifi 0000:00:0c.0: Failed to run INIT ucode: -110 Any more information you need from me? Chris On Mon, Nov 6, 2017 at 3:22 PM, Luca Coelho <luca@coelho.fi> wrote: > On Mon, 2017-11-06 at 11:22 +0800, Chris Chiu wrote: >> Hi Luca, > > Hi Chris, > > >> Any update for the firmware approval? > > Yes, I published it last Thursday. Sorry, I was in such a hurry that I > forgot to tell you about it. > > You can find it here: > > https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-9260-th-b0-jf-b0-33.ucode?id=f132386b542b52ade0416ecb6cb7aef426f5d175 > > Let me know how it goes. > > -- > Cheers, > Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-07 4:26 ` Chris Chiu @ 2017-11-09 3:11 ` Chris Chiu 2017-11-09 6:29 ` Luca Coelho 2017-11-16 9:49 ` Luca Coelho 0 siblings, 2 replies; 23+ messages in thread From: Chris Chiu @ 2017-11-09 3:11 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Luca, Any suggestion for the "Failed to start INIT ucode: -110" issue for the firmware? Chris On Tue, Nov 7, 2017 at 12:26 PM, Chris Chiu <chiu@endlessm.com> wrote: > Hi Luca, > I just tried the firmware but seems still something wrong. dmesg > shows me the following > > [ 17.786041] Intel(R) Wireless WiFi driver for Linux > [ 17.786042] Copyright(c) 2003- 2015 Intel Corporation > [ 18.120052] iwlwifi 0000:00:0c.0: loaded firmware version > 33.610294.0 op_mode iwlmvm > [ 20.995731] iwlwifi 0000:00:0c.0: Detected Intel(R) Dual Band > Wireless AC 9460, REV=0x318 > [ 22.012109] iwlwifi 0000:00:0c.0: SecBoot CPU1 Status: 0x3, CPU2 > Status: 0x2339 > [ 22.012115] iwlwifi 0000:00:0c.0: Failed to start INIT ucode: -110 > [ 22.024100] iwlwifi 0000:00:0c.0: Failed to run INIT ucode: -110 > > Any more information you need from me? > > Chris > > On Mon, Nov 6, 2017 at 3:22 PM, Luca Coelho <luca@coelho.fi> wrote: >> On Mon, 2017-11-06 at 11:22 +0800, Chris Chiu wrote: >>> Hi Luca, >> >> Hi Chris, >> >> >>> Any update for the firmware approval? >> >> Yes, I published it last Thursday. Sorry, I was in such a hurry that I >> forgot to tell you about it. >> >> You can find it here: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/plain/iwlwifi-9260-th-b0-jf-b0-33.ucode?id=f132386b542b52ade0416ecb6cb7aef426f5d175 >> >> Let me know how it goes. >> >> -- >> Cheers, >> Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-09 3:11 ` Chris Chiu @ 2017-11-09 6:29 ` Luca Coelho 2017-11-16 9:49 ` Luca Coelho 1 sibling, 0 replies; 23+ messages in thread From: Luca Coelho @ 2017-11-09 6:29 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Chris, On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: > Hi Luca, > Any suggestion for the "Failed to start INIT ucode: -110" issue > for the firmware? We are investigating this now. This seems to be related to the secure boot key not being valid... I'll let you know when we progress on this. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-09 3:11 ` Chris Chiu 2017-11-09 6:29 ` Luca Coelho @ 2017-11-16 9:49 ` Luca Coelho 2017-11-17 6:39 ` Chris Chiu 1 sibling, 1 reply; 23+ messages in thread From: Luca Coelho @ 2017-11-16 9:49 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Chris, On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: > Hi Luca, > Any suggestion for the "Failed to start INIT ucode: -110" issue > for the firmware? There were a few problems which should now be fixed. We published new firmwares in our linux-firmware.git tree[1] and also made some fixes in the driver[2]. Please update your system accordingly and let me know if it works for you. Thanks! [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/ [2] https://patchwork.kernel.org/patch/10059871/ https://patchwork.kernel.org/patch/10059875/ https://patchwork.kernel.org/patch/10059873/ -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-16 9:49 ` Luca Coelho @ 2017-11-17 6:39 ` Chris Chiu 2017-11-17 6:46 ` Luca Coelho 0 siblings, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-11-17 6:39 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> wrote: > Hi Chris, > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >> Hi Luca, >> Any suggestion for the "Failed to start INIT ucode: -110" issue >> for the firmware? > > There were a few problems which should now be fixed. We published new > firmwares in our linux-firmware.git tree[1] and also made some fixes in > the driver[2]. Please update your system accordingly and let me know > if it works for you. > > Thanks! > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/ > [2] https://patchwork.kernel.org/patch/10059871/ > https://patchwork.kernel.org/patch/10059875/ > https://patchwork.kernel.org/patch/10059873/ > > -- > Cheers, > Luca. Hi Luca, Thanks for your patch and updated firmware. The driver can initialize w/o error now. However, it always fails on ip-config after 4-way handshake complete. I have to mention that I removed the field ".soc_latency" in all new iwl_cfg you added in https://patchwork.kernel.org/patch/10059875/ to remove compile error based on the linux mainline 4.14. I don't know whether if this causes the problem. Do you need me to do anything for more information? Chris ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-17 6:39 ` Chris Chiu @ 2017-11-17 6:46 ` Luca Coelho 2017-11-17 7:23 ` Luca Coelho 2017-11-17 7:38 ` Chris Chiu 0 siblings, 2 replies; 23+ messages in thread From: Luca Coelho @ 2017-11-17 6:46 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> wrote: > > Hi Chris, > > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: > > > Hi Luca, > > > Any suggestion for the "Failed to start INIT ucode: -110" > > > issue > > > for the firmware? > > > > There were a few problems which should now be fixed. We published > > new > > firmwares in our linux-firmware.git tree[1] and also made some > > fixes in > > the driver[2]. Please update your system accordingly and let me > > know > > if it works for you. > > > > Thanks! > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-f > > irmware.git/ > > [2] https://patchwork.kernel.org/patch/10059871/ > > https://patchwork.kernel.org/patch/10059875/ > > https://patchwork.kernel.org/patch/10059873/ > > > > -- > > Cheers, > > Luca. > > Hi Luca, Hi Chris, > Thanks for your patch and updated firmware. The driver can > initialize w/o error now. However, it always fails on ip-config after > 4-way handshake complete. I have to mention that I removed the field > ".soc_latency" in all new iwl_cfg you added in > https://patchwork.kernel.org/patch/10059875/ to remove compile error > based on the linux mainline 4.14. > I don't know whether if this causes the problem. Do you need me > to > do anything for more information? That was my fault, I forgot to include one file in my commit. I have sent v2 of the two last patches to solve the problem. Can you try them? The problem you're seeing could be related to that, because we use a bit longer wait period for HW stabilization with integrated devices. And if you remove it, you may encounter random problems... -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-17 6:46 ` Luca Coelho @ 2017-11-17 7:23 ` Luca Coelho 2017-11-17 7:38 ` Chris Chiu 1 sibling, 0 replies; 23+ messages in thread From: Luca Coelho @ 2017-11-17 7:23 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Here are the links to v2 of the last two patches, please try with these instead (keep the first one that you already have): https://patchwork.kernel.org/patch/10060837/ https://patchwork.kernel.org/patch/10060839/ -- Cheers, Luca. On Fri, 2017-11-17 at 08:46 +0200, Luca Coelho wrote: > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> > > wrote: > > > Hi Chris, > > > > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: > > > > Hi Luca, > > > > Any suggestion for the "Failed to start INIT ucode: -110" > > > > issue > > > > for the firmware? > > > > > > There were a few problems which should now be fixed. We > > > published > > > new > > > firmwares in our linux-firmware.git tree[1] and also made some > > > fixes in > > > the driver[2]. Please update your system accordingly and let me > > > know > > > if it works for you. > > > > > > Thanks! > > > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux > > > -f > > > irmware.git/ > > > [2] https://patchwork.kernel.org/patch/10059871/ > > > https://patchwork.kernel.org/patch/10059875/ > > > https://patchwork.kernel.org/patch/10059873/ > > > > > > -- > > > Cheers, > > > Luca. > > > > Hi Luca, > > Hi Chris, > > > > Thanks for your patch and updated firmware. The driver can > > initialize w/o error now. However, it always fails on ip-config > > after > > 4-way handshake complete. I have to mention that I removed the > > field > > ".soc_latency" in all new iwl_cfg you added in > > https://patchwork.kernel.org/patch/10059875/ to remove compile > > error > > based on the linux mainline 4.14. > > I don't know whether if this causes the problem. Do you need me > > to > > do anything for more information? > > That was my fault, I forgot to include one file in my commit. I have > sent v2 of the two last patches to solve the problem. Can you try > them? > > The problem you're seeing could be related to that, because we use a > bit longer wait period for HW stabilization with integrated devices. > And if you remove it, you may encounter random problems... > > -- > Cheers, > Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-17 6:46 ` Luca Coelho 2017-11-17 7:23 ` Luca Coelho @ 2017-11-17 7:38 ` Chris Chiu 2017-11-17 7:53 ` Luca Coelho 2017-11-22 13:48 ` Chris Chiu 1 sibling, 2 replies; 23+ messages in thread From: Chris Chiu @ 2017-11-17 7:38 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> wrote: > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: >> On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> wrote: >> > Hi Chris, >> > >> > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >> > > Hi Luca, >> > > Any suggestion for the "Failed to start INIT ucode: -110" >> > > issue >> > > for the firmware? >> > >> > There were a few problems which should now be fixed. We published >> > new >> > firmwares in our linux-firmware.git tree[1] and also made some >> > fixes in >> > the driver[2]. Please update your system accordingly and let me >> > know >> > if it works for you. >> > >> > Thanks! >> > >> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-f >> > irmware.git/ >> > [2] https://patchwork.kernel.org/patch/10059871/ >> > https://patchwork.kernel.org/patch/10059875/ >> > https://patchwork.kernel.org/patch/10059873/ >> > >> > -- >> > Cheers, >> > Luca. >> >> Hi Luca, > > Hi Chris, > > >> Thanks for your patch and updated firmware. The driver can >> initialize w/o error now. However, it always fails on ip-config after >> 4-way handshake complete. I have to mention that I removed the field >> ".soc_latency" in all new iwl_cfg you added in >> https://patchwork.kernel.org/patch/10059875/ to remove compile error >> based on the linux mainline 4.14. >> I don't know whether if this causes the problem. Do you need me >> to >> do anything for more information? > > That was my fault, I forgot to include one file in my commit. I have > sent v2 of the two last patches to solve the problem. Can you try > them? > > The problem you're seeing could be related to that, because we use a > bit longer wait period for HW stabilization with integrated devices. > And if you remove it, you may encounter random problems... > > -- > Cheers, > Luca. Hi Luca, Thanks for your quick response. I tried your v2 patch but things remain the same. The signal strength and scan results seems nothing wrong but still fail to get ip from DHCP server. Please let me know what I can help here. Chris ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-17 7:38 ` Chris Chiu @ 2017-11-17 7:53 ` Luca Coelho 2017-11-17 10:14 ` Chris Chiu 2017-11-22 13:48 ` Chris Chiu 1 sibling, 1 reply; 23+ messages in thread From: Luca Coelho @ 2017-11-17 7:53 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, 2017-11-17 at 15:38 +0800, Chris Chiu wrote: > On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> wrote: > > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: > > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> > > > wrote: > > > > Hi Chris, > > > > > > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: > > > > > Hi Luca, > > > > > Any suggestion for the "Failed to start INIT ucode: -110" > > > > > issue > > > > > for the firmware? > > > > > > > > There were a few problems which should now be fixed. We > > > > published > > > > new > > > > firmwares in our linux-firmware.git tree[1] and also made some > > > > fixes in > > > > the driver[2]. Please update your system accordingly and let > > > > me > > > > know > > > > if it works for you. > > > > > > > > Thanks! > > > > > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/lin > > > > ux-f > > > > irmware.git/ > > > > [2] https://patchwork.kernel.org/patch/10059871/ > > > > https://patchwork.kernel.org/patch/10059875/ > > > > https://patchwork.kernel.org/patch/10059873/ > > > > > > > > -- > > > > Cheers, > > > > Luca. > > > > > > Hi Luca, > > > > Hi Chris, > > > > > > > Thanks for your patch and updated firmware. The driver can > > > initialize w/o error now. However, it always fails on ip-config > > > after > > > 4-way handshake complete. I have to mention that I removed the > > > field > > > ".soc_latency" in all new iwl_cfg you added in > > > https://patchwork.kernel.org/patch/10059875/ to remove compile > > > error > > > based on the linux mainline 4.14. > > > I don't know whether if this causes the problem. Do you need > > > me > > > to > > > do anything for more information? > > > > That was my fault, I forgot to include one file in my commit. I > > have > > sent v2 of the two last patches to solve the problem. Can you try > > them? > > > > The problem you're seeing could be related to that, because we use > > a > > bit longer wait period for HW stabilization with integrated > > devices. > > And if you remove it, you may encounter random problems... > > > > -- > > Cheers, > > Luca. > > Hi Luca, > Thanks for your quick response. I tried your v2 patch but things > remain the same. The signal strength and scan results seems nothing > wrong but still fail to get ip from DHCP server. Please let me know > what I can help here. Can you provide the dmesg output and trace-cmd logs as explained here? https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-17 7:53 ` Luca Coelho @ 2017-11-17 10:14 ` Chris Chiu 0 siblings, 0 replies; 23+ messages in thread From: Chris Chiu @ 2017-11-17 10:14 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, Nov 17, 2017 at 3:53 PM, Luca Coelho <luca@coelho.fi> wrote: > On Fri, 2017-11-17 at 15:38 +0800, Chris Chiu wrote: >> On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> wrote: >> > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: >> > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> >> > > wrote: >> > > > Hi Chris, >> > > > >> > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >> > > > > Hi Luca, >> > > > > Any suggestion for the "Failed to start INIT ucode: -110" >> > > > > issue >> > > > > for the firmware? >> > > > >> > > > There were a few problems which should now be fixed. We >> > > > published >> > > > new >> > > > firmwares in our linux-firmware.git tree[1] and also made some >> > > > fixes in >> > > > the driver[2]. Please update your system accordingly and let >> > > > me >> > > > know >> > > > if it works for you. >> > > > >> > > > Thanks! >> > > > >> > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/lin >> > > > ux-f >> > > > irmware.git/ >> > > > [2] https://patchwork.kernel.org/patch/10059871/ >> > > > https://patchwork.kernel.org/patch/10059875/ >> > > > https://patchwork.kernel.org/patch/10059873/ >> > > > >> > > > -- >> > > > Cheers, >> > > > Luca. >> > > >> > > Hi Luca, >> > >> > Hi Chris, >> > >> > >> > > Thanks for your patch and updated firmware. The driver can >> > > initialize w/o error now. However, it always fails on ip-config >> > > after >> > > 4-way handshake complete. I have to mention that I removed the >> > > field >> > > ".soc_latency" in all new iwl_cfg you added in >> > > https://patchwork.kernel.org/patch/10059875/ to remove compile >> > > error >> > > based on the linux mainline 4.14. >> > > I don't know whether if this causes the problem. Do you need >> > > me >> > > to >> > > do anything for more information? >> > >> > That was my fault, I forgot to include one file in my commit. I >> > have >> > sent v2 of the two last patches to solve the problem. Can you try >> > them? >> > >> > The problem you're seeing could be related to that, because we use >> > a >> > bit longer wait period for HW stabilization with integrated >> > devices. >> > And if you remove it, you may encounter random problems... >> > >> > -- >> > Cheers, >> > Luca. >> >> Hi Luca, >> Thanks for your quick response. I tried your v2 patch but things >> remain the same. The signal strength and scan results seems nothing >> wrong but still fail to get ip from DHCP server. Please let me know >> what I can help here. > > Can you provide the dmesg output and trace-cmd logs as explained here? > > https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging > > > -- > Cheers, > Luca. Hi Luca, Here's the dmesg log of the fail case on DHCP. https://gist.github.com/mschiu77/ec1a4579e6b863da68b703205cf8a0e4 Chris ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: Need support for Intel new wifi module 9462NGW 2017-11-17 7:38 ` Chris Chiu 2017-11-17 7:53 ` Luca Coelho @ 2017-11-22 13:48 ` Chris Chiu 2017-11-26 9:49 ` [linuxwifi] " Luca Coelho 1 sibling, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-11-22 13:48 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, Nov 17, 2017 at 3:38 PM, Chris Chiu <chiu@endlessm.com> wrote: > On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> wrote: >> On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: >>> On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> wrote: >>> > Hi Chris, >>> > >>> > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >>> > > Hi Luca, >>> > > Any suggestion for the "Failed to start INIT ucode: -110" >>> > > issue >>> > > for the firmware? >>> > >>> > There were a few problems which should now be fixed. We published >>> > new >>> > firmwares in our linux-firmware.git tree[1] and also made some >>> > fixes in >>> > the driver[2]. Please update your system accordingly and let me >>> > know >>> > if it works for you. >>> > >>> > Thanks! >>> > >>> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-f >>> > irmware.git/ >>> > [2] https://patchwork.kernel.org/patch/10059871/ >>> > https://patchwork.kernel.org/patch/10059875/ >>> > https://patchwork.kernel.org/patch/10059873/ >>> > >>> > -- >>> > Cheers, >>> > Luca. >>> >>> Hi Luca, >> >> Hi Chris, >> >> >>> Thanks for your patch and updated firmware. The driver can >>> initialize w/o error now. However, it always fails on ip-config after >>> 4-way handshake complete. I have to mention that I removed the field >>> ".soc_latency" in all new iwl_cfg you added in >>> https://patchwork.kernel.org/patch/10059875/ to remove compile error >>> based on the linux mainline 4.14. >>> I don't know whether if this causes the problem. Do you need me >>> to >>> do anything for more information? >> >> That was my fault, I forgot to include one file in my commit. I have >> sent v2 of the two last patches to solve the problem. Can you try >> them? >> >> The problem you're seeing could be related to that, because we use a >> bit longer wait period for HW stabilization with integrated devices. >> And if you remove it, you may encounter random problems... >> >> -- >> Cheers, >> Luca. > > Hi Luca, > Thanks for your quick response. I tried your v2 patch but things > remain the same. The signal strength and scan results seems nothing > wrong but still fail to get ip from DHCP server. Please let me know > what I can help here. > > Chris Hi Luca, Some more observation I want to point out and maybe you can suggest. After your v2 patch and the latest firmware. I'm pretty sure there's no problem on my 9462NGW module to associate to an AP (4-way handshaking complete) dmesg in https://gist.github.com/mschiu77/1fe1f5128f1c49a93055ce23976c09b5 here also shows [ 59.338785] wlp0s12f0: associated Then I do air sniffer with my mac book air and only dump DHCP packets in https://gist.github.com/mschiu77/677b5fbfdea0fea2eda4a36a84bcac8e As you see, 4 DHCP Discovery here but no response. I do the same thing on the other laptop to associate to the same AP SSID, there's no problem. And yet another interesting thing is, every time I was trying to associate The ifconfig always give me a totally different ether address. I log 5 times in https://gist.github.com/mschiu77/54169d52b9fcf205d5c26752988f8a3d The read HW address should be 34:13:e8:6f:34:25 and it's also true in tcpdump log. I think maybe it's related. Can you suggest anything that I can try? Chris ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-11-22 13:48 ` Chris Chiu @ 2017-11-26 9:49 ` Luca Coelho 2017-11-30 13:18 ` Chris Chiu 0 siblings, 1 reply; 23+ messages in thread From: Luca Coelho @ 2017-11-26 9:49 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Wed, 2017-11-22 at 21:48 +0800, Chris Chiu wrote: > On Fri, Nov 17, 2017 at 3:38 PM, Chris Chiu <chiu@endlessm.com> > wrote: > > On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> > > wrote: > > > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: > > > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> > > > > wrote: > > > > > Hi Chris, > > > > > > > > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: > > > > > > Hi Luca, > > > > > > Any suggestion for the "Failed to start INIT ucode: > > > > > > -110" > > > > > > issue > > > > > > for the firmware? > > > > > > > > > > There were a few problems which should now be fixed. We > > > > > published > > > > > new > > > > > firmwares in our linux-firmware.git tree[1] and also made > > > > > some > > > > > fixes in > > > > > the driver[2]. Please update your system accordingly and let > > > > > me > > > > > know > > > > > if it works for you. > > > > > > > > > > Thanks! > > > > > > > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/l > > > > > inux-f > > > > > irmware.git/ > > > > > [2] https://patchwork.kernel.org/patch/10059871/ > > > > > https://patchwork.kernel.org/patch/10059875/ > > > > > https://patchwork.kernel.org/patch/10059873/ > > > > > > > > > > -- > > > > > Cheers, > > > > > Luca. > > > > > > > > Hi Luca, > > > > > > Hi Chris, > > > > > > > > > > Thanks for your patch and updated firmware. The driver can > > > > initialize w/o error now. However, it always fails on ip-config > > > > after > > > > 4-way handshake complete. I have to mention that I removed the > > > > field > > > > ".soc_latency" in all new iwl_cfg you added in > > > > https://patchwork.kernel.org/patch/10059875/ to remove compile > > > > error > > > > based on the linux mainline 4.14. > > > > I don't know whether if this causes the problem. Do you > > > > need me > > > > to > > > > do anything for more information? > > > > > > That was my fault, I forgot to include one file in my commit. I > > > have > > > sent v2 of the two last patches to solve the problem. Can you > > > try > > > them? > > > > > > The problem you're seeing could be related to that, because we > > > use a > > > bit longer wait period for HW stabilization with integrated > > > devices. > > > And if you remove it, you may encounter random problems... > > > > > > -- > > > Cheers, > > > Luca. > > > > Hi Luca, > > Thanks for your quick response. I tried your v2 patch but > > things > > remain the same. The signal strength and scan results seems nothing > > wrong but still fail to get ip from DHCP server. Please let me know > > what I can help here. > > > > Chris > > Hi Luca, > Some more observation I want to point out and maybe you can > suggest. > After your v2 patch and the latest firmware. I'm pretty sure there's > no problem > on my 9462NGW module to associate to an AP (4-way handshaking > complete) > dmesg in https://gist.github.com/mschiu77/1fe1f5128f1c49a93055ce23976 > c09b5 > here also shows > [ 59.338785] wlp0s12f0: associated > > Then I do air sniffer with my mac book air and only dump DHCP packets > in > https://gist.github.com/mschiu77/677b5fbfdea0fea2eda4a36a84bcac8e > > As you see, 4 DHCP Discovery here but no response. I do the same > thing on > the other laptop to associate to the same AP SSID, there's no > problem. > > And yet another interesting thing is, every time I was trying to > associate > The ifconfig always give me a totally different ether address. I log > 5 times in > https://gist.github.com/mschiu77/54169d52b9fcf205d5c26752988f8a3d > > The read HW address should be 34:13:e8:6f:34:25 and it's also true in > tcpdump > log. > > I think maybe it's related. Can you suggest anything that I can try? Hey Chris, Thanks for the update and sorry for the delay. I'll take a look into this in the coming week, there's probably something missing in the driver that is causing this issue... -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-11-26 9:49 ` [linuxwifi] " Luca Coelho @ 2017-11-30 13:18 ` Chris Chiu 2017-12-01 5:29 ` Chris Chiu 0 siblings, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-11-30 13:18 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Luca, I got another machine which has Intel 9461NGW (31dc:0264) and stuck at the same problem. I can't see the DHCP response on the air. However, the router does respond to the DHCP discover. Please check the following tcpdump here. The 9461's mac address is 60:f6:77:9a:f4:ed https://gist.github.com/mschiu77/8f613ba6e3c41a3bd5206f1e903b0bbd Then I go to AP and do tcpdump, I can still see the DHCP reply packet on the corresponding interface. Don't know why can't I see this packet on the air? maybe wrong channel? Chris On Sun, Nov 26, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> wrote: > On Wed, 2017-11-22 at 21:48 +0800, Chris Chiu wrote: >> On Fri, Nov 17, 2017 at 3:38 PM, Chris Chiu <chiu@endlessm.com> >> wrote: >> > On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> >> > wrote: >> > > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: >> > > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> >> > > > wrote: >> > > > > Hi Chris, >> > > > > >> > > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >> > > > > > Hi Luca, >> > > > > > Any suggestion for the "Failed to start INIT ucode: >> > > > > > -110" >> > > > > > issue >> > > > > > for the firmware? >> > > > > >> > > > > There were a few problems which should now be fixed. We >> > > > > published >> > > > > new >> > > > > firmwares in our linux-firmware.git tree[1] and also made >> > > > > some >> > > > > fixes in >> > > > > the driver[2]. Please update your system accordingly and let >> > > > > me >> > > > > know >> > > > > if it works for you. >> > > > > >> > > > > Thanks! >> > > > > >> > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/l >> > > > > inux-f >> > > > > irmware.git/ >> > > > > [2] https://patchwork.kernel.org/patch/10059871/ >> > > > > https://patchwork.kernel.org/patch/10059875/ >> > > > > https://patchwork.kernel.org/patch/10059873/ >> > > > > >> > > > > -- >> > > > > Cheers, >> > > > > Luca. >> > > > >> > > > Hi Luca, >> > > >> > > Hi Chris, >> > > >> > > >> > > > Thanks for your patch and updated firmware. The driver can >> > > > initialize w/o error now. However, it always fails on ip-config >> > > > after >> > > > 4-way handshake complete. I have to mention that I removed the >> > > > field >> > > > ".soc_latency" in all new iwl_cfg you added in >> > > > https://patchwork.kernel.org/patch/10059875/ to remove compile >> > > > error >> > > > based on the linux mainline 4.14. >> > > > I don't know whether if this causes the problem. Do you >> > > > need me >> > > > to >> > > > do anything for more information? >> > > >> > > That was my fault, I forgot to include one file in my commit. I >> > > have >> > > sent v2 of the two last patches to solve the problem. Can you >> > > try >> > > them? >> > > >> > > The problem you're seeing could be related to that, because we >> > > use a >> > > bit longer wait period for HW stabilization with integrated >> > > devices. >> > > And if you remove it, you may encounter random problems... >> > > >> > > -- >> > > Cheers, >> > > Luca. >> > >> > Hi Luca, >> > Thanks for your quick response. I tried your v2 patch but >> > things >> > remain the same. The signal strength and scan results seems nothing >> > wrong but still fail to get ip from DHCP server. Please let me know >> > what I can help here. >> > >> > Chris >> >> Hi Luca, >> Some more observation I want to point out and maybe you can >> suggest. >> After your v2 patch and the latest firmware. I'm pretty sure there's >> no problem >> on my 9462NGW module to associate to an AP (4-way handshaking >> complete) >> dmesg in https://gist.github.com/mschiu77/1fe1f5128f1c49a93055ce23976 >> c09b5 >> here also shows >> [ 59.338785] wlp0s12f0: associated >> >> Then I do air sniffer with my mac book air and only dump DHCP packets >> in >> https://gist.github.com/mschiu77/677b5fbfdea0fea2eda4a36a84bcac8e >> >> As you see, 4 DHCP Discovery here but no response. I do the same >> thing on >> the other laptop to associate to the same AP SSID, there's no >> problem. >> >> And yet another interesting thing is, every time I was trying to >> associate >> The ifconfig always give me a totally different ether address. I log >> 5 times in >> https://gist.github.com/mschiu77/54169d52b9fcf205d5c26752988f8a3d >> >> The read HW address should be 34:13:e8:6f:34:25 and it's also true in >> tcpdump >> log. >> >> I think maybe it's related. Can you suggest anything that I can try? > > Hey Chris, > > Thanks for the update and sorry for the delay. I'll take a look into > this in the coming week, there's probably something missing in the > driver that is causing this issue... > > -- > Cheers, > Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-11-30 13:18 ` Chris Chiu @ 2017-12-01 5:29 ` Chris Chiu 2017-12-01 5:53 ` Luca Coelho 0 siblings, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-12-01 5:29 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Luca, I think the problem is not missing DHCP reply. I installed tcpdump on the machine with Intel 9461NGW and start monitoring on the wlan interface. The result is following https://gist.github.com/mschiu77/f4cc14ddae6adf137da15675cca59b30 I also attach the ifconfig result at the end of the above url. Hope this can help a little. Chris On Thu, Nov 30, 2017 at 9:18 PM, Chris Chiu <chiu@endlessm.com> wrote: > Hi Luca, > I got another machine which has Intel 9461NGW (31dc:0264) and > stuck at the same problem. I can't see the DHCP response on the air. > However, the router does respond to the DHCP discover. Please check > the following tcpdump here. The 9461's mac address is > 60:f6:77:9a:f4:ed > https://gist.github.com/mschiu77/8f613ba6e3c41a3bd5206f1e903b0bbd > > Then I go to AP and do tcpdump, I can still see the DHCP reply > packet on the corresponding interface. Don't know why can't I see this > packet on the air? maybe wrong channel? > > Chris > > On Sun, Nov 26, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> wrote: >> On Wed, 2017-11-22 at 21:48 +0800, Chris Chiu wrote: >>> On Fri, Nov 17, 2017 at 3:38 PM, Chris Chiu <chiu@endlessm.com> >>> wrote: >>> > On Fri, Nov 17, 2017 at 2:46 PM, Luca Coelho <luca@coelho.fi> >>> > wrote: >>> > > On Fri, 2017-11-17 at 14:39 +0800, Chris Chiu wrote: >>> > > > On Thu, Nov 16, 2017 at 5:49 PM, Luca Coelho <luca@coelho.fi> >>> > > > wrote: >>> > > > > Hi Chris, >>> > > > > >>> > > > > On Thu, 2017-11-09 at 11:11 +0800, Chris Chiu wrote: >>> > > > > > Hi Luca, >>> > > > > > Any suggestion for the "Failed to start INIT ucode: >>> > > > > > -110" >>> > > > > > issue >>> > > > > > for the firmware? >>> > > > > >>> > > > > There were a few problems which should now be fixed. We >>> > > > > published >>> > > > > new >>> > > > > firmwares in our linux-firmware.git tree[1] and also made >>> > > > > some >>> > > > > fixes in >>> > > > > the driver[2]. Please update your system accordingly and let >>> > > > > me >>> > > > > know >>> > > > > if it works for you. >>> > > > > >>> > > > > Thanks! >>> > > > > >>> > > > > [1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/l >>> > > > > inux-f >>> > > > > irmware.git/ >>> > > > > [2] https://patchwork.kernel.org/patch/10059871/ >>> > > > > https://patchwork.kernel.org/patch/10059875/ >>> > > > > https://patchwork.kernel.org/patch/10059873/ >>> > > > > >>> > > > > -- >>> > > > > Cheers, >>> > > > > Luca. >>> > > > >>> > > > Hi Luca, >>> > > >>> > > Hi Chris, >>> > > >>> > > >>> > > > Thanks for your patch and updated firmware. The driver can >>> > > > initialize w/o error now. However, it always fails on ip-config >>> > > > after >>> > > > 4-way handshake complete. I have to mention that I removed the >>> > > > field >>> > > > ".soc_latency" in all new iwl_cfg you added in >>> > > > https://patchwork.kernel.org/patch/10059875/ to remove compile >>> > > > error >>> > > > based on the linux mainline 4.14. >>> > > > I don't know whether if this causes the problem. Do you >>> > > > need me >>> > > > to >>> > > > do anything for more information? >>> > > >>> > > That was my fault, I forgot to include one file in my commit. I >>> > > have >>> > > sent v2 of the two last patches to solve the problem. Can you >>> > > try >>> > > them? >>> > > >>> > > The problem you're seeing could be related to that, because we >>> > > use a >>> > > bit longer wait period for HW stabilization with integrated >>> > > devices. >>> > > And if you remove it, you may encounter random problems... >>> > > >>> > > -- >>> > > Cheers, >>> > > Luca. >>> > >>> > Hi Luca, >>> > Thanks for your quick response. I tried your v2 patch but >>> > things >>> > remain the same. The signal strength and scan results seems nothing >>> > wrong but still fail to get ip from DHCP server. Please let me know >>> > what I can help here. >>> > >>> > Chris >>> >>> Hi Luca, >>> Some more observation I want to point out and maybe you can >>> suggest. >>> After your v2 patch and the latest firmware. I'm pretty sure there's >>> no problem >>> on my 9462NGW module to associate to an AP (4-way handshaking >>> complete) >>> dmesg in https://gist.github.com/mschiu77/1fe1f5128f1c49a93055ce23976 >>> c09b5 >>> here also shows >>> [ 59.338785] wlp0s12f0: associated >>> >>> Then I do air sniffer with my mac book air and only dump DHCP packets >>> in >>> https://gist.github.com/mschiu77/677b5fbfdea0fea2eda4a36a84bcac8e >>> >>> As you see, 4 DHCP Discovery here but no response. I do the same >>> thing on >>> the other laptop to associate to the same AP SSID, there's no >>> problem. >>> >>> And yet another interesting thing is, every time I was trying to >>> associate >>> The ifconfig always give me a totally different ether address. I log >>> 5 times in >>> https://gist.github.com/mschiu77/54169d52b9fcf205d5c26752988f8a3d >>> >>> The read HW address should be 34:13:e8:6f:34:25 and it's also true in >>> tcpdump >>> log. >>> >>> I think maybe it's related. Can you suggest anything that I can try? >> >> Hey Chris, >> >> Thanks for the update and sorry for the delay. I'll take a look into >> this in the coming week, there's probably something missing in the >> driver that is causing this issue... >> >> -- >> Cheers, >> Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-12-01 5:29 ` Chris Chiu @ 2017-12-01 5:53 ` Luca Coelho 2017-12-03 8:39 ` Luca Coelho 0 siblings, 1 reply; 23+ messages in thread From: Luca Coelho @ 2017-12-01 5:53 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, 2017-12-01 at 13:29 +0800, Chris Chiu wrote: > Hi Luca, > I think the problem is not missing DHCP reply. I installed > tcpdump > on the machine with Intel 9461NGW and start monitoring on the wlan > interface. > The result is following > https://gist.github.com/mschiu77/f4cc14ddae6adf137da15675cca59b30 > > I also attach the ifconfig result at the end of the above url. Hope > this can help a little. Hi Chris, Sorry for the delay. We've been testing this internally, but couldn't reproduce it at first. The problems seems to be with the firmware that we released. I'll provide you an update today or latest by Monday next week. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-12-01 5:53 ` Luca Coelho @ 2017-12-03 8:39 ` Luca Coelho 2017-12-04 5:36 ` Chris Chiu 0 siblings, 1 reply; 23+ messages in thread From: Luca Coelho @ 2017-12-03 8:39 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Fri, 2017-12-01 at 07:53 +0200, Luca Coelho wrote: > On Fri, 2017-12-01 at 13:29 +0800, Chris Chiu wrote: > > Hi Luca, > > I think the problem is not missing DHCP reply. I installed > > tcpdump > > on the machine with Intel 9461NGW and start monitoring on the wlan > > interface. > > The result is following > > https://gist.github.com/mschiu77/f4cc14ddae6adf137da15675cca59b30 > > > > I also attach the ifconfig result at the end of the above url. Hope > > this can help a little. > > Hi Chris, > > Sorry for the delay. We've been testing this internally, but > couldn't > reproduce it at first. The problems seems to be with the firmware > that > we released. > > I'll provide you an update today or latest by Monday next week. Hi Chris, We found a patch that was missing from upstream and causes data corruption on secure associations: https://patchwork.kernel.org/patch/10088939/ Can you try to apply this patch and see if it fixes the problem you are having? -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-12-03 8:39 ` Luca Coelho @ 2017-12-04 5:36 ` Chris Chiu 2017-12-04 11:43 ` Luca Coelho 0 siblings, 1 reply; 23+ messages in thread From: Chris Chiu @ 2017-12-04 5:36 UTC (permalink / raw) To: Luca Coelho Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team Hi Luca, I applied https://patchwork.kernel.org/patch/10088929/ and https://patchwork.kernel.org/patch/10088939/, I can access internet thru 9461/9462NGW now. Thanks so much. Chris On Sun, Dec 3, 2017 at 4:39 PM, Luca Coelho <luca@coelho.fi> wrote: > On Fri, 2017-12-01 at 07:53 +0200, Luca Coelho wrote: >> On Fri, 2017-12-01 at 13:29 +0800, Chris Chiu wrote: >> > Hi Luca, >> > I think the problem is not missing DHCP reply. I installed >> > tcpdump >> > on the machine with Intel 9461NGW and start monitoring on the wlan >> > interface. >> > The result is following >> > https://gist.github.com/mschiu77/f4cc14ddae6adf137da15675cca59b30 >> > >> > I also attach the ifconfig result at the end of the above url. Hope >> > this can help a little. >> >> Hi Chris, >> >> Sorry for the delay. We've been testing this internally, but >> couldn't >> reproduce it at first. The problems seems to be with the firmware >> that >> we released. >> >> I'll provide you an update today or latest by Monday next week. > > Hi Chris, > > We found a patch that was missing from upstream and causes data > corruption on secure associations: > > https://patchwork.kernel.org/patch/10088939/ > > > Can you try to apply this patch and see if it fixes the problem you are > having? > > -- > Cheers, > Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [linuxwifi] Need support for Intel new wifi module 9462NGW 2017-12-04 5:36 ` Chris Chiu @ 2017-12-04 11:43 ` Luca Coelho 0 siblings, 0 replies; 23+ messages in thread From: Luca Coelho @ 2017-12-04 11:43 UTC (permalink / raw) To: Chris Chiu Cc: johannes.berg, linuxwifi, linux-wireless, Linux Upstreaming Team On Mon, 2017-12-04 at 13:36 +0800, Chris Chiu wrote: > Hi Luca, > I applied https://patchwork.kernel.org/patch/10088929/ and > https://patchwork.kernel.org/patch/10088939/, I can access internet > thru 9461/9462NGW now. Thanks so much. Thanks for testing! Great that it works now. I'll queue this patches for stable. -- Cheers, Luca. ^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2017-12-04 11:43 UTC | newest] Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-10-31 4:13 Need support for Intel new wifi module 9462NGW Chris Chiu 2017-10-31 7:25 ` Luca Coelho 2017-10-31 7:29 ` Chris Chiu 2017-11-06 3:22 ` Chris Chiu 2017-11-06 7:22 ` Luca Coelho 2017-11-07 4:26 ` Chris Chiu 2017-11-09 3:11 ` Chris Chiu 2017-11-09 6:29 ` Luca Coelho 2017-11-16 9:49 ` Luca Coelho 2017-11-17 6:39 ` Chris Chiu 2017-11-17 6:46 ` Luca Coelho 2017-11-17 7:23 ` Luca Coelho 2017-11-17 7:38 ` Chris Chiu 2017-11-17 7:53 ` Luca Coelho 2017-11-17 10:14 ` Chris Chiu 2017-11-22 13:48 ` Chris Chiu 2017-11-26 9:49 ` [linuxwifi] " Luca Coelho 2017-11-30 13:18 ` Chris Chiu 2017-12-01 5:29 ` Chris Chiu 2017-12-01 5:53 ` Luca Coelho 2017-12-03 8:39 ` Luca Coelho 2017-12-04 5:36 ` Chris Chiu 2017-12-04 11:43 ` Luca Coelho
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.