* ath10k fail to load firmware
@ 2016-07-19 7:09 Stanislaw Gruszka
2016-07-19 7:18 ` Michal Kazior
0 siblings, 1 reply; 25+ messages in thread
From: Stanislaw Gruszka @ 2016-07-19 7:09 UTC (permalink / raw)
To: Kalle Valo; +Cc: Michal Kazior, ath10k, perry_yuan
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
Perry from Dell has ath10k device, which do not work with current
linux-firmware. It's on RHEL kernel, however wirelss stack and drivers
are from 4.7-rc1 (I did not update to 4.7 final yet, since I do not see
ath10k fix, which could possibly help here). Partial dmesg is in
the attachment.
Thanks
Stanislaw
[-- Attachment #2: dmesg_ath10k_firmware_error.txt --]
[-- Type: text/plain, Size: 18769 bytes --]
[ 3657.824833] ath10k_pci 0000:01:00.0: irq 127 for MSI/MSI-X
[ 3657.824850] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 3658.026412] ath10k_pci 0000:01:00.0: Direct firmware load failed with error -2
[ 3658.026415] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 3718.215979] ath10k_pci 0000:01:00.0: Direct firmware load failed with error -2
[ 3718.215983] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 3778.377278] ath10k_pci 0000:01:00.0: Direct firmware load failed with error -2
[ 3778.377281] ath10k_pci 0000:01:00.0: Falling back to user helper
[ 3838.538737] ath10k_pci 0000:01:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[ 3838.539093] ath10k_pci 0000:01:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1028:0310
[ 3838.539096] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 3838.539676] ath10k_pci 0000:01:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data for bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device=0310 from ath10k/QCA6174/hw3.0/board-2.bin
[ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 ed5f849a
[ 3840.719768] ath10k_pci 0000:01:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 3840.774653] ath: EEPROM regdomain: 0x6c
[ 3840.774657] ath: EEPROM indicates we should expect a direct regpair map
[ 3840.774659] ath: Country alpha2 being used: 00
[ 3840.774660] ath: Regpair used: 0x6c
[ 3840.806880] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 3846.032903] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3849.032954] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3855.033103] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3860.316236] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 3866.316381] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3871.595515] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3874.595587] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3880.595733] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3885.878861] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3888.878966] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3894.879083] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3900.159214] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3903.159290] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3909.159436] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3914.441566] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3917.441639] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3923.441811] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3928.721921] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 3931.721989] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3937.722141] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3943.006271] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 3949.006419] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3954.289546] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 3957.289619] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3963.291067] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3968.595899] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3971.595972] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3977.596123] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3982.888250] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 3985.888324] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 3991.888474] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 3997.170623] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4000.170679] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4005.673217] usb 1-3: USB disconnect, device number 9
[ 4006.170824] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4011.453957] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 4017.454133] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4022.733233] ath10k_pci 0000:01:00.0: failed to enable adaptive qcs: -11
[ 4028.733380] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4034.014508] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4037.014584] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4043.014732] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4048.297860] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4051.297952] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4057.298086] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4062.582212] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 4068.582368] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4073.866492] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4076.866569] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4082.866730] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4088.145842] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4091.145914] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4097.146076] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4102.427194] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 4108.427367] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4113.708515] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4116.708558] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4122.708698] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4127.986823] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4130.986897] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4136.987045] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4142.269176] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4145.269248] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4151.269508] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4156.549528] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4159.549604] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4165.549748] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4170.829877] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4173.829952] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4179.830102] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4185.110229] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4188.110302] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4194.110449] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4199.390615] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4202.390653] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4208.390800] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4213.671964] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 4219.672080] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4224.951209] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4227.951283] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4233.951430] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4239.231565] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4242.231863] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4248.231786] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4253.512913] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4256.512987] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4262.513152] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4267.794282] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4270.794346] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4276.794486] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4282.077630] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4285.077694] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4291.077838] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4296.356967] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4299.357040] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4305.357187] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4310.637320] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 4316.637467] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4321.917596] ath10k_pci 0000:01:00.0: failed to enable dynamic BW: -11
[ 4327.917742] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4333.198873] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4335.383925] usb 1-3: new high-speed USB device number 10 using xhci_hcd
[ 4335.549396] usb 1-3: New USB device found, idVendor=0930, idProduct=6545
[ 4335.549400] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4335.549403] usb 1-3: Product: TransMemory
[ 4335.549405] usb 1-3: Manufacturer: TOSHIBA
[ 4335.549407] usb 1-3: SerialNumber: C03FD5FBC7ECE020B0006F57
[ 4335.550532] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 4335.552690] scsi host5: usb-storage 1-3:1.0
[ 4336.198950] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4336.555509] scsi 5:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 6
[ 4336.555860] sd 5:0:0:0: Attached scsi generic sg1 type 0
[ 4336.556179] sd 5:0:0:0: [sdd] 30253056 512-byte logical blocks: (15.4 GB/14.4 GiB)
[ 4336.556391] sd 5:0:0:0: [sdd] Write Protect is off
[ 4336.556395] sd 5:0:0:0: [sdd] Mode Sense: 45 00 00 00
[ 4336.556591] sd 5:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4336.610953] sdd: sdd1
[ 4336.612040] sd 5:0:0:0: [sdd] Attached SCSI removable disk
[ 4338.782315] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4342.199098] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4344.921485] FAT-fs (sdc1): FAT read failed (blocknr 988)
[ 4347.491288] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4350.491331] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4353.447107] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4356.035732] FAT-fs (sdc1): Directory bread(block 8192) failed
[ 4356.035737] FAT-fs (sdc1): Directory bread(block 8193) failed
[ 4356.035739] FAT-fs (sdc1): Directory bread(block 8194) failed
[ 4356.035741] FAT-fs (sdc1): Directory bread(block 8195) failed
[ 4356.035742] FAT-fs (sdc1): Directory bread(block 8196) failed
[ 4356.035744] FAT-fs (sdc1): Directory bread(block 8197) failed
[ 4356.035745] FAT-fs (sdc1): Directory bread(block 8198) failed
[ 4356.035746] FAT-fs (sdc1): Directory bread(block 8199) failed
[ 4356.035748] FAT-fs (sdc1): Directory bread(block 8200) failed
[ 4356.035749] FAT-fs (sdc1): Directory bread(block 8201) failed
[ 4356.491450] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4360.795098] usb 1-3: USB disconnect, device number 10
[ 4361.772579] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4361.978580] usb 1-3: new high-speed USB device number 11 using xhci_hcd
[ 4362.143504] usb 1-3: New USB device found, idVendor=0930, idProduct=6545
[ 4362.143509] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4362.143511] usb 1-3: Product: TransMemory
[ 4362.143513] usb 1-3: Manufacturer: TOSHIBA
[ 4362.143515] usb 1-3: SerialNumber: C03FD5FBC7ECE020B0006F57
[ 4362.144382] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 4362.144498] scsi host6: usb-storage 1-3:1.0
[ 4363.146215] scsi 6:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 6
[ 4363.146501] sd 6:0:0:0: Attached scsi generic sg1 type 0
[ 4363.147387] sd 6:0:0:0: [sdd] 30253056 512-byte logical blocks: (15.4 GB/14.4 GiB)
[ 4363.147606] sd 6:0:0:0: [sdd] Write Protect is off
[ 4363.147610] sd 6:0:0:0: [sdd] Mode Sense: 45 00 00 00
[ 4363.147824] sd 6:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4363.203504] sdd: sdd1
[ 4363.204555] sd 6:0:0:0: [sdd] Attached SCSI removable disk
[ 4363.386793] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4364.772651] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4365.018219] FAT-fs (sdc1): FAT read failed (blocknr 988)
[ 4370.772800] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4375.491274] fat__get_entry: 374 callbacks suppressed
[ 4375.491278] FAT-fs (sdc1): Directory bread(block 8192) failed
[ 4375.491283] FAT-fs (sdc1): Directory bread(block 8193) failed
[ 4375.491285] FAT-fs (sdc1): Directory bread(block 8194) failed
[ 4375.491287] FAT-fs (sdc1): Directory bread(block 8195) failed
[ 4375.491289] FAT-fs (sdc1): Directory bread(block 8196) failed
[ 4375.491291] FAT-fs (sdc1): Directory bread(block 8197) failed
[ 4375.491293] FAT-fs (sdc1): Directory bread(block 8198) failed
[ 4375.491295] FAT-fs (sdc1): Directory bread(block 8199) failed
[ 4375.491297] FAT-fs (sdc1): Directory bread(block 8200) failed
[ 4375.491299] FAT-fs (sdc1): Directory bread(block 8201) failed
[ 4376.076929] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[ 4379.077003] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4380.825017] fat__get_entry: 758 callbacks suppressed
[ 4380.825022] FAT-fs (sdc1): Directory bread(block 8192) failed
[ 4380.825025] FAT-fs (sdc1): Directory bread(block 8193) failed
[ 4380.825028] FAT-fs (sdc1): Directory bread(block 8194) failed
[ 4380.825030] FAT-fs (sdc1): Directory bread(block 8195) failed
[ 4380.825042] FAT-fs (sdc1): Directory bread(block 8196) failed
[ 4380.825045] FAT-fs (sdc1): Directory bread(block 8197) failed
[ 4380.825048] FAT-fs (sdc1): Directory bread(block 8198) failed
[ 4380.825051] FAT-fs (sdc1): Directory bread(block 8199) failed
[ 4380.825053] FAT-fs (sdc1): Directory bread(block 8200) failed
[ 4380.825055] FAT-fs (sdc1): Directory bread(block 8201) failed
[ 4381.253552] FAT-fs (sdd1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4385.077150] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4387.400123] fat__get_entry: 630 callbacks suppressed
[ 4387.400127] FAT-fs (sdc1): Directory bread(block 8192) failed
[ 4387.400131] FAT-fs (sdc1): Directory bread(block 8193) failed
[ 4387.400133] FAT-fs (sdc1): Directory bread(block 8194) failed
[ 4387.400135] FAT-fs (sdc1): Directory bread(block 8195) failed
[ 4387.400138] FAT-fs (sdc1): Directory bread(block 8196) failed
[ 4387.400140] FAT-fs (sdc1): Directory bread(block 8197) failed
[ 4387.400142] FAT-fs (sdc1): Directory bread(block 8198) failed
[ 4387.400144] FAT-fs (sdc1): Directory bread(block 8199) failed
[ 4387.400147] FAT-fs (sdc1): Directory bread(block 8200) failed
[ 4387.400149] FAT-fs (sdc1): Directory bread(block 8201) failed
[ 4390.359284] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4393.359353] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4399.359502] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4404.642633] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4407.642724] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4413.642887] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4414.220306] usb 1-3: USB disconnect, device number 11
[ 4418.959019] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4421.959090] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4427.959209] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4433.257338] ath10k_pci 0000:01:00.0: failed to set rx-chainmask: -11, req 0x3
[ 4436.257470] ath10k_pci 0000:01:00.0: failed to set arp ac override parameter: -11
[ 4438.436778] usb 1-3: new high-speed USB device number 12 using xhci_hcd
[ 4438.601141] usb 1-3: New USB device found, idVendor=0930, idProduct=6545
[ 4438.601145] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 4438.601146] usb 1-3: Product: TransMemory
[ 4438.601148] usb 1-3: Manufacturer: TOSHIBA
[ 4438.601149] usb 1-3: SerialNumber: C03FD5FBC7ECE020B0006F57
[ 4438.601617] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 4438.602075] scsi host7: usb-storage 1-3:1.0
[ 4439.604125] scsi 7:0:0:0: Direct-Access TOSHIBA TransMemory PMAP PQ: 0 ANSI: 6
[ 4439.604931] sd 7:0:0:0: Attached scsi generic sg1 type 0
[ 4439.605131] sd 7:0:0:0: [sde] 30253056 512-byte logical blocks: (15.4 GB/14.4 GiB)
[ 4439.605325] sd 7:0:0:0: [sde] Write Protect is off
[ 4439.605329] sd 7:0:0:0: [sde] Mode Sense: 45 00 00 00
[ 4439.605574] sd 7:0:0:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4439.666342] sde: sde1
[ 4439.667442] sd 7:0:0:0: [sde] Attached SCSI removable disk
[ 4439.860368] FAT-fs (sde1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 4441.095233] FAT-fs (sdd1): Directory bread(block 28256) failed
[ 4441.095237] FAT-fs (sdd1): Directory bread(block 28257) failed
[ 4441.095238] FAT-fs (sdd1): Directory bread(block 28258) failed
[ 4441.095240] FAT-fs (sdd1): Directory bread(block 28259) failed
[ 4441.095241] FAT-fs (sdd1): Directory bread(block 28260) failed
[ 4441.095242] FAT-fs (sdd1): Directory bread(block 28261) failed
[ 4441.095244] FAT-fs (sdd1): Directory bread(block 28262) failed
[ 4441.095245] FAT-fs (sdd1): Directory bread(block 28263) failed
[ 4441.095246] FAT-fs (sdd1): Directory bread(block 28264) failed
[ 4441.095247] FAT-fs (sdd1): Directory bread(block 28265) failed
[ 4442.257558] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 4447.592688] ath10k_pci 0000:01:00.0: failed to set tx-chainmask: -11, req 0x3
[-- 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] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 7:09 ath10k fail to load firmware Stanislaw Gruszka
@ 2016-07-19 7:18 ` Michal Kazior
2016-07-19 7:27 ` Stanislaw Gruszka
2016-08-02 12:10 ` Valo, Kalle
0 siblings, 2 replies; 25+ messages in thread
From: Michal Kazior @ 2016-07-19 7:18 UTC (permalink / raw)
To: Stanislaw Gruszka; +Cc: Kalle Valo, perry_yuan, ath10k
On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> Perry from Dell has ath10k device, which do not work with current
> linux-firmware. It's on RHEL kernel, however wirelss stack and drivers
> are from 4.7-rc1 (I did not update to 4.7 final yet, since I do not see
> ath10k fix, which could possibly help here). Partial dmesg is in
> the attachment.
hw.3 qca6174 chips tend to require very specific board data for proper
calibration.
[ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
for bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device=0310
from ath10k/QCA6174/hw3.0/board-2.bin
[ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
crc32 ed5f849a
Your board-2.bin doesn't contain the matching board data and the
driver then falls back to the older board API1 which is pretty much
doomed to fail on qca6174 hw.3.
@Kalle: Perhaps ath10k needs to fail early with an adequate message
for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
because this seems to be quite closely coupled with hardware itself).
@Stanislaw: You either need to grab a more recent board-2.bin
(https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
ask Kalle & wait, or cook up your own (if you really need it working
*now*) by getting Windows driver and dissecting it (the .inf file
contains enough information for you to map board data also referred to
as eeprom-something in the Windows blob).
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 7:18 ` Michal Kazior
@ 2016-07-19 7:27 ` Stanislaw Gruszka
2016-07-19 8:07 ` Perry_Yuan
` (3 more replies)
2016-08-02 12:10 ` Valo, Kalle
1 sibling, 4 replies; 25+ messages in thread
From: Stanislaw Gruszka @ 2016-07-19 7:27 UTC (permalink / raw)
To: Michal Kazior; +Cc: Kalle Valo, perry_yuan, ath10k
On Tue, Jul 19, 2016 at 09:18:01AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > Perry from Dell has ath10k device, which do not work with current
> > linux-firmware. It's on RHEL kernel, however wirelss stack and drivers
> > are from 4.7-rc1 (I did not update to 4.7 final yet, since I do not see
> > ath10k fix, which could possibly help here). Partial dmesg is in
> > the attachment.
>
> hw.3 qca6174 chips tend to require very specific board data for proper
> calibration.
>
> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
> for bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device=0310
> from ath10k/QCA6174/hw3.0/board-2.bin
> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 ed5f849a
>
> Your board-2.bin doesn't contain the matching board data and the
> driver then falls back to the older board API1 which is pretty much
> doomed to fail on qca6174 hw.3.
>
> @Kalle: Perhaps ath10k needs to fail early with an adequate message
> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
> because this seems to be quite closely coupled with hardware itself).
>
> @Stanislaw: You either need to grab a more recent board-2.bin
> (https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
@Perry, could you replace board-2.bin from above link on
/lib/firmware/ath10k/QCA6174/hw3.0/ and check if that work ?
> ask Kalle & wait, or cook up your own (if you really need it working
> *now*) by getting Windows driver and dissecting it (the .inf file
> contains enough information for you to map board data also referred to
> as eeprom-something in the Windows blob).
I think we can wait till firmware will be updated upstream, however
Dell would like to know if what we provide in new RHEL7 release
will work on their hardware.
Thanks
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 7:27 ` Stanislaw Gruszka
@ 2016-07-19 8:07 ` Perry_Yuan
2016-07-19 8:24 ` Perry_Yuan
` (2 subsequent siblings)
3 siblings, 0 replies; 25+ messages in thread
From: Perry_Yuan @ 2016-07-19 8:07 UTC (permalink / raw)
To: sgruszka, michal.kazior; +Cc: kvalo, ath10k
Dell - Internal Use - Confidential
Hi all:
I will try this firmware now . Give you feedback later.
(https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0)
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Stanislaw Gruszka [mailto:sgruszka@redhat.com]
Sent: Tuesday, July 19, 2016 3:28 PM
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Yuan, Perry <Perry_Yuan@Dell.com>
Subject: Re: ath10k fail to load firmware
On Tue, Jul 19, 2016 at 09:18:01AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > Perry from Dell has ath10k device, which do not work with current
> > linux-firmware. It's on RHEL kernel, however wirelss stack and
> > drivers are from 4.7-rc1 (I did not update to 4.7 final yet, since I
> > do not see ath10k fix, which could possibly help here). Partial
> > dmesg is in the attachment.
>
> hw.3 qca6174 chips tend to require very specific board data for proper
> calibration.
>
> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
> for
> bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device
> =0310
> from ath10k/QCA6174/hw3.0/board-2.bin
> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 ed5f849a
>
> Your board-2.bin doesn't contain the matching board data and the
> driver then falls back to the older board API1 which is pretty much
> doomed to fail on qca6174 hw.3.
>
> @Kalle: Perhaps ath10k needs to fail early with an adequate message
> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
> because this seems to be quite closely coupled with hardware itself).
>
> @Stanislaw: You either need to grab a more recent board-2.bin
> (https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
@Perry, could you replace board-2.bin from above link on /lib/firmware/ath10k/QCA6174/hw3.0/ and check if that work ?
> ask Kalle & wait, or cook up your own (if you really need it working
> *now*) by getting Windows driver and dissecting it (the .inf file
> contains enough information for you to map board data also referred to
> as eeprom-something in the Windows blob).
I think we can wait till firmware will be updated upstream, however Dell would like to know if what we provide in new RHEL7 release will work on their hardware.
Thanks
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 7:27 ` Stanislaw Gruszka
2016-07-19 8:07 ` Perry_Yuan
@ 2016-07-19 8:24 ` Perry_Yuan
2016-07-19 8:32 ` Michal Kazior
2016-07-29 7:45 ` Perry_Yuan
2016-07-29 9:07 ` Perry_Yuan
3 siblings, 1 reply; 25+ messages in thread
From: Perry_Yuan @ 2016-07-19 8:24 UTC (permalink / raw)
To: sgruszka, michal.kazior; +Cc: kvalo, ath10k
[-- Attachment #1: Type: text/plain, Size: 3115 bytes --]
Dell - Internal Use - Confidential
HI All:
I have replaced the new firmware files to old one. And I build new ath10k_pci.ko ,ath10k_core.ko to get some
debug info.
The new firmware is still not loaded by ath10k driver .
And I compare the driver codes with 4.7 -rc7 , the codes are almost same.
So the issue should be in firmware scope.
[ 590.486970] ath10k_pci 0000:02:00.0: Hardware name qca6174 hw3.2 version 0x5030000
[ 590.487158] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
[ 590.487159] ath10k_pci 0000:02:00.0: Falling back to user helper
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Stanislaw Gruszka [mailto:sgruszka@redhat.com]
Sent: Tuesday, July 19, 2016 3:28 PM
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Yuan, Perry <Perry_Yuan@Dell.com>
Subject: Re: ath10k fail to load firmware
On Tue, Jul 19, 2016 at 09:18:01AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > Perry from Dell has ath10k device, which do not work with current
> > linux-firmware. It's on RHEL kernel, however wirelss stack and
> > drivers are from 4.7-rc1 (I did not update to 4.7 final yet, since I
> > do not see ath10k fix, which could possibly help here). Partial
> > dmesg is in the attachment.
>
> hw.3 qca6174 chips tend to require very specific board data for proper
> calibration.
>
> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
> for
> bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device
> =0310
> from ath10k/QCA6174/hw3.0/board-2.bin
> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 ed5f849a
>
> Your board-2.bin doesn't contain the matching board data and the
> driver then falls back to the older board API1 which is pretty much
> doomed to fail on qca6174 hw.3.
>
> @Kalle: Perhaps ath10k needs to fail early with an adequate message
> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
> because this seems to be quite closely coupled with hardware itself).
>
> @Stanislaw: You either need to grab a more recent board-2.bin
> (https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
@Perry, could you replace board-2.bin from above link on /lib/firmware/ath10k/QCA6174/hw3.0/ and check if that work ?
> ask Kalle & wait, or cook up your own (if you really need it working
> *now*) by getting Windows driver and dissecting it (the .inf file
> contains enough information for you to map board data also referred to
> as eeprom-something in the Windows blob).
I think we can wait till firmware will be updated upstream, however Dell would like to know if what we provide in new RHEL7 release will work on their hardware.
Thanks
Stanislaw
[-- Attachment #2: ath10k_log_new_fw_1.txt --]
[-- Type: text/plain, Size: 7129 bytes --]
[ 590.269290] ath10k_pci 0000:02:00.0: pci probe 168c:003e 1028:0410
[ 590.270412] ath10k_pci 0000:02:00.0: boot pci_mem 0xffffc90004c00000
[ 590.278968] ath10k_pci 0000:02:00.0: irq 134 for MSI/MSI-X
[ 590.279207] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 590.279219] ath10k_pci 0000:02:00.0: boot qca6174 chip reset
[ 590.279220] ath10k_pci 0000:02:00.0: boot cold reset
[ 590.320444] ath10k_pci 0000:02:00.0: boot cold reset complete
[ 590.320446] ath10k_pci 0000:02:00.0: boot waiting target to initialise
[ 590.320607] ath10k_pci 0000:02:00.0: boot target indicator 2
[ 590.320753] ath10k_pci 0000:02:00.0: boot target initialised
[ 590.320753] ath10k_pci 0000:02:00.0: boot warm reset
[ 590.343475] ath10k_pci 0000:02:00.0: boot init ce src ring id 0 entries 16 base_addr ffff880039c20000
[ 590.344046] ath10k_pci 0000:02:00.0: boot ce dest ring id 1 entries 512 base_addr ffff880039c48000
[ 590.344160] ath10k_pci 0000:02:00.0: boot ce dest ring id 2 entries 128 base_addr ffff88001edd9000
[ 590.344271] ath10k_pci 0000:02:00.0: boot init ce src ring id 3 entries 32 base_addr ffff88001efdb000
[ 590.344390] ath10k_pci 0000:02:00.0: boot init ce src ring id 4 entries 8192 base_addr ffff880039ca0000
[ 590.344504] ath10k_pci 0000:02:00.0: boot init ce src ring id 7 entries 2 base_addr ffff88001ef97000
[ 590.345041] ath10k_pci 0000:02:00.0: boot ce dest ring id 7 entries 2 base_addr ffff880039c7f000
[ 590.345041] ath10k_pci 0000:02:00.0: boot waiting target to initialise
[ 590.345044] ath10k_pci 0000:02:00.0: boot target indicator 0
[ 590.355215] ath10k_pci 0000:02:00.0: boot target indicator 2
[ 590.355221] ath10k_pci 0000:02:00.0: boot target initialised
[ 590.367089] ath10k_pci 0000:02:00.0: boot init ce src ring id 0 entries 16 base_addr ffff880039c20000
[ 590.367203] ath10k_pci 0000:02:00.0: boot ce dest ring id 1 entries 512 base_addr ffff880039c48000
[ 590.367318] ath10k_pci 0000:02:00.0: boot ce dest ring id 2 entries 128 base_addr ffff88001edd9000
[ 590.367712] ath10k_pci 0000:02:00.0: boot init ce src ring id 3 entries 32 base_addr ffff88001efdb000
[ 590.368530] ath10k_pci 0000:02:00.0: boot init ce src ring id 4 entries 8192 base_addr ffff880039ca0000
[ 590.369392] ath10k_pci 0000:02:00.0: boot init ce src ring id 7 entries 2 base_addr ffff88001ef97000
[ 590.370143] ath10k_pci 0000:02:00.0: boot ce dest ring id 7 entries 2 base_addr ffff880039c7f000
[ 590.370143] ath10k_pci 0000:02:00.0: boot waiting target to initialise
[ 590.370300] ath10k_pci 0000:02:00.0: boot target indicator 0
[ 590.380463] ath10k_pci 0000:02:00.0: boot target indicator 2
[ 590.380761] ath10k_pci 0000:02:00.0: boot target initialised
[ 590.380762] ath10k_pci 0000:02:00.0: boot warm reset complete
[ 590.380763] ath10k_pci 0000:02:00.0: boot qca6174 chip reset complete (cold)
[ 590.380827] ath10k_pci 0000:02:00.0: boot hif power up
[ 590.381164] ath10k_pci 0000:02:00.0: boot qca6174 chip reset
[ 590.381165] ath10k_pci 0000:02:00.0: boot cold reset
[ 590.422506] ath10k_pci 0000:02:00.0: boot cold reset complete
[ 590.422510] ath10k_pci 0000:02:00.0: boot waiting target to initialise
[ 590.422513] ath10k_pci 0000:02:00.0: boot target indicator 2
[ 590.422518] ath10k_pci 0000:02:00.0: boot target initialised
[ 590.422519] ath10k_pci 0000:02:00.0: boot warm reset
[ 590.444457] ath10k_pci 0000:02:00.0: boot init ce src ring id 0 entries 16 base_addr ffff880039c20000
[ 590.444468] ath10k_pci 0000:02:00.0: boot ce dest ring id 1 entries 512 base_addr ffff880039c48000
[ 590.444492] ath10k_pci 0000:02:00.0: boot ce dest ring id 2 entries 128 base_addr ffff88001edd9000
[ 590.444504] ath10k_pci 0000:02:00.0: boot init ce src ring id 3 entries 32 base_addr ffff88001efdb000
[ 590.444517] ath10k_pci 0000:02:00.0: boot init ce src ring id 4 entries 8192 base_addr ffff880039ca0000
[ 590.444529] ath10k_pci 0000:02:00.0: boot init ce src ring id 7 entries 2 base_addr ffff88001ef97000
[ 590.444539] ath10k_pci 0000:02:00.0: boot ce dest ring id 7 entries 2 base_addr ffff880039c7f000
[ 590.444540] ath10k_pci 0000:02:00.0: boot waiting target to initialise
[ 590.444542] ath10k_pci 0000:02:00.0: boot target indicator 0
[ 590.454566] ath10k_pci 0000:02:00.0: boot target indicator 2
[ 590.454571] ath10k_pci 0000:02:00.0: boot target initialised
[ 590.465478] ath10k_pci 0000:02:00.0: boot init ce src ring id 0 entries 16 base_addr ffff880039c20000
[ 590.465489] ath10k_pci 0000:02:00.0: boot ce dest ring id 1 entries 512 base_addr ffff880039c48000
[ 590.465499] ath10k_pci 0000:02:00.0: boot ce dest ring id 2 entries 128 base_addr ffff88001edd9000
[ 590.465511] ath10k_pci 0000:02:00.0: boot init ce src ring id 3 entries 32 base_addr ffff88001efdb000
[ 590.465525] ath10k_pci 0000:02:00.0: boot init ce src ring id 4 entries 8192 base_addr ffff880039ca0000
[ 590.465537] ath10k_pci 0000:02:00.0: boot init ce src ring id 7 entries 2 base_addr ffff88001ef97000
[ 590.465546] ath10k_pci 0000:02:00.0: boot ce dest ring id 7 entries 2 base_addr ffff880039c7f000
[ 590.465547] ath10k_pci 0000:02:00.0: boot waiting target to initialise
[ 590.465550] ath10k_pci 0000:02:00.0: boot target indicator 0
[ 590.475553] ath10k_pci 0000:02:00.0: boot target indicator 2
[ 590.475558] ath10k_pci 0000:02:00.0: boot target initialised
[ 590.475559] ath10k_pci 0000:02:00.0: boot warm reset complete
[ 590.475560] ath10k_pci 0000:02:00.0: boot qca6174 chip reset complete (cold)
[ 590.475572] ath10k_pci 0000:02:00.0: boot init ce src ring id 0 entries 16 base_addr ffff880039c20000
[ 590.475582] ath10k_pci 0000:02:00.0: boot ce dest ring id 1 entries 512 base_addr ffff880039c48000
[ 590.475591] ath10k_pci 0000:02:00.0: boot ce dest ring id 2 entries 128 base_addr ffff88001edd9000
[ 590.475603] ath10k_pci 0000:02:00.0: boot init ce src ring id 3 entries 32 base_addr ffff88001efdb000
[ 590.475616] ath10k_pci 0000:02:00.0: boot init ce src ring id 4 entries 8192 base_addr ffff880039ca0000
[ 590.475628] ath10k_pci 0000:02:00.0: boot init ce src ring id 7 entries 2 base_addr ffff88001ef97000
[ 590.475637] ath10k_pci 0000:02:00.0: boot ce dest ring id 7 entries 2 base_addr ffff880039c7f000
[ 590.486970] ath10k_pci 0000:02:00.0: Hardware name qca6174 hw3.2 version 0x5030000
[ 590.487158] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
[ 590.487159] ath10k_pci 0000:02:00.0: Falling back to user helper
[ 650.495425] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
[ 650.495428] ath10k_pci 0000:02:00.0: Falling back to user helper
[ 710.656398] ath10k_pci 0000:02:00.0: trying fw api 5
[ 710.656739] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
[ 710.656740] ath10k_pci 0000:02:00.0: Falling back to user helper
[ 770.817912] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[ 770.817933] ath10k_pci 0000:02:00.0: trying fw api 4
[ 770.818273] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
[ 770.818274] ath10k_pci 0000:02:00.0: Falling back to user helper
[-- 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] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 8:24 ` Perry_Yuan
@ 2016-07-19 8:32 ` Michal Kazior
2016-07-19 9:02 ` Perry_Yuan
2016-08-02 12:19 ` Valo, Kalle
0 siblings, 2 replies; 25+ messages in thread
From: Michal Kazior @ 2016-07-19 8:32 UTC (permalink / raw)
To: Perry_Yuan; +Cc: Kalle Valo, Stanislaw Gruszka, ath10k
On 19 July 2016 at 10:24, <Perry_Yuan@dell.com> wrote:
> Dell - Internal Use - Confidential
>
> HI All:
> I have replaced the new firmware files to old one. And I build new ath10k_pci.ko ,ath10k_core.ko to get some
> debug info.
>
> The new firmware is still not loaded by ath10k driver .
> And I compare the driver codes with 4.7 -rc7 , the codes are almost same.
> So the issue should be in firmware scope.
>
> [ 590.486970] ath10k_pci 0000:02:00.0: Hardware name qca6174 hw3.2 version 0x5030000
> [ 590.487158] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
> [ 590.487159] ath10k_pci 0000:02:00.0: Falling back to user helper
You didn't attach a complete log so it's hard to tell. ath10k tends to
print a few messages that may look like an error but aren't (there's a
fallback mechanism for finding firmware files which is overly
verbose).
@Perry: You need to rename the
firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 to firmware-4.bin in case
you merely mirrored the github repo.
@Kalle: I think it'd be very useful to maintain ath10k-firmware in a
way so that it is easier to the uninitiated to `git clone` it into
/lib/firmware, e.g. maintain firmware-X.bin symlinks in each
QCAxxx/hw.y/ to the latest one. Thoughts?
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 8:32 ` Michal Kazior
@ 2016-07-19 9:02 ` Perry_Yuan
2016-07-19 9:17 ` Michal Kazior
2016-08-02 12:19 ` Valo, Kalle
1 sibling, 1 reply; 25+ messages in thread
From: Perry_Yuan @ 2016-07-19 9:02 UTC (permalink / raw)
To: michal.kazior; +Cc: kvalo, Yijun_Shen, sgruszka, ath10k
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
Dell - Internal Use - Confidential
I rename the bin file . and capture new full logs from booting to firmware error .
The error still happened. Please help to check it .
I want to know whether the new firmware bin are updated the right one in this git ?
If the firmware is good , the errors should be gone .
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Michal Kazior [mailto:michal.kazior@tieto.com]
Sent: Tuesday, July 19, 2016 4:33 PM
To: Yuan, Perry <Perry_Yuan@Dell.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>; Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org
Subject: Re: ath10k fail to load firmware
On 19 July 2016 at 10:24, <Perry_Yuan@dell.com> wrote:
> Dell - Internal Use - Confidential
>
> HI All:
> I have replaced the new firmware files to old one. And I build new
> ath10k_pci.ko ,ath10k_core.ko to get some debug info.
>
> The new firmware is still not loaded by ath10k driver .
> And I compare the driver codes with 4.7 -rc7 , the codes are almost same.
> So the issue should be in firmware scope.
>
> [ 590.486970] ath10k_pci 0000:02:00.0: Hardware name qca6174 hw3.2
> version 0x5030000 [ 590.487158] ath10k_pci 0000:02:00.0: Direct
> firmware load failed with error -2 [ 590.487159] ath10k_pci
> 0000:02:00.0: Falling back to user helper
You didn't attach a complete log so it's hard to tell. ath10k tends to print a few messages that may look like an error but aren't (there's a fallback mechanism for finding firmware files which is overly verbose).
@Perry: You need to rename the
firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 to firmware-4.bin in case you merely mirrored the github repo.
@Kalle: I think it'd be very useful to maintain ath10k-firmware in a way so that it is easier to the uninitiated to `git clone` it into /lib/firmware, e.g. maintain firmware-X.bin symlinks in each QCAxxx/hw.y/ to the latest one. Thoughts?
Michał
[-- Attachment #2: logs-ath10k.zip --]
[-- Type: application/x-zip-compressed, Size: 38749 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] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 9:02 ` Perry_Yuan
@ 2016-07-19 9:17 ` Michal Kazior
2016-07-19 9:27 ` Stanislaw Gruszka
0 siblings, 1 reply; 25+ messages in thread
From: Michal Kazior @ 2016-07-19 9:17 UTC (permalink / raw)
To: Perry_Yuan; +Cc: Kalle Valo, Yijun_Shen, Stanislaw Gruszka, ath10k
On 19 July 2016 at 11:02, <Perry_Yuan@dell.com> wrote:
> Dell - Internal Use - Confidential
>
> I rename the bin file . and capture new full logs from booting to firmware error .
> The error still happened. Please help to check it .
> I want to know whether the new firmware bin are updated the right one in this git ?
> If the firmware is good , the errors should be gone .
Thanks for checking!
Apparently the available board-2.bin doesn't contain any subsystem
vendor=1028 board data (just checked).
Also, you guys (i.e. Perry & Stanislaw) seem to be using 2 slightly
different devices. One reports its subsystem ids as 1028:0310 (in the
original log Stanislaw provided) and 1028:0410 (found in logs attached
by Perry).
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 9:17 ` Michal Kazior
@ 2016-07-19 9:27 ` Stanislaw Gruszka
2016-07-19 9:41 ` Perry_Yuan
2016-07-20 3:14 ` Perry_Yuan
0 siblings, 2 replies; 25+ messages in thread
From: Stanislaw Gruszka @ 2016-07-19 9:27 UTC (permalink / raw)
To: Michal Kazior; +Cc: Kalle Valo, Yijun_Shen, Perry_Yuan, ath10k
On Tue, Jul 19, 2016 at 11:17:03AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 11:02, <Perry_Yuan@dell.com> wrote:
> > Dell - Internal Use - Confidential
> >
> > I rename the bin file . and capture new full logs from booting to firmware error .
> > The error still happened. Please help to check it .
> > I want to know whether the new firmware bin are updated the right one in this git ?
> > If the firmware is good , the errors should be gone .
Please use reply-to-all, so I could see messages. You can drop ML
eventually if you thing your data is confidential.
> Thanks for checking!
>
> Apparently the available board-2.bin doesn't contain any subsystem
> vendor=1028 board data (just checked).
>
> Also, you guys (i.e. Perry & Stanislaw) seem to be using 2 slightly
> different devices. One reports its subsystem ids as 1028:0310 (in the
> original log Stanislaw provided) and 1028:0410 (found in logs attached
> by Perry).
I provided dmesg, which I get from Perry, hence seems that Perry tests
on 2 different devices :-)
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 9:27 ` Stanislaw Gruszka
@ 2016-07-19 9:41 ` Perry_Yuan
2016-07-20 3:14 ` Perry_Yuan
1 sibling, 0 replies; 25+ messages in thread
From: Perry_Yuan @ 2016-07-19 9:41 UTC (permalink / raw)
To: sgruszka, michal.kazior; +Cc: kvalo, Yijun_Shen, ath10k
Dell - Internal Use - Confidential
Yeah , I provide the logs from two system . but I don't notice the wireless card system ID is different .
In my opinion . even the subsystem ID is not same . at least one wireless car should work well .
The two cards all not working with current firmware .
So could you tell me how to make it available ?
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Stanislaw Gruszka [mailto:sgruszka@redhat.com]
Sent: Tuesday, July 19, 2016 5:27 PM
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Yuan, Perry <Perry_Yuan@Dell.com>; Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Shen, Yijun <Yijun_Shen@Dell.com>
Subject: Re: ath10k fail to load firmware
On Tue, Jul 19, 2016 at 11:17:03AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 11:02, <Perry_Yuan@dell.com> wrote:
> > Dell - Internal Use - Confidential
> >
> > I rename the bin file . and capture new full logs from booting to firmware error .
> > The error still happened. Please help to check it .
> > I want to know whether the new firmware bin are updated the right one in this git ?
> > If the firmware is good , the errors should be gone .
Please use reply-to-all, so I could see messages. You can drop ML eventually if you thing your data is confidential.
> Thanks for checking!
>
> Apparently the available board-2.bin doesn't contain any subsystem
> vendor=1028 board data (just checked).
>
> Also, you guys (i.e. Perry & Stanislaw) seem to be using 2 slightly
> different devices. One reports its subsystem ids as 1028:0310 (in the
> original log Stanislaw provided) and 1028:0410 (found in logs attached
> by Perry).
I provided dmesg, which I get from Perry, hence seems that Perry tests on 2 different devices :-)
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 9:27 ` Stanislaw Gruszka
2016-07-19 9:41 ` Perry_Yuan
@ 2016-07-20 3:14 ` Perry_Yuan
2016-07-20 6:58 ` Michal Kazior
1 sibling, 1 reply; 25+ messages in thread
From: Perry_Yuan @ 2016-07-20 3:14 UTC (permalink / raw)
To: sgruszka, michal.kazior; +Cc: kvalo, Yijun_Shen, ath10k, Jared_Dominguez
Dell - Internal Use - Confidential
Add Jared
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Stanislaw Gruszka [mailto:sgruszka@redhat.com]
Sent: Tuesday, July 19, 2016 5:27 PM
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Yuan, Perry <Perry_Yuan@Dell.com>; Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Shen, Yijun <Yijun_Shen@Dell.com>
Subject: Re: ath10k fail to load firmware
On Tue, Jul 19, 2016 at 11:17:03AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 11:02, <Perry_Yuan@dell.com> wrote:
> > Dell - Internal Use - Confidential
> >
> > I rename the bin file . and capture new full logs from booting to firmware error .
> > The error still happened. Please help to check it .
> > I want to know whether the new firmware bin are updated the right one in this git ?
> > If the firmware is good , the errors should be gone .
Please use reply-to-all, so I could see messages. You can drop ML eventually if you thing your data is confidential.
> Thanks for checking!
>
> Apparently the available board-2.bin doesn't contain any subsystem
> vendor=1028 board data (just checked).
>
> Also, you guys (i.e. Perry & Stanislaw) seem to be using 2 slightly
> different devices. One reports its subsystem ids as 1028:0310 (in the
> original log Stanislaw provided) and 1028:0410 (found in logs attached
> by Perry).
I provided dmesg, which I get from Perry, hence seems that Perry tests on 2 different devices :-)
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-20 3:14 ` Perry_Yuan
@ 2016-07-20 6:58 ` Michal Kazior
2016-07-20 7:23 ` Perry_Yuan
[not found] ` <A3D794F1192BBF449DF2EC3D7EE263F44A5402F40A@SHAX7MCDC101.APAC.DELL.COM>
0 siblings, 2 replies; 25+ messages in thread
From: Michal Kazior @ 2016-07-20 6:58 UTC (permalink / raw)
To: Perry_Yuan
Cc: Kalle Valo, Yijun_Shen, Stanislaw Gruszka, ath10k, Jared_Dominguez
Hi Perry,
I've been told that Dell apparently maintains their subsystem ids
independently (from QCA). You should probably ask your Windows driver
team (or whoever is responsible for the subsystem id stuff at Dell)
for subsystem ids and board/eeprom files associated with them and then
provide them on ath10k mailing list so Kalle can add them to
board-2.bin.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-20 6:58 ` Michal Kazior
@ 2016-07-20 7:23 ` Perry_Yuan
[not found] ` <A3D794F1192BBF449DF2EC3D7EE263F44A5402F40A@SHAX7MCDC101.APAC.DELL.COM>
1 sibling, 0 replies; 25+ messages in thread
From: Perry_Yuan @ 2016-07-20 7:23 UTC (permalink / raw)
To: michal.kazior; +Cc: kvalo, Yijun_Shen, sgruszka, ath10k, Jared_Dominguez
Dell - Internal Use - Confidential
Hi Michal:
I will contact with Windows driver team to get the right board-2.bin file .
Thanks a lot .
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Michal Kazior [mailto:michal.kazior@tieto.com]
Sent: Wednesday, July 20, 2016 2:58 PM
To: Yuan, Perry <Perry_Yuan@Dell.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>; Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Shen, Yijun <Yijun_Shen@Dell.com>; Dominguez, Jared <Jared_Dominguez@DELL.com>
Subject: Re: ath10k fail to load firmware
Hi Perry,
I've been told that Dell apparently maintains their subsystem ids independently (from QCA). You should probably ask your Windows driver team (or whoever is responsible for the subsystem id stuff at Dell) for subsystem ids and board/eeprom files associated with them and then provide them on ath10k mailing list so Kalle can add them to board-2.bin.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
[not found] ` <A3D794F1192BBF449DF2EC3D7EE263F44A5402F40A@SHAX7MCDC101.APAC.DELL.COM>
@ 2016-07-25 10:25 ` Michal Kazior
0 siblings, 0 replies; 25+ messages in thread
From: Michal Kazior @ 2016-07-25 10:25 UTC (permalink / raw)
To: Perry_Yuan
Cc: Kalle Valo, Yijun_Shen, Stanislaw Gruszka, ath10k, Jared_Dominguez
On 21 July 2016 at 03:24, <Perry_Yuan@dell.com> wrote:
> HI All:
>
> I got two board files for subsystem id 0310 .
>
> eeprom_ar6320_3p0_NFA344A_power1213_DE_5459.bin
> eeprom_ar6320_3p0_NFA344A_power1213.bin
>
> But I am not sure which files should be used , and I want know which board
> file should be replaced.
>
> In the /lib/firmware/ath10k/QCA6174/hw3.0/ directory , I found two file
> named “ board.bin” and ” board-2.bin “
Remove board-2.bin and copy eeprom_ar6320_3p0_NFA344A_power1213.bin as
board.bin. If it doesn't work try
eeprom_ar6320_3p0_NFA344A_power1213_DE_5459.bin as board.bin.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 7:27 ` Stanislaw Gruszka
2016-07-19 8:07 ` Perry_Yuan
2016-07-19 8:24 ` Perry_Yuan
@ 2016-07-29 7:45 ` Perry_Yuan
2016-07-29 9:07 ` Perry_Yuan
3 siblings, 0 replies; 25+ messages in thread
From: Perry_Yuan @ 2016-07-29 7:45 UTC (permalink / raw)
To: sgruszka, michal.kazior; +Cc: David_D_Wang, karl, kvalo, Yijun_Shen, ath10k
Dell - No Restrictions - Confidential
HI Stanislaw:
Now we have got the available firmware for DW1820 wireless card ,but we found one new problem .
I built upstream 4.6.4 and 4.7 kernel code and install the kernel images , the wireless driver can work , which means I can get IP address and ping external network successfully .
But it cannot work with RHEL 7.3 test kernel kernel-3.10.0-473.el7.x86_64.rpm . This kernel will occur panic frequently .
Even system can get IP address from AP . but it cannot ping external network .
So I would think the backport driver have some issue .
I have found some differences with upstream 4.7 kernel code where you do backport . I will provide the kernel panic log later .
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Stanislaw Gruszka [mailto:sgruszka@redhat.com]
Sent: Tuesday, July 19, 2016 3:28 PM
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Yuan, Perry <Perry_Yuan@Dell.com>
Subject: Re: ath10k fail to load firmware
On Tue, Jul 19, 2016 at 09:18:01AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > Perry from Dell has ath10k device, which do not work with current
> > linux-firmware. It's on RHEL kernel, however wirelss stack and
> > drivers are from 4.7-rc1 (I did not update to 4.7 final yet, since I
> > do not see ath10k fix, which could possibly help here). Partial
> > dmesg is in the attachment.
>
> hw.3 qca6174 chips tend to require very specific board data for proper
> calibration.
>
> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
> for
> bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device
> =0310
> from ath10k/QCA6174/hw3.0/board-2.bin
> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 ed5f849a
>
> Your board-2.bin doesn't contain the matching board data and the
> driver then falls back to the older board API1 which is pretty much
> doomed to fail on qca6174 hw.3.
>
> @Kalle: Perhaps ath10k needs to fail early with an adequate message
> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
> because this seems to be quite closely coupled with hardware itself).
>
> @Stanislaw: You either need to grab a more recent board-2.bin
> (https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
@Perry, could you replace board-2.bin from above link on /lib/firmware/ath10k/QCA6174/hw3.0/ and check if that work ?
> ask Kalle & wait, or cook up your own (if you really need it working
> *now*) by getting Windows driver and dissecting it (the .inf file
> contains enough information for you to map board data also referred to
> as eeprom-something in the Windows blob).
I think we can wait till firmware will be updated upstream, however Dell would like to know if what we provide in new RHEL7 release will work on their hardware.
Thanks
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* RE: ath10k fail to load firmware
2016-07-19 7:27 ` Stanislaw Gruszka
` (2 preceding siblings ...)
2016-07-29 7:45 ` Perry_Yuan
@ 2016-07-29 9:07 ` Perry_Yuan
3 siblings, 0 replies; 25+ messages in thread
From: Perry_Yuan @ 2016-07-29 9:07 UTC (permalink / raw)
To: sgruszka, michal.kazior; +Cc: David_D_Wang, karl, kvalo, Yijun_Shen, ath10k
Hi Stanislaw:
We got the right firmware but the kernel kernel-3.10.0-473.el7.x86_64.rpm is still not working at all .
In order to fix the issue for DW1820 . I am afraid that you have to merge the below patches for RHEL7.3 kernel. I have verified those patches . DW1820 card driver is working well on -473 kernel now .
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e50525bef593c3dd0564df676c567d77f7c20322
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8d0a0710ea0d22881fdb40eb79d346a98cc64ae6
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fee48cf8374569a3888fd8c8536283e6067f0cfb
Thanks .
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer
office +86 21 22030689, mobile +86 18521512823
perry_yuan@dell.com
Please consider the environment before printing this email.
-----Original Message-----
From: Yuan, Perry
Sent: Friday, July 29, 2016 3:45 PM
To: 'Stanislaw Gruszka' <sgruszka@redhat.com>; Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Shen, Yijun <Yijun_Shen@Dell.com>; David D Wang (David_D_Wang@dell.com) <David_D_Wang@dell.com>; Karl Hastings <karl@redhat.com>
Subject: RE: ath10k fail to load firmware
Dell - No Restrictions - Confidential
HI Stanislaw:
Now we have got the available firmware for DW1820 wireless card ,but we found one new problem .
I built upstream 4.6.4 and 4.7 kernel code and install the kernel images , the wireless driver can work , which means I can get IP address and ping external network successfully .
But it cannot work with RHEL 7.3 test kernel kernel-3.10.0-473.el7.x86_64.rpm . This kernel will occur panic frequently .
Even system can get IP address from AP . but it cannot ping external network .
So I would think the backport driver have some issue .
I have found some differences with upstream 4.7 kernel code where you do backport . I will provide the kernel panic log later .
keep up the good work
Perry Yuan
Dell | Client Software Group | Platform Sftwr Senior Engineer office +86 21 22030689, mobile +86 18521512823 perry_yuan@dell.com Please consider the environment before printing this email.
-----Original Message-----
From: Stanislaw Gruszka [mailto:sgruszka@redhat.com]
Sent: Tuesday, July 19, 2016 3:28 PM
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>; ath10k@lists.infradead.org; Yuan, Perry <Perry_Yuan@Dell.com>
Subject: Re: ath10k fail to load firmware
On Tue, Jul 19, 2016 at 09:18:01AM +0200, Michal Kazior wrote:
> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
> > Perry from Dell has ath10k device, which do not work with current
> > linux-firmware. It's on RHEL kernel, however wirelss stack and
> > drivers are from 4.7-rc1 (I did not update to 4.7 final yet, since I
> > do not see ath10k fix, which could possibly help here). Partial
> > dmesg is in the attachment.
>
> hw.3 qca6174 chips tend to require very specific board data for proper
> calibration.
>
> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
> for
> bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device
> =0310
> from ath10k/QCA6174/hw3.0/board-2.bin
> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 ed5f849a
>
> Your board-2.bin doesn't contain the matching board data and the
> driver then falls back to the older board API1 which is pretty much
> doomed to fail on qca6174 hw.3.
>
> @Kalle: Perhaps ath10k needs to fail early with an adequate message
> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
> because this seems to be quite closely coupled with hardware itself).
>
> @Stanislaw: You either need to grab a more recent board-2.bin
> (https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
@Perry, could you replace board-2.bin from above link on /lib/firmware/ath10k/QCA6174/hw3.0/ and check if that work ?
> ask Kalle & wait, or cook up your own (if you really need it working
> *now*) by getting Windows driver and dissecting it (the .inf file
> contains enough information for you to map board data also referred to
> as eeprom-something in the Windows blob).
I think we can wait till firmware will be updated upstream, however Dell would like to know if what we provide in new RHEL7 release will work on their hardware.
Thanks
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 7:18 ` Michal Kazior
2016-07-19 7:27 ` Stanislaw Gruszka
@ 2016-08-02 12:10 ` Valo, Kalle
2016-08-03 7:00 ` Michal Kazior
2016-08-22 8:40 ` Stanislaw Gruszka
1 sibling, 2 replies; 25+ messages in thread
From: Valo, Kalle @ 2016-08-02 12:10 UTC (permalink / raw)
To: michal.kazior; +Cc: Stanislaw Gruszka, perry_yuan, ath10k
Michal Kazior <michal.kazior@tieto.com> writes:
> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
>> Perry from Dell has ath10k device, which do not work with current
>> linux-firmware. It's on RHEL kernel, however wirelss stack and drivers
>> are from 4.7-rc1 (I did not update to 4.7 final yet, since I do not see
>> ath10k fix, which could possibly help here). Partial dmesg is in
>> the attachment.
>
> hw.3 qca6174 chips tend to require very specific board data for proper
> calibration.
>
> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
> for bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device=0310
> from ath10k/QCA6174/hw3.0/board-2.bin
> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
> crc32 ed5f849a
>
> Your board-2.bin doesn't contain the matching board data and the
> driver then falls back to the older board API1 which is pretty much
> doomed to fail on qca6174 hw.3.
>
> @Kalle: Perhaps ath10k needs to fail early with an adequate message
> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
> because this seems to be quite closely coupled with hardware itself).
Sounds like a good idea. Or maybe we should always fail when using
board-2.bin (no matter what hw version is used)? Dunno.
> @Stanislaw: You either need to grab a more recent board-2.bin
> (https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0),
> ask Kalle & wait, or cook up your own (if you really need it working
> *now*) by getting Windows driver and dissecting it (the .inf file
> contains enough information for you to map board data also referred to
> as eeprom-something in the Windows blob).
I pushed a new board-2.bin:
https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-07-19 8:32 ` Michal Kazior
2016-07-19 9:02 ` Perry_Yuan
@ 2016-08-02 12:19 ` Valo, Kalle
1 sibling, 0 replies; 25+ messages in thread
From: Valo, Kalle @ 2016-08-02 12:19 UTC (permalink / raw)
To: michal.kazior; +Cc: Stanislaw Gruszka, Perry_Yuan, ath10k
Michal Kazior <michal.kazior@tieto.com> writes:
> On 19 July 2016 at 10:24, <Perry_Yuan@dell.com> wrote:
>> Dell - Internal Use - Confidential
>>
>> HI All:
>> I have replaced the new firmware files to old one. And I build new ath10k_pci.ko ,ath10k_core.ko to get some
>> debug info.
>>
>> The new firmware is still not loaded by ath10k driver .
>> And I compare the driver codes with 4.7 -rc7 , the codes are almost same.
>> So the issue should be in firmware scope.
>>
>> [ 590.486970] ath10k_pci 0000:02:00.0: Hardware name qca6174 hw3.2 version 0x5030000
>> [ 590.487158] ath10k_pci 0000:02:00.0: Direct firmware load failed with error -2
>> [ 590.487159] ath10k_pci 0000:02:00.0: Falling back to user helper
>
> You didn't attach a complete log so it's hard to tell. ath10k tends to
> print a few messages that may look like an error but aren't (there's a
> fallback mechanism for finding firmware files which is overly
> verbose).
>
> @Perry: You need to rename the
> firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 to firmware-4.bin in case
> you merely mirrored the github repo.
>
> @Kalle: I think it'd be very useful to maintain ath10k-firmware in a
> way so that it is easier to the uninitiated to `git clone` it into
> /lib/firmware, e.g. maintain firmware-X.bin symlinks in each
> QCAxxx/hw.y/ to the latest one. Thoughts?
Yeah, something like that would be really nice. It would also make it
easier for me to update linux-firmware.git.
What about if we had a script which installs the latest ath10k firmware
files from ath10k-firmware.git? Something along lines of:
$ cd ~/git/ath10k-firmware
$ git pull
$ sudo ath10k-fw-install /lib/firmware/ath10k
I could also add a simple menu to select older firmware versions. But
this is just a wild idea.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-02 12:10 ` Valo, Kalle
@ 2016-08-03 7:00 ` Michal Kazior
2016-08-22 8:40 ` Stanislaw Gruszka
1 sibling, 0 replies; 25+ messages in thread
From: Michal Kazior @ 2016-08-03 7:00 UTC (permalink / raw)
To: Valo, Kalle; +Cc: Stanislaw Gruszka, perry_yuan, ath10k
On 2 August 2016 at 14:10, Valo, Kalle <kvalo@qca.qualcomm.com> wrote:
> Michal Kazior <michal.kazior@tieto.com> writes:
>
>> On 19 July 2016 at 09:09, Stanislaw Gruszka <sgruszka@redhat.com> wrote:
>>> Perry from Dell has ath10k device, which do not work with current
>>> linux-firmware. It's on RHEL kernel, however wirelss stack and drivers
>>> are from 4.7-rc1 (I did not update to 4.7 final yet, since I do not see
>>> ath10k fix, which could possibly help here). Partial dmesg is in
>>> the attachment.
>>
>> hw.3 qca6174 chips tend to require very specific board data for proper
>> calibration.
>>
>> [ 3838.601884] ath10k_pci 0000:01:00.0: failed to fetch board data
>> for bus=pci,vendor=168c,device=003e,subsystem-vendor=1028,subsystem-device=0310
>> from ath10k/QCA6174/hw3.0/board-2.bin
>> [ 3838.601920] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A
>> crc32 ed5f849a
>>
>> Your board-2.bin doesn't contain the matching board data and the
>> driver then falls back to the older board API1 which is pretty much
>> doomed to fail on qca6174 hw.3.
>>
>> @Kalle: Perhaps ath10k needs to fail early with an adequate message
>> for qca6174 hw.3 if board API2 lookup fails (e.g. hw_params flag
>> because this seems to be quite closely coupled with hardware itself).
>
> Sounds like a good idea. Or maybe we should always fail when using
> board-2.bin (no matter what hw version is used)? Dunno.
Hmm, failing if no matching entry is found in board-2.bin sounds good
but doesn't cover the case when user doesn't even have board-2.bin in
the first place.
The downside of forcing board-2.bin for qca6174 hw3.2+ would be more
difficult one-shot testing via board.bin (it's easier to copy eeprom*
file from windows driver as board.bin than to re-generate board-2.bin)
- but maybe this isn't really something we should care about so much
to allow board.bin for hw that normally can't work with it.
Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-02 12:10 ` Valo, Kalle
2016-08-03 7:00 ` Michal Kazior
@ 2016-08-22 8:40 ` Stanislaw Gruszka
2016-08-22 10:29 ` Valo, Kalle
1 sibling, 1 reply; 25+ messages in thread
From: Stanislaw Gruszka @ 2016-08-22 8:40 UTC (permalink / raw)
To: Valo, Kalle; +Cc: michal.kazior, ath10k, perry_yuan
On Tue, Aug 02, 2016 at 12:10:46PM +0000, Valo, Kalle wrote:
> I pushed a new board-2.bin:
>
> https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
Kalle, when do you plan to propagate this to upstream linux-firmware ?
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-22 8:40 ` Stanislaw Gruszka
@ 2016-08-22 10:29 ` Valo, Kalle
2016-08-22 11:02 ` Stanislaw Gruszka
0 siblings, 1 reply; 25+ messages in thread
From: Valo, Kalle @ 2016-08-22 10:29 UTC (permalink / raw)
To: Stanislaw Gruszka; +Cc: michal.kazior, ath10k, perry_yuan
Stanislaw Gruszka <sgruszka@redhat.com> writes:
> On Tue, Aug 02, 2016 at 12:10:46PM +0000, Valo, Kalle wrote:
>> I pushed a new board-2.bin:
>>
>> https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
>
> Kalle, when do you plan to propagate this to upstream linux-firmware ?
I usually send firmware updates to linux-firmware in a bigger update. I
have quite a lot of patches pending so I wasn't planning to do it quite
not yet.
Why are you asking, is this urgent?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-22 10:29 ` Valo, Kalle
@ 2016-08-22 11:02 ` Stanislaw Gruszka
2016-08-22 14:05 ` Valo, Kalle
0 siblings, 1 reply; 25+ messages in thread
From: Stanislaw Gruszka @ 2016-08-22 11:02 UTC (permalink / raw)
To: Valo, Kalle; +Cc: Yijun_Shen@Dell.com, michal.kazior, ath10k, perry_yuan
On Mon, Aug 22, 2016 at 10:29:24AM +0000, Valo, Kalle wrote:
> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>
> > On Tue, Aug 02, 2016 at 12:10:46PM +0000, Valo, Kalle wrote:
> >> I pushed a new board-2.bin:
> >>
> >> https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
> >
> > Kalle, when do you plan to propagate this to upstream linux-firmware ?
>
> I usually send firmware updates to linux-firmware in a bigger update. I
> have quite a lot of patches pending so I wasn't planning to do it quite
> not yet.
>
> Why are you asking, is this urgent?
Well, we want to add support to Dell ath10k devices to our system,
but we are also a bit reluctant to have difference between
linux-firmware package in our system and upstream linux-firmware
git tree. Could you post just board-2.bin changes upstream soon ?
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-22 11:02 ` Stanislaw Gruszka
@ 2016-08-22 14:05 ` Valo, Kalle
2016-08-23 18:55 ` Valo, Kalle
0 siblings, 1 reply; 25+ messages in thread
From: Valo, Kalle @ 2016-08-22 14:05 UTC (permalink / raw)
To: Stanislaw Gruszka; +Cc: Yijun_Shen@Dell.com, michal.kazior, ath10k, perry_yuan
Stanislaw Gruszka <sgruszka@redhat.com> writes:
> On Mon, Aug 22, 2016 at 10:29:24AM +0000, Valo, Kalle wrote:
>> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>>
>> > On Tue, Aug 02, 2016 at 12:10:46PM +0000, Valo, Kalle wrote:
>> >> I pushed a new board-2.bin:
>> >>
>> >> https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
>> >
>> > Kalle, when do you plan to propagate this to upstream linux-firmware ?
>>
>> I usually send firmware updates to linux-firmware in a bigger update. I
>> have quite a lot of patches pending so I wasn't planning to do it quite
>> not yet.
>>
>> Why are you asking, is this urgent?
>
> Well, we want to add support to Dell ath10k devices to our system,
> but we are also a bit reluctant to have difference between
> linux-firmware package in our system and upstream linux-firmware
> git tree. Could you post just board-2.bin changes upstream soon ?
Ok. I'll try to do it tomorrow.
I'll also implement a script to help with that so that I don't need to
do so much manual work and can update the firmware images more often.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-22 14:05 ` Valo, Kalle
@ 2016-08-23 18:55 ` Valo, Kalle
2016-08-24 6:33 ` Stanislaw Gruszka
0 siblings, 1 reply; 25+ messages in thread
From: Valo, Kalle @ 2016-08-23 18:55 UTC (permalink / raw)
To: Stanislaw Gruszka; +Cc: Yijun_Shen@Dell.com, michal.kazior, ath10k, perry_yuan
"Valo, Kalle" <kvalo@qca.qualcomm.com> writes:
> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>
>> On Mon, Aug 22, 2016 at 10:29:24AM +0000, Valo, Kalle wrote:
>>> Stanislaw Gruszka <sgruszka@redhat.com> writes:
>>>
>>> > On Tue, Aug 02, 2016 at 12:10:46PM +0000, Valo, Kalle wrote:
>>> >> I pushed a new board-2.bin:
>>> >>
>>> >> https://github.com/kvalo/ath10k-firmware/commit/7c0411643b195b246d3871f409f9219f528b39c1
>>> >
>>> > Kalle, when do you plan to propagate this to upstream linux-firmware ?
>>>
>>> I usually send firmware updates to linux-firmware in a bigger update. I
>>> have quite a lot of patches pending so I wasn't planning to do it quite
>>> not yet.
>>>
>>> Why are you asking, is this urgent?
>>
>> Well, we want to add support to Dell ath10k devices to our system,
>> but we are also a bit reluctant to have difference between
>> linux-firmware package in our system and upstream linux-firmware
>> git tree. Could you post just board-2.bin changes upstream soon ?
>
> Ok. I'll try to do it tomorrow.
>
> I'll also implement a script to help with that so that I don't need to
> do so much manual work and can update the firmware images more often.
I submitted it now:
http://marc.info/?l=linux-wireless&m=147197824810492
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: ath10k fail to load firmware
2016-08-23 18:55 ` Valo, Kalle
@ 2016-08-24 6:33 ` Stanislaw Gruszka
0 siblings, 0 replies; 25+ messages in thread
From: Stanislaw Gruszka @ 2016-08-24 6:33 UTC (permalink / raw)
To: Valo, Kalle; +Cc: Yijun_Shen@Dell.com, michal.kazior, ath10k, perry_yuan
On Tue, Aug 23, 2016 at 06:55:53PM +0000, Valo, Kalle wrote:
> I submitted it now:
>
> http://marc.info/?l=linux-wireless&m=147197824810492
Thanks!
Stanislaw
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2016-08-24 6:37 UTC | newest]
Thread overview: 25+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-19 7:09 ath10k fail to load firmware Stanislaw Gruszka
2016-07-19 7:18 ` Michal Kazior
2016-07-19 7:27 ` Stanislaw Gruszka
2016-07-19 8:07 ` Perry_Yuan
2016-07-19 8:24 ` Perry_Yuan
2016-07-19 8:32 ` Michal Kazior
2016-07-19 9:02 ` Perry_Yuan
2016-07-19 9:17 ` Michal Kazior
2016-07-19 9:27 ` Stanislaw Gruszka
2016-07-19 9:41 ` Perry_Yuan
2016-07-20 3:14 ` Perry_Yuan
2016-07-20 6:58 ` Michal Kazior
2016-07-20 7:23 ` Perry_Yuan
[not found] ` <A3D794F1192BBF449DF2EC3D7EE263F44A5402F40A@SHAX7MCDC101.APAC.DELL.COM>
2016-07-25 10:25 ` Michal Kazior
2016-08-02 12:19 ` Valo, Kalle
2016-07-29 7:45 ` Perry_Yuan
2016-07-29 9:07 ` Perry_Yuan
2016-08-02 12:10 ` Valo, Kalle
2016-08-03 7:00 ` Michal Kazior
2016-08-22 8:40 ` Stanislaw Gruszka
2016-08-22 10:29 ` Valo, Kalle
2016-08-22 11:02 ` Stanislaw Gruszka
2016-08-22 14:05 ` Valo, Kalle
2016-08-23 18:55 ` Valo, Kalle
2016-08-24 6:33 ` Stanislaw Gruszka
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.