princerock Posted March 5, 2016 Share #1 Posted March 5, 2016 I have been running Xpenology in a VM. The host is Arch Linux. I'm passing a nic to the VM and it's been working fine. Yesterday I was trying to update the DSM from 5592.4 to 5644. I used the latest XPEnoboot but somehow I couldn't connect to it (that means I didn't install or upgrade anything). So I went back to 5592 but this time I still cannot connect to the VM! When I log in through local VNC I saw the following in dmesg: [14.959510] r8169 0000:00.08.0 eth0: unable to load firmware patch rtl_nic/rt8168g-2.fw (-2) [15.164073] r8169 0000:00.08.0 eth0: rtl_phy_reset_cond == 1 (loop: 100 delay: 1). [15.166654] r8169 0000:00.08.0 eth0: link down Does anyone know why all of a sudden the firmware cannot be loaded? Can I install it? I did updated some packages on the host (arch linux). Not sure if that could cause this. But again everything was working before I tried the update. Many thanks in advance. Link to comment Share on other sites More sharing options...
princerock Posted March 6, 2016 Author Share #2 Posted March 6, 2016 OK after some debug I believe it's most likely caused by this update: 5.2-5644.4 (23/12/2015) Disable old crappy realtek r8169 module, update r8101 / r8168 / r8169 drivers If I use 5.2-5644.1 there is no such a problem. Both 5.2-5644.4 and 5.2-5644.5 have this problem. My NIC is 8111G. It looks like when this happens something messed up in the NIC. I couldn't access it unless I do a full power cycle on the machine. Reboot doesn't help. Does anyone else see an issue with the NIC after the update? Is there a way to contact sancome and/or the team about this? I would like to find a way to bring back the "old crappy" module back if possible, as that works for my card! Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts