This is a request for keeping a feature that is already working. Booting LibreELEC via PXE works perfectly and is really useful in HTPC environments. In the latest release OpenELEC removed PXE and iSCSI boot (is also mentioned in the changelog: "NFS, NBD, iSCSI Network boot support removed") and i've seen many people complaining about it. I really hope LibreELEC will keep the feature. Thanks
Please keep PXE boot capabilities
-
megavolt -
October 29, 2017 at 12:24 AM -
Thread is Unresolved
-
-
- Official Post
I'd caution that nobody I'm aware of among staff uses PXE boot so there is ~zero testing done before releases, but as long as it continues to work there are no plans to remove or sabotage the feature.
-
I'd be glad to write a howto for the wiki and do testing for standard-pxelinux and ipxe in pcbios and efi32/64 flavours if someone is interessted.
-
Where can I find a LibreELEC image for PXE booting?
-
- Official Post
All images support PXE boot as long as you customise the boot process to PXE boot.
-
Does anyone have directions on how to do this. OpenELEC had a KERNEL and SYSTEM image in their tar file. How do I get the same from LibreELEC and I assume the process is the same, i.e.:
EDIT: OK, I found it here: Index of /pub/LibreELEC
-
OK, works now. Had to do something from this thread for the shutdown hang issue:
Copy /etc/connman/main.conf to /storage/.config/connman_main.conf
and add the network interface to NetworkInterfaceBlacklist optionCreate an autostart script to add default gateway and connman resolv.conf
nano /storage/.config/autostart.sh
Code/sbin/route add -net 0.0.0.0 gw 192.168.90.1 echo -e "search mydomain.org\nnameserver 192.168.90.1" > /run/connman/resolv.conf
chmod +x /storage/.config/autostart.sh
-
BTW - Thank you for keep PXE boot capability and not dumping it like the previous distribution did.
-
- Official Post
PXE booting is niche but the code bits haven't been touched in years and require no maintenance so it's no issue to leave it in the codebase. Glad you got it working
-
PXE booting is niche but the code bits haven't been touched in years and require no maintenance so it's no issue to leave it in the codebase. Glad you got it working
Great...yes, it is nothing better than to have several diskless clients able to use a central media server. I actually am able to remove and use the SSD that came with my boxes for other purposes so a win-win. In case OE gets rid of the article and for posterity, here is a link to it. (sorry, will need to rotate it with your PDF client).
-
OK, works now. Had to do something from this thread for the shutdown hang issue:
Copy /etc/connman/main.conf to /storage/.config/connman_main.conf
and add the network interface to NetworkInterfaceBlacklist optionCreate an autostart script to add default gateway and connman resolv.conf
nano /storage/.config/autostart.sh
Code/sbin/route add -net 0.0.0.0 gw 192.168.90.1 echo -e "search mydomain.org\nnameserver 192.168.90.1" > /run/connman/resolv.conf
chmod +x /storage/.config/autostart.sh
I did exactly this but mine still crashes on reboot/shutdown. My logs are here (created the same was as instructed). Any ideas?
-
I did exactly this but mine still crashes on reboot/shutdown. My logs are here (created the same was as instructed). Any ideas?
I'm not sure if this is related. But it could be due to some hardware storage issues? I see a lot of these in your logs:
CodeMar 24 09:12:25 RPi-TV systemd-udevd[270]: Failure opening block device (null): Bad address Mar 24 09:12:25 RPi-TV systemd-udevd[269]: seq 849 queued, 'add' 'bus' Mar 24 09:12:25 RPi-TV systemd-udevd[278]: IMPORT builtin 'blkid' /usr/lib/udev/rules.d/95-udevil-mount.rules:9 Mar 24 09:12:25 RPi-TV systemd-udevd[270]: IMPORT builtin 'blkid' returned non-zero
It doesn't appear you are boot via iSCSI and still using local storage.
-
Interesting. Did you do do a fresh install of Kodi with network booting? I simply copied everything from my SD card to my NAS and then made the modification to cmdline.txt.
-
This is what I followed:
-
-
Yes, iscsi support has been dropped quite a while ago https://github.com/LibreELEC/LibreELEC.tv/pull/6356
so long,
Hias
-
Yes, iscsi support has been dropped quite a while ago https://github.com/LibreELEC/LibreELEC.tv/pull/6356
so long,
Hias
I'm trying to follow the netboot from NFS but not sure of all the parts since the e.g. IPs are different.
-
So, this method to use NFS instead of iscsi for netboot is much slower (about 1-2 min vs. instant).
This is my previous and new ipxe files:
Previous:
Shell session#!ipxe echo Ready for iscsi boot ! :retry_sanboot sanboot iscsi:<server IP>::::<iscsi target IQN> goto retry_sanboot
``New:
Code
Display More#!ipxe echo Ready for TFTP and NFS boot! set nfs-server <NFS server IP> set libreelec-version 11.0.3 set nfs-root /export/ipxeNFS/ set archl x86_64 set libreelec-storage-dir ${nfs-server}:${nfs-root}libreelec-storage/ echo Booting LibreELEC Generic ${libreelec-version} from NFS ${nfs-server} set base-url LibreELEC-Generic.${archl}-${libreelec-version} echo NFS path is: ${nfs-server}:${nfs-root}${base-url}/target kernel KERNEL initrd SYSTEM imgargs KERNEL ip=dhcp boot=NFS=${nfs-server}:${nfs-root}${base-url}/target disk=NFS=${libreelec-storage-dir} overlay boot || goto failed :failed echo Booting failed, dropping to shell goto shell
-