> Board: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac > I have this problem since I bought my laptop (which was last year) and I do > related to a firmware problem, because after I lose my connection the firmware > I use WiFi everyday, but from time to time I lose my connection. > Hello everyone, I would like to report a bug for QCA6174. > To: ath10k at > Subject: Reporting a bug for QCA6174 802.11ac
#DLINK DMG 6661 DRIVER#
> With the latest firmware, you might also need to get the latest driver backport package.
> Also would you mind try to pick up the latest firmware to see if that help? > e.g how far the AP from you and is there any specific scenario you're seeing the failure open? > Not sure how exactly the issue and scenario of your usage. > I'm using WiFi 802.11n, 2.4ghz with AES. > happens while I'm using firefox, sometimes it happens when my laptop > It looks like that there is not specific scenario, sometimes it > Sometimes it does not happens for days, but sometimes it happens 3/4 There's no specific scenario for this failure to happen. > My AP is in the same room that I use my notebook, it's right in front > days to tell you guys if the new driver/firmware resolved the problem. > I've installed the new firmware/driver. > I really don't know what to do anymore.
#DLINK DMG 6661 DRIVERS#
> Hi, unfortunately the problem happened with the new drivers and firmware. > Cc: ath10k at > Subject: Re: Reporting a bug for QCA6174 802.11ac > The last thing is, your previous logs only stuffed with the register access failure logs, can you share a full dmesg logs as well? > Let's start from the basic, could you provide the ftrace logs and also the AP model you're using? try without security or different phy mode to see if it would behave differently? > I guess that the dmesg output will not help us, maybe ftrace will be After the "failed to wake target" problem happens it keeps > Btw, just after I read your email the bug happened.
> if it happens and if it happens I'll provide de ftrace logs. I attached the patch so you guys can take a look. Problem that I hardcoded "ar_pci->pci_ps" to false, thus the board Guys, I noticed that for some reason the board was not being properlyĪwake ( ath10k_pci_wake_wait() returns ETIMEOUT). By looking at the dmesg output that I provided to you After my lastĮmail, I cloned the linux repo and started to hack around the driver I would like to inform that I "fixed" the problem.
0 kommentar(er)
