module load fail for qcacld-usb.ko #19
Comments
|
working fine with next condition branch: linux-5.4.y/CNSS.LEA.NRT_3.0 |
|
My guess that is a result between target firmware (binary blob provided by vendor: athwlan.bin, etc, .ini files) and driver version. I refer to the part |
|
I tried to compile and run 3.1 on 5.4.0-139 (ubuntu 20.04/LTS) linux kernel. I cant load and run 3.1 either. but i dont get any firmware crash errors and etc: relevant OS info: |
|
Even if i tried compiling and running driver from Some URB requests are failing. |
|
Funny enough, i took 9337 and moved from one usb port to another, and it worked (3.0 version). |
|
driver built from it works too. I had just: to increase debug verbosity i edited qcom_cfg.init and replaced with line: |
|
Can you try enabling higher debug level and make sure firmware files including .ini are copied under /lib/firmware/ |
|
i will 5.15.x linux kenrel on linux/x86 that comes with 22.04.1 LTS on monday (up to date) and will let you know if it works. |
|
I tried vosTraceEnableHDD. add below settings to .ini and more informations firmware and setting files Makefile changes git log for branch |
|
Hi It could be power issues, maybe qca/9377 draws too much on start up and crashes ? So far i was not able to recreate. Can you try the same qca/9377 on standard linux pc and check if it works this way instead ? Although that does not explain why 3.0 work (as i understood) but 3.1 - does not. I tried both versions and as you could see from the log files i posted it both versions do work for me. Just to double check, |
|
"firmware_bin/qcom_cfg.ini" does not included in branch "linux-5.14.y/CNSS.LEA.NRT_3.1". |
|
I tried another usb port. 1st time, firmware crashed same part. dmesg below: I will try Standard pc + 5.15. |
|
use same result |
For some reason you are getting USB/layer errors: -110, as a result BMI errors that in essence mean that firmware loaded on 9377 is failing to start (quite possible it crashes on when it is executed). I am inclined to think that 9377 at blame maybe. I will try 5.15.x linux kernel later today, on standard linux/PC - i cant explain what is going on yet |
|
I tried standard pc.
Makefile $ make $ sudo dmesg |
|
I cant fix kernel 5.15 + NRT_3.1 problem. so, I tried porting linux-5.4.y/CNSS.LEA.NRT_3.0 to linux-5.15.y/CNSS.LEA.NRT_3.0 kernel: 5.15.71-rt51-intel-pk-preempt-rt modprobe dmesg below: |
|
@Hiroshi-tnk san, I am sidetracked on other projects. At the moment i cant spare much time on this. Can you share the changes you have made ? I can try them on my setup too. Maybe I can spot something you had missed during the changes. |
|
Thank you for co-operation. I'm not use to github. Please advise for push. |
|
Just attach diff/patch to this issue. No problem. |
|
$ git diff linux-5.4.y/CNSS.LEA.NRT_3.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for developers.
module load fail for qcacld-usb.ko.
Do you have any idea what might lead to this error?
We use branch: linux-5.14.y/CNSS.LEA.NRT_3.1
kernel: 5.15.71-rt51-intel-pk-preempt-rt (with yocto custom kernel)
wlan module : QCA9377-7 with usb connector type
related lsmod:
ID 0cf3:9378 Qualcom atheros communications USBWLAN
ID 0cf3:e500 Qualcom atheros communications
dmesg show below:
The text was updated successfully, but these errors were encountered: