Author: swordfish6975

Openelec Build for OPI PC and 2 now with HW decoding

  [Copy link]

0

threads

6

posts

46

credits

Novice

Rank: 1

credits
46
Published in 2016-1-22 19:31:24 | Show all floors
jeevasv replied at 2016-1-22 14:03
Nops. It should be in the range of ~100MB.  Check the build log. Something would have failed durin ...

Thansk, I will check again.

3

threads

165

posts

1203

credits

Gold member

Rank: 6Rank: 6

credits
1203
Published in 2016-1-22 21:01:34 | Show all floors
Anyone any advise how to extract the SYSTEM file just to update an existing installation?

11

threads

286

posts

1924

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
1924
Published in 2016-1-22 21:08:33 | Show all floors
how to get terminal on your image?

4

threads

1118

posts

9303

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9303
Published in 2016-1-22 22:43:39 | Show all floors
you can enable SSH in OpenELEC settings in Kodi or you can use serial cable with standard 115200 8n1 settings.

@Dima,
what do you want to achieve? Usually it easier to change build system and build an image.

@jeevasv,
I was thinking about CPU frequency and I think it's best just to change CPU governor to ondemand as suggested by me and lymon and leave CPU & SDRAM frequency as they are. That way there would still be possibility to SW decode unsupported codecs. I'm still not sure what to do with GPU clock. When GPU is used for video rendering, speed is needed, but that happens only with HW unsupported codecs. It would be possible to avoid even that case, but that would need a big amount of work, which I'm not willing to do.

0

threads

2

posts

74

credits

Registered member

Rank: 2

credits
74
Published in 2016-1-22 22:49:54 | Show all floors
jernej replied at 2016-1-22 22:43
you can enable SSH in OpenELEC settings in Kodi or you can use serial cable with standard 115200 8n1 ...

Please note that it seems that thermal problems are caused mainly by overvolting not only overclocking : http://linux-sunxi.org/User_talk:Tkaiser#Tests_without_a_heatsink.

4

threads

1118

posts

9303

credits

Moderator

Rank: 7Rank: 7Rank: 7

credits
9303
Published in 2016-1-22 23:03:20 | Show all floors
This is not about overheating anymore but how to keep things cool, which should also lower power consumption. jeevasv also reports that other HW works better in that case.

2

threads

94

posts

629

credits

Senior member

Rank: 4

credits
629
Published in 2016-1-23 06:25:25 | Show all floors
Edited by jeevasv at 2016-1-23 06:31
jernej replied at 2016-1-22 23:03
This is not about overheating anymore but how to keep things cool, which should also lower power con ...

Ok. Yesterday I made a mistake in one of my script.bin and forgot to make ddr_clk change and noticed that one board run's almost 10C hotter than the other one in which I tested the Wifi and all. That board was connected to ethernet. So just to make sure I removed the ethernet and tried to test that board which was kept closer to the router and it was barely useable. So I double checked the script.bin and found that ddr_clk is kept at 672. So I quickly changed it back to 480 and to my surprise the wifi started working again  and temperature is back to normal.

So what I can conclude is that changing ddr_clk alone from 672mhz to 480mhz reduces the temp by 10c and make the wifi perform as faster as 100M Ether in ideal conditions. I am not really a fan of down clocking good  samsung dram which is capable og 800Mhz. But that is not a priority.

I am not sure what is happening in the USB bus when ddr_clk is set to 672. I don't have a bench at my disposal and too little time. But can someone monitor the USB lines using a good scope and see what is going on. Probably Xunlong can fix this once we find out in future versions.

So I don't think we need to change any other clock except the dram_clk. And probably we don't need to go as low as 480, but someone needs to test these and if possible scope the usb lines before confirming.

In that case do we need to really change the governor? Sure if there is substantial reduction in the idle consumption certainly as most of us will be running this 24/7.

I noticed that the script.bin's that I provided earlier do not have the dram_clk set to 480. Re-uploaded it again. Whoever want's to test please re-download it again.

https://mega.nz/#F!Yx40iB5K!yZlGjLIffmDv0vc1t_eRIw
        


3

threads

165

posts

1203

credits

Gold member

Rank: 6Rank: 6

credits
1203
Published in 2016-1-23 16:25:49 | Show all floors
Edited by Dima at 2016-1-23 16:31
jernej replied at 2016-1-22 22:43
what do you want to achieve? Usually it easier to change build system and build an image.

I just want to update my existing OPENELEC installation. If I flash the image, it'll overwrite everything, right? And I don't want to config everything all over again. Even the config restore doesn't restore everything (like remote).

I didn't have the time yet to mess around to get my Linux machine building.

2

threads

94

posts

629

credits

Senior member

Rank: 4

credits
629
Published in 2016-1-23 17:33:18 | Show all floors
Dima replied at 2016-1-23 16:25
I just want to update my existing OPENELEC installation. If I flash the image, it'll overwrite ever ...

You just have to extract and replace two files: SYSTEM and KERNEL.

Easy way:
If you have an extra sdcard or usbstick lying around then use that to flash this image, then access the file system in the new sdcard/usbstick to copy and replace these files in your OPI sd card. Doable?

3

threads

165

posts

1203

credits

Gold member

Rank: 6Rank: 6

credits
1203
Published in 2016-1-23 17:56:27 | Show all floors
Yeah, that's what I also thought bu don't really have extra SD/USB's lying around. That's why I asked if there is any easy method to extract from image? 7zip, winrar, ... all of them say it's a corrupt file.
I'll just update in a few days when I'll be able to build stuff :-)
You need to log in before you can reply login | Register

Points Rule

Quick reply Top Return list