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
Miracle-wifid tells that my driver doesn't support p2p, but test-hardware-capabilities.sh tells it supports #147
Comments
There is a overview of brcmfmac driver https://wireless.wiki.kernel.org/en/users/drivers/brcm80211 |
What distro are you using? Important info:
|
Ubuntu 16.04 root@XPS-15-9550:/home/victorcrimea# wpa_supplicant -v |
Everythins seems ok. Please post here logs as described in https://github.com/albfan/miraclecast/wiki/FAQ |
xps15-miraclecast.zip |
Already addded |
Dod you kill actual wpa_supplicant? Miraclecast reuses existing process if avaliable but that wpa_supplicant will not fit with miraclecast requirements. If that's the case, shutdown networkmanager service as it tries to restart wpa_supplicant if something kills it |
My fault. I haven't killed them. Now I definitely killed network manager and wpa_supplicant with res/kill-wpa.sh. |
This line on journal.log
tells your system is using that interface in some process. check for running
Restarting does the trick too but it's nastier |
Give it another try if you want. stopping network manager after a reboot should be enough to have interfaces ready for miraclecast. (We are working to improve the way final users use it) |
I'm using Dell XPS 15 (9550) with Broadcom BCM43602 card served by brcmfmac driver.
When I running res/test-hardware-capabilites.sh script it tells: wlp2s0 supports P2P.
But when I'm trying to run miracle-wifid it throws a warning:
WARNING: supplicant: wpa_supplicant or driver does not support P2P (supplicant_status_fn() in /home/victorcrimea/projects/miraclecast/src/wifi/wifid-supplicant.c:1682)
And obviosly nothing works afterwards :(
What is the possible reason of the problem?
In fact: miracast is working well with Windows 10 both as a receiver and as a transmitter, so it's supposed to be driver/software issue.
The text was updated successfully, but these errors were encountered: