LattePanda - Lakka stuck on flower at boot

Hi, Can anyone offer any advice on getting Lakka to run on a 2GB lattepanda please?

I have seen 1 youtube video which shows it running on a development build but no details on which one.

I presume my problem is a graphics driver issue Are there any bootloader options I need to enable?

Many thanks in advance Phil

edit… here is output from verbose mode…

[INFO] RetroArch 1.7.5 (Git fcf75fd)

[INFO] === Build =======================================

Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 SSSE3 SSE4 SSE4.2 AES

Built: Dec 26 2018

[INFO] Version: 1.7.5

[INFO] Git: fcf75fd

[INFO] =================================================

[INFO] Environ SET_PIXEL_FORMAT: RGB565.

[INFO] Redirecting save file to “/storage/savefiles/.srm”.

[INFO] Redirecting savestate to “/storage/savestates/.state”.

[INFO] Version of libretro API: 1

[INFO] Compiled against API: 1

[INFO] [Audio]: Set audio input rate to: 29970.03 Hz.

[INFO] [Video]: Video @ fullscreen

[INFO] [Video]: Starting threaded video driver …

[INFO] [DRM]: Found 5 connectors.

[INFO] [DRM]: Connector 0 connected: yes

[INFO] [DRM]: Connector 0 has 1 modes.

[INFO] [DRM]: Connector 0 assigned to monitor index: #1.

[INFO] [DRM]: Connector 1 connected: no

[INFO] [DRM]: Connector 1 has 0 modes.

[INFO] [DRM]: Connector 2 connected: no

[INFO] [DRM]: Connector 2 has 0 modes.

[INFO] [DRM]: Connector 3 connected: no

[INFO] [DRM]: Connector 3 has 0 modes.

[INFO] [DRM]: Connector 4 connected: yes

[INFO] [DRM]: Connector 4 has 30 modes.

[INFO] [DRM]: Connector 4 assigned to monitor index: #2.

[INFO] [DRM]: Mode 0: (1024x600) 1024 x 600, 60 Hz

[INFO] [GL]: Found GL context: kms

[INFO] [GL]: Detecting screen resolution 1024x600.

[INFO] [EGL] Found EGL_EXT_platform_base, trying eglGetPlatformDisplayEXT

[INFO] [EGL]: EGL version: 1.4

[INFO] [EGL]: Current context: 0xb458db98.

[INFO] [KMS]: New FB: 1024x600 (stride: 4096).

[INFO] [GL]: Vendor: Intel Open Source Technology Center, Renderer: Mesa DRI Intel® HD Graphics (Cherrytrail) x86/MMX/SSE2.

[INFO] [GL]: Version: 3.0 Mesa 17.1.3.

[INFO] [GL]: Using resolution 1024x600

[INFO] [GL]: Default shader backend found: glsl.

[INFO] [Shader driver]: Using GLSL shader backend.

[INFO] [GLSL]: Checking GLSL shader support …

[WARN] [GL]: Stock GLSL shaders will be used.

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] Setting up menu pipeline shaders for XMB …

[INFO] [GLSL]: Compiling ribbon shader…

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Compiling simple ribbon shader…

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Compiling snow shader…

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Compiling modern snow shader…

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Compiling bokeh shader…

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] [GLSL]: Compiling snowflake shader…

[INFO] [GLSL]: Found GLSL vertex shader.

[INFO] [GLSL]: Found GLSL fragment shader.

[INFO] [GLSL]: Linking GLSL program.

[INFO] Resetting shader to defaults …

[INFO] [GL]: Using 4 textures.

[INFO] [GL]: Loaded 1 program(s).

[INFO] [GL]: Using GL_RGB565 for texture uploads.

[INFO] [Font]: Using font rendering backend: freetype.

[INFO] [Video]: Graphics driver did not initialize an input driver. Attempting to pick a suitable driver.

[INFO] [udev]: Keyboard #0 (/dev/input/event3).

[INFO] [udev]: Keyboard #1 (/dev/input/mouse0).

[INFO] [udev]: Keyboard #2 (/dev/input/event4).

[INFO] [udev]: Mouse #0 (/dev/input/event3).

[INFO] [udev]: Mouse #1 (/dev/input/mouse0).

[INFO] [udev]: Mouse #2 (/dev/input/event5).

[INFO] [udev]: Mouse #3 (/dev/input/mouse1).

[INFO] [Joypad]: Found joypad driver: “udev”.

[INFO] [Video]: Found display server: null

[INFO] Found shader “/tmp/shaders/bilinear.glslp”

[INFO] Found shader “/tmp/shaders/nearest.glslp”

[INFO] Found shader “/tmp/shaders/slang-conversion-template.glsl”

[INFO] Found shader “/tmp/shaders/stock.glsl”

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/confmisc.c:767:(parse_card) cannot find card ‘0’

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/conf.c:4554:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/confmisc.c:392:(snd_func_concat) error evaluating strings

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/conf.c:4554:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/confmisc.c:1246:(snd_func_refer) error evaluating name

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/conf.c:4554:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/conf.c:5033:(snd_config_expand) Evaluate error: No such file or directory

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib-1.1.4.1/src/pcm/pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM default

[ERROR] ALSA: Failed to initialize…

[ERROR] Failed to initialize audio driver. Will continue without audio.

[INFO] [Menu]: Found menu display driver: “gl”.

[INFO] [Font]: Using font rendering backend: freetype.

[INFO] [Font]: Using font rendering backend: freetype.

[INFO] [LED]: LED driver = ‘null’ 0x8417a14

[INFO] [MIDI]: Initializing …

ALSA lib /mnt/data/PROJECTS/Lakka-LibreELEC/build.Lakka-Generic.i386-2.2-devel/alsa-lib1.1.4.1/src/seq/seq_hw.c:466:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory

[ERROR] [MIDI]: snd_seq_open failed with error -2.

[ERROR] [MIDI]: Initialization failed (list of input devices unavailable).

[INFO] SRAM will not be saved.

[INFO] Loading history file: [/storage/.config/retroarch/content_history.lpl].

[INFO] Loading history file: [/storage/.config/retroarch/content_favorites.lpl].

[INFO] Loading history file: [/storage/.config/retroarch/content_music_history.lpl].

[INFO] Loading history file: [/storage/.config/retroarch/content_video_history.lpl].

[INFO] Loading history file: [/storage/.config/retroarch/content_image_history.lpl].

[ERROR] failed_to_start_audio_driver

[INFO] [Font]: Using font rendering backend: freetype.

[INFO] [Font]: Using font rendering backend: freetype.

[INFO] [KMS]: New FB: 1024x600 (stride: 4096).

[INFO] [KMS]: New FB: 1024x600 (stride: 4096).

Same problem here. Stuck at the flower screen.

Former owner of the LattePanda board here. I do believe you have to disable the UEFI boot sequence and enable it to Legacy instead in order to do the proper installation to the eMMC module on board the Lattepanda in order for Lakka (or any Linux builds for that matter) to work properly. Go into the LattePanda BIOS/Setup upon booting and try changing that first. Then install Lakka onto the eMMC and try booting it up.

Thanks very much for responding.

I was trying to run Lakka from a pen drive at least to start with, and see what the performance is like , however if eMMC is the only way it is going to work I am willing to erase Win10 which is currently on the internal flash.

I have flashed the “linux compatable” BIOS for the LattePanda, and I can succesfully boot live Ubuntu from a pen drive.

The youtube video I mentioned earlier is running Lakka from the pen drive, with a development build, however the poster seems to be unwilling to share how he achieved this.

If you’re referring to ETA Prime’s video for the LattePanda: https://www.youtube.com/watch?v=POJxmI3HPF0

gouchi was the one who provided the build I believe. ETA is also a member of these forums, so you can hit him up directly if you wish. But the LattePanda builds are the LibreElec-based builds you probably should look here (and referring to booting from the pen drive, initially, I did have a hard time, but did get it to work eventually, but forgot how, and sold off my LattePanda board later on): http://nightly.builds.lakka.tv/

Thanks for responding.

Just to clarify… I’m looking in the experimental LE master directory and choosing a Generic X86 build?

Many thanks for your assistance

Phil

That’s what I would try. NO guarantee of success, but that is what I tried.

I have the same ALSA problem with installing latest Lakka. I was able to boot /experimental_LE-master referred to here, but only from command line. Any suggestions on how to get the latest lakka builds to run on lattepanda?

thanks in advance

Ok, got 2.2.2 lakka installed on lattepanda. For others benefit that are new to both, like me…this is what I had to do:

  1. install Lakka 2.2.2 on eMMC from USB stick

  2. boot ‘live ssh’ from USB stick, and ssh into your lattepanda

  3. once you’re in, df -h should reveal your eMMC partitions, but easy path is /storage/roms/System files: syslinux.cfg EFI/BOOT/syslinux.cfg there, you’ll need to append ‘ssh video=DSI-1:d’ to you kernel boot The last line in the syslinux.cfg files should look similar to this: APPEND boot=LABEL=System disk=LABEL=Storage vt.global_cursor_default=0 loglevel=2 ssh video=DSI-1:d (this is to use the hdmi input, and allow ssh into your lakka at all times)

  4. now you should boot fine and get to main menu. If you have trouble with retroarch.cfg, you can try to remove the config and run it cmd line ‘retroarch -v’, to create a fresh cfg.

Wish I had these instructions when i started tinkering with lattepanda… :slight_smile:

1 Like