Add it to /flash/EFI/BOOT/syslinux.cfg.
Posts by escalade
-
-
-
I'm using Chrome in my community build, perhaps it can be of interest. Netflix works fine.
-
-
-
Is it confirmed that Gemini lake will have native HDMI? AFAIK even the next coffee lake NUC's will have LSPCon converter.
-
20171012:
Codelinux: update to 4.13.6 emulationstation: add dos to romdir and es_systems dosbox-sdl2: use /storage/.config/dosbox by default and add shaders alsa-lib: add another upstream cherry trail / baytrail patch kodi: add patch to fix accelerometer preventing screensaver dosbox-sdl2: add mt-32 support munt: update to 0ace855
I've attempted to improve the DOSBox support in this build. DOS games can now be put under /storage/roms/dos, this directory is mounted as your C drive by dosbox's default configuration /storage/.config/dosbox/dosbox-SDL2.conf. Emulationstation looks for .conf files here as well.
Here's an example how to add a game:
1. Copy your game directory to /storage/roms/dos/example.
2. Copy over the default configuration to /storage/roms/dos/example.conf.
3. Modify example.conf and adapt the autoexec in the bottom to start the game.
4. Launch Emulationstation and you'll see your game under "PC".
You can also run dosbox.sh to simply start dosbox with the default configuration.
- The crt-easymode shader is enabled by default
- Gravis Ultrasound data files can be installed to /storage/roms/dosbox/ULTRASND
- Roland MT-32 ROMs can be installed to /storage/roms/dosbox/MT32
- Gamepad can easily be mapped to keyboard presses using the examples here (set mapperfile= to something unique in your game .conf)
Been having a lot of fun playing LBA2, Raptor Call of the Shadows and Pinball Fantasies on the bigscreen with my DS4.
-
What do you mean? There's been several people that were successful in getting 4k@60 on Intel, although xrandr was needed (don't know if that's true for everyone).
-
Intel is the better choice for HTPC, Apollo lake and up does HEVC 10 bit in hardware.
-
-
Well yeah, depends on if they merge it. I can't see why not though, and then it'll be in the next LE release.
-
-
-
In that case you could try the Cherry trail build, it also has 4.14 kernel (which is what I wanted to test).
The only difference I can spot in the log is this:
Code[ 3.993082] wl 0000:03:00.0: enabling device (0100 -> 0102) [ 4.246427] wlan0: Broadcom BCM43a0 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334)
No idea why this isn't happening in my build. Perhaps some kernel option changed and now needs enabling or similar. Doesn't seem to be any calls for firmware. If you can point to what's lacking I'll fix it.
-
The autostart.sh file is the last thing that's run before Kodi starts, so the system is otherwise fully booted. So creating a sleep loop there will prevent Kodi from starting.
I'm still confused as to what you are going to do next. You realize that LibreELEC is not a standard Linux distribution with a package manager, right? There's no webserver shipped with LibreELEC. There is OpenVPN so you can set up your box as a VPN client, but then what?
-
You could put a sleep loop in autostart, but what would you use LibreELEC for then?
-
This is due to a long standing Kodi bug regarding accelerometers being interpreted as actions and thus preventing the screensaver. There's a PR for it that might be included for 17.5: [Backport] Joysticks: Fix accelerometers preventing screensaver by garbear · Pull Request #12900 · xbmc/xbmc · GitHub
-