How can I use the Ethernet port to communicate with other devices? I checked if it is enabled with ip link show and ip addr show in sys-net, but it says state DOWN mode DEFAULT on the line for ens7. I also tried to turn it on with sudo ip link set ens7 up, but it turns itself off again, and nmcli device status says it is unmanaged. What do I need to do?
And is it normal that the devices attached to sys-net don’t show an Ethernet port?
There are two attached devices:
You need to identify the ethernet controller with sudo lspci -v in dom0, and make
sure that that is attached to sys-net.
The fact that it’s showing as “unknown PCI device” makes me think that
you’re lacking modules or drivers for the controller.
When you start sys-net, check the logs with journalctl -b in sys-net
and look for any errors relating to that device. It may be that you
need to add drivers for the specific device.
(It would help if you identified the machine and/or network controller,
but I undderstand that you may be reluctant to do this. But it would
help.)
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I checked the devices in dom0 and the unknown device (00:1f.6) is the Ethernet controller. dom0 says it uses the “pciback” driver and a kernel module called “e1000e”. sys-net says it uses “e1000e” as both the driver and the kernel module.
In the terminals the Ethernet controller is named correctly, only the device settings in Qubes cannot recognize the controller and label it as an “unknown PCI device”.
I also checked the systemd logs, but I haven’t found any errors.
I tried an Ethernet USB Adapter and started by attaching the USB device with the device manager to sys net and checked with `ip link show` the ethernet adapter (enu1) which was down. Setting it up with `sudo ip link set enu1 up` showed it didn’t have enough memory. I gave sys net 300MB more memory so 600MB in total. More probably also works, and this fixed the problem. After that the wired connection is established automatically.