Author: swordfish6975

Openelec Build for OPI PC and 2 now with HW decoding

  [Copy link]

4

threads

1118

posts

9504

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9504
Published in 2016-5-5 02:48:35 | Show all floors
@Dima,

maybe this pull request will solve your LIRC issues: https://github.com/xbmc/xbmc/pull/9751/files

Can you test it?

3

threads

165

posts

1203

credits

Gold member

Rank: 6Rank: 6

credits
1203
Published in 2016-5-5 03:37:11 | Show all floors
jernej replied at 2016-5-5 02:48
@Dima,

maybe this pull request will solve your LIRC issues: https://github.com/xbmc/xbmc/pull/9751/ ...

Will test next week ;-) Will also test without DI driver.

0

threads

5

posts

18

credits

Novice

Rank: 1

credits
18
Published in 2016-5-5 14:42:55 | Show all floors
hi,

I launched openelec from sd card and am dropped into a shell. Now how to launch Kodi and all.


Thanks,
Ragu
Enter Cookie as format:
(ex: name=val;) separate with ';'

OKCancel

0

threads

5

posts

392

credits

Intermediate member

Rank: 3Rank: 3

credits
392
Published in 2016-5-5 16:37:43 | Show all floors
Hello, I have Orange Pi Plus and I was using OpenElec for about half a year, but now I am not able to run latest images. The latest one that boots is H3.OPiPlus.arm-6.95.1 from 22.03.2016.
I've already tried precompiled images by Jernej and compile by myself but neither of them boots. Even the green led does not light up. I don't have the debug cable right now but if necessary I may get one to check why it does not boot. For me it looks like u-boot issue.

Do you also have Opi Plus and have the same issue?

4

threads

1118

posts

9504

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9504
Published in 2016-5-6 00:09:51 | Show all floors
slayx replied at 2016-5-5 09:37
Hello, I have Orange Pi Plus and I was using OpenElec for about half a year, but now I am not able t ...

I have only OPi2, but please read this issue thread: https://github.com/jernejsk/OpenELEC-OPi2/issues/44

4

threads

1118

posts

9504

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9504
Published in 2016-5-7 00:20:48 | Show all floors
Dima replied at 2016-5-4 20:37
Will test next week ;-) Will also test without DI driver.

I think I figured out what is the issue with suspend/resume:
  • Backported IR driver has no suspend/resume handling. I think this is your issue. Please confirm it with the next steps:
    • connect serial console
    • Enter this command:
      1. echo 8 > /proc/sys/kernel/printk
      Copy code

    • trigger the bug
    • Check if there is any crash/bug report in serial console. If it is, please post it here.
  • Deinterlace driver has very bad resume/suspend handling. While it would be easy to make a workaround in Kodi, I think it is better to fix kernel driver properly (I have an idea how and it is not so hard)
  • USB host driver has problems with hubs to which devices are attached. Can you or anybody else confirm this on OPiPC or One? This is the only reasonable explanation I could find. I finaly get crash report from kernel for this one. It was for usb1, which is connected to USB hub chip on OPi2 and Plus. It seems that something hangs and watchdog is triggered. Sometimes it is general watchdog and sometimes it is DPM (https://lwn.net/Articles/548967/). Currently, I am clueless how to debug/fix this (but then, I was also for deinterlace driver ).

Implementing suspend/resume for the first potential issue should also be relatively easy.

4

threads

1118

posts

9504

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9504
Published in 2016-5-7 02:08:33 | Show all floors
Edited by jernej at 2016-5-6 19:10

One more thing, why missing suspend/resume code in backported IR driver is problematic:
Arisc core on H3 has a special FW which waits for IR command to resume main ARM cores. So, when H3 goes into suspend, it reconfigures IR registers. If IR driver doesn't reconfigure registers back at resume, it simply can't work.

BTW, only NEC remotes are supported by arisc core. So whoever wants resume functionality with remote, NEC remote is requirement. I will test it once resume/suspend code is added.

3

threads

165

posts

1203

credits

Gold member

Rank: 6Rank: 6

credits
1203
Published in 2016-5-7 19:33:21 | Show all floors
Ok, I still haven't found my serial console thingy, but I've done the USB host test. When using a generic USB hub, it did indeed go to sleep, but didn't wake up. The LED on the USB hub also blinked a few times (which means it was connected and disconnected a few times in a row). However, there are no issues at all when devices are connected without a USB hub.

Will test later today / tomorrow with a USB serial console (if I can find it). The DI image is currently building

4

threads

1118

posts

9504

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9504
Published in 2016-5-7 19:46:55 | Show all floors
Thanks for confirming my suspicions.

Interesting test for USB hub issue would be if you would execute following command before suspend:
  1. echo 0 > /sys/power/pm_async
Copy code

3

threads

165

posts

1203

credits

Gold member

Rank: 6Rank: 6

credits
1203
Published in 2016-5-7 20:23:51 | Show all floors
Quick update:

1) the command doesn't help at all with the USB hub bug.
2) With DI driver patch, the suspend bug is still present (regarding lircd).
3) With the DI patch, the playback is perfectly OK now, even after suspend and resume!

Todo: find the damn serial console and test why lircd is flipping out the power button. I actually always wanted to put it to sleep through power button on remote, which works. But would still be fun to find out what's breaking things
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list