On Sun, 30 Aug 2015 13:18:19 +0200 Sven Hartge <s...@svenhartge.de> wrote:
> bri...@aracnet.com wrote: > > On Sun, 30 Aug 2015 04:25:36 +0200 Sven Hartge <s...@svenhartge.de> wrote: > >> bri...@aracnet.com wrote: > > >>> There's no way anyone can help until i can get a trace of what's > >>> going on at boot. > >> > >> Jessie or newer? With systemd? > >> > >> systemd-analyze blame > > > > 29.597s networking.service > > 3.256s systemd-suspend.service > > > aha. So I need to dig deeper into networking.service > > networking.service is /etc/init.d/networking. Somehow the parsing and > acting upon /etc/network/interfaces is slow. > > Please share the contents of /etc/network/interfaces, maybe something > odd stands out in there. > cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp there's this in dmesg: [ 6.210098] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null) [ 35.827945] r8169 0000:03:00.0: firmware: failed to load rtl_nic/rtl8168f-1.fw (-2) [ 35.827963] r8169 0000:03:00.0: Direct firmware load failed with error -2 [ 35.827965] r8169 0000:03:00.0: Falling back to user helper [ 35.828580] r8169 0000:03:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168f-1.fw (-12) so it is the dreaded r8169 firmware crappola. the system works fine not loading it. is there any way to tell the module to not even try and load it ? Brian
