Posts by escalade
-
-
-
If you want to hack it, you could remove that limitation here: LibreELEC.tv/systemd-0005-ignore-storage-flash-mount-points.patch at master · LibreELEC/LibreELEC.tv · GitHub
I believe this was introduced for the purpose of not trying to unmount /storage on shutdown as it would fail.
Is SD card corruption really that likely though? Can't say I ever experienced that, and they are so cheap anyways.
-
-
You might be able to do it but you would need to compile yourself and add a service that mounts /storage over NFS right after network comes up.
-
It's impossible to do it via wifi, as the initramfs doesn't have the means to set up a wireless connection. If you can make your RPi PXE boot then you could have /storage (and /flash) on NFS.
-
-
20170919:
Codelibretro-database: remove metadata for mame versions we don't use nfs-utils: minor changes Python: update to 2.7.14 mesa: update to bd903d4 (17.2.1) llvm: update to 5.0.0 RPi,RPi2: add alsa card conf for IQAudIODigi to enable passthrough busybox: disable nfs mounting support so the helper from nfs-utils is used instead busybox: update to 1.27.2 RPi: update firmware to 756dd85 init: recover from a failed upgrade
With LLVM 5.0 and Mesa 17.2.1 the AMD Vega graphics card (which seems to create a lot of buzz these days) should be supported. There's also some minor improvements to Busybox and some fixes to NFS mounting.
-
You could manually partition, install a bootloader and set it up to boot LibreELEC. This requires advanced knowledge of how to boot Linux. There's some dual-boot howto's here and there if you search.
-
I have two, the Wintel CX-W8 Pro and the Tronsmart Ara X5 Plus. Both work great with LibreELEC, but only the Tronsmart has working wifi/bluetooth due to it being an onboard Intel chip. The Intel Compute stick has cherry trail as well, and I've seen reports that wifi/bluetooth work on them too.
-
-
-
Do official .img.gz's work? I guess I can go back to .tar's as I can easily keep below 512MB with Zstd compression. It would be helpful if you could manually do the update steps in the busybox init file, and perhaps see if you can find out why it's failing. I suppose it's the actual mount command, but I can't see why that would fail. When you are in the shell you might find a clue.
-
-
I was talking about the older 1.4 version. I don't believe I've used that version in my docker image, you can probably check the version in the menus somewhere.
I haven't included any auto update feature, so for now you can update the docker images like this to get the last version:
docker pull escalade1/arch-pcsx2
-
20170917:
Code
Display Morealsa-lib: add upstream patch for cherrytrail / baytrail retroarch: update to e5fdc50 retroarch-joypad-autoconfig: update to 837e5d2 libretro-database: update to 525e1f5 vice-libretro: update to 3ef72ef parallel-n64-libretro: update to c052e43 mgba-libretro: update to 24fb0a5 genesis-plus-gx-libretro: update to 04268ad fbalpha-libretro: update to b20cfd4 beetle-saturn-libretro: update to e8afa19 beetle-psx-libretro: update to 05892b1 linux: update to 4.13.2 bluez: update to 5.47 linux: add patch to set connector type when updating ELD (fixes skylake hdmi audio issue)
-
-
The resolution you are running at doesn't matter. PCSX2 renders at native PS2 resolution by default and it'll get upscaled to 1080p or whatever.
I already have a simpler automated setup. PCSX2 1.4 is ancient btw, nearly two years old. Had artifacts and issues with several games on my haswell until I upgraded to the latest git version.