Hacking Dev LaunchmyCraft Ported Lakka to the Switch

  • Thread starter Thread starter Deleted User
  • Start date Start date
  • Views Views 56,575
  • Replies Replies 328
  • Likes Likes 18
OK @Natehaxx I just encountered the same error with missing files on a fresh clone.
It is missing stuff in /home/USER/Lakka-LibreELEC-Lakka-V2.1-dev/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c/include

I've zipped up the files needed to be added in there. Please note. the asm folder in include is NOT the same as the asm in the include/uapi dir. Adding the contents of this zip to the directory above will fix the compile to a 100% image
 

Attachments

Gotcha, I am down for testing some builds since my switch is just collecting dust. What is working right now?
 
Ok don't kill me bc I dont remember fully, as I was not documenting anything. The folder was /home/natehaxx/Lakka-LibreELEC-Lakka-V2.1-dev/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c/include/uapi. This folder will give a compile error as it is missing somewhere (or was missing here, and I got it from another folder --one way or the other i cant remember). But it's definitely that one. Again, this won't fix the glob.c thing, that seems to be an environment issue. It can't be a toolchain issue, because @natinusala is a frigging BEAST scripting this whole friggin compile. Seriously, most beautiful work I have ever seen. I commend you @natinusala; just the sheer precision, forethought, detail... It's gorgeous....

Anyway, you'll know where the folder goes. His makefile continues, so once it errors, you add, and run the make command, it will continue until you make mrproper or clean

I didn't make all this though. Lakka is a fork of LibreELEC with basically RetroArch instead of Kodi. I just made it compatible with the Switch.

By the way you should have a build error for barrier.h while building Linux somewhere. To fix it just delete the linux-* folder in the build.* folder and run the make command again.
 
No, it doesn't. You can just stop the battery from desyncing. Charge to 100% in horizon. Power off. Boot to Linux. Either leave it plugged in the whole time, or plug in for a while before you shutdown Linux. 100% battery before, 100% battery after. Synced. Don't say things are useless just because you can't do it, or because it inconveniences you. Kthx

Nice Idea, had the same Idea myself. To bad it doesnt work.
I work with Shofel2 since day one, trying to get a Stable Ubuntu with all the Stuff working. A friend of mine currently works on Audio and makes great process but I have not found a fix for that stupid Desync.
 
  • Like
Reactions: Deleted User
OK @Natehaxx I just encountered the same error with missing files on a fresh clone.
It is missing stuff in /home/USER/Lakka-LibreELEC-Lakka-V2.1-dev/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c/include

I've zipped up the files needed to be added in there. Please note. the asm folder in include is NOT the same as the asm in the include/uapi dir. Adding the contents of this zip to the directory above will fix the compile to a 100% image

this is my issue i got inside the switch lakka folder only configtools , make-4.2.1 and toolchain any clue ?
 
I didn't make all this though. Lakka is a fork of LibreELEC with basically RetroArch instead of Kodi. I just made it compatible with the Switch.

By the way you should have a build error for barrier.h while building Linux somewhere. To fix it just delete the linux-* folder in the build.* folder and run the make command again.
Oh gotcha. As far as the barrier.h thing, I fixed it by adding that asm folder in include , see first post of this page.

@Natehaxx the build folder is created once you start the make. At some point it will error out with barrier.h, you can fix it how @natinusala mentioned above by deleting the file, or by adding the files in my .zip (you will have to run the distro project make to get the build folder started)

--------------------- MERGED ---------------------------

Nice Idea, had the same Idea myself. To bad it doesnt work.
I work with Shofel2 since day one, trying to get a Stable Ubuntu with all the Stuff working. A friend of mine currently works on Audio and makes great process but I have not found a fix for that stupid Desync.
It works at least for me. My theory is higher fw people have a harder time with the desyncing. I had the desyncing originally at 67%. Unplugged battery and have been using the 100% thing.

as far as fixing battery monitor in Linux, it isn't as simple as it sounds. The OS is running from an SD, the fuel gauge is embedded and likely encrypted into the lower level storage of the nx... So yea, it won't be easy, it won't be pretty, and it won't be any time soon. It will eventually get fixed, but may as well love with it. Battery unplug only takes like 4 minutes if anything.
 
Oh gotcha. As far as the barrier.h thing, I fixed it by adding that asm folder in include , see first post of this page.

@Natehaxx the build folder is created once you start the make. At some point it will error out with barrier.h, you can fix it how @natinusala mentioned above by deleting the file, or by adding the files in my .zip (you will have to run the distro project make to get the build folder started)

--------------------- MERGED ---------------------------


It works at least for me. My theory is higher fw people have a harder time with the desyncing. I had the desyncing originally at 67%. Unplugged battery and have been using the 100% thing.

as far as fixing battery monitor in Linux, it isn't as simple as it sounds. The OS is running from an SD, the fuel gauge is embedded and likely encrypted into the lower level storage of the nx... So yea, it won't be easy, it won't be pretty, and it won't be any time soon. It will eventually get fixed, but may as well love with it. Battery unplug only takes like 4 minutes if anything.

well i got those alloc errors
 
well i got those alloc errors
i dont see anything, just your text. switch to debian 9.4, install all build deps, and let'er rip. you don't understand how many ours i spent fixing 18.04 until i finally just flicked it off, screw new ubuntu

also @natinusala i boot the new commit, ad its beautiful. joycon dpad indeed works. i was able to load up the 2048 core and play a little lol.

im late af to work so i cant do much...meh... but i had to at leaset run something lmao.

i wouldn't stress the barrier.h compile issue too much as it's only like a minute fix.

well done sir! ill try to test some gba or something later... i had to leave this compiling overnight on my i5 ultrabook, as the skylake i7 desktop only has ubuntu 18.04 for now... and i hate 18.04...im betting 18.10 will be like... melted.
 
I suggest you enable Hard GPU sync in latency settings to fix the lag in the menu. Games will hovewer run too fast, if you have a fix / configuration to address this issue I'd be glad to include it in the image
 
I suggest you enable Hard GPU sync in latency settings to fix the lag in the menu. Games will hovewer run too fast, if you have a fix / configuration to address this issue I'd be glad to include it in the image

normally inside the RA settings you could change the FPS Rate , i will try when i am back home
 
not actually quoting you

hey so interesting thing just happened...
i used the reboot (rcm) button, and it took me to this safe-mode looking lakka with 8 bit font. the interesting thing is, joycon sticks respond here... also, touchscreen. albeit, very badly.... but they work!

actually, touchscreen is precise. and stick also precise, its just off to the right, it's weird. i made a clip
 
Last edited by Tilde88,
The 8-bit font is what happens when the storage gets corrupted somehow and the retroarch config file gets reset. All the paths are wrong and you don't have the font, the images or the joypad autoconfig. However this is quite interesting as it will help me to find the correct configuration ; could you pull the file .config/retroarch/retroarch.cfg file from the storage partition and give it to me please ? I'll see how the joypad and touch screen gets configured (the touch screen is not calibrated though, it's currently flickering)
 
  • Like
Reactions: Deleted User
The 8-bit font is what happens when the storage gets corrupted somehow and the retroarch config file gets reset. All the paths are wrong and you don't have the font, the images or the joypad autoconfig. However this is quite interesting as it will help me to find the correct configuration ; could you pull the file .config/retroarch/retroarch.cfg file from the storage partition and give it to me please ? I'll see how the joypad and touch screen gets configured (the touch screen is not calibrated though, it's currently flickering)

Ahhh, ok makes sense... Here is the full story. I was being naughty, and thought the OS was loaded to RAM. I took out the SD card while boot. Then I realized it did not pick up any cores (after re-inserting the SD card with new roms and such), used the reboot (rcm) and landed me there. SO with that knowledge it may not be useful to you. However, i did not boot lakka back up, so if something was written in that config, it shouldn't have been undone/overwritten. idk. here is the file, and vid also
https://sendvid.com/fm5ugqo0
 

Attachments

Last edited by Tilde88,
hey so interesting thing just happened...
i used the reboot (rcm) button, and it took me to this safe-mode looking lakka with 8 bit font. the interesting thing is, joycon sticks respond here... also, touchscreen. albeit, very badly.... but they work!

actually, touchscreen is precise. and stick also precise, its just off to the right, it's weird. i made a clip

Code:
root@debian:~/Lakka-LibreELEC/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c# make -f Makefile
  YACC    scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
scripts/Makefile.lib:217: recipe for target 'scripts/kconfig/zconf.tab.c' failed
make[2]: *** [scripts/kconfig/zconf.tab.c] Error 127
Makefile:507: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'.  Stop.
root@debian:~/Lakka-LibreELEC/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c

any clue
 
Code:
root@debian:~/Lakka-LibreELEC/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c# make -f Makefile
  YACC    scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
scripts/Makefile.lib:217: recipe for target 'scripts/kconfig/zconf.tab.c' failed
make[2]: *** [scripts/kconfig/zconf.tab.c] Error 127
Makefile:507: recipe for target 'silentoldconfig' failed
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'.  Stop.
root@debian:~/Lakka-LibreELEC/build.Lakka-Switch.aarch64-2.1-devel/linux-01b404c

any clue
yes sir. use the string he provides within the /project/switch folder.
somethings like DISTRO=lakka PROJECT-switch yadda yadda make image

also you need to cd ../../
 
Last edited by Tilde88,
  • Like
Reactions: natinusala
I also get the same joystick and touchscreen response when failing to load a DS rom. it eventually says failed to load, and goes back to lakka. but in the core it seems something is going right with the drivers :-p.

anyway, hope this info helps. great work with this!!
 

Site & Scene News

Popular threads in this forum