Did Rufus create an EFI boot partition?
Did you also make sure your BIOS is setup to enable booting from USB?
I have never used rufus before. There could be an issue with how it writes the partition or sets the boot flags. I can run a few tests tonight and see if I can discover your issue.
Is there any particular reason why you aren't installing LibreELEC to the internal memory?
No, I am using the Intel Compute Stick BOXSTCK1A8LFCL.
Thank you for the extra information!
Ryan,
I just looked over the hardware for the Hipstreet PC2GO, looks like it's a rebranded BOXSTCK1A32WFC.
I need a little more information about what you are doing. Based on your description, it sounds like you're trying to boot from a usb drive. Is that correct?
Walk me through the process you are using to install your image.
yes that change TARGET_CPU="x86-64" to TARGET_CPU="silvermont" is correct but
then find line PROJECT_CFLAGS="-mmmx -msse -msse2 -mfpmath=sse" and change to PROJECT_CFLAGS=""
Why would you blank out $PROJECT_CFLAGS?
In my personal build, I replaced
TARGET_CPU="x86-64"
with
TARGET_CPU="silvermont"
and
PROJECT_CFLAGS="-mmmx -msse -msse2 -mfpmath=sse"
with
PROJECT_CFLAGS="-mmovbe -mmmx -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -mpopcnt -maes -mpclmul -mrdrnd -mfpmath=sse"
So far all addons function. In fact I have noticed slightly lower memory usage, roughly 20-23% on average. However, I should state that I did not perform riguorus double-blind tests.
Oddly enough, before I implemented these changes Chromium produced choppy output from NetFlix videos. After the custom changes, Chromium produced better output. There is still a degree of dropped frames, but only during highly dynamic scenes (fast action on high quality videos). Which makes me wonder about recompiling Chromium with the same customizations...
Thanks for clarification! Btw. thumbs up for your effort making LE such a great product.
I concur with backslah, LibreELEC is awesome!
Thank you and sorry for the confusion!
If you use a recent milhouse build you can play games right now.
From what I read, it seemed that the milhouse builds were including extra patches and sources from other repos. I was hoping to build the system myself (in order to add the required drivers for my Wi-Fi and Bluetooth) rather than rely on premade builds.
I will do my homework and learn more about how milhouse is creating the custom builds.
Thank you for taking the time to explain this to me!
I understand and will be working to update my GitHub repo in case a PR occurs.
I have a post in the Development forum currently, thread-7740.html, should I continue to post there or create a new under the General Support forum? Or is there the possiblity of an Admin migrating my thread to the correct forum?
I have only worked on projects, in the past, where members merely submitted patches for acceptance. I apologize for my lack of understand and thank you for your patience.
If you want to release a community version of LE for that device via these forums you are welcome.
I accept the responsibility of maintaining and releasing a community version of LE for the Intel Compute Stick.
Which fourm is the most apropriate for me to post updates concerning my build? I do not want to get into trouble for random posts...
Thank you for providing a reference link. It looks like I have a lot of homework ahead of me... I think this may be too bleeding edge at the moment and may wait until the rest of the components make it into LibreELEC master.
Thank you for the response!
I find it confusing that there are .mk files for the libretro packages in packages/mediacenter/kodi-binary-addons/ and in packages/emulation/
Howerver, with your input, I found that I could build specific items in packages/mediacenter/kodi-binary-addons/ using the command 'PROJECT=Generic ARCH=x86_64 scripts/create_addon game.libretro.*'
I can then install the individual addons without issue.
Does anyone know what the next step is? How does one actually use one of the emulators?
Greetings,
I have tried looking through the scripts but cannot seem to find where the items located in packages/emulation/ should be placed in order to be built during the make image request.
Can anyone point out what I am missing?
Thank you for responding!
I would be more than happy to maintain this community version, as I do realize it is in reality a very small community. What is the most appropriate method for releasing a community version of LibreELEC via the forums? I don't want to cause any problems by posting on the wrong boards.
I knew about the Wi-Fi driver inclusion in the Linux-next kernel, but also knew that it could be months before it made it into an official kernel and then months more before LibreELEC acceptance. However, as far as I know the Bluetooth code is not set for upstream as it is not written as a kernel module but as a user space application. I can maintain my community build independently until the Wi-Fi driver is officially included in LibreELEC, while at the same time I can work to legitimately include the Bluetooth code. Afterwards my fork will no longer be necessary.
I will watch for the next PR and make appropriate comments for required changes to support the BOXSTK1A8LFC and BOXSTCK1A32WFC.
erythros
I apologize for posting here, but I was unsure as to where to make the following request:
I have developed a new community build of LibreELEC based on version 8.0.1 that fully supports the hardware of the Intel Compute Stick BOXSTCK1A8LFC/BOXSTCK1A32WFC. The current Generic x86_64 project did not support the SDIO WiFi or UART HCI Bluetooth due to inadequate driver and kernel support. I forked LibreELEC and implemented the additional hardware support to coexist with the originally supported platforms. Thus, if my fork was to be merged back into version 8.0.1, it should integrate seamlessly with the original source and be transparent for developers working on other platforms. I am currently referring to my LibreELEC as version 8.0.1.2.
Being new to the LibreELEC community, I didn't know if I am allowed (or even how) to request my fork be included into the officially supported source or if I can request a new dedicated community for Intel Compute Sticks such as the BOXSTCK1A8LFC and the BOXSTCK1A32WFC.
Any and all feedback is appreciated.
v/r,
erythros
I have successfully built LibreELEC 8.0.1 for the Intel Compute Stick BOXSTCK1A8LFCL.
The BOXSTCK1A8LFCL has the following hardware:
Currently working:
What does not work:
The source is located here:
GitHub - sorhtyre/LibreELEC.tv at 8.0.1.2
A compiled image is located here:
BOXSTCK1A8LFC - 8.0.1.2
UPDATE - 29 May 2017
* Generic - 8.0.2.1 - Based on LibreELEC 8.0.2 using Generic build options to maintain compatibility with addons.
projects/Generic/filesystem/lib/firmware/myfirmware.dat <= will add a specific file to a specific folder in the image
Turns out for my purpose I needed:
projects/BOXSTCK1A8LFC/filesystem/usr/lib/firmware/rtlwifi/myfirmware.bin
I just figured out where this copy operation occurs:
# copy project related files to filesystem
if [ -d "$PROJECT_DIR/$PROJECT/filesystem" ]; then
cp -PR $PROJECT_DIR/$PROJECT/filesystem/* $INSTALL
I apologize for wasting time...
Fantastic! Under my current set up, I have created a new project folder in order to minimize my impact on the rest of the build tree. I copied Generic and renamed the new project BOXSTCK1A8LFC. I will modify the myfirmware.dat accordingly.
Thank you very much!
