beta2

[mk01]

(24th Oct, 2013 05:01 AM)IriDium Wrote:  It seems to be stable with the known problems, plus a possible new problem, that it won't "shutdown" or "poweroff" as it just restarts!!

this was known issue with firmware package above 1.4-4 and kernels < 3.10.x. last time I checked (1.4-6 firmware and 3.10.x) it was working, since then I pushed 1.4-7 firmware (kernel wasn't changed for a long time) package to repo as there were no reported issues - don't remember if I tried this particular functionality.

will retest myself and report back, in-between you can grab 1.4-6 or 1.4-3 from here and install with dpkg -i [package].

http://xbian.brantje.com/devel/rollback/

---

(28th Oct, 2013 11:41 PM)Smultie Wrote:  Another (small) thing: for me it seems like when @mk01 is not available (for whatever reason: holiday, work, illness, we just don't know) all development seems to stop. A little worrying in my opinion.

currently that only means that there is code freeze for Beta2 (I was posting that at that time somewhere in this thread). The last two package under development are xbian-config (xbmc/ssh) as we are trying with Belese to put as much features / settings to XBIAN-CONFIG XBMC. system itself already is providing them, but without having them accessible via GUI (XBMC/SSH) we would limit user experience for large group of users.

I introduced ~ 2 weeks ago a bug making UDEV daemon never start under some combinations / conditions which could lead to: keyboards / input devices not working, inaccessible external drives, inaccessible WiFi dongles (wlan0), wrong permissinos on VCHIQ - XBMC unable to start etc. It has been fixed few hours ago and committed to repo. beside this I'm considering the current status as Release Candidate 1 and will create new image.

(I still have to go through this forum watching for possible bug reports, so if any reported I'm not yet aware of them).

---

(22nd Oct, 2013 01:13 PM)darrylb Wrote:  @mk01 had a custom update for me, and last update he created a new update for me to try out, though it doesnt seem to be fixing it. Hopefully we will have this worked out soon!

@all

thanks for all that reports, with all the info here I found the problem and fixed. see previous post.