Posts by Da Flex

For 4K you need an HDMI 2.0 or 2.1 cable. Slow HDMI cables can cause the described issues.

Quote from myshit

It shutdowns ok with SSH or from GUI. The only thing is the red LED that still keeps turned on preveting me from turn the Rpi again back on after shutdown - I have to manually press the button for few seconds.

I see. Then the shutdown actually doesn't work as expected, because the red LED stays on.

The cause of such issues is often a file system with errors. Broken file systems can't be unmounted at shutdown. If you only use the microSD for files, then install LE from scratch, or use a repair tool for checking / repairing.

Quote from myshit

Yes, the poweroff command is working ok via SSH. I don't think that bluetooth is has something in coincidence with it

So shutting down from GUI hangs, but shutting down from SSH works as expected.

Both tested without the Argon One case. Are those statements correct?

If yes, then I'll ping the devs to have a look.

Go to the forums main page, click on the magnifier icon (top right), and search for "Argon One". You'll find a lot of results.

Thanks. The YouTube API error doesn't appear at the new logs. So that's obviously not the cause of the issue.

Next I'll test testfile2.TS (post #41) on my RPi (LE 11.0.3). Stay tuned.

Thanks for the log.

• Login by SSH, and use the poweroff command. Does that work correctly?
• I've seen a Bluetooth error at the log. Not sure whether it's relevant, but disable Bluetooth, and try again.

Yes, use curl for a remote shutdown: Click!

Quote from badi1220

in config.txt, rebooted, no audio yet or rather ony bluetooth is present in the audio output devices list, after disconnecting hdmi.

That's correct for analogue audio. Check whether the connector is completely plugged in. If possible, try another cable.

Maybe the analogue audio volume is just zero.

Check the lower content of /storage/.kodi/userdata/guisettings.xml. The audio part should look like this:

<audio>
    <mute>false</mute>
    <fvolumelevel>1.000000</fvolumelevel>
</audio>

I don't see any related errors at the log. Maybe you should create another one, because logging was just activate during that session.

The STORAGE partition (/storage) is an EXT4 file system, so you need a tool to view EXT4 on Windows.

Your last session is recorded at kodi.old.log, your current session at kodi.log.

pastekodi only uploads kodi.log. Unfortunately that's not the one with the shutdown recordings.

Sounds like a plan.

Instead of debug logging from GUI, it's smarter to use advancedsettings.xml. Set it to log level 2 when you start experimenting with LE 11.0.3.

Right after detecting a bug, login by SSH, run pastekodi, and share the resulting URL. So we can see what happened.

Quote from myshit

Here it is: http://ix.io/4C4p

That's the log of your current session, which lacks the shutdown recordings.

Logs are at /storage/.kodi/temp. We need one with a shutdown attempt.

Quote from myshit

I tried it without the case and with clean install, but the results are still the same.

Important: Now don't use the Argon One case, until we found the shutdown issue.

Activate debug logging at GUI, and try to shutdown from GUI again.

• If you still have SSH after that, you can use pastekodi to upload kodi.log, and post the resulting link on the forum.
• If you don't have SSH after the shutdown attempt, remove power, remove microSD, and copy the kodi.log content from microSD to PasteBin. Then post the link.

PS: The 3 seconds (long-press) on the Argon One power button is probably the "hard power-off", which eventually corrupted your file system. I suggest not to use the long-press again on a fresh LE installation.

LE 9.2.8 is EOL. You have to use the search function to find CRT threads for that version.

To get fresh support from us, use latest stable LE, as suggested by HiassofT . With a current LE version, we are able to fix CRT bugs.

Remove the case, and shutdown from GUI. If RPi shuts down correctly, then your case is the problem.

If it still hangs without the case, then your microSD eventually has a corrupted file system, and I suggest to install from scratch.

We've banned him for a week, just to see if he can learn. No learning curve, so permanent banishment now.