XBMC 12.2 improvements & Linux 3.10

[Koenkk]

NOTE: Advanced users only

This version of XBMC Frodo contains improvements that are backported from XBMC Gotham. Linux 3.10 contains various improvements and bug fixes.

How to install (XBian 1.0 Beta 1.1 recommended)

Terminal

sudo su
stop xbmc
wget http://tinyurl.com/xbiantestmirror && chmod +x xbiantestmirror && sudo ./xbiantestmirror
apt-get clean
apt-get update
apt-get install xbian-package-xbmc xbian-package-kernel
reboot

Please share your results here!

[Fred]

Quote:NOTE: Advanced users only

I can see fine so it's probably just you.

[Koenkk]

(29th Jul, 2013 11:01 PM)IriDium Wrote:  Is it just me, but it looks like black code on a black background.
It can be seen by selecting it with the mouse

Should be fixed now, thanks for reporting

[IriDium]

I've added an apt-get clean to remove any links to the old mirrors.

As the script needs to be run as root.
1. sudo su.
2. stop xbmc
3. wget http://dikonist.asuscomm.com:82/XBian/APT/installTestMirror.sh && chmod +x installTestMirror.sh && sudo ./installTestMirror.sh
4a. apt-get clean
4.apt-get update
5.apt-get install xbian-package-xbmc xbian-package-kernel
6.reboot

Update:
W: GPG error: http://dikonist.asuscomm.com wheezy Release: The following signatures were invalid: BADSIG 5D3294C2529968ED CurlyMo <development@xbian.org>
Upgrade:
Starting Hardware RNG entropy gatherer daemon: (Hardware RNG device inode not found)
/etc/init.d/rng-tools: Cannot find a hardware RNG device to use.
invoke-rc.d: initscript rng-tools, action "start" failed
dpkg: warning: unable to delete old directory '/lib/modules/3.9.8+': Directory not empty

+++ Seems to be hanging at +++++++
Preparing to replace xbian-package-xbmc 2.3-0.4 (using .../xbian-package-xbmc_2.3-1_armhf.deb) ...
Unpacking replacement xbian-package-xbmc ...

Seems to be caused by a "hidden" confirmation message. Only seen when issued poweroff command.

Configuration file `/etc/default/xbmc'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** xbmc (Y/I/N/O/D/Z) [default=N] ?

So tried.
sudo sudo dpkg --configure -a
Semed to cure the problem.

XBMC starts but does not recognise keyboard. Standard USB tried, and Logitech Cordless. Both do not work in XBMC but they are recognised in "dmesg".

dmesg also reports:
init: Unable to connect to the system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
init: xbmc post-start process (415) terminated with status 1

[Uncle_Tubbie]

Quote:root@xbian:~# sudo sudo dpkg --configure -a
root@xbian:~# wget http://dikonist.asuscomm.com:82/XBian/AP...tMirror.sh && chmod +x installTestMirror.sh && sudo ./installTestMirror.sh
--2013-07-31 01:25:27-- http://dikonist.asuscomm.com:82/XBian/AP...tMirror.sh
Resolving dikonist.asuscomm.com (dikonist.asuscomm.com)... 88.159.202.11
Connecting to dikonist.asuscomm.com (dikonist.asuscomm.com)|88.159.202.11|:82... connected.
HTTP request sent, awaiting response... 404 Not Found
2013-07-31 01:25:28 ERROR 404: Not Found.

Any thoughts on how to get past this error?

Thank you

update: tentatively this worked

Quote:As the script needs to be run as root.
1. sudo su.
2. stop xbmc
3. echo "deb http://dikonist.asuscomm.com:82/XBian/APT/ wheezy main" >> /etc/apt/sources.list
4a. apt-get clean
4.apt-get update
5.apt-get install xbian-package-xbmc xbian-package-kernel
6.reboot
.

[doug]

My flirc (USB IR receiver) has stopped working with this. As above, it's there in dmesg. Is there any way to roll this back?

Aside from that (and that's a big issue for me) it's working. I was able to reduce my overclock from High to Medium and was able to play the Cloud Atlas mkv (1080p rip) that I use as a benchmark without seeing stuttering/buffering. So it seems like the DTS decode is better although my testing is *far* from comprehensive.

Just a note. I also saw this just before the reboot step...

Code:

Configuration file `/etc/default/xbmc'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
The default action is to keep your current version.
*** xbmc (Y/I/N/O/D/Z) [default=N] ?

It may be worthwhile to others to accept the default "N" to proceed.

[f1vefour]

@doug

What is the output from 'lsusb -v' and 'lsmod' (Please post this on pastebin and provide a link here).

[doug]

(1st Aug, 2013 08:41 AM)f1vefour Wrote:  @doug

What is the output from 'lsusb -v' and 'lsmod' (Please post this on pastebin and provide a link here).

lsmod: http://pastebin.com/n0xET37V
lsusb -v: http://pastebin.com/rNP3K1id ( I think the flirc is appearring as "Bus 001 Device 006: ID 20a0:0001 Clay Logic" which is different from what dmesg indicates
dmesg | grep usb: http://pastebin.com/NSdKyC8T

[f1vefour]

From what I gather you may need to flash the latest firmware to your flirc dongle if you haven't done so already.

Also is the XBMC setting under System -> Input Devices for "Remote control sends keyboard presses" enabled or disabled?

I see your device is registered and should be functional from your dmesg output so short of the batteries being dead in the remote or the firmware being corrupted I'm at a loss.

[doug]

(1st Aug, 2013 10:49 AM)f1vefour Wrote:  From what I gather you may need to flash the latest firmware to your flirc dongle if you haven't done so already.

Also is the XBMC setting under System -> Input Devices for "Remote control sends keyboard presses" enabled or disabled?

I see your device is registered and should be functional from your dmesg output so short of the batteries being dead in the remote or the firmware being corrupted I'm at a loss.

It seems odd that upgrading the firmware would be a fix given that it worked before and also works in other devices. I doubled checked the flirc and remote and they still work. Regardless, I flashed the latest RC of the flirc firmware and it still doesn't work.

The "Remote control sends keyboard presses" is enabled.

[f1vefour]

Upgrading the firmware came from the flirc FAQ , apparently powering down improperly can cause firmware corruption.

---

I'm unsure if beta1.1 takes snapshots before upgrading.

What is the output of

Terminal

btrfs subvolume list -a /

[doug]

(1st Aug, 2013 11:14 AM)f1vefour Wrote:  What is the output of

Terminal

btrfs subvolume list -a /

Code:

xbian@xbian ~ $ sudo btrfs subvolume list -a /
[sudo] password for xbian:
btrfs subvolume list: invalid option -- 'a'
usage: btrfs subvolume list [-p] <path>

    List subvolumes (and snapshots)

    -p     print parent ID

Code:

xbian@xbian ~ $ sudo btrfs subvolume list -p /
xbian@xbian ~ $

[f1vefour]

I will take that as a no it does not.

[doug]

(1st Aug, 2013 12:51 PM)f1vefour Wrote:  I will take that as a no it does not.

I'm guessing no too, but I know nothing of these things. :-)

No worries on getting it to work. It's experimental, afterall. I'm back on Beta 1.1 and it's working great!

Thanks!

[mk01]

(1st Aug, 2013 11:14 AM)f1vefour Wrote:  I'm unsure if beta1.1 takes snapshots before upgrading.

no. beta1.2 does.

---

(1st Aug, 2013 08:25 AM)doug Wrote:  My flirc (USB IR receiver) has stopped working with this. As above, it's there in dmesg. Is there any way to roll this back?

definitely yes. put the official xbian repo back to sources.list, do apt-get clean, apt-get update and then:

apt-get install —reinstall xbian-package-xbmc xbian-package-kernel

or with beta1.2 just rollback snapshot.

anyhow, I have no idea with which commit on xbmc (or kernel which I was lately compiling myself), but i lost keyboard in XBMC.

I would be very happy to know, I we messed something, or upstream XBMC. And with the non-working keyb I'm not alone. Have already seen here on forum.

Ok, now see it was IriDium reporting and in this thread. So I can confirm.

@IriDium, but in other use cases the keyb is working, right? (console, initramfs etc)