Posts by cosmos

Quote from didi82

Check my last post:

pcf8563_get_datetime: read error

That seems to do the trick rfegarding this warning, thanks!

No, it doesn't.

Possibly a bug, see: pcf8563_get_datetime: read error

Apologies for hijacking this thread, but I had the exact same errors with official 8.2.2 running on C2, my thread: [Odroid C2]: Repeated errors in dmesg, bug or feature?

Executable /usr/lib/libreelec/odroid-rtc does not exist and I do not have an RTC battery. Which would be the recommended command(s) to run?

EDIT: Running systemctl status hwclock produces a

Unit hwclock.service could not be found.

I presume you might have exhausted all possible propositions to solve this, but in case you haven't I'm more than eager to give any thought a try

Quote from cosmos

One more thingie: I've got an old pinnacle remote control (MCE). Any idea why it doesn't work with LE on C2? Having read a couple of threads, it seemed like it was a plug and play proposition.

RTFM: disabling and enabling LIRC under Programs -> LibreELEC, followed by a reboot did the trick

buky is your system a Pi2 or 3?

I have been using a Pi2 for years and I have never encountered any over-temperature warnings when playing back HEVC material. I do have a 3-piece heatsink set installed (2 on top and a copper at the bottom). Additionally I am using the (official) case with the upper part permanently open.

Pi3 has increased temperatures, if you do not have means of active cooling (fan) I believe it would be easy to observe this.

I am receiving a lot of errors constantly repeating every second or so on my Odroid C2/official LE 8.2.2, when running dmesg:

Quote

[ 7694.416298@1] rtc-pcf8563 1-0051: pcf8563_get_datetime: read error

[ 7695.415998@1] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)

[ 7695.416012@1] i2c i2c-1: token 1, master_no(1) 300K addr 0x51

[ 7695.416064@1] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)

[ 7695.416069@1] i2c i2c-1: token 1, master_no(1) 300K addr 0x51

[ 7695.416120@1] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)

[ 7695.416125@1] i2c i2c-1: token 1, master_no(1) 300K addr 0x51

[ 7695.416133@1] rtc-pcf8563 1-0051: pcf8563_set_datetime: err=-11 addr=02, data=36

[ 7695.416194@1] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)

[ 7695.416199@1] i2c i2c-1: token 1, master_no(1) 300K addr 0x51

[ 7695.416250@1] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)

[ 7695.416255@1] i2c i2c-1: token 1, master_no(1) 300K addr 0x51

[ 7695.416305@1] i2c i2c-1: [aml_i2c_xfer] error ret = -5 (-EIO)

[ 7695.416311@1] i2c i2c-1: token 1, master_no(1) 300K addr 0x51

[ 7695.416315@1] rtc-pcf8563 1-0051: pcf8563_get_datetime: read error

Display More

Is this normal behavior?

No, it does not have anything to do with HEVC requirements, it is an undervoltage warning, see Under-voltage warnings - Raspberry Pi Forums

It used to be a rainbow square icon, but it has been replaced with a yellow lightning bolt icon in more recent versions. Bad USB connections with the power charger can also produce this.

You cannot use just any power supply. For RPi2 (RPi3) you need a power brick that can provide constantly a 2Amp (2.5Amp respectively) supply current. Having a supply that simply states 5V/2A doesn't simply cut it; I've seen a lot of power supplies (even brand ones) not being able to cope with the power needs of an RPi...

Hello,

I've got an older MCE-type remote hanging around (Pinnacle PCTV). I know it worked just fine some time ago with my PC-based Openelec (at the time) Kodi. I've lost the IR sensor, but got an Odroid C2 device for which I made a fresh LE 8.2 install. C2 seems insensitive to me leisure watching needs (read: does not work). Is this a bug or a feature, ie should I perhaps switch/configure something first in order for this to work?

Yes, of course. BTW, I stated at the start that I had enabled frame rate auto switching. But trying to locate this option I could not locate it. I clearly remember seeing it over the last 3 years or so...

Additional info:

* Under system -> display settings I am only given options to switch to either 50 or 60 Hz. No 24/30 options at all.

* Googling around found some commands from ODROID • View topic - AMLOGIC & HDMI , I'm adding here outputs in case it might help here:

I implemented the changes, as per your suggestions. There was no /storage/.kodi/userdata/disp_cap before I started. Running cat /sys/class/amhdmitx/amhdmitx0/disp_cap produced the following modes:

Quote

480p60hz

576i50hz

576p50hz

720p60hz

1080i60hz

1080p60hz*

720p50hz

1080i50hz

1080p50hz

Display More

I created the disp_cap file by using cat /sys/class/amhdmitx/amhdmitx0/disp_cap > /storage/.kodi/userdata

/disp_cap and then edited the latter file to include 1080p24 and 1080p30 modes. disp_cap contained the following then:

Quote

480p60hz

576i50hz

576p50hz

720p60hz

1080i60hz

1080p60hz*

720p50hz

1080i50hz

1080p50hz

1080p30hz

1080p24hz

Display More

Note that I did not use any specific order in this file, should I?

I restarted kodi with systemctl and tried to play some material. Trying both 30Hz and 23.97Hz material did not switch to the relevant mode. Instead Sammy stayed at 60Hz (as depicted when I press the samsung "info" button).

What could/should I look for?

Thanks for your fast and informative responses! Been on a trip and just returned, will try your suggestions and get back to you.

This is my first C2 install, after having some good 3 years on RPi2. I've got a Sammy TV which could support perfect 24p playback. On RPi2 unfortunately, the 24p mode was not detected. So I made a custom EDID file (there's a faq somewhere) and included the relevant option in LE's config.txt file to boot using this speficic EDID info. Doing so, my RPi2 happily switched between 60Hz, 50 Hz and 24Hz!

After switching to C2 I am encountering the exact same situation: System happily boots up on 1080p60, however TV does not switch to 24p when 24p material is played. It sticks with 60Hz.

Can I pull a similar trick on C2, like I used on RPi2? That is, trick C2 into thinking that TV can also support 1080p24? FYI, I have enabled the relevant option in the Kodi UI to auto-change rate.

Changed cable and HDMI port and LE booted in all its greatness

One more thingie: I've got an old pinnacle remote control (MCE). Any idea why it doesn't work with LE on C2? Having read a couple of threads, it seemed like it was a plug and play proposition.

/me facepalms :p

Funny thing is that I had already read the blue LED change...

Problem is that since this is a new LE install, SSH does not get enabled until after the user reaches the specific point in the wizard. Your recommendation to check my router's DHCP was awesome though; will check that when I get back home.

My assumption is that I have a non-grounded HDMI cable, as described in ODROID • View topic - No HDMI output

But that's easy to check, got plenty of HDMI cables and monitors at home

Awesome work BTW with LE, you guys rock!

After shipping my RPi2-based LE 8 box to my dad, I replaced it with a used C2. Downloaded and flashed a stock LE 8.2 image for it on a 16Gb SD card (tried both Samsung and Kingston). Installed it and ... nothing. Red light lights up constantly. Blue LED lights constantly for a while and then goes off permanently.

I've tried flashing with both your flashing app as well as win32diskimager. And also used different 2Amp PSUs, same type I've been powering my own RPi2 without a hitch for some 3 years. Same deal. Additionally, display (a 6-year Samsung 40" high quality at the time tv) remains blank.

For the sake of checking I also flashed a stock Android image from the Odroid site. This time there is definite kernel activity, the blue LED lights intermittently. I still do not have tv output, however I do hope this is a HDMI issue.

Any ideas what might be going wrong here?