If I did this, would it break anything..? Or does it simply have to be Fedora..?
Is it true to say
"enp0s1" is the sys-net equivalent of "eth0"
and "wlp0s0" is the sys-net equivalent of "wlan0"
I shut down sys-net and sys-firewall
Switched them both over to debian8
First thing, it said "Internet disconnected" in network manager, and simply wouldn't show any WiFi networks at all.
Second thing, it wouldn't even open the terminal for "sys-net".
So, this really did not work for me.
Chris Laprise, what did you do, other than shutting down VMs and changing to debian..?
Did you have to shut down sys-usb as well..?
Or do I have to do a bunch of other VMs or other stuff..?
This certainly didn't work smoothly for me at all. I've switched back over to Fedora just to type this.
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7bacb435-a9d7-466e-a4f3-30c21f7ee570%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
But WiFi doesn't.
So this is actually I think related to this issue:
Wifi no longer recognised in Debian-based sys-net VM after 3.0 -> 3.1 upgrade
I have an Intel 3165 WiFi chip.
There is something where Debian in Qubes no longer works with WiFi or something. They say to downgrade to a lower kernel.. Errgh
See my post here where I solved it: