Mailinglist Archive: opensuse (1264 mails)

< Previous Next >
Re: [opensuse] no wireless in new laptop
12.06.2017 01:42, George from the tribe пишет:
...>
One question, though, that is confusing me, and I am wondering what I
should do. In the firmware directory, there are 2 directories, hw2.1 and
hw3.0. The hw3.0 directory has firmware-4.bin, as you mentioned. I
still have an error in dmesg, like so:


Directory depends on hardware you have, it is not something you can
chose. Driver selects directory suitable for your card.

--------------
# dmesg | grep ath
[ 13.817175] ath10k_pci 0000:01:00.0: enabling device (0000 -> 0002)
[ 13.818409] ath10k_pci 0000:01:00.0: pci irq msi-x interrupts 8
irq_mode 0 reset_mode 0
[ 14.113322] ath10k_pci 0000:01:00.0: Direct firmware load for
ath10k/cal-pci-0000:01:00.0.bin failed with error -2
[ 14.119406] ath10k_pci 0000:01:00.0: Direct firmware load for
ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[ 14.119426] ath10k_pci 0000:01:00.0: could not fetch firmware file
'ath10k/QCA6174/hw3.0/firmware-5.bin': -2

It's not necessary an error. Driver attempts to load the "best" firmware
starting with the highest version it supports. Such firmware may
actually never be even released to public and only used internally by
developers.

[ 16.345323] ath10k_pci 0000:01:00.0: qca6174 hw3.2 (0x05030000,
0x00340aff sub 1028:0310) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4 bdapi

So it loaded firmware-4.bin after it attempted to load firmware-5.bin.

2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
features wowlan,ignore-otp,no-4addr-pad
[ 16.345330] ath10k_pci 0000:01:00.0: debug 0 debugfs 0 tracing 0 dfs
0 testmode 0
[ 16.410614] ath: EEPROM regdomain: 0x6c
[ 16.410621] ath: EEPROM indicates we should expect a direct regpair map
[ 16.410624] ath: Country alpha2 being used: 00
[ 16.410624] ath: Regpair used: 0x6c
-----------------

So I am wondering, should I go ahead and change the name in the hw3.0
directory also?

At the best it makes no sense, at the worst driver may change behavior
depending on which version it /believes/ was loaded.


The one in the hw2.1 directory is already
firmware-5.bin, and so that is why it is working.


What is "it" and how you determine it is "working"?

Maybe the hw3.0 directory is for the bluetooth or something?




--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >