Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ath9k : high video latency and low transfer speed #107

Open
Yes21 opened this issue Dec 16, 2018 · 2 comments
Open

Ath9k : high video latency and low transfer speed #107

Yes21 opened this issue Dec 16, 2018 · 2 comments

Comments

@Yes21
Copy link
Contributor

Yes21 commented Dec 16, 2018

No description provided.

@Yes21
Copy link
Contributor Author

Yes21 commented Dec 22, 2018

I copy here @user1321 observations :

I have some news..

  1. After replacing firmware file:
    /lib/firmware/ath9k_htc/htc_9271-1.4.0.fw
    with htc_9271-1.4.0.fw from build tree video not freezing anymore.
    It`s look like ImageBuilder script DONT overwrite existing files.
    I have some errors during build process, so, maybe my guess is incorrect. But I belive I am correct in my guess.
    Also, I strongly recommend to take a look at /etc/fstab file.
    As file system in RW state.

So, solution can be:

remove file first, or maybe add some parameter to replace if file exist.

So, to confirm, you may try to replace file at your side.
https://github.com/RespawnDespair/wifibroadcast-image-builder/tree/master/stages/04-Wifibroadcast/FILES/overlay/lib/firmware

file to replace:
/lib/firmware/ath9k_htc/htc_9271-1.4.0.fw

also, it`a good idea to check file system state. Is it ReadOnly or ReadWrite. Run: mount

Other possible reason: if there someware command apt-get upgrade. But, as file /etc/fstab look like in default state, probably problem just with copy process

@Yes21
Copy link
Contributor Author

Yes21 commented Dec 22, 2018

vitaliy zlidnev, [22.12.18 19:02]
I just noticed that firmware copied not to /lib/firmware/ath9k_htc/
but to /lib/firmware/
Maybe it`s just wrong path?))

And its explaining why its work fine when firmware was replaced manually.

Jelle Tigchelaar, [22.12.18 19:03]
Damn, thats an easy fix, just move it to the correct folder in the overlay...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant