XBian DEVEL and STAGING repositories

[dharmabm]

(7th Apr, 2014 06:27 AM)CurlyMo Wrote:  Does mode2 output anything? Are you using a GPIO IR receiver?

no it doesn't, not once i've gotten to staging. i should probably move this discussion to the remotes forum though, as occasionally i have a similar issue on my stable build as well... every once in awhile the remote stop working fully or at all, and i reboot a few times and it works.

this message appears in /var/log/lircd

Code:

xbian lircd: WARNING: can't get exclusive access to events coming from `/dev/input/event0' interface

which seems to indicate something else besides lirc is taking control.. google refers to hal, but we're not running hal.... ir-keytables or even cec perhaps?. anyway, i have troubleshot this extensively and am not getting anywhere, but i think i should start a thread in the remotes section as it isn't really a 'bug' in staging. will post more complete info there.

<edit> i just realized i didn't answer you second question, it is not, it is an HP branded mceusb remote with USB IR received, dmesg detects as

Code:

[   16.700161] Registered IR keymap rc-rc6-mce
[   16.700714] input: Media Center Ed. eHome Infrared Remote Transceiver (1934:5168) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/rc/rc0/input0
[   16.701823] rc0: Media Center Ed. eHome Infrared Remote Transceiver (1934:5168) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.3/1-1.3.3:1.0/rc/rc0
[   16.864166] mceusb 1-1.3.3:1.0: Registered FINTEK eHome Infrared Transceiver with mce emulator interface version 2
[   16.864197] mceusb 1-1.3.3:1.0: 0 tx ports (0x0 cabled) and 2 rx sensors (0x1 active)
[   16.864393] usbcore: registered new interface driver mceusb

</edit>

[CurlyMo]

The best way to debug is to make sure mode2 works again. Without a working mode2, nothing will work.

[mk01]

(7th Apr, 2014 12:41 PM)dharmabm Wrote:  

Code:

xbian lircd: WARNING: can't get exclusive access to events coming from `/dev/input/event0' interface

which seems to indicate something else besides lirc is taking control.. google refers to hal, but we're not running hal.... ir-keytables or even cec perhaps?.

most probably ir-keytable. input0 is created after keymap is loaded. keymap is loaded after "protocol" is installed. (ir-keymap -c clears table, ir-keymap -p allows specific protocols).

protocols are loaded through modules called "ir-XXX-decode". so if you put them into blacklist, /rc0 should remain free for lirc.

(there is also ir-lirc-decode which emulates LIRC interface so maybe you even can ir-keymap -p LIRC, then proceed with lircd. that works flawlessly on Cubox).

[syco]

Hi guys,

I am having some problems lately. I did get a message, that my
RPI needs to get updated (I am on 1.0 RC 1). So, I tried that.

When updating, I get an error and it tells me, I should try:

apt-get -f install

So, I did this and then I get another error, which you can see in
my screenshot.

Also, I added an screenshot of my sources list. Maybe I have got
this wrong?

Thank you in advance, guys.

[Smultie]

(1st Sep, 2014 10:24 PM)syco Wrote:  Hi guys,

I am having some problems lately. I did get a message, that my
RPI needs to get updated (I am on 1.0 RC 1). So, I tried that.

When updating, I get an error and it tells me, I should try:

apt-get -f install

So, I did this and then I get another error, which you can see in
my screenshot.

Also, I added an screenshot of my sources list. Maybe I have got
this wrong?

Thank you in advance, guys.

roblems while updating python

If you can't run the update proper because of an error with python, run the following commands. 1)
Afterwards the update should work well.

sudo sed -i '/_hashlib.so/d' /var/lib/dpkg/info/python2.7.list
sudo sed -i '/_ssl.so/d' /var/lib/dpkg/info/python2.7.list

[syco]

Thank you, but still something is wrong. I did your two commands and afterwards I did:

apt-get clean; apt-get update; apt-get upgrade

That came out:

Fetched 15.8 kB in 2s (7,284 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libpython2.7 : Depends: python2.7 (= 2.7.3-6+deb7u2) but 2.7.3-6 is installed
E: Unmet dependencies. Try using -f.
root@xbian:/home/xbian# E: Error: BrokenCount > 0

So I did:

apt-get -f install

... and that did get through without an error.

BUT then I did "Check deb upgrades" and I received that error again:

"A serious error occured while processing these packages."

So, the blue menu commands do not work here and I tried that again in console:

apt-get clean; apt-get update; apt-get upgrade

This time it took a really long time, but it finished without an error.

BUT the blue menu command is still not working. I add a screenshot with that
installation log output.

[f1vefour]

I think the libc6 is a package that is being held back for a reason (breaks stuff).

[syco]

(2nd Sep, 2014 04:52 PM)f1vefour Wrote:  I think the libc6 is a package that is being held back for a reason (breaks stuff).

So, shall I uninstall it? If yes, how do I do that?

[f1vefour]

No you can't uninstall it, it's an important system file. I was saying until the updated libc6 package is marked safe by the maintainer the login0 package update can't proceed.

[f1vefour]

From the Xbian FAQ page:

Quote:[Raspberry Pi] When updating XBian RC2 libsystemd-login0 is held back. How to I upgrade this package?

You can’t. As you might have seen while trying to install the package, it has unmet dependencies:

The following packages have unmet dependencies:
libsystemd-login0 : Depends: libc6 (>= 2.14) but 2.13-38+rpi2+deb7u3 is to be installed

This is an issue of Raspbian that we can’t do much about.

http://www.xbian.org/faq/

[syco]

Thank you very much.

[tojo2503]

Hi,

updating fails for me on the latest CuBox release (CuBox i4). Where is the problem?
/etc/apt/sources.list:

Quote:deb http://http.debian.net/debian jessie main non-free
deb http://apt.xbian.org wheezy main
deb http://apt.xbian.org staging main
#deb http://xbian.brantje.com devel main

and

/etc/apt/sources.list:

Quote:deb mirror://apt.xbian.org/mirror.txt stable main imx6-jessie
deb mirror://apt.xbian.org/mirror.txt staging main imx6-jessie

The error I get on apt-get update is:

Quote:Hit http://apt.xbian.org wheezy InRelease
Hit http://http.debian.net jessie InRelease
Get:1 http://apt.xbian.org staging InRelease [3,791 B]
Get:2 http://apt.xbian.org staging/main armhf Packages [1,689 B]
Get:3 http://http.debian.net jessie/main armhf Packages [8,855 kB]
Get:4 http://http.debian.net jessie/non-free armhf Packages [75.2 kB]
Get:5 http://http.debian.net jessie/main Translation-en [4,606 kB]
Hit http://apt1.xbian.org stable InRelease
Ign http://apt.xbian.org staging/main Translation-en_US
Ign http://apt.xbian.org staging/main Translation-en
Hit http://apt1.xbian.org staging InRelease
Hit http://apt1.xbian.org stable/main armhf Packages
E: Method gave invalid 103 Redirect message

Can somebody help me please? Thanks in advance.

[CurlyMo]

Nothing, just try again later Due to apt mirrors being synced.

[tojo2503]

Hi,
thanks for the quick reply. Now it works better, but I'm still getting the error on apt-get update:

Quote:Fetched 13.8 MB in 13s (1,006 kB/s)
W: Failed to fetch http://apt.xbian.org/dists/wheezy/InRelease No Hash entry in Release file /var/lib/apt/lists/partial/apt.xbian.org_dists_wheezy_InRelease

E: Some index files failed to download. They have been ignored, or old ones used

And trying to install the latest staging build: ~ $ sudo apt-get install xbian-package-xbmc
I get:

Quote:Package xbian-package-xbmc is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
xbian-package-xbmc-scripts

E: Package 'xbian-package-xbmc' has no installation candidate

Again, I am helpless. My fault this time or still something else. Thanks again! :-)

[CurlyMo]

You probably didn't follow the frontpage FAQ.