No Network Connection in Qubes 3.2
babel
From within sys-net, I see..
lspci
00:00.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21)
00:01.0 Network controller: Intel Corporation Device 24fd (rev 78)
[user@sys-net ~]$ lspci -k
00:00.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V (rev 21)
Subsystem: Intel Corporation Device 2068
00:01.0 Network controller: Intel Corporation Device 24fd (rev 78)
Subsystem: Intel Corporation Device 9010
No kernel module being loaded there...
Anyone have any advice?
babel
Hmm.
So for some reason, I'm loading the wrong kernel modules, or not at all.
I tried shutting down the netvm as found here..
https://www.qubes-os.org/doc/assigning-devices/
Then bringing it back to dom0
echo 0000:<BDF> > /sys/bus/pci/drivers/pciback/unbind
MODALIAS=`cat /sys/bus/pci/devices/0000:<BDF>/modalias`
alone, cat brings a pci-value. Thanks to this thread
https://groups.google.com/forum/#!topic/qubes-users/LqhHWJ6GZZU
I figured out to just assign to pci next, but..
the link happens to be unassigned at kernel, because the next command..
MOD=`modprobe -R $MODALIAS | head -n 1`
modprobe: FATAL: Module pci:v00..... not found in directory /lib/modules/4.4.14-11.pvops.qub...
So I thought I would get clever, but you can't modify anything within /sys/bus/pci/devices/0000\:00../ folder as far as I can tell.
Also, just adding an alias to the /lib/modules/kernel_version/modules.alias doesn't work, so I'm stumped here.
echo 0000:00:xx.x > /sys/bus/pci/drivers/e1000e/bind
gives me
-bash: echo: write error: No such device. (even after I add an alias for the pci:xxx to /.../modules.alias
If anyone has some insight it would be valuable.
wannabe...@gmail.com
I am having the same issue with Kaby Lake NUC. Tried debian netvm no luck. Manual install of driver from Intel, no luck thus far. Per advice from Qubes Team I am trying Fed 25 and debian stretch next. I will pass along if I have any luck.