* ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file
@ 2021-08-24 16:44 Hans de Goede
2022-01-21 14:16 ` Kalle Valo
0 siblings, 1 reply; 4+ messages in thread
From: Hans de Goede @ 2021-08-24 16:44 UTC (permalink / raw)
To: Kalle Valo; +Cc: ath10k
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
Hi Kalle,
Here is a board-file for the QCA6174 PCI 168c:003e subsys: 168c:3370 wifi
card found on Microsoft Surface Go devices.
I'm submitting this per the docs in:
https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
I hope those are still up to date.
Currently the kernel gives the following message when loading on this card:
"failed to fetch board data for
bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370
from ath10k/QCA6174/hw3.0/board-2.bin"
And then errors out with a bunch of -110 (-ETIMEOUT) errors.
Replacing the fallback board.bin file with the attached .bin file fixes
these errors and results in working wifi (I tested at both 2.4G and 5G).
There are various internet forum posts which point to this board file:
https://web.archive.org/web/20201111213909/http://www.killernetworking.com/support/K1535_Debian/board.bin
But the killer 1535 wifi card uses completely different subsys-ids
of 1a56:1535, so even though that happens to work I do not believe
that is the correct file.
So instead, inspired by this report:
https://bugzilla.redhat.com/show_bug.cgi?id=1651779
I started looking at the driverstore directory of the original windows
install on the device I found "netathr10x.inf" there which has this line:
eDesc.6320_3% = ATHR_DEV_OS63_988x_TX8.ndi, PCI\VEN_168C&DEV_003E&SUBSYS_3370168C&REV_32; WiFi Only SKU
Note the "WiFi Only SKU" remark is there to differentiate this from
the 168c:3371 subsys one which also has LTE (marked as "WiFi/LTE SKU")
This led me to the "ATHR_DEV_OS63_988x_TX8.ndi" section of the .inf file:
[ATHR_DEV_OS63_988x_TX8.ndi.NTamd64]
...
CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles, atheros_BD_TX8.CopyFiles
...
And "atheros_BD_TX8.CopyFiles" is:
[atheros_BD_TX8.CopyFiles]
eeprom_ar6320_3p0_TX8_clpc.bin,,,2
The "windows\system32\driverstore\netathr10x" dir has a ton of
eeprom files (let me know if you want a copy of the whole dir)
including the mentioned one. Where as "windows\system32\drivers"
only has the one eeprom_ar6320_3p0_TX8_clpc.bin eeprom... file,
further indicating that that is the one actually being used.
So this is the file which I've tested with and which is attached to this email as:
"bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin"
md5sum:
bc52aa5640b27fa50f9d4d144f81e169 bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin
Regards,
Hans
[-- Attachment #2: bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin.gz --]
[-- Type: application/gzip, Size: 3143 bytes --]
[-- Attachment #3: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file
2021-08-24 16:44 ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file Hans de Goede
@ 2022-01-21 14:16 ` Kalle Valo
2022-01-21 15:13 ` Hans de Goede
0 siblings, 1 reply; 4+ messages in thread
From: Kalle Valo @ 2022-01-21 14:16 UTC (permalink / raw)
To: Hans de Goede; +Cc: ath10k
Hans de Goede <hans@hansg.org> writes:
> Here is a board-file for the QCA6174 PCI 168c:003e subsys: 168c:3370 wifi
> card found on Microsoft Surface Go devices.
>
> I'm submitting this per the docs in:
> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
> I hope those are still up to date.
>
> Currently the kernel gives the following message when loading on this card:
> "failed to fetch board data for
> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370
> from ath10k/QCA6174/hw3.0/board-2.bin"
>
> And then errors out with a bunch of -110 (-ETIMEOUT) errors.
>
> Replacing the fallback board.bin file with the attached .bin file fixes
> these errors and results in working wifi (I tested at both 2.4G and 5G).
>
> There are various internet forum posts which point to this board file:
> https://web.archive.org/web/20201111213909/http://www.killernetworking.com/support/K1535_Debian/board.bin
>
> But the killer 1535 wifi card uses completely different subsys-ids
> of 1a56:1535, so even though that happens to work I do not believe
> that is the correct file.
>
> So instead, inspired by this report:
> https://bugzilla.redhat.com/show_bug.cgi?id=1651779
>
> I started looking at the driverstore directory of the original windows
> install on the device I found "netathr10x.inf" there which has this line:
>
> eDesc.6320_3% = ATHR_DEV_OS63_988x_TX8.ndi,
> PCI\VEN_168C&DEV_003E&SUBSYS_3370168C&REV_32; WiFi Only SKU
>
> Note the "WiFi Only SKU" remark is there to differentiate this from
> the 168c:3371 subsys one which also has LTE (marked as "WiFi/LTE SKU")
>
> This led me to the "ATHR_DEV_OS63_988x_TX8.ndi" section of the .inf file:
>
> [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64]
> ...
> CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles, atheros_BD_TX8.CopyFiles
> ...
>
> And "atheros_BD_TX8.CopyFiles" is:
>
> [atheros_BD_TX8.CopyFiles]
> eeprom_ar6320_3p0_TX8_clpc.bin,,,2
>
> The "windows\system32\driverstore\netathr10x" dir has a ton of
> eeprom files (let me know if you want a copy of the whole dir)
> including the mentioned one. Where as "windows\system32\drivers"
> only has the one eeprom_ar6320_3p0_TX8_clpc.bin eeprom... file,
> further indicating that that is the one actually being used.
>
> So this is the file which I've tested with and which is attached to this email as:
> "bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin"
>
> md5sum:
> bc52aa5640b27fa50f9d4d144f81e169
> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin
I assume this is the same version as you submitted directly to
linux-firmware[1], so I'm dropping this request.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4d74f4dec175363fa24c95702dd86f477cef232c
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file
2022-01-21 14:16 ` Kalle Valo
@ 2022-01-21 15:13 ` Hans de Goede
2022-01-24 9:05 ` Kalle Valo
0 siblings, 1 reply; 4+ messages in thread
From: Hans de Goede @ 2022-01-21 15:13 UTC (permalink / raw)
To: Kalle Valo; +Cc: ath10k
Hi,
On 1/21/22 15:16, Kalle Valo wrote:
> Hans de Goede <hans@hansg.org> writes:
>
>> Here is a board-file for the QCA6174 PCI 168c:003e subsys: 168c:3370 wifi
>> card found on Microsoft Surface Go devices.
>>
>> I'm submitting this per the docs in:
>> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
>> I hope those are still up to date.
>>
>> Currently the kernel gives the following message when loading on this card:
>> "failed to fetch board data for
>> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370
>> from ath10k/QCA6174/hw3.0/board-2.bin"
>>
>> And then errors out with a bunch of -110 (-ETIMEOUT) errors.
>>
>> Replacing the fallback board.bin file with the attached .bin file fixes
>> these errors and results in working wifi (I tested at both 2.4G and 5G).
>>
>> There are various internet forum posts which point to this board file:
>> https://web.archive.org/web/20201111213909/http://www.killernetworking.com/support/K1535_Debian/board.bin
>>
>> But the killer 1535 wifi card uses completely different subsys-ids
>> of 1a56:1535, so even though that happens to work I do not believe
>> that is the correct file.
>>
>> So instead, inspired by this report:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1651779
>>
>> I started looking at the driverstore directory of the original windows
>> install on the device I found "netathr10x.inf" there which has this line:
>>
>> eDesc.6320_3% = ATHR_DEV_OS63_988x_TX8.ndi,
>> PCI\VEN_168C&DEV_003E&SUBSYS_3370168C&REV_32; WiFi Only SKU
>>
>> Note the "WiFi Only SKU" remark is there to differentiate this from
>> the 168c:3371 subsys one which also has LTE (marked as "WiFi/LTE SKU")
>>
>> This led me to the "ATHR_DEV_OS63_988x_TX8.ndi" section of the .inf file:
>>
>> [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64]
>> ...
>> CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles, atheros_BD_TX8.CopyFiles
>> ...
>>
>> And "atheros_BD_TX8.CopyFiles" is:
>>
>> [atheros_BD_TX8.CopyFiles]
>> eeprom_ar6320_3p0_TX8_clpc.bin,,,2
>>
>> The "windows\system32\driverstore\netathr10x" dir has a ton of
>> eeprom files (let me know if you want a copy of the whole dir)
>> including the mentioned one. Where as "windows\system32\drivers"
>> only has the one eeprom_ar6320_3p0_TX8_clpc.bin eeprom... file,
>> further indicating that that is the one actually being used.
>>
>> So this is the file which I've tested with and which is attached to this email as:
>> "bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin"
>>
>> md5sum:
>> bc52aa5640b27fa50f9d4d144f81e169
>> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin
>
> I assume this is the same version as you submitted directly to
> linux-firmware[1],
Correct, note that my upstream linux-firmware submission contains
2 new board files. I've also submitted this to the ath10k-firmware repo here:
https://github.com/kvalo/ath10k-firmware/pull/11
Regards,
Hans
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file
2022-01-21 15:13 ` Hans de Goede
@ 2022-01-24 9:05 ` Kalle Valo
0 siblings, 0 replies; 4+ messages in thread
From: Kalle Valo @ 2022-01-24 9:05 UTC (permalink / raw)
To: Hans de Goede; +Cc: ath10k
Hans de Goede <hans@hansg.org> writes:
> On 1/21/22 15:16, Kalle Valo wrote:
>> Hans de Goede <hans@hansg.org> writes:
>>
>>> Here is a board-file for the QCA6174 PCI 168c:003e subsys: 168c:3370 wifi
>>> card found on Microsoft Surface Go devices.
>>>
>>> I'm submitting this per the docs in:
>>> https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles
>>> I hope those are still up to date.
>>>
>>> Currently the kernel gives the following message when loading on this card:
>>> "failed to fetch board data for
>>> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370
>>> from ath10k/QCA6174/hw3.0/board-2.bin"
>>>
>>> And then errors out with a bunch of -110 (-ETIMEOUT) errors.
>>>
>>> Replacing the fallback board.bin file with the attached .bin file fixes
>>> these errors and results in working wifi (I tested at both 2.4G and 5G).
>>>
>>> There are various internet forum posts which point to this board file:
>>> https://web.archive.org/web/20201111213909/http://www.killernetworking.com/support/K1535_Debian/board.bin
>>>
>>> But the killer 1535 wifi card uses completely different subsys-ids
>>> of 1a56:1535, so even though that happens to work I do not believe
>>> that is the correct file.
>>>
>>> So instead, inspired by this report:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1651779
>>>
>>> I started looking at the driverstore directory of the original windows
>>> install on the device I found "netathr10x.inf" there which has this line:
>>>
>>> eDesc.6320_3% = ATHR_DEV_OS63_988x_TX8.ndi,
>>> PCI\VEN_168C&DEV_003E&SUBSYS_3370168C&REV_32; WiFi Only SKU
>>>
>>> Note the "WiFi Only SKU" remark is there to differentiate this from
>>> the 168c:3371 subsys one which also has LTE (marked as "WiFi/LTE SKU")
>>>
>>> This led me to the "ATHR_DEV_OS63_988x_TX8.ndi" section of the .inf file:
>>>
>>> [ATHR_DEV_OS63_988x_TX8.ndi.NTamd64]
>>> ...
>>> CopyFiles = atheros.CopyFiles, atheros_FW_3X.CopyFiles,
>>> atheros_BD_TX8.CopyFiles
>>> ...
>>>
>>> And "atheros_BD_TX8.CopyFiles" is:
>>>
>>> [atheros_BD_TX8.CopyFiles]
>>> eeprom_ar6320_3p0_TX8_clpc.bin,,,2
>>>
>>> The "windows\system32\driverstore\netathr10x" dir has a ton of
>>> eeprom files (let me know if you want a copy of the whole dir)
>>> including the mentioned one. Where as "windows\system32\drivers"
>>> only has the one eeprom_ar6320_3p0_TX8_clpc.bin eeprom... file,
>>> further indicating that that is the one actually being used.
>>>
>>> So this is the file which I've tested with and which is attached to this email as:
>>> "bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin"
>>>
>>> md5sum:
>>> bc52aa5640b27fa50f9d4d144f81e169
>>> bus=pci,vendor=168c,device=003e,subsystem-vendor=168c,subsystem-device=3370.bin
>>
>> I assume this is the same version as you submitted directly to
>> linux-firmware[1],
>
> Correct, note that my upstream linux-firmware submission contains
> 2 new board files. I've also submitted this to the ath10k-firmware repo here:
>
> https://github.com/kvalo/ath10k-firmware/pull/11
I see that you closed it also, thanks for that.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-01-24 9:06 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-08-24 16:44 ath10k-firmware: QCA6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 168c:3370 board file Hans de Goede
2022-01-21 14:16 ` Kalle Valo
2022-01-21 15:13 ` Hans de Goede
2022-01-24 9:05 ` Kalle Valo
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.