Should suspand/standy work when booted with PXE?
OpenELEC Forum
Generic Forum
NETWORK
PXE / Network boot
Should suspand/standy work when booted with PXE?
OpenELEC Forum
Generic Forum
NETWORK
PXE / Network boot
Should suspand/standy work when booted with PXE?
|
11-04-2013, 05:25 PM
It looks as the connman .cache was moved so that you could edit certain properties from within the new OE settings manager for 3.2. This would not be possible if located on read only /flash (or equivalent for non Pi devices).
Well I got suspend/resume working on a PXE boot. What I did was modify the connman source to use /tmp/connman as the location for its config files instead of /storage/.cache/connman. Modified the 21_connman initt.d script to copy the contents of /storage/.cache/connman to /tmp/connman just bore its starts connmand on bootup and added a shutdown.sh script which copies /tmp/connman to /storage/.cache/connman on shutdown to persist the configuration across reboots.
I completed ~10 suspend/resumes in a row on my Asrock ION 330 without any issues. So I think this proves that running the connman config on a ramdisk works. The openelc settings plugin could be modified to persist the config changes to /storage/.cache/connman which would probably be a better solution then the shutdown script. SeeDrs
11-10-2013, 09:39 PM
Thanks for the info.
Could you please provide more details about the scripts ? I am a complete Linux noob  Anyway, I find openelec an amazing piece of software both powerfull and friendly.
11-10-2013, 10:24 PM
If you go to the github link posted by LossAngeles a few post back, there is a second method of just added a few NFS options to pxe settings to fix the issue, which is much easier.
11-10-2013, 10:48 PM
I just read that. For the moment I use SMB shares and the pxe settings do not work.
Thanks for the quick reply 
01-01-2014, 06:41 AM
Adding "-I eth0" to the connmand invocation in the network startup script is giving me a good result. This tells connmand to leave the interface unmanaged, so it retains its PXE boot / dhcp settings.
More detail at https://github.com/OpenELEC/OpenELEC.tv/...t-31419438
02-17-2014, 02:30 PM
Anyone managed to make this work correctly?
I did try to add the -I eth0 to 21_network file, resume worked perfectly but I have no DNS when I do this and can't figure out how to solve this. I guess the next step would be to have connman save the config file on /flash or /tmp but I have no idea how to do it. Any help would be appreciated.
02-17-2014, 04:50 PM
(This post was last modified: 02-17-2014, 04:54 PM by Cheddoleum.
Edit Reason: reminder
)
ObiFredKenobi post=98129 Wrote:Anyone managed to make this work correctly?. Well, yes. As I described in the github issue comment that I linked, you can force DNS in autostart.sh. For now I'm getting by with a simple hardcode: /storage/.config/autostart.sh Code: #!/bin/bashReplace the IP with that of your router/DNS server or upstream DNS provider if that's how you roll. Hardcoding like this is kind of uncool but at least here you don't have to rebuild and can change it as necessary. Again, a maintenance-based fix would allow you to configure this sort of thing in the OpenELEC system and network configuration. (Reminder: make autostart.sh executable)
02-17-2014, 05:30 PM
(This post was last modified: 02-17-2014, 11:20 PM by Cheddoleum.
Edit Reason: Add squashfs howto
)
As far as persisting the change to the network startup script, you may have some luck unsquashing the SYSTEM file, making the change and resquashing -- hopefully there's something in the forum that describes how to do that successfully.
I just rebuilt 3.2.4 from source as I was doing that anyway for other reasons. (Edit: here's a posting that describes modifying the squashfs system volume: http://wiki.openelec.tv/index.php?title=..._bluetooth)
02-17-2014, 09:31 PM
Cheddoleum post=98137 Wrote:ObiFredKenobi post=98129 Wrote:Anyone managed to make this work correctly?. Just tried it and it's working perfectly now! Thank you very much! |
|
|
