Openelec Build for OPI PC and 2 now with HW decoding

chaszim

jernej replied at 2017-2-25 20:31
I had to write driver for bootloader first

I won't express this right so forgive me. On cold boot, I now see the OPI seal, the OpenELEC Splash, then I get a error "ding", and just Black screen, with no video on my 24" Vizio monitor @1080p. I've got a workaround, but, it's kind of annoying to have to keep using it. By toggeling the HDMI input, the video starts displaying normally. I'm supprised ther isn't a simple way to get it to start up without this error?
And, I've got a theory that may help someone, on my NTP time/date fall back issue (without using the DS3231 RTC's I bought). The OPI misses the internet (routers) signal, after a household power loss. Or, to say it different the OPI starts, before the router finishes it's starting up routine, So, it falls back to the Unix time/date stamp application and desplays "January 31, 1969 07:00". Wouldn't the "Wait for internet option" in OpenELEC config, allow for correction, delaying the OpenELEC startup?
It doesn't help that, I run my router/cable modem, into a seperate switch. So, it tends not to recover, until I've run the units back to the modem direct & cold boot it again. It's not all that easy to recreate the error, so, it's all theory on why it ocours, beause it normally takes me, a long time to get it to correct it's self.  

jernej

chaszim replied at 2017-2-25 15:11
I won't express this right so forgive me. On cold boot, I now see the OPI seal, the OpenELEC Splas ...

Maybe TV doesn't like HDMI signal switching between bootloader and Linux. Armbian uses same code for boot screen and not much complaints there except for flickering. Try with another TV or monitor. I know that this is not ideal, but because of such unneeded issues I decided to stop working with old Linux kernel code.

Waiting on network connection is time limited to 10 seconds I think.

kaynemo

Hey all ! First of all  - great great job on openelec for OPI+2. Now a question - just upgraded (via Kodi interface) to a new build (feb212017, I think) and it seems that the system became very slow and sluggish. Would you suggest doing a clean install, upgrading to the latest image and then restoring kodi backup ? Thanks

chaszim

You can set the "Wait time" above 10 sec limit. But, the SBG6580 cable modem, takes over 90 seconds to boot, acquire & stabilize anyway. Since I now know this, I'll just have to plan on re-booting the OPI, after the modem is at ready state.

Monitor wise, the only other HDMI monitor I've got, is also a Vizio 55", other than a couple of VGA's that don't cover the audio. I can try with my HP, but, I think I already did, and, it did the same thing. So, no real joy there either. Looks like I'll remain stuck, till there's a kernel swap then.

thanks again

chaszim

kaynemo replied at 2017-2-26 02:11
Hey all ! First of all  - great great job on openelec for OPI+2. Now a question - just upgraded (via ...

My guess would be first, "Clear cache", "Purge Packages", and, then look at your "Advanced XML settings" to tune up your "Cache" memory usage, related to what free memory is available.

kaynemo

Hmmm... Cleared cache, purged Packages, my advanced settings state 10 for minvii

kaynemo

The weirdest thing, apart from.being sluggish, some.mkv files began to stutter, while.others don't...

chaszim

thc013 replied at 2017-2-24 00:34
@chazsim it was with a smile  

you could check the http://linux-sunxi.org/I2Cdev

is this:

# I2C RTC drivers
	#
	# CONFIG_RTC_DRV_DS1307 is not set
	# CONFIG_RTC_DRV_DS1374 is not set
	# CONFIG_RTC_DRV_DS1672 is not set
	# CONFIG_RTC_DRV_DS3232 is not set          <-----------yea but no
	# CONFIG_RTC_DRV_MAX6900 is not set
	# CONFIG_RTC_DRV_RS5C372 is not set
	# CONFIG_RTC_DRV_ISL1208 is not set
	# CONFIG_RTC_DRV_ISL12022 is not set
	# CONFIG_RTC_DRV_X1205 is not set
	# CONFIG_RTC_DRV_PCF8563 is not set
	# CONFIG_RTC_DRV_PCF8583 is not set
	# CONFIG_RTC_DRV_M41T80 is not set
	# CONFIG_RTC_DRV_BQ32K is not set
	# CONFIG_RTC_DRV_S35390A is not set
	# CONFIG_RTC_DRV_FM3130 is not set
	# CONFIG_RTC_DRV_RX8581 is not set
	# CONFIG_RTC_DRV_RX8025 is not set
	# CONFIG_RTC_DRV_EM3027 is not set
	# CONFIG_RTC_DRV_RV3029C2 is not set
	#
	# SPI RTC drivers
	#
	# CONFIG_RTC_DRV_M41T93 is not set
	# CONFIG_RTC_DRV_M41T94 is not set
	# CONFIG_RTC_DRV_DS1305 is not set
	# CONFIG_RTC_DRV_DS1390 is not set
	# CONFIG_RTC_DRV_MAX6902 is not set
	# CONFIG_RTC_DRV_R9701 is not set
	# CONFIG_RTC_DRV_RS5C348 is not set
	# CONFIG_RTC_DRV_DS3234 is not set
	# CONFIG_RTC_DRV_PCF2123 is not set
	#
	# Platform RTC drivers
	#
	# CONFIG_RTC_DRV_CMOS is not set
	# CONFIG_RTC_DRV_DS1286 is not set
	# CONFIG_RTC_DRV_DS1511 is not set
	# CONFIG_RTC_DRV_DS1553 is not set
	# CONFIG_RTC_DRV_DS1742 is not set
	# CONFIG_RTC_DRV_STK17TA8 is not set
	# CONFIG_RTC_DRV_M48T86 is not set
	# CONFIG_RTC_DRV_M48T35 is not set
	# CONFIG_RTC_DRV_M48T59 is not set
	# CONFIG_RTC_DRV_MSM6242 is not set
	# CONFIG_RTC_DRV_BQ4802 is not set
	# CONFIG_RTC_DRV_RP5C01 is not set
	# CONFIG_RTC_DRV_V3020 is not set
	#
	# on-CPU RTC drivers
	#
	CONFIG_RTC_DRV_SUNXI=y
	CONFIG_DMADEVICES=y
	# CONFIG_DMADEVICES_DEBUG is not set

Though most of it is remarkes and marked "not set"

kaynemo

Was this for me ?

chaszim

kaynemo replied at 2017-2-26 06:37
Was this for me ?

No, not really sorry. I'm looking if RTC I2C is active in the kernel.THC013 kind of told me to get my shouvle and sand pail out and go digging in some kernel stuff for it.
For you look under system and see how much memory is not in use. them multliply that time 1024 I think it's 3 times, then devide by 3. the number that generates is very big but put it in the advanced directives as catche memory size. I use this to lower the buffering on live stream IPTV, but it should have other uses as well.