Open haukepribnow opened 7 years ago
Thanks for detail info. I only have a rpi 3 so I cannot debug this miself. Let me see if I can point out where to hack to fix this, but I need you to test the changes
Sure, I'm happy to test. :)
Anything I can be of help in narrowing down the problem?
I have a Raspberry 2 with the brand-new Raspbian Stretch installed. I use a Atheros AR9001-based USB wifi dongle (AVM GmbH Fritz!WLAN N 2.4) that runs on the carl9170 driver.
The following log entries are from
journalctl -f
.When running miracle-sinkctl and use my smartphone to do screen mirroring, I get a video stream for some time (a few seconds usually). Then my usb device seems to "crash":
The device restart will immediately be organized... but obviously some items in some processing queue cannot be processed during restart, leading to some failure log entries:
At some point, the miraclecast daemons will also notice that something went wrong:
Now something interesting happens:
miracle-wifid
will try to re-initialize the interface and tries tobind
to it somehow. Binding fails with an "Address already in use" error message:Then some kernel messages appear that I don't really understand:
At some point,
miracle-wifid
realizes that it has lost its peer (because of the interface that went down):And at some point later, the USB dongle gets successfully restarted:
Then come some kernel error messages I don't really understand again:
And finally,
miracle-wifid
tries to handle the situation after the restart of the device again:Here, some binding fails again with a "Address already in use" error message. It appears that some process did not properly "release" its bind when the USB device "crashed".
Because of these binding errors, I will not be able to establish a new p2p connection before a system restart. (I haven't tried shutting down relevant services yet... that might also work.)
The relevant sections of
miracle-wifid
's log look like this:Is there a way to make miraclecast handle situations like these more "gracefully"?