Posts by bite_your_idols


    Everything works fine with LE8 and AEL. Only the NES Emulator is not working. When i load the rom, then LE shut down. Is it possible to change the NES emulator by hand?

    Is it also possible to change the screen in 16:9?

    Sorry for my bad english... :D

    It is an error I miss when I rename some cores. You can edit with context menu and change advance settings, then look for arguments or something similar.
    Find "fceu %ROM%" and replace with "fceumm %ROM%" . Just add "mm" at the end of the core name.

    In the upcoming new version this will be fixed and a lot of another things will be included...

    About 16:9 browse in retroarch video settings.


    Ah, I see why now. Looks like I've lost the commit between branches at some point, I'll enable it for the next release.

    If you boot from USB and enter "live" at the boot prompt that should give you a tty so you can check the Xorg log.

    If I enter "live" it tries to boot libreelec, then the same error prompts, and I am in the same situation, no console, no write...
    I have plugged the usb to lakka hdd and I can get syslinux.cfg:

    I don't know if I can edit this to "add" a console option to look for the log...


    If you call getting a logfile a challenge, then I guess so :) I'm guessing you don't have a console because you upgraded from Lakka or whatever. You need "tty" in the kernel commandline (i.e. /flash/syslinux.cfg or /flash/EFI/BOOT/syslinux.cfg for EFI). My builds have that by default when you do a new install. Swapping the harddrive won't work because /var is on tmpfs, but you will be able to edit syslinux.cfg.

    I use different HDDs for lakka and LE so it is not the problem...

    I burn your build to my flash USB, plug into PC, boot from flash, install LE in HDD, after installation a reboot message appears. After rebooting, LE splash screen appears and then xorg error prompts. If I try to enter console during booting, only cursor appears and then xorg error in every console. If I try to open console after error prompts, just cursor blinking and no text input response.

    I understand I need to access "/var/log/Xorg.0.log" to know what is happening, but I don't know how... How do I tty in the command line? using installation USB? Maybe using "live" version instead of installing in the HDD would help?


    Doesn't sound like you spent any time at all other than booting it up. Your problem is most likely easily fixable and the answer should be in the log, but if that's a task too big then I can't help :)


    are you challenging me? :D Only thing I think I can try is attaching the HDD to another linux based PC and try to get the log... maybe in the same PC booting lakka can access your build's log...


    You can connect a keyboard and do CTR+ALT+F3 and you have a shell.

    Yes I have a keyboard connected but I can not write or control anything. In error screen (or during boot with LE splashscreen) I can not open any shell, if I do CTR+ALT+F3 it just shows a black screen with a blinking cursor but I can not write in it...

    Anyways, thanks for your patience and help, but I think it does not deserve the time I am (and you are) spending on it... I will stick into lakka. Thanks again.


    And what does your /var/log/Xorg.0.log say?

    I can not reach that log... Since there is no wired network connection I can not access this PC until libreelec starts and wifi connects.

    If I use LibreELEC's alpha build it also happens, but in LibreELEC 7 it works fine, it installs in a cople of minutes, stars and wiffi connects... :huh:

    EDIT: if I unplug video card error still happens but in your previous build when I unplug it kodi enters and no error prompts.


    bibi

    Because Dolphin is not a libretro core and isn't supported by RetroArch, you need to use Emulationstation instead. Also update to the latest build, it adds -v to retroarch options so there should be something in /tmp/retroarch.log when you launch a saturn game.

    bite_your_idols

    Try the latest full rebuild :)

    New build 20161121:

    Code
    - Switched to duganchen's Dosbox fork using SDL2 (https://github.com/duganchen/dosbox/blob/master/ENHANCEMENTS.md)
    - Rebased on latest LE master which now uses GCC6 and has quite a few updated packages
    - Updates to RetroArch, Mesa, Dolphin, SDL2
    - Added mkfs.ntfs and other NTFS tools (like ntfsresize)

    no way.

    New build 20161115:

    Code
    - Added back nvidia legacy drivers (this will probably need to go to make room for other things as I've maxed out 512MB for generic at this point)
    - Enable SMB2 and SMB3 support for the kernel CIFS module
    - Updated kernel to 4.8.7
    - Updates to glupen64-libretro, retroarch-joypad-autoconfig, libretro-database, snes9x2010-libretro, scummvm-libretro, mgba-libretro, mesa and retroarch
    - Fixed an issue with nmon

    I tried this build in my PC and the xorg error still happens... can I manually fix that? Yes, I get bored of retroarch frontend so quickly... :D

    Hi bite_your_idols! I love your addon so far but I am a little confused about the changelogs:

    You mentioned advanced emulator launcher and I just downloaded your newest zip after manually cleaning out my libreelec installation of previous addons from the .kodi and .config directories/subdirectories.

    Now after a fresh install and a reboot I still find advanced launcher installed and not advanced emulator launcher from wintermute0110. Am I missing something or are you only including advanced emulator launcher into the LE8 builds? (I am running 7.0.2 still because of a PVR addon which is currently still in early beta on LE8 due to imputstream.mpd implementation and stuff, so I am stuck with 7.0.2 for the moment, otherwise my wife would kill me if our TV wouldn't work ^^)

    yes, you are right:
    LibreELEC8 -> Advanced Emulator Launcher
    Open/LibreELEC 7/6 -> Advanced Launcher

    you can install AEL manually with this zip, then unzip the content of this package and place into /storage/userdata/addon_data/plugin.program.advanced.emulator.launcher/ and you will have the default gamestarter emulator list in AEL


    If you follow the first Makefile, you'll see that a "make image" runs "scripts/image". You should read that to get a better understanding of how packages are installed. Basically, everything gets installed in there through running "scripts/install package". I simply add dependencies to the "oem" virtual package which is already included in scripts/install. The scripts locates package.mk inside any subdirectory in there.

    yeah! I followed your steps and found OEM_EMU_COMMON, OEM_EMU_GENERIC and OEM_EMU_RPI. I replace your lists with mines and I waiting for compiler...
    Thanks a lot!


    I've got both mame2010 and mame2014 running on the rpi now after borrowing some cross compilation patches from lrusak :exclamation: They work good but you can see small slowdowns in some games on '10 and on most games with '14. The binary size of '10 is 50MB and '14 is 97MB. Guess it's like they say, later versions of mame are more accurate but at the cost of performance. Also the rpi isn't very powerful. Everything is silky smooth in the mame2003 core though.


    mame2003 FTW! also, in latest builds it includes core input configurations from retroarch quick menu instead using system settings menu.


    anyways, anyone using a 8bitdo controller? I am in love with the SFC30 model but I need to be sure that it works in LibreELEC/retroarch...


    As they often do in RetroPie they probably used an old commit and/or fixed it up. If the latest available code does not compile and work I consider it broken and unsupported. I got it compiled for generic, but when I run it the aspect looks wrong and the graphics are grainy.

    I just tried mame2014 on generic and it runs great. Works on rpi as well except there is no sound. Will investigate a bit but it looks to me like mame2003 is still the way to go...

    If you want to try it, you can download here. I tried your mame2014 core and it runs more slowly and with choppy sound, my 2010 works better, at least with the only game I tried. But, as you said, the best mame is 2003, it is what I use, mame2010 core is just for that game I posted before, a classic arcade game of my chilhood.


    One quick question about compiling , when you exec "make image" does it detect automatically all packages defined in packages folder or you have to define them in some file?


    @bite_my_idols

    I'd say you give up quick, but sure use whatever works for you :) Maybe your card is an older geforce 6 or 7 series? I removed the nvidia legacy drivers from recent builds to save some space didn't think anyone used those. If I include them them the generic build is at a full 512MB. As for the wireless issue, surely there are hints in the system log. LibreELEC uses connman and so should support most wireless configurations.

    Regarding the mame core I'm currently investigating the status of the different versions. I went with 2003 previously as it was the only one that was properly maintained, and it's also just 30MB binary. If you are using the 2010 core on your pi then I guess it's an old binary from somewhere because the current mame2010 core does not compile for the rpi.

    I've uploaded mame2014 for the rpi on my gdrive if you want to give it a go.

    yeah, you're right, I give up quick this time :P... In my pi I can spend all time it needs but in the arcade PC I don't want to spend a minute more than it needs, it is just for a quick mame plays occaionally. The card is a geforce 6 series and I guess wireless issue can be easily fixed but since the PC is inside the arcade cabinet, far away from wired internet connection I give up.
    Maybe, when I get bored from retroarch and want emulationstation give LibreELEC a new try...

    About mame2010, I compiled it some months ago using retropie's experimental menu, and it works. Today I compiled it for generic using lakka toolchain and now it is working in my arcade cabinet, but I will take a look to mame2014, I will try it later in my py, thanks for the binary.


    I've removed the shutdown options, look in the emulationstation patches. I'm using default Estuary, look here.

    About Arcade PC, I am going to stay in lakka because my graphic card is not compatible with your build. I removed it but then retroarch is so laggy. Also, once in Kodi, it detects my wifi signal but give me error after my password input... And finally, there is the startup/shutdown issues... so I think it not deserves all the time it need to config the system just to play a couple of mame games occasionally. Anyways, thank you.

    About skin mod I discovered that files are in usr folder, I copied them, rename skin and upload to storage folder. Now I edit home.xml as you said. Everything is ok. thanks again.

    One more thing, don't you consider to include mame2010 core? I use in my pi for a couple of more modern games and it works. Is the only way I have to play my lovely World Rally

    nice! first I will try this hack in my pi, then I will install your build in my arcade PC.

    thanks!

    I tried in my Pi and kodi does not start, that's ok, but it seems that external drives are not mounted because emulationstation does not show roms in folder from my external HDDs, just from the ones I have in the sd.

    Another issue with this "hack" is that when you are exiting emulationstation kodi starts... a shutdown option in ES is missing... can this menu be edited in somewhere before compilaton to include that option?


    Also, I want to ask you about Estuary skin. Is the one included in your build the "Estuary mod" skin or you have edited the default Estuary skin?
    I would like to edit/tweak it by myself to include a shortcut in my installed alpha release but I can not find skin files in the habitual addon folder...

    thanks!


    It's certainly possible but it would require some modification. I have been thinking to make it configurable through a file in /storage/.config, but haven't gotten around to it yet.

    As a quick hack you could disable the kodi service in your squashfs and then launch your frontend through autostart.sh.

    ok, the autostart method is what I was thinking about, kill kodi and launch frontend using autostart.sh but I suppose kodi has to start then kill so this will take some extra time during boot.

    I need to get some info about squashfs and its modification.

    thanks again!