Lakka on Kangaroo mini pc

Libretro Lakka
#34

What is the vesamenu.c32 error @gouchi ?

#35

Can you try to copy vesamenu.c32 to EFI/BOOT directory from Lakka system partition ?

#36

Wouldn’t that mean I would have installed it already ? Lol @gouchi

#37

i tried copying the file from the root of the usb i created into EF /BOOT and it just gives me the static cursor in the top left corner

#38

When you press Enter, it does nothing ?

I am running out of ideas :slight_smile: Last thing you can try is to update syslinux ? Try to change this link to this one and recompile to see if it may fix your issue.

#39

no the whole system locks up when i press enter . i tried the updated syslinux and still wont work …i dont know why i can load windows 10 ubuntu and androidx86 on this kangaroo but not lakka its soooo annoying :frowning: thanks for your help @gouchi

#40

is there a way i can change the kernel like i did the syslinux ?

#41

Yes you can by changing the version here.

To be sure your rebuild it with the new version, can you try DISTRO=Lakka PROJECT=Generic ARCH=x86_64 scripts/clean syslinux DISTRO=Lakka PROJECT=Generic ARCH=x86_64 scripts/build syslinux

Thank you for your tests !

#42

i tried to clean and rebuild same thing …im compiling now with kernel version 4.4.46 …the bad news is i had to remove a few patches in order to get it to build properly …hopefully this works

#43

Can you try to enter run ? Then It should boot to run mode.

#44

do u mean when it says “boot:” ? ive done that it just locks up :frowning:

#45

Can you try to edit syslinux.cfg for run mode and append textmode if you can get to boot to a terminal. If it still doesn’t work, try to append debugging.

Source

#46

Just curious, what happens when you try to boot from USB again? It’s got the same specs as the Lattepanda I have and the LP is working now (as in, it doesn’t need its hand held by another machine in order for it to work LOL).

#47

The menu issue has been fixed with this commit, next nightly after February 11th will have the fix.

#48

I’ve tried the things u asked @gouchi and it still just halts after typing run and appending text mode debugging does not work either @shockwave I just can’t get to the splash screen as it just shows a static cursor on the top left . What did you do to get it working on lattepanda? … I will try the new nightly shortly …

#49

You can try nightly build from today.

#50

Here’s what I did to get it working on Lattepanda:

  1. Download the latest nightly from the LE batch of Lakka images: http://le.builds.lakka.tv/Generic.x86_64/Lakka-Generic.x86_64-8.0-devel-20170212225257-r25640-gc52c1c8.img.gz

  2. Use Rufus to create the image: http://www.techspot.com/downloads/6062-rufus.html

  3. Once you do this, go to the LattePanda, and using a mouse/keyboard, connect the USB drive to the SBC and turn on your PC.

  4. Tap F7 to boot to the BIOS menu and go to the Boot Drive Menu, and select the USB drive to boot from.

  5. The LattePanda wil boot, but this is where I get the vesamenu.c32 error message. But with a blinking cursor after this message, I type “run”, and hit the Enter key on my KB. This takes me to the Lakka boot process and flower.

  6. Lakka boots from the USB and I’m up and running.

Note: When selecting the drive from the BIOS menu, do NOT select the UEFI USB drive. Select the one with the actual manufacturer’s name of the drive on it because that will be the partition that has Lakka and the boot info on it!

#51

the lattepanda must support non efi devices while my kangaroo only supports UEFI devices it only shows the efi boot device in boot menu …

#52

I’ll upload a pic of the boot menu on the Lattepanda to show you what I’m talking about when the boot drive screen pops up later on. I’m at work right now. I’ll try to do it over lunch. :slight_smile:

#53

https://drive.google.com/file/d/0B59oSVMD5Q0lN2Q2bF9uWkRMcnJJT2hxd0I1ZXJoUDFmM200/view?usp=sharing

The drive name is still attached even though the UEFI is in front.