I had installed initially with Debian as default after updating I lost my wired connection to sysnet. I reinstalled with Fedora as default (which I initially intended to do) now unable to connect at all to sysnet. I’m not a computer scientist but could it possibly be driver related or lack of I should say. Reading through docs and posts without progress. I’ve failed to get qubes up and running in any state so maybe it’s just a simple setting config issue! I’m beyond frustrated plz help qubes maestros!
Hi Whatamidoinghere
Can you share the version of Qubes OS / debian / fedora you are using/testing?
– from your other post1, it sounded like you only had dom0 and never saw the “Initial Setup” screen.
I used that command to get me to the initial install. That was in 4.3.0 now I’m on 4.3.1
Do you have sys-net qube in your system?
If yes, then are you able to start it or is it fails to start?
It’s there just says disconnected in light gray under wired and wireless is disconnected and right click won’t bring up any options or even exit.
Illon the initial install selections should I make sysnet disposable? IDK if that has anything to do with my connection issues or the purpose of that anyways. I’m just shooting in the dark at this point lol
What PCI devices are attached to sys-net?
Maybe there is a problem with drivers for your network controllers and that’s why there is nothing in the network manager applet.
It shouldn’t be related.
Do you mean like wireless mouse and keyboard?
No, I mean Ethernet controller or Wireless network controller PCI devices.
What devices are listed in the sys-net’s Qube Settings → Devices tab under “Devices always connected to this qube”?
There’s 3 do i just post a pic of them? Is that safe idk
The wireless seems to be working after reboot fyi. Don’t understand why Ethernet cable isn’t.
It should be safe. I want to know what devices do you have to check if there could be some known problems with their drivers.
Did you suspend/resume your computer? Some PCI devices have a problem with suspend and they stop working after resume from suspend.
You need to check the log in sys-net to see if there is a problem with your network controllers drivers.
You can check the log using sudo journalctl -b | cat command in sys-net terminal.
To summarize my troubles it’s started with initial install failing to start the final set up where specific templates and settings can be selected had to be manually triggered in terminal. System seemed ok until updates had been applied and loss of both wired and wifi began. I ran analytics but I don’t understand how to decipher the results. Should I post the LONG LONG results of the sysnet analytics test I’m sure someone out there can enlighten me. Please help this seems to be my last hurtle I hope.
Wifi becomes available occasionally now. Could I possibly be missing one if these drivers in photo
Well, your adapters are identified, so probably no driver issue.
Sure, share the “long long results”, so far what you show and tell does not point to a distinct issue.
Maybe also try to have your wired connection use a static address instead of dhcp - would be nice to know if and how it also fails.
There must have been a bug fix in fedora or something. I updated and it connected to Ethernet this time. Edit: I restarted and once again it won’t direct wired only WiFi
How can I change it to a static address?
open your terminal and run nmtui
For others, looking for the prequels:
- Qubes OS 4.3.1 Reinstallation Cannot Connect to Fedora-based sys-net
- Installation attempts missing all templates