As mentioned above, I have been using Qubes for a bit now and thought I would upgrade my laptop to something a little faster.
My Qubes runs off an external SSD, Once I launched into qubes on my new laptop no wifi card was available, I tried moving wifi/network controllers along with USB controllers (I know silly me…why would I do this) into devices on sys-net and now qubes has crashed and I am unable to get into qubes upon boot.
Have the following errors in red upon boot:
[FAILED] Failed unmounting boot-efi.moun
[FAILED] Failed to start qubes-vm@sys-firewall.service
[FAILED] Failed to start qubes-vm@sys-net.service
[FAILED] Failed to start qubes-vm@sys-whonix.service.
Then check the PCI devices attached to sys-net and remove the one that is causing this issue.
I guess the issue is that you’ve connected the PCI USB controller to which you’re connecting your external USB SSD to the sys-net qube.
Also the wifi network is now showing which is awesome.
I don’t suppose you would know how I can add usb-ethernet into the mix? This laptop doesn’t have an ethernet port, however you can connect into the USB or USB-C port and it will give direct connection (Essentially Ethernet connection) to the 4G modem I am using as opposed to having to connect wirelessly (This was tested and worked on Tails and other linux distros)
If you have sys-usb qube then you can attach USB Ethernet adapter from sys-usb to some other qube (e.g. sys-net or create a separate sys-ethernet) and use it there.
Or you can attach the whole PCI USB controller to sys-net/sys-ethernet and USB Ethernet adapter will be available there directly without attaching it from other qube.
But since you’re using Qubes OS on USB disk then the PCI USB controller to which the disk is connected must stay in dom0.
If you have only this one PCI USB controller available in your machine then you won’'t be able to use USB devices in your qubes.
All you USB ports could be connected to the same PCI USB controller.
You can find out to which PCI USB controller each of your ports are connected to like this:
Check it in dom0 if you have all your PCI USB controllers attached to dom0.
I was reading through the above quoted and I input lsusb which has the following:
Bus 004 Device 004: ID XX Mobile broadband
Bus 004 Device 001: ID XX Linux 3.0 root hub
Bus 003 Device 004: ID XX Web Camera
Bus 003 Device 005: ID XX Bluetooth
Bus 002 Device 002: External SSD
etc
etc
How do I know if I can use the usb/usb-c port for ethernet attached directly to sys-net? Sorry this is all a little overwhelming for me. How do I also check in dom0 if all my PCI USB controllers are attached to dom0?
Just running lsusb won’t tell you to which PCI USB controller is device attached to.
You need to copy the script from that topic to dom0 and run it In it’s output you’ll be able to see the BDF ID of the PCI device to which your USB device is connected to.
Connect the USB devices to all your USB ports and run the script. Or connect one USB device to each port one by one and rerun the script each time.
It means that you have multiple PCI USB controllers and maybe you can use one of them in your qubes but you need to check all your USB ports to determine which PCI USB controller they use.
You can check it by connecting the USB devices to your ports, running the script from the topic that I linked in dom0 and checking it’s output.
