beta2

[f1vefour]

(2nd Nov, 2013 01:32 AM)mk01 Wrote:  

(2nd Nov, 2013 12:23 AM)f1vefour Wrote:  The double movement issue is still happening with lircd, if I stop lircd and simply issue the command 'lircd' the double direction issue is resolved.

can you check what command line args are used when you just start lircd and when started via upstart and also check, if in case of upstart any others daemons are started with lircd. as /usr/local/sbin/lircmd or /usr/local/bin/irexec .

No other daemons are running.

From 'ps ax' after I run lircd the running command is simply 'lircd' with no trailing arguments.

[mpnico]

A small update about audio dropouts when using DTS Passthrough (which still occurs). I'm not alone with this problem, it seems to be a combinaison of receiver / firmware / xbmc build.

I found more info on xbmc forum, popcornmix is aware of the problem and it's not xbian related : http://forum.xbmc.org/showthread.php?tid=155877&page=4

Now, I just have to wait for a fix in firmware or xbmc.

[IriDium]

@waterpolo Are you on the latest update?

I've just checked on my machine at it seems to play.

I know there has always been a problem with menus, so any ISO really should have been remastered to remove the menus.

I've just ripped a DVD, removed the menus and created an ISO of that - Plays perfectly. So something is up with you machine, or file.

Do you get any output? Sound but no video? Have you got a license installed?

If neither of them, then send the output of xbmc.log - details are in my signature - read before you post.

[mk01]

(3rd Nov, 2013 09:08 AM)f1vefour Wrote:  No other daemons are running.

From 'ps ax' after I run lircd the running command is simply 'lircd' with no trailing arguments.

ok isn't this caused by the -u parameter (when used by lirc)? two-three posts have been there about it already.

[belese]

my pi is again very very slow.
am i again out of space?
unable to open pidfile '/tmp/transmission-daemon.pid' for writing (No space left on device)

Terminal

df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 3600384 2099328 1377872 61% /
/dev/mmcblk0p2 3600384 2099328 1377872 61% /
devtmpfs 191796 4 191792 1% /dev
none 38376 304 38072 1% /run
/dev/mmcblk0p1 34662 19207 15455 56% /boot
/dev/mmcblk0p2 3600384 2099328 1377872 61% /home
/dev/mmcblk0p2 3600384 2099328 1377872 61% /lib/modules
/dev/mmcblk0p2 3600384 2099328 1377872 61% /xbmc-backup

Terminal

sudo btrfs fi df /
Data: total=3.05GB, used=1.73GB
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=183.00MB, used=137.07MB
Metadata: total=8.00MB, used=0.00

is tmp was not in ramfs?
but i've space too in ram

Terminal

KiB Mem: 383724 total, 272052 used, 111672 free, 2492 buffers
KiB Swap: 346104 total, 0 used, 346104 free, 184504 cached

now, i can't even type a command, it takes me 10sec by letter and 1-2 minutes to run it (like ls). and i'm scarred to reboot it
:-( i just want to do an image yesterday and don't do it..

[CurlyMo]

My experiences i described earlier about a unusable slow OS is similar to the one @belese is describing.

[belese]

I confirm it's a out of space problem.
i'm currently remove snapshot, and reduce number of auto snapshot
df and btrfs -fi give me strange value.
@mk01, i didn't dollow your advice to backup and reflash card, it's a update from beta 1.
but the test for df < 30% don't work here, and i'm not find any value that could be interpreted,

should be possible to select where backup snapshot are stored (usb?)

i can't remove snasphot :
Delete subvolume '/tmp/btrfs-snap/root/@btrfs-auto-snap_daily-2013-11-03-0757'
ERROR: cannot delete '/tmp/btrfs-snap/root/@btrfs-auto-snap_daily-2013-11-03-0757' - No space left on device
Warning: btrfs sub delete /tmp/btrfs-snap/root/@btrfs-auto-snap_daily-2013-11-03-0757 returned 11

[Smultie]

Yep, sounds like the same thing I've experienced some time ago:

http://forum.xbian.org/thread-1312-post-16240.html#pid16240
http://forum.xbian.org/thread-1312-post-16253.html#pid16253
http://forum.xbian.org/thread-1312-post-16296.html#pid16296
http://forum.xbian.org/thread-1312-post-16302.html#pid16302

Definately something to take a good look at!

[IriDium]

Beta 2 users - Please respond to This Thanks,

[rikardo1979]

@mk01 can we keep OP post updated please? I mean like a DL link for the latest testing image?
-thx-

[adepssimius]

Apologies if this has already been answered, but I didn't get meaningful results when I searched for several error messages I found.

I used the instructions in the OP to upgrade from B1.1:

Change sources.list to devel repo, then

Terminal

apt-get clean && apt-get update && apt-get upgrade -y && apt-get install xbian-update

at this point I made note of the packages that were held back before I confirmed that I wanted to install xbian-update.
I then ran

Terminal

rm -f /etc/init.d/mountall*
insserv -f
apt-get upgrade

and finally I installed xbian-update with held back packages with

Terminal

apt-get install xbian-package-config-shell xbian-package-config-xbmc xbian-package-initramfs-tools xbian-package-kernel xbian-package-samba xbian-package-splash xbian-package-xbmc xbian-update

at this point I confirmed that there were no remaining held back packages before I confirmed the installation. At the end of the installation, apt returned

Terminal

Errors were encountered while processing:
/var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

So I checked the history, and sure enough there was something going on when xbmc installed. Here are the relevant bits.

Terminal

dpkg: considering deconfiguration of xbian-update, which would be broken by installation of xbian-package-xbmc ...
dpkg: no, xbian-update is essential, will not deconfigure
it in order to enable installation of xbian-package-xbmc
dpkg: error processing /var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb (--unpack):
installing xbian-package-xbmc would break existing software
dpkg: considering deconfiguration of xbian-package-xbmc, which would be broken by installation of xbian-update ...
dpkg: yes, will deconfigure xbian-package-xbmc (broken by xbian-update)
(Reading database ... 40436 files and directories currently installed.)
Preparing to replace xbian-update 1.0-1.1 (using .../xbian-update_1.0.2-8d_armhf.deb) ...
De-configuring xbian-package-xbmc ...
Unpacking replacement xbian-update ...
Replacing files in old package upstart ...
Replacing files in old package base-files ...
Selecting previously unselected package xbian-package-xbmc-scripts.
Unpacking xbian-package-xbmc-scripts (from .../xbian-package-xbmc-scripts_1.0.1-13c_armhf.deb) ...
Replacing files in old package xbian-package-xbmc ...
Processing triggers for xbian-package-initramfs-tools ...
Errors were encountered while processing:
/var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

A full transcript of the SSH session is here

Any idea where I go from here? Should I (and can I) install xbian-update without including the new xbmc package?

---

(7th Nov, 2013 05:00 AM)adepssimius Wrote:  Apologies if this has already been answered, but I didn't get meaningful results when I searched for several error messages I found.

I used the instructions in the OP to upgrade from B1.1:

Change sources.list to devel repo, then

Terminal

apt-get clean && apt-get update && apt-get upgrade -y && apt-get install xbian-update

at this point I made note of the packages that were held back before I confirmed that I wanted to install xbian-update.
I then ran

Terminal

rm -f /etc/init.d/mountall*
insserv -f
apt-get upgrade

and finally I installed xbian-update with held back packages with

Terminal

apt-get install xbian-package-config-shell xbian-package-config-xbmc xbian-package-initramfs-tools xbian-package-kernel xbian-package-samba xbian-package-splash xbian-package-xbmc xbian-update

at this point I confirmed that there were no remaining held back packages before I confirmed the installation. At the end of the installation, apt returned

Terminal

Errors were encountered while processing:
/var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

So I checked the history, and sure enough there was something going on when xbmc installed. Here are the relevant bits.

Terminal

dpkg: considering deconfiguration of xbian-update, which would be broken by installation of xbian-package-xbmc ...
dpkg: no, xbian-update is essential, will not deconfigure
it in order to enable installation of xbian-package-xbmc
dpkg: error processing /var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb (--unpack):
installing xbian-package-xbmc would break existing software
dpkg: considering deconfiguration of xbian-package-xbmc, which would be broken by installation of xbian-update ...
dpkg: yes, will deconfigure xbian-package-xbmc (broken by xbian-update)
(Reading database ... 40436 files and directories currently installed.)
Preparing to replace xbian-update 1.0-1.1 (using .../xbian-update_1.0.2-8d_armhf.deb) ...
De-configuring xbian-package-xbmc ...
Unpacking replacement xbian-update ...
Replacing files in old package upstart ...
Replacing files in old package base-files ...
Selecting previously unselected package xbian-package-xbmc-scripts.
Unpacking xbian-package-xbmc-scripts (from .../xbian-package-xbmc-scripts_1.0.1-13c_armhf.deb) ...
Replacing files in old package xbian-package-xbmc ...
Processing triggers for xbian-package-initramfs-tools ...
Errors were encountered while processing:
/var/cache/apt/archives/xbian-package-xbmc_2.9-10.13_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

A full transcript of the SSH session is here

Any idea where I go from here? Should I (and can I) install xbian-update without including the new xbmc package?

I resolved this already. I was able to fix with an

Terminal

apt-get -f install

which fixed the issue. A week or two ago when I tried (what i thought was) the same procedure I got a different result. Either way, resolution is documented for posterity.

[zilexa]

I am not sure if I should hop on and test, is there something left to test atm? Or better to wait untill cause and fix is available for the issue reported by CurlyMo, belese and Smultie?

[nsviper]

Just a quick query from me, beta 2 installed from the IMG file, installed ok and running.

But debug mode on screen only seems to show 256MB on my 512MB Pi?

[IriDium]

@nsviper
Have you run:
1) sudo apt-get clean
2) sudo apt-get update
3) sudo apt-get upgrade (answer yes to SMB installation - Yes to reboot)

When you say "Debug mode" do you mean System -> System information -> Hardware?

I've just checked and by the power vested in the Great God Omm., you are right. I've never noticed that before.

However, a quick check of config.txt shows that 256mb is allocated to the GPU, so when that "slipped" in is a mystery, maybe someone can enlighten us. But thanks for pointing it out.

I don't think it affects performance in anyway - probably enhances it

[nsviper]

(8th Nov, 2013 05:09 AM)IriDium Wrote:  @nsviper
Have you run:
1) sudo apt-get clean
2) sudo apt-get update
3) sudo apt-get upgrade (answer yes to SMB installation - Yes to reboot)

When you say "Debug mode" do you mean System -> System information -> Hardware?

I've just checked and by the power vested in the Great God Omm., you are right. I've never noticed that before.

However, a quick check of config.txt shows that 256mb is allocated to the GPU, so when that "slipped" in is a mystery, maybe someone can enlighten us. But thanks for pointing it out.

I don't think it affects performance in anyway - probably enhances it

Cheers dude