Forum
beta2 - Printable Version

+- Forum (http://forum.xbian.org)
+-- Forum: Software (/forum-6.html)
+--- Forum: Testing & Experimental (/forum-21.html)
+--- Thread: beta2 (/thread-1312.html)



RE: beta2 - mk01 - 18th Sep, 2013 12:45 AM

(18th Sep, 2013 12:35 AM)IriDium Wrote:  I've never had this delay before - and the RPi was always put to bed. Whilst testing these past months, my process was switch RPi on, and then see

exactly. the APT night update - anacron was committed weeks ago. not yesterday. yesterday I designed button to config.

so the missed apt was for weeks started with your RPI.

this is reaction, symptom. not root cause.

wifi topic: but module is loaded and wlan0 created ?

look at this file. this file is introducing the regular apt-get update. 24days ago already (at minimum)

https://github.com/xbianonpi/xbian-update/blob/0fb08d4e31de0570fa074ff65dc14239e0a2000b/content/etc/apt/apt.conf.d/05xbian

Iri, if you still have the packages as kept back, can you post whole output of apt-get upgrade ? I will again do the fix, but need the layout.


RE: beta2 - IriDium - 18th Sep, 2013 12:58 AM

TV Machine - Just upgraded.

1) Multiple - possibly continuous - messages
15:50:50 T:2987390016 WARNING: CecLogMessage - unhandled response received: opcode=90 initiator=1 destination=0 response=0

Restarting XBMC solves the problem.
2) Dump/Trace error messages on startup - Seen on PC upgrade aswell.

DMESG


RE: beta2 - mk01 - 18th Sep, 2013 01:02 AM

(18th Sep, 2013 12:41 AM)IriDium Wrote:  
(18th Sep, 2013 12:38 AM)mk01 Wrote:  after you put credentials, can you please check content of /etc/network/interfaces ?
auto lo
iface lo inet loopback
iface eth0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
wireless-power off
iface default inet dhcp

There's no activity on the lights, so it's as if it is not there.

I meant Airwolfuk, you are a step before something gets written there. On your system even the wlan0 doesn't exists. I'm right ?


RE: beta2 - IriDium - 18th Sep, 2013 01:17 AM

I tested the WIFI a couple of weeks ago - specifically for the space in the SSID - and it worked.

That machine is shutdown now - working on CEC and TV related stuff now.

After exitting XBMC xbian-config. Error in log:
16:28:03 T:3041395328 ERROR: ClearBlock: Trying to clear non existent block /home/xbian/.xbmc/addons/plugin.xbianconfig
16:28:03 T:2814321728 WARNING: The python script "/home/xbian/.xbmc/addons/plugin.xbianconfig/default.py" has left several classes in memory that we couldn't clean up. The classes include: WindowXML,Addon

As Beta 1.2 is drawing to a close - and no new additions or major upgrades are anticipated - can we at some stage close this release and do any upgrades via a hotfix release strategy where the problem and fix is detailed. I'm not saying to the general public, but enthusiastic users, who want to experience the delights of Beta 1.2.

I've spent a long time testing this and that - only to find that what I had tested previously now does not work. I know it is difficult, to iron - or at least steamroller - all the bugs, critters and other little slimy things, but we have to come to a timeline, when Beta 1.2 is released.

I came on the scene with Aplha 5 and it was great - I still have the SD card! - Beta 1 was not as expected nor was the hotfix Beta 1.1. I don't want the same scenario with Beta 1.2 as it has my footprint on it.

Let's settle on a particular release and test that - add hotfixes as required, but don't mess anything up.

Issue an IMG as pre release Beta 1.2 on the website and get users to try it - depending on the issues found, we can go for a full release or hold back until we believe it is stable. I don't want Beta 1.2 to go out and be unstable or riddled with stupid untested bugs........

Right, I'm going for a lie down........


RE: beta2 - IriDium - 18th Sep, 2013 02:21 AM

Is this normal?

[ 6842.383459] init: xbian-xbmc-bridge main process ended, respawning
[ 6980.502279] init: xbian-xbmc-bridge main process ended, respawning
[ 7118.557654] init: xbian-xbmc-bridge main process ended, respawning
[ 7256.645373] init: xbian-xbmc-bridge main process ended, respawning
[ 7394.892386] init: xbian-xbmc-bridge main process ended, respawning
[ 7533.132703] init: xbian-xbmc-bridge main process ended, respawning
[ 7671.210655] init: xbian-xbmc-bridge main process ended, respawning

Any idea why this is happening? Seems excessive every 5 minutes....
xbian@xbian ~ $ more /home/xbian/.xbmc/temp/xbmc.log |grep -i reboot
15:51:16 T:2921235520 NOTICE: XBian : checking if reboot needed
15:56:17 T:2921235520 NOTICE: XBian : checking if reboot needed
16:01:17 T:2921235520 NOTICE: XBian : checking if reboot needed
16:01:19 T:2921235520 NOTICE: XBian : checking if reboot needed
16:06:18 T:2921235520 NOTICE: XBian : checking if reboot needed
16:11:19 T:2921235520 NOTICE: XBian : checking if reboot needed
16:16:19 T:2921235520 NOTICE: XBian : checking if reboot needed
16:18:47 T:2921235520 NOTICE: XBian : checking if reboot needed
16:21:21 T:2921235520 NOTICE: XBian : checking if reboot needed
16:25:07 T:2921235520 NOTICE: XBian : checking if reboot needed
16:26:23 T:2921235520 NOTICE: XBian : checking if reboot needed
16:31:25 T:2921235520 NOTICE: XBian : checking if reboot needed
16:34:08 T:2921235520 NOTICE: XBian : checking if reboot needed
16:36:26 T:2921235520 NOTICE: XBian : checking if reboot needed
16:41:26 T:2921235520 NOTICE: XBian : checking if reboot needed
16:46:27 T:2921235520 NOTICE: XBian : checking if reboot needed
16:51:27 T:2921235520 NOTICE: XBian : checking if reboot needed
16:56:27 T:2921235520 NOTICE: XBian : checking if reboot needed
17:01:28 T:2921235520 NOTICE: XBian : checking if reboot needed
17:06:28 T:2921235520 NOTICE: XBian : checking if reboot needed
17:11:29 T:2921235520 NOTICE: XBian : checking if reboot needed
17:16:29 T:2921235520 NOTICE: XBian : checking if reboot needed
17:21:30 T:2921235520 NOTICE: XBian : checking if reboot needed


RE: beta2 - mk01 - 18th Sep, 2013 02:40 AM

Iri,

you have again system in semi - complete - upgraded state. I was more than once quite clear telling that in case held packages, they needs to be installed as well. that can specially between versions happen, that a change in one package is depended on a change in second package (specially if the second is xbian-update).

it already happend once to you. now you are experiencing strange things and you ask me whether the other packages (and even xbian-update is on the list) should be installed as well? I really like you bud sometimes you are making me crazy.

yes, the other packages needs to be installed as well.

just to say again: networking has not been touched since you tested two weeks ago. only development happening in this period is xbian-config-xbmc and shell (because xbmc is using shell's functions). changes to other packages are more polishing - like you don't like not properly adjusted text.

and no, it is not normal. but if you really wants to get onto it, get your systems in sync with repo (so manualy specify held back packages to apt-get install). together with them you also get the fix for those (kept back) packages not being displayed for upgrade ever.

the adapter should (or system remembers it as wlan0 or wlan1)?


RE: beta2 - Airwolfuk - 18th Sep, 2013 02:44 AM

(18th Sep, 2013 01:02 AM)mk01 Wrote:  
(18th Sep, 2013 12:41 AM)IriDium Wrote:  
(18th Sep, 2013 12:38 AM)mk01 Wrote:  after you put credentials, can you please check content of /etc/network/interfaces ?
auto lo
iface lo inet loopback
iface eth0 inet dhcp
allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
wireless-power off
iface default inet dhcp

There's no activity on the lights, so it's as if it is not there.

I meant Airwolfuk, you are a step before something gets written there. On your system even the wlan0 doesn't exists. I'm right ?

Not near my Pi but I checked the contents of the file earlier and my WLAN details were there after I set up my WLAN as described earlier


RE: beta2 - mk01 - 18th Sep, 2013 03:10 AM

ok, so this was ok. can it be with the 3.10.12 kernel ? I willl post link to previous 3.10.11 can you then wget and dpkg with Iridium, whether it will help to the WIFI problems you suddenly have?

I have RTL8192 and one more BRCM and those are ok as before.

(now realized that on my repo kernel 1.3-5 is 3.11.y kernel ! this is a big mistake of mine. put back 3.10.12 as 1.3-5.1)

so if by accident you already have 3.11.1+ (uname -r), upgrade / reinstall with 1.3-5.1 http://ivka57.dyndns-ip.com/pool/main/x/xbian-package-kernel/xbian-package-kernel_1.3-5.1_armhf.deb

(18th Sep, 2013 02:21 AM)IriDium Wrote:  Any idea why this is happening? Seems excessive every 5 minutes....
xbian@xbian ~ $ more /home/xbian/.xbmc/temp/xbmc.log |grep -i reboot
15:51:16 T:2921235520 NOTICE: XBian : checking if reboot needed
15:56:17 T:2921235520 NOTICE: XBian : checking if reboot needed
16:01:17 T:2921235520 NOTICE: XBian : checking if reboot needed
16:01:19 T:2921235520 NOTICE: XBian : checking if reboot needed
16:06:18 T:2921235520 NOTICE: XBian : checking if reboot needed
16:11:19 T:2921235520 NOTICE: XBian : checking if reboot needed
16:16:19 T:2921235520 NOTICE: XBian : checking if reboot needed
16:18:47 T:2921235520 NOTICE: XBian : checking if reboot needed
16:21:21 T:2921235520 NOTICE: XBian : checking if reboot needed
16:25:07 T:2921235520 NOTICE: XBian : checking if reboot needed
16:26:23 T:2921235520 NOTICE: XBian : checking if reboot needed
16:31:25 T:2921235520 NOTICE: XBian : checking if reboot needed
16:34:08 T:2921235520 NOTICE: XBian : checking if reboot needed
16:36:26 T:2921235520 NOTICE: XBian : checking if reboot needed
16:41:26 T:2921235520 NOTICE: XBian : checking if reboot needed
16:46:27 T:2921235520 NOTICE: XBian : checking if reboot needed
16:51:27 T:2921235520 NOTICE: XBian : checking if reboot needed
16:56:27 T:2921235520 NOTICE: XBian : checking if reboot needed
17:01:28 T:2921235520 NOTICE: XBian : checking if reboot needed
17:06:28 T:2921235520 NOTICE: XBian : checking if reboot needed
17:11:29 T:2921235520 NOTICE: XBian : checking if reboot needed
17:16:29 T:2921235520 NOTICE: XBian : checking if reboot needed
17:21:30 T:2921235520 NOTICE: XBian : checking if reboot needed

this is happening (as I also this said before - in general way) because as of testing release debugging messages are on for most of packages. otherwise I have no tool to track any issue anybody will report.


beta2 - Airwolfuk - 18th Sep, 2013 05:23 AM

(18th Sep, 2013 03:10 AM)mk01 Wrote:  ok, so this was ok. can it be with the 3.10.12 kernel ? I willl post link to previous 3.10.11 can you then wget and dpkg with Iridium, whether it will help to the WIFI problems you suddenly have?

I have RTL8192 and one more BRCM and those are ok as before.

(now realized that on my repo kernel 1.3-5 is 3.11.y kernel ! this is a big mistake of mine. put back 3.10.12 as 1.3-5.1)

so if by accident you already have 3.11.1+ (uname -r), upgrade / reinstall with 1.3-5.1 http://ivka57.dyndns-ip.com/pool/main/x/xbian-package-kernel/xbian-package-kernel_1.3-5.1_armhf.deb

.

Before I try this tomorrow, I tried to setup my WLAN again and as before it failed. However, when I went into Xbian Config (OS) to set it up, my settings were there and wifi was working. Rebooting into Xbian again and wifi works there also......


RE: beta2 - mk01 - 18th Sep, 2013 06:07 AM

ok, got the point. configs and such is ok, just wifi seems to stuck or something and as a result config-xbmc will not handle this situation well. I experienced this as well but with very old USB stick making troubles to connect from any pc/notebook anything. but then I have seen exactly as you say, you want to abort, but somehow it jumps the list ….

I will try to look into the workflow around wifi, maybe tomorrow


RE: beta2 - Dave400 - 18th Sep, 2013 06:11 AM

(15th Sep, 2013 10:09 AM)mk01 Wrote:  
(14th Sep, 2013 11:01 AM)Dave400 Wrote:  Only problem I still have that I didn't have before is lirc isn't working with my mce remote, is this something to follow in a public beta2?

and clean image beta1.1 is working with it?

can you provide please "sudo tail -50 /var/log/upstart/lirc.log",
Code:
tail: cannot open `/var/log/upstart/lirc.log' for reading: No such file or directory

mk01 Wrote:your /etc/modules
http://pastebin.com/7YA4neKE

mk01 Wrote:and dmesg on pastebin.com?
http://pastebin.com/jqiZqydP

It last worked in A5, with Beta 1, 1,1 and now 1,2 it hasn't worked..


RE: beta2 - mk01 - 18th Sep, 2013 06:20 AM

Dave400 and + "lsmod" command from terminal. is it the first rc0 is detected by kernel, loading ir-keymaps and then on top lirc is coming with lirc_rpi module ?

what happens if you set lirc service to disable ? if still not full operations, if you specifies a keymap in /etc/rc_maps.cfg it's self explanatory, or first row kernel module shown on "lsmod" second row you can put * and third row would be /lib/udev/rc_keymaps/rc6_mce . but looks loaded already. you can check with "ir-keytable" or "ir-keytable -r" (i suppose - I don't have IR to test).


RE: beta2 - mpnico - 18th Sep, 2013 06:32 AM

Hi,

I installed beta2 some days ago, it's working fine. I just noticed some audio drops on some 1080p / DTS movies (using a DTS receiver). I just bought the receiver so I didn't try it with beta 1.1.

Btw, are the popcornmix backports included is beta 2 ? (https://github.com/popcornmix/xbmc/commits/frodo_rbp_backports). Do XBMC 13 builds exists for xbian ?

Thx


RE: beta2 - mk01 - 18th Sep, 2013 06:52 AM

so I assume the audio is going pass through ? for beta2 i was always taking latest firmwares from upstream, but users on beta1.1 reported issues with them and reverted back to xbian's package firmware 1.4-3 . they were no audio related, but still the 1.4-3 seems as way to go. can you check it ? it is available there:

http://ivka57.dyndns-ip.com/rollback/xbian-package-firmware1.4-3.deb ( you can wget it and dpkg -i )

yes, XBian is providing XBMC13 builds, it's on github: https://github.com/xbianonpi/xbian-package-xbmc . just clone the repo, run gen.package.sh, deb package will be generated and you can install with dpkg -i .

for some time Gotham was part of beta2 testing, but there were issues with DTS-MA(ES) tracks, with navigation and some video controls. Then Frodo nightlies progressed and we changed back. For specific patches look at git or ask @koen.

part of xbian-package-xbmc is xbian-package-xbmc-scripts which is shared among them - as you are on Beta2 you should be on that setup, I'm just saying this because the change is 1-2 days old so before you switch just be sure you have the latest state (splitted xbmc into these two packages).

with public release of Beta2, all three branches (master, 12.2 nightly and 13) will go to APT repo as well so once you change future updates should be provided automatically via apt-get . Until then git - pull - gen.package.sh - dpkg -i


RE: beta2 - mpnico - 18th Sep, 2013 07:53 AM

Thx for you quick answer. I just upgraded beta 2 with apt-get update/upgrade to be sure and tried to install the xbian-package-firmware1.4-3.deb but failed with dependencies pb :

Terminal
dpkg: warning: downgrading xbian-package-firmware from 1.4-6 to 1.4-3
(Reading database ... 33537 files and directories currently installed.)
Preparing to replace xbian-package-firmware 1.4-6 (using xbian-package-firmware1.4-3.deb) ...
Unpacking replacement xbian-package-firmware ...
dpkg: dependency problems prevent configuration of xbian-package-firmware:
xbian-update (1.0-1.2) breaks xbian-package-firmware (<< 1.4-5.1) and is installed.
Version of xbian-package-firmware to be configured is 1.4-3.

dpkg: error processing xbian-package-firmware (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
xbian-package-firmware

For Gotham i was just curious but if backports from popcornmix are part of beta 2 there is no need for me to try Gotham builds.