I’ve just tried updating manually to the latest nightly (Lakka-imx6.arm-devel-20160303085716-r21349-g1212325) and after installation and rebooting the screen goes black, nothing happens and the device is inaccessible. I had to reflash, copy all my stuff to the SD and try again.This time with the SSH update (lakka-update) - same thing happened again 
Is there maybe something wrong with the latest version? Did anyone else have the same problem, maybe?
Hi,
There is recent commit about imx6 that may fix your problem. Can you retry with the latest nightly available.
Thank you for your test.
[QUOTE=gouchi;35446]Hi,
There is recent commit about imx6 that may fix your problem. Can you retry with the latest nightly available.
Thank you for your test.[/QUOTE]
No success unfortunately - after installation the device won’t boot and needs re-flashing :-/
Can you boot with liveusb and try to ssh your device if it is connected on ethernet to get some information ?
I’ve installed the release-version from february and this works fine - updates have been working fine so far as well except for the last nightlies. I can - of course - SSH to the device. But what information shall I get?
Can you try to type :
systemctl stop retroarch
retroarch --menu --verbose >> log.txt 2>&1
And copy also the output of dmesg to hastebin for example, just type :
dmesg
[QUOTE=gouchi;35635]Can you try to type :
systemctl stop retroarch
retroarch --menu --verbose >> log.txt 2>&1
And copy also the output of dmesg to hastebin for example, just type :
dmesg
[/QUOTE]
I don’t get why this could be helpful for debugging since the version I can SSH to is working perfectly. After the update the issue arises - and I can’t SSH after the update because it’s not booting anymore.
Do you know which last version was working for you ? I know that recently graphic packages have been updated.
So if you can’t ssh, can you try some boot arguments (Press Tab when the menu shows up and add them at the end of the line) ? debugging or textmode so that you can get some information on what is going on.
[QUOTE=gouchi;35646]Do you know which last version was working for you ? I know that recently graphic packages have been updated.
So if you can’t ssh, can you try some boot arguments (Press Tab when the menu shows up and add them at the end of the line) ? debugging or textmode so that you can get some information on what is going on.[/QUOTE]
The last released version (February) works fine. I’m a bit afraid of trying to update again as it’s really time consuming to reflash and copy all the roms to the empty card. But I’ll try debugging checking boot arguments once I’m up for another try 
To me it seems it’s not even booting though - there’s no “red light” on my Cubox - there seems to be an issue already at that stage - but I’ll check.
Thanks a lot for your help!
Ok, I will ask twinaphex to test the image.
The imx6 image works well on my UDOO.
What hardware are you using exactly?
[QUOTE=Kivutar;35654]Ok, I will ask twinaphex to test the image.
The imx6 image works well on my UDOO.
What hardware are you using exactly?[/QUOTE]
I’m on a CuBox-i4Pro, really have no clue what’s different from the previous updates :-/
I have the same issue with the same hardware (CuBox-i4Pro). Just a black screen. Currently running a build from November that works.
Can you try to boot by adding boot arguments debugging textmode ?
To get some log.
dmesg
systemctl stop retroarch
retroarch --menu --verbose >> log.txt 2>&1
I’ll try to do that this evening, but I’ll be getting home late tonight. I’ll also need to make a new backup of my card and run the update again. I lied apparently, I’m actually currently on a working build from February, just like the OP.
Okay, I now have a second microsd for testing, so I don’t have to worry about messing up my working setup.
With the latest nightly (20160410), I was unable to SSH into the system at all.
Per your comment above, I added “debugging textmode” to my uEnv.txt file on the card, so that the full file reads:
zImage=/KERNELbootfile=/KERNEL mmcargs=setenv bootargs 'boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 quiet video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24,bpp=32 dmfc=3 consoleblank=0 loglevel=2 vt.global_cursor_default=0 ssh debugging textmode'
Still no love from SSH.
If that’s not correct, could you please give me a little more direction. I’d really like to figure this out.
The option textmode should boot into a local terminal. Try to make tests with other boot arguments (noplash, break=load_modules or break=load_splash).
Adding those, one at a time, to the boot arguments did nothing. (I also assume you meant nosplash, although I tried both.)
Did you try with only textmode as boot argument ?
My first attempt was adding “debugging textmode” to the default boot arguements, as I had shown above. If that’s not what you meant, then you might need to be a little more specific.