[warrmr]

Afternoons,

I wonder if you guys could help me, I have nearly got my XBMC pc setup how I want it with the exception of a few minor issues.

When booting the PC up from Hibernate (S3) it takes around 20-30s to get to the XBMC display and you can start navigating menus which is fine considering the age of the motherboard and CPU. The issue that I have noted is that it takes the system an additional 30s for it to start responding on the network and for the remote to be usable.

Is there a way that the network can be sped up so that when the XBMC does its library scan on load it can actually contact the outside world without halting for 30s.

I did see this thread http://forum.xbmc.org/showthread.php?tid=124428 and have made the modifications to the /etc/network/interfaces file and that doesn't appear to have made any difference. Im nto sure if it is related but when I set XBMC up for the first time I used the network manager GUI rather than editing the config files.

Code:

matt@XBMC:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
     address 192.168.1.250
     network 192.168.1.0
     netmask 255.255.255.0
     gateway 192.168.1.1

matt@XBMC:~$

[warrmr]

Here is my syslog if it helps, I can provide more logs if required just let me know what you need or where I should be looking.

http://paste.ubuntu.com/1511295/

cheers

[un1versal]

Ah resume on fgrlx I read somewhere is a bit of hit and miss.

Your log points to this https://bugs.launchpad.net/ubuntu/+sourc...bug/191889

Code:

Jan  2 19:17:18 XBMC NetworkManager[961]: <info> wake requested (sleeping: yes  enabled: yes)
Jan  2 19:17:18 XBMC NetworkManager[961]: <info> waking up and re-enabling...
Jan  2 19:17:18 XBMC NetworkManager[961]: <info> WWAN now enabled by management service
Jan  2 19:17:18 XBMC NetworkManager[961]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jan  2 19:17:18 XBMC NetworkManager[961]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)

You may need only that then adding a nonexisting interface to the config file...

uNi

[warrmr]

Thanks uNi, I spotted that in the log but it didn't seem relevant as the bug report was talking about firefox and the way it sets offline mode. I have just tried adding a fake eth100 interface and it seems to force xbmc to wait for the real interface and the fake one to become online before giving me the GUI.

I think I would much rather see the GUI and it not have network connection than wait at the XBMC logo screen for an aditional 60 seconds while it trys to bring up the fake iface.

[un1versal]

Well you know what the answer is, shutdown properly and dont hibernate since cold boot is likely less than 60 seconds and everything is available anyway.

Alternatively you can probably make a script to restart networking on resume max 5 seconds wait then, though dont ask me how to do that for you. Some reading https://bbs.archlinux.org/viewtopic.php?pid=1163903

You could try to send iface down and up on resume.

uNi

[warrmr]

I have tried a couple of things, I added the line "sudo ifconfig eth0 down" and "sudo ifconfig eth0 up" to my hibernate scripts in /etc/pm/sleep.d and that didn't appear to do anything when coming back from hibernate.

I have also checked and it seems to do it from a cold start as well.

I wonder if it is trying to initalise IPv6 and that is what is causing the delay

Code:

matt@XBMC:~$ dmesg | grep eth0
[    1.188609] forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 44:87:fc:85:e4:78
[    3.766916] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.038476] forcedeth 0000:00:07.0: eth0: MSI enabled
matt@XBMC:~$

[un1versal]

Probably who knows, you could try to disable ipv6 and see.

Though it sounds to me restarting networking service on resume after its reloaded the module, would probably do what sending the interface down/up isnt doing idk.

It could be that when you sending the interface down/up the whole thing isn't quite ready yet. Only the logs would tell whats being processed first on wake up. Though Im more inclined to restarting the whole networking service provided that is done when the modules finish reloading.

uNi