You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the driver has issues with gnome network displays due to p2p issues.
The docs for Gnome Network Displays (i will call gnd from now on) says;
iw dev should show an Unnamed/non-netdev interface device with type P2P-device.
If this is not the case, then the device is likely unsupported. One example of this are legacy wext drivers, which may support P2P operation, but are not (and will not be) supported by this software.
The image above is what i get. There are no Unnamed/non-netdev interface listed.
This is related to supported interface combinations I preassume. GND connects via p2p-device mode.
Network manager logs show that ; ... call-p2p-connect: failed with connect failed due to channel unavailability.
Which i assume is unrelated.
Currently running a 8852AE with kernel 6.2.6-76060206-generic, on pop os and drivers installed directly from the source.
The text was updated successfully, but these errors were encountered:
Gnome Network Displays: https://gitlab.gnome.org/GNOME/gnome-network-displays
Currently the driver has issues with gnome network displays due to p2p issues.
The docs for Gnome Network Displays (i will call gnd from now on) says;
The image above is what i get. There are no Unnamed/non-netdev interface listed.
This is related to supported interface combinations I preassume. GND connects via p2p-device mode.
Network manager logs show that ;
... call-p2p-connect: failed with connect failed due to channel unavailability.
Which i assume is unrelated.
Currently running a 8852AE with kernel 6.2.6-76060206-generic, on pop os and drivers installed directly from the source.
The text was updated successfully, but these errors were encountered: