(20th Oct, 2013 01:51 AM)Darkguy Wrote:  "starting xbmc..." boot loop!!!

(20th Oct, 2013 02:09 AM)IriDium Wrote:  

(20th Oct, 2013 01:51 AM)Darkguy Wrote:  "starting xbmc..." boot loop!!!

@Darkguy No need to get angry! - this is a beta test image still, and testing is still in progress.

Yes I have had this booting loop too. KB not working and by the looks of it other problems.

I reflashed from the beta2.resized image mentioned around page 33 but did not upgrade. Things seemed to work a lot better then. There is obviously a conflict somewhere which the Dark Wizard will soon sort out (Debian vs Xbian?). So in the mean time, I would suggest you do your testing on the working image until the upgrade issues are sorted out.

You can't be on the bleeding edge without a few lacerations

Stick with it - it will be worth it.

(20th Oct, 2013 02:13 AM)Smultie Wrote:  Why do you think he's angry? He even put a smiley there.....

(20th Oct, 2013 02:09 AM)IriDium Wrote:  @Darkguy No need to get angry! - this is a beta test image still, and testing is still in progress.

(20th Oct, 2013 02:56 AM)CurlyMo Wrote:  Did you try my suggestion!

(20th Oct, 2013 03:15 AM)IriDium Wrote:  @CurlyMo - What suggestion? All cognitive receptors are currently unavilable as too is ESP, and mind reading although the process of detecting Umbala is very accute.

Make your point, or don't bother. Trolling is not an acceptable form for this forum, so please desist. I have enough issues to worry about rather than your puerile comments.

If you have an issue, then please post it, otherwise please keep your adolescence replies in abeyance.

(20th Oct, 2013 03:15 AM)IriDium Wrote:  @CurlyMo - What suggestion? All cognitive receptors are currently unavilable as too is ESP, and mind reading although the process of detecting Umbala is very accute.

Make your point, or don't bother. Trolling is not an acceptable form for this forum, so please desist. I have enough issues to worry about rather than your puerile comments.

If you have an issue, then please post it, otherwise please keep your adolescence replies in abeyance.

(20th Oct, 2013 02:26 AM)IriDium Wrote:  

(20th Oct, 2013 02:13 AM)Smultie Wrote:  Why do you think he's angry? He even put a smiley there.....

@Smultie Err... on my screen is angry, I don't know what you see?

(15th Oct, 2013 05:36 PM)mk01 Wrote:  @b0rna,

if it holds to be fine and steady until ~200 it is more than I would expect as I would expect the system to be stuck at high io && iowaits at around 10x less (as the SoC design handles all this via the slow CPU).

this test is of high value to me, so thanks for it. just a most important final question, did it finish successfully ? as there were reported issues with Beta1X like OOM XBMC crashing or even kernel panics / total freez on Library operations with this size (even smaller).

probably turning off compression on filesystem would make this better, setting vm.dirty_ratio and vm.dirty_background_ratio to lower values as are now by default should have positive effect as well for this one particular action. but this can be tuned later as we get more feedback. unfortunately compression on/off is btrfs pool wide mount setting, it can't be turned off for /home mount and kept for / if they are on the same btrfs filesystem as sub volumes (in contrast ZFS allows that for fine control).

---

(15th Oct, 2013 08:51 AM)Dizzy Wrote:  @mk01, of course, I'll check that tomorrow.

btw, found out that inputlirc doesn't start.
steps to reproduce are to install through : "apt-get install inputlirc",
running inputlirc with -g gives a seg fault.
"-g" is used to grab the input device exclusively. maybe a permissions issue?
used to work.

@Dizzy

can look into it later, but you can maybe investigate more yourself (and quicker than myself) by installing strace package and then running inputlirc binary via it. it will output lots of operations currently happening on the system and related to the inputlirc so probably before the seg fault you will se a operation which resulted in it.