Posts by Da Flex

Quote from bacsom

My logs:

http://ix.io/1vk0

The I2S line looks good.

This lines of your log are a potential problem:

Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/pulse/.config/pulse/cookie': No such file or directory
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/pulse/.config/pulse/cookie': No such file or directory
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/pulse/.pulse-cookie': No such file or directory
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/pulse/.pulse-cookie': No such file or directory

I don't have those pulseaudio warnings in my kodi.log, but I don't have a Hifiberry shield.

Maybe user HiassofT can have a look at his log to verify whether the warnings are critical or not.

I think that's bad HDMI programming inside Kodi. The wake-up call to the AVR should get some kind of a feedback. I'm not into HDMI code, so I'm not sure whether it's doable.

Quote from bacsom

You mean, I should try out something like this?

No, I mean an adapter, which has one HDMI input, and two HDMI outputs. But your adapter could be right, if you don't have a receiver with HDMI.

That Hifiberry shield is special RPi hardware. That's why I expect a driver problem. So, giving a kernel log may help to see, whether the driver has been loaded.

Quote

It uses the I2S sound port that connects directly to the CPU without the need for an additional USB conversion.

The I2S is the the keyword to search for in the kodi log. That means, there is no special Hifiberry driver.

Can you check your config.txt please? Those lines should be in it:

dtoverlay=hifiberry-digi
dtdebug=1

I don't know, if the Hifiberry driver is broken or not. Maybe using an HDMI splitter instead of Hifiberry could be a solution (if you can connect it with your Samsung receiver).

Deactivating the CEC add-on is maybe worth a try.

Quote from Klojum

One way of manually expanding the current system partition is to use a tool called Gparted. You can create a Linux bootable USB stick and adjust your disk partitions with it.

@Pashovski:

I agree. If you can boot from an external device, Gparted is the right way to expand the partition.

Can you boot from an external device?

Or does the LibreELEC installer start, but shows an error when trying to install?

If the installer starts, what's the error message?

Quote from Pashovski

Thanks for the tip! Im looking through the options and don't see this function. I even put the skin back to stock to just in case there was a hidden menu I wasnt seeing. Is this an advanced feature?

Some PC's have two menus: One for general settings, and one for boot order. For my notebook, I have to hold F12 right after power-on. Your manual may give an advice, how to access the menu for boot order. It could be a different key for your HTPC.

Quote from Pashovski

Both times it wrote to the USB disk, and when i boot up the HTPC it just loads as normal, no clean install.

1. Stay calm.

2. Check the boot options of your HTPC. Maybe the boot order has to be changed. It should search for a bootable USB device at first place.

Quote from jcjefferies

It seems much more sensitive than the Wi-Fi built in RPi3B+ as it finds many more local Wi-Fi routers. However when it switches to 5GHz the signal strength drops dramatically and the connection drops out after a few minutes. Although its better than the 5GHZ Wi-Fi in the RPi3 the 5GHZ signal strength in that particular location is just too low so will find another solution to get more speed at that location.

Interesting. So, receiving signals works fine, but sending signals fails. Because sending signals needs more wattage, it might be a PSU issue.

Copy and paste to Pastebin. Then post the generated link.

Quote from jcjefferies

/bin/sh: 1: bc: not found

This means you have to install the package "bc". It could be hard, if you never compiled a driver module before. Anyway, you will find so much info about RPi, so it's possible even for a beginner.

Use the GUI: System -> LibreELEC -> System -> System Name

That's the hostname.

Finally.

Please mark this thread as solved.

PS: You will need some fe-ma-le cables, too, to connect to GPIO: 40 fe-ma-le cables

(had to split a word, because it's censored - funny)

Quote from xevipc1

Yes already opened port 22 in my router but still doesn't work. Same result trying SSH tunnel..

Now I'm running out of ideas, too.

You could go to a friend, and try to connect at his/here router setup.

You could join an internet security forum, and ask for SSH help there.

If nothing helps, buy a second RPi, if you only have one now.

Quote from serguzest

are you suggesting pl 2023 chip?

please give me a link at least please.

This is what I bought at Amazon Germany: TTL-to-RS232 converter

Quote from serguzest

Suddenly it's started to work :S, i am not sure what was the problem.

But most of the time i need to send same command few times to work.

See, that's why. You will have a stable connection, if you follow my suggestion.

Maybe the SSH port has been blocked somehow by your router. Check the port settings of your router.

And/or you can try SSH tunneling: SSH Tunnel with PuTTY