I’m about to install OpenPHT on two new PCs (Intel NUC SWIFT CANYON NUC6I3SYK, hope it meets specs). Previously I had the OpenPlex install, so far worked very well with a couple of issues, mainly high CPU load.
Anyway, here are my questions. Yes, I used the search, but obviously I did it wrong…
Which build? OpenPHT-Embedded…GENERIC, or OpenPHT-Embedded…INTEL?
I downloaded the generic build file (OpenPHT-Embedded-1.6.2.123-e23a7eef-Generic.x86_64.img.gz) just to have a look inside. How do I create the USB stick from the img files? I’d like to boot from an internal SSD, no USB stick boot. I’ve got Windows 10 to build the USB stick.
That’s basically it. Might I also suggest pinning a “getting started” thread on top of this section in the forum to help out people like me? Thanks!
Flash the installer to an SD card or USB stick, insert the SD card or USB stick into your PC, boot from it and the installer will run, be warned, installing to your hard drive will completely overwrite the hard drive. I normally install onto another SD card or USB stick and then boot and run from that, but either way will work.
What exactly do you mean with “flash the installer”? If I look into the archive, all I see is a .img file. I can open that, too, then end up with two more .img, both called “primary.img”. One has “Windows BDP” as file system, the other one some GUID. The bigger one with the “Windows DBP” file system has the following content:
EFI
syslinux.cfg
ldlinux.sys
ldlinux.c32
KERNEL
SYSTEM
KERNEL.md5
SYSTEM.md5
So I just copy this onto a blank (FAT formatted?) usb stick? Way too easy, sorry, I’m used to Windows
The Generic build should work for most devices, for your NUC I would give the Intel_EGL a try.
The Intel_EGL build includes some of the improved Intel VAAPI related code from Kodi Krypton and makes use of “zero copy” to boost performance. On a Braswell NUC it is possible to play 4K@30hz 8-bit HEVC with the Intel_EGL build, something that won’t work with the Generic build.
I would recommend all NUC and Chromebox users to test the Intel_EGL build and switch back to the Generic build if any problems occur. You can place the other img.gz-file in /storage/.update/ and reboot to switch build.
@Kwiboo said:
The Generic build should work for most devices, for your NUC I would give the Intel_EGL a try.
The Intel_EGL build includes some of the improved Intel VAAPI related code from Kodi Krypton and makes use of “zero copy” to boost performance. On a Braswell NUC it is possible to play 4K@30hz 8-bit HEVC with the Intel_EGL build, something that won’t work with the Generic build.
Thanks! 4K isn’t planned, yet, but good to know. I also have an older NUC, as you can see in my signature. If I install it on that machine - would you also suggest going with the Intel build?
@ferminator said:
I also have an older NUC, as you can see in my signature. If I install it on that machine - would you also suggest going with the Intel build?
Your older NUC have a Ivy Bridge cpu so I would try the Intel_EGL build.
The Intel_EGL build includes optimizations specifically targeted Intel Sandy Bridge and newer cpu, such as an updated Intel video driver and use of EGL. Other than that it is very similar to the “stable” Generic build and even contains Nvidia video drivers.
OpenPHT-Embedded-1.6.2.123-e23a7eef-Intel_EGL.x86_64.img.gz and
OpenPHT-Embedded-1.6.2.123-e23a7eef-Generic.x86_64.img.gz
both have the same content:
OpenPHT-Embedded-1.6.2.123-e23a7eef-Generic.x86_64.img
Shouldn’t the file name of the .img in the Intel_EGL Archive have a different name? File sizes of both .img files are the same, too. However, the CRC is “2C28B2A8” for the Generic and “E25A38D3” for the Intel build.
And, maybe as an additional question - if I go ahead and install the Intel build but later would like to test out the Generic (or the other way around), can I just put the KERNEL and SYSTEM files into the update folder, reboot and it will switch over? I did that with the “old” OpenPlex, worked flawlessly.
Good catch, will rename and replace the Intel_EGL file on GitHub. The Intel_EGL image is just a Generic build with additional patches.
If you are upgrading from an older OpenELEC based OS you need to place KERNEL/SYSTEM/.md5 into the update folder and reboot. But with the LibreELEC base OS we are using it is now possible to “upgrade” just by placing the img.gz file into the update folder and reboot.
And once more me, maybe/hopefully for the last time tonight: I’ve downloaded win32diskimager, now all I need to know is which .img file to feed it:
The big one directly in the .gz archive?
primary.img, size about 536 MB, with a “Windows BDP” file system (as shown in 7-zip)?
primary.img, size about 33 MB, with “0FC63…7DE4” as file system?
Then I’ll be on my way And yes, I’d experiment, but I don’t have the hardware here yet, I’ll be doing the install tomorrow evening and would like to be as prepared as possible.
