[mk01]

(30th Jun, 2014 09:22 PM)IriDium Wrote:  I don't think you can just flash the image to the USB stick and hope it will work. Unfortunately the Xbian-clone function isn't working at the moment either.

actually Cubox-i is not different from RPI in the base premise that it doesn't have own boot poartition (internal storage).

as with RPI FAT partition must exists with firmware & kernel present stored on SD card inserted into it, the same applies for cubox. only that the 1st part doesn't need to be FAT (can be ext2) and firmware (u-boot + SPL) can load kernel from 'any' destination.

[Sine]

(30th Jun, 2014 09:22 PM)IriDium Wrote:  @Sine I've just installed a new image and upgraded - all without issue. So I have no idea what is going wrong.

Low level formatted the flash card, reflashed a fresh image, boots.

But now the thing craps itself when updating the 137(!!) updates it has to do. Reflashed it three times, it seems like the updates get strangled in their own dependancies.
Manually upgrading using apt-get, b0rkes it even further.

I think I'll let this release sit for a while and mature a bit, some things seem quite a ways from being complete and stable.

Thanks for the help so far!

[mk01]

@Sine

that is the problem with Jessie unfortunately. Debian is issuing hundreds of updated debs weekly, if not daily.
it makes sense to re-build img from wheezy.

-----
the new auto-building system allows that easily. just target platform for xbmc will change from jessie to wheezy and source http for img creation from jessie to wheezy too. who will mod the build configs and confirm it works has a lollypop from me.

[Xbianfan]

Does anyone know how to get irexec working?
I followed the instruction for remotes (http://www.solid-run.com/wiki/index.php?title=XBian), that's all working, but then I try to start irexec all I get is:

Code:

root@cubox:/home/xbian# irexec
irexec: could not connect to socket
irexec: No such file or directory

[mk01]

irexec needs lirc running

(so socket means /run/lirc......)

[Xbianfan]

(2nd Jul, 2014 10:46 AM)mk01 Wrote:  irexec needs lirc running

Thank you for helping me!

Unfortunately lirc is already running, but irexec won't run anyway:

Code:

root@cubox:/home/xbian# service lirc start
start: Job is already running: lirc
root@cubox:/home/xbian# irexec
irexec: could not connect to socket
irexec: No such file or directory

[mk01]

how does your configuration look like ?

(/etc/lirc/lircrc or /root/.lircrc)

[Xbianfan]

(2nd Jul, 2014 11:13 AM)mk01 Wrote:  how does your configuration look like ?

Code:

root@cubox:/var/run/lirc# cat /root/.lircrc
begin
  prog = irexec
  remote = X10-OR32E
  button = KEY_1
  config = python /home/xbian/fhem/switch_lamp_on.py
  repeat = 0
end

Is irexec working on your cubox-i?

[mk01]

yes

are you (again) sure your LIRC is running and LIRC created socket files at /run/lirc/lircd ?

[Xbianfan]

(2nd Jul, 2014 11:39 AM)mk01 Wrote:  are you (again) sure your LIRC is running and LIRC created socket files at /run/lirc/lircd ?

It seems to be running:

Code:

root@cubox:/run/lirc# start lirc
start: Job is already running: lirc

or is there a better way to check this?

but there are no files under: /run/lirc even no lircd-folder

I already did: apt-get install --reinstall xbian-package-lirc
but still the same result

[mk01]

probably the most direct is to "ps axu| grep lirc"

if it is not running then probably the main configuration at /etc/lirc is not correct. you can check log from starting lirc like this

Code:

less /var/log/upstart/lirc.log

mine shows

Code:

Starting remote control daemon(s) : LIRC
Starting execution daemon: irexec

[Xbianfan]

Thank you for your patient help, I really appreciate that!
You pointed in the right direction, the configuration-file under /etc/lirc was not correct, and now I feel really ashamed because I caused all this trouble, then I tried to connect a new remote with 'irrecord' (for this I renamed lircd.conf to lircd.conf_old)

Sorry!

[mk01]

@Xbianfan

no problem at all. you are welcome!

[IriDium]

*** LATEST upgrade 3rd July 2014 ***

1) If you upgrade via Xbian-config - it may not work - in XBMC it will appear to work but doesn't. Upgrading via ssh xbian-config, shows an error briefly. To see it you need to run apt-get upgrade. This will show a dependency error and a prompt 'Yes, do as I say!' (From memory) type it EXACTLY without the quotes but with the comma and the exclamation mark!! - it worked for me.

2) 2nd attempt - system crashed for no reason. Had to run dpkg --configure -a to clear the error.
3) 3rd attempt - ssh xbian-config failed on package-home stating only half dependences met (or something similar)
Xbian tried to restart but hung. SSH still ok.
4) 4th attempt - ssh apt-get dist-upgrade worked.

Issues: (So far :cool
1) Upgrade will replace .bashrc so if you have made changes, make a backup.
2) Occasionally will get CEC connection lost - not Xbian but noting it.


On another subjects:

1) Assuming bluetooth will eventually work, we will need a Bluetooth config menu in xbian-config.
2) Still cannot connect via airplay (but that could be my android app)
3) Backup function still not working.
4) Another July image should be created with all of the latest updates - ideally a nightly option.

Apart from that - all is looking good.
3) It would be nice to have the ability to show/save multiple Wifi access points as Openelec.

[CurlyMo]

1) Put the linux-image-3.10.30-armmp package on hold so it doesn't get upgraded.