Kodi Community Forum
OpenELEC Testbuilds for RaspberryPi Part 2 - Printable Version

Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166)
---- Thread: OpenELEC Testbuilds for RaspberryPi Part 2 (/showthread.php?tid=184866)



RE: OpenELEC Testbuilds for RaspberryPi Part 2 - FAMMAR - 2014-03-27

Running the latest build on a overclocked Pi but when I play for example a movie and in that movie the camera goes from left to right (or otherwise) The picture is not fluid but, how to say, it sturrers a little


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - popcornmix - 2014-03-27

(2014-03-27, 22:08)FAMMAR Wrote: Running the latest buil on a overclocked Pi but when I play for example a movie and in that movie the camera goes from left to right (or otherwise) The picture is not fluid but, how to say, it sturrers a little

Is adjust display refresh rate to match video enabled?


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - FAMMAR - 2014-03-27

(2014-03-27, 22:11)popcornmix Wrote:
(2014-03-27, 22:08)FAMMAR Wrote: Running the latest buil on a overclocked Pi but when I play for example a movie and in that movie the camera goes from left to right (or otherwise) The picture is not fluid but, how to say, it sturrers a little

Is adjust display refresh rate to match video enabled?

Yes, have checked that


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-03-27

(2014-03-27, 21:32)SenorLoco Wrote: Well just for fun I tried connecting to my pi again (still haven't been home to reboot) and it did reconnect to wifi at home point. Here is the dmesg http://sprunge.us/dYhO

OK so it is using the recently updated rtl8192cu kernel module.

Code:
[   14.631071] rtl8192cu: Chip version 0x10
[   15.342790] rtl8192cu: MAC address: 80:1f:02:86:e4:fd
[   15.342830] rtl8192cu: Board Type 0
[   15.343031] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
[   15.343179] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[   15.349096] usbcore: registered new interface driver rtl8192cu
[   15.357593] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[   15.375720] rtlwifi: wireless switch is on
[   15.523133] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   15.523900] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.528002] input: lircd as /devices/virtual/input/input0
[   16.674516] rtl8192cu: MAC auto ON okay!
[   16.972203] rtl8192cu: Tx queue select: 0x05
[   18.131949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

However when it tries to authenticate with your Access Point, it times out, eventually connecting 325 seconds later.

Code:
[   19.962060] wlan0: authenticate with bc:ae:c5:c4:f0:d3
[   19.991210] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 1/3)
[   20.094325] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 2/3)
[   20.197757] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 3/3)
[   20.301029] wlan0: authentication with bc:ae:c5:c4:f0:d3 timed out
...
[  342.760231] rtl8192cu: MAC auto ON okay!
[  342.816690] rtl8192cu: Tx queue select: 0x05
[  343.368658] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  345.203139] wlan0: authenticate with bc:ae:c5:c4:f0:d3
[  345.230725] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 1/3)
[  345.241607] wlan0: authenticated
[  345.244864] wlan0: associate with bc:ae:c5:c4:f0:d3 (try 1/3)
[  345.248054] wlan0: RX AssocResp from bc:ae:c5:c4:f0:d3 (capab=0x411 status=0 aid=5)
[  345.248463] wlan0: associated

then timing out several times much later:
Code:
[ 5222.167250] wlan0: associate with bc:ae:c5:c4:f0:d3 (try 1/3)
[ 5222.269939] wlan0: associate with bc:ae:c5:c4:f0:d3 (try 2/3)
[ 5222.373276] wlan0: associate with bc:ae:c5:c4:f0:d3 (try 3/3)
[ 5222.476655] wlan0: association with bc:ae:c5:c4:f0:d3 timed out
[ 5587.974333] wlan0: authenticate with bc:ae:c5:c4:f0:d3
[ 5587.991192] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 1/3)
[ 5588.093203] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 2/3)
[ 5588.196566] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 3/3)
[ 5588.299866] wlan0: authentication with bc:ae:c5:c4:f0:d3 timed out
[ 5953.965413] wlan0: authenticate with bc:ae:c5:c4:f0:d3
[ 5953.987748] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 1/3)
[ 5954.089793] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 2/3)
[ 5954.193139] wlan0: send auth to bc:ae:c5:c4:f0:d3 (try 3/3)
[ 5954.296470] wlan0: authentication with bc:ae:c5:c4:f0:d3 timed out

There is discussion about the instability of the rtl8192cu driver here (scroll to the bottom, comments underneath the commits) - any information you can add will help as they seem to be lacking logs.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - host505 - 2014-03-27

(2014-03-27, 03:47)MilhouseVH Wrote: New OpenELEC Gotham build: #0327
.
.
Fix for mono GUI sounds (requires new firmware)
.
.

Is there something (appart from the usual update procedure) we need to do to update firmware?Huh


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-03-27

Nope, nothing - the update procedure takes care of the firmware too (as long as your boot= partition is the SD card, ie. /dev/mmcblk0p1).


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - host505 - 2014-03-27

Oh, ok thanks.
I really don't have anything to report for the last builds, everything works good (better than beta imo) for the simple things I use with my raspi. Really appreciate all you've done to make xbmc a better experience on the pi.

Some time ago you've introduced some CEC mods, that you pulled back later. Does this mean that the advancedsettings.xml options that came allong with this mod no longer work on the builds that followed the cancelation?
You see I use cec with a panasonic tv and I'd like to experiment with these settings because navigation is very slow.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-03-27

(2014-03-27, 23:14)host505 Wrote: Some time ago you've introduced some CEC mods, that you pulled back later. Does this mean that the advancedsettings.xml options that came allong with this mod no longer work on the builds that followed the cancelation?
You see I use cec with a panasonic tv and I'd like to experiment with these settings because navigation is very slow.

You mean the CEC suppression and auto-repeat patch that appeared in build #0301 (and subsequently pulled in build #0304)? Yes, if you still have those CEC entries in your advancedsettings.xml then they will be having no effect with current builds.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - matthias76 - 2014-03-28

(2014-03-27, 18:30)SenorLoco Wrote: I have been noticing issues with the wifi connection dropping randomly (in fact it just happened since my last post. I'm currently away from home so I'll try to get the dmesg later today). When the wifi connection has been dropping openELEC is still running fine, just no network connection.

i got Tenda 11N Wireless USB Adapter W311U
works fine on frodo

on gotham Beta2 only randomly find the WifiUSBStick.
tried latest milhouse build -> same problem.
Coldstart 70 % find the WiFiDongle
Warmstart never find the WiFiDongle.

if its not found i cant connect to wlan. turn on and off in wlan settings no success.
do a coldstart sometimes help and wlan in working.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - maratonomak - 2014-03-28

(2014-03-27, 23:01)MilhouseVH Wrote: Nope, nothing - the update procedure takes care of the firmware too (as long as your boot= partition is the SD card, ie. /dev/mmcblk0p1).

I'm booting from SD card with SanDisk Extreme 16 GB USB 3.0 as storage. Could you tell me what should be on cmdline.txt in order to update the firmware ?
Thanks


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-03-28

(2014-03-28, 00:31)maratonomak Wrote: I'm booting from SD card with SanDisk Extreme 16 GB USB 3.0 as storage. Could you tell me what should be on cmdline.txt in order to update the firmware ?

Just make sure the line in cmdline.txt contains the following option:
Code:
boot=/dev/mmcblk0p1

If your boot= option is set to anything other than /dev/mmcblk0p1 the upgrade process is going to either not work at all, or fail silently.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - maratonomak - 2014-03-28

(2014-03-28, 01:02)MilhouseVH Wrote:
(2014-03-28, 00:31)maratonomak Wrote: I'm booting from SD card with SanDisk Extreme 16 GB USB 3.0 as storage. Could you tell me what should be on cmdline.txt in order to update the firmware ?

Just make sure the line in cmdline.txt contains the following option:
Code:
boot=/dev/mmcblk0p1

If your boot= option is set to anything other than /dev/mmcblk0p1 the upgrade process is going to either not work at all, or fail silently.

My cmdline contains : boot=LABEL=SYSTEM disk=/dev/sda1 ssh quiet.
As of now I'm placing your build inside update folder or using leopold addon.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Trickname - 2014-03-28

Hey Millhouse
this ´New OpenELEC Gotham build: #0327`

gives my a loop in XBMC logo
fortunately samba is still working so its easy to downgrade for the moment


Re: RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Milhouse - 2014-03-28

(2014-03-28, 02:03)Trickname Wrote: Hey Millhouse
this ´New OpenELEC Gotham build: #0327`

gives my a loop in XBMC logo
fortunately samba is still working so its easy to downgrade for the moment

ssh in and check your xbmc.log/xbmc.old.log for an error.


RE: OpenELEC Testbuilds for RaspberryPi Part 2 - Trickname - 2014-03-28

http://pastebin.com/7XpXidA9


This forum uses Lukasz Tkacz MyBB addons.