moritz.morawietz at informatik.uni-oldenburg.de
Thu Apr 30 06:03:21 PDT 2015
I used 4.0.0-2. Also i had one kernel build where it worked, but,
because I didn't knew that you have to install nvidia drivers again, I
deletet it. I am not sure how i did it, so I'm currently trying again.
Maybe I need to understand the patching mechanisms, guess that would
help :D I did something with git…
Thank you a lot for your help so far!
2015-04-30 2:07 GMT+02:00 Gabriele Martino <g.martino at gmx.com>:
> On 28/04/2015 13:55, Moritz Morawietz wrote:
>> Many thanks for your fast help!
>> I've made some progress, but ran into other problems.
>> If i compile ath10_pci, ath10k_core and ath from kvalo's tree and load
>> them, i get following dmesg output:
>> [ 2.980448] ath10k_pci 0000:06:00.0: enabling device (0000 -> 0002)
>> [ 2.980750] ath10k_pci 0000:06:00.0: pci irq msi-x interrupts 8
>> irq_mode 0 reset_mode 0
>> [ 3.158860] ath10k_pci 0000:06:00.0: Direct firmware load for
>> ath10k/cal-pci-0000:06:00.0.bin failed with error -2
>> [ 3.159611] ath10k_pci 0000:06:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/board-pci-168c:003e:1a56:1525.bin failed with
>> error -2
>> [ 3.159613] ath10k_pci 0000:06:00.0: failed to load spec board
>> file, falling back to generic: -2
>> [ 3.159922] ath10k_pci 0000:06:00.0: Direct firmware load for
>> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
>> [ 3.159924] ath10k_pci 0000:06:00.0: could not fetch firmware file
>> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>> [ 4.360946] ath10k_pci 0000:06:00.0: qca6174 hw2.1 (0x05010000,
>> 0x003405ff, 168c:003e:1a56:1525 fallback) fw killer-n1525-fw api 4 htt
>> 3.1 wmi 4 cal otp max_sta 32
>> [ 4.360950] ath10k_pci 0000:06:00.0: debug 1 debugfs 1 tracing 1
>> dfs 0 testmode 0
>> [ 4.430068] ath: EEPROM regdomain: 0x6c
>> [ 4.430070] ath: EEPROM indicates we should expect a direct regpair map
>> [ 4.430072] ath: Country alpha2 being used: 00
>> [ 4.430072] ath: Regpair used: 0x6c
>> [ 4.430078] ath10k_pci 0000:06:00.0: failed to register ieee80211: -22
>> [ 4.430097] ath10k_pci 0000:06:00.0: could not register to mac80211 (-22)
>> So I compiled mac80211, and tried to load it. What i get is a load of
>> that messages:
>> [ 226.812494] mac80211: Unknown symbol cfg80211_cqm_rssi_notify (err -22)
>> [ 226.812497] mac80211: disagrees about version of symbol cfg80211_auth_timeout
>> [ 226.812497] mac80211: Unknown symbol cfg80211_auth_timeout (err -22)
>> [ 226.812498] mac80211: disagrees about version of symbol
>> [ 226.812499] mac80211: Unknown symbol cfg80211_rx_unprot_mlme_mgmt (err -22)
>> Because mac80211 depends on cfg80211, i compilied and tested it. The
>> error messages reduced to
>> [ 632.208849] mac80211: Unknown symbol rhashtable_insert_rehash (err 0)
>> [ 632.208881] mac80211: Unknown symbol rhashtable_insert_slow (err 0)
>> Know I'm stuck. I'll try to compile and use the whole kernel (it's
>> compiling right now), but would prefer to just change the modules.
> I could find some references to "rhashtable_insert_rehash" with grep:
> /usr/src/linux/lib/rhashtable.c:int rhashtable_insert_rehash(struct
> rhashtable *ht)
> This file is present in 3.18.11 kernel (I don't have older sources on
> this laptop).
> Which distribution and kernel are you using?
> You are compiling 4.0 (-> 3.20) modules, so you're likely to get strange
> issues if your kernel is too old.
> ath10k mailing list
> ath10k at lists.infradead.org
More information about the ath10k