(19th May, 2014 05:45 PM)CurlyMo Wrote: [ -> ] (13th May, 2014 08:21 PM)josch Wrote: [ -> ]If you are already running on RC2, all you have to do is installing the gotham package to finally have a RC2 gotham (stable) setup.
Terminal
sudo apt-get install xbian-package-xbmc-gotham-nightly
This package delivers a stable build of XBMC 13.
From fresh Beta2 install, you should update your Xbian at first.
The package xbian-package-xbmc currently consists of XBMC 13 Beta 2. So no need to install the nightly packages.
13 beta 2 or 13.1 beta 2?
(17th May, 2014 06:22 PM)josch Wrote: [ -> ] (17th May, 2014 01:17 AM)IriDium Wrote: [ -> ]Terminal
sudo service xbmc restart
I'm sure we had this issue a while ago with Beta 2.
Can someone else confirm this!
Confirmed! Same behavior here...
Could be related to
https://bugs.launchpad.net/upstart/+bug/703800?
Reported in 2011. I'm not that confident it's going to be fixed soon...
Wow, I finally took the time to upgrade from Beta 1.1 to RC 2 Gotham, and the difference is amazing.
Everything is so responsive! Thanks so much!
There's just one odd issue that I'm experiencing since the upgrade -- a very slow boot. Seems like it's getting stuck for a long time (over a minute?) after displaying "network started".
Here's the dmesg output:
http://pastebin.com/JDd6cFyU
The relevant lines seem to be:
Code:
...
[ 15.381320] btrfs: device label xbian-root-btrfs devid 1 transid 75239 /dev/root
[ 15.645122] btrfs: device label xbian-root-btrfs devid 1 transid 75239 /dev/root
[ 15.790695] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 17.355860] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
[ 91.062896] vchiq: vchiq_init_state: slot_zero = 0xd8884000, is_master = 0
[ 91.068784] bcm2835-cpufreq: switching to governor powersave
[ 91.068813] bcm2835-cpufreq: switching to governor powersave
[ 91.132515] bcm2835-cpufreq: switching to governor performance
[ 91.132547] bcm2835-cpufreq: switching to governor performance
[ 91.856018] init: xbian-failaccess main process (445) killed by TERM signal
[ 92.535592] udevd[1273]: starting version 175
...
I'd really appreciate some help, and thanks again.
@
deadcat
Yes you're right - that is a slow boot time.
Mine is:
14.730171] smsc95xx 1-1.1:1.0 eth0: link up,
14.039734] bcm2835-cpufreq: switching to governor powersave.
I would look at your network connections - are they set correctly? Is the eth connected directly to the RPi?, are you using dhcp or static. If dhcp, try static and see if that improves matters.
Anyone got Navi-X to install?
I see there is a fix if it was already installed, but not for new installations: Errors with dependencies not met.
(20th May, 2014 07:02 PM)IriDium Wrote: [ -> ]I would look at your network connections - are they set correctly? Is the eth connected directly to the RPi?, are you using dhcp or static. If dhcp, try static and see if that improves matters.
The network cable is connected directly to the RPi and the router. It was DHCP (static DHCP), and the issue stays the same with a static IP.
What else can I do to troubleshoot? Where to look?
EDIT: not sure if it's related, but /boot is not mounted automatically for some reason, which causes xbian-config to throw errors and/or show incorrect information.
Problem?
I've just got a TP-link extender
This one and it works well on Windoze, Mac OSX and Android (Selecting the SSID with the best signal strength.
However, it seems not to work for the RPi. System is very sluggish as well.
Whilst an IP address is obtained (Static) the network is not available - even though a scan shows it.
Looking in System Information shows that there is no gateway even though one is set.
Reconfiguring via xbian-config the scan shows the "2" SSIDs (Both the same) with the extender shown as the highest signal. Selecting that and saving, with a reboot doesn't solve the issue.
Has anyone managed to get an extender working?
Would love to get a quick little rundown on how you guys usually update. I've never been satisfied with upgrading if it's not a clean install and as there is no official image of RC2 that seems to be the only option I have. Thanks!
I have a fresh beta 2 install.
Hi everyone,
SSH issue now - I did apt-get update and upgrade today and all seemed fine.
Now I find that I can SSH in once and then log out, after that I can't get back in without a reboot of the pi.
I'll get the logs and post them but in the meantime does anyone else see this behaviour or have an idea what it might be?
Cheers
Skywatch
***UPDATE***
More trouble so did a couple of reflashes and updates/upgrades and now the issue is gone.
skywatch.
Anyone else having issues with audio pops when leaving a video in passthrough mode?