(18th Mar, 2014 05:55 AM)IriDium Wrote:  How about moving forward and not backwards?

(24th Mar, 2014 07:51 AM)mk01 Wrote:  @killerbrain

if your Alpha does not suffer from the usb "problems" then you should be documenting this and reporting to RPI development team (firmware & kernel) as they are looking for solution since I remember (Jan/2013).

(24th Mar, 2014 06:51 PM)mk01 Wrote:  @killerbrain

sure, you can alter priority according to various "states" of xbmc in /etc/init/xbmc-priority.conf. states alone have docs in bridge-xbmc service code /usr/local/sbin/upstart-xbmc-bridge.py

and feel free to use raspbmc kernel to boot xbian and vice versa (for testing) - including firmware files. if you are saying it is XBian only, it should not be that hard to track down.

---

what version of xbian-package-kernel and -firmware you are running ?

---

can you also provide cmdline.txt and config.txt from raspbmc to compare ?

(24th Mar, 2014 06:51 PM)mk01 Wrote:  @killerbrain

sure, you can alter priority according to various "states" of xbmc in /etc/init/xbmc-priority.conf. states alone have docs in bridge-xbmc service code /usr/local/sbin/upstart-xbmc-bridge.py

and feel free to use raspbmc kernel to boot xbian and vice versa (for testing) - including firmware files. if you are saying it is XBian only, it should not be that hard to track down.

---

what version of xbian-package-kernel and -firmware you are running ?

---

can you also provide cmdline.txt and config.txt from raspbmc to compare ?

(26th Mar, 2014 01:52 PM)mk01 Wrote:  are you sure with the config.txt?

as RaspBMC is officially stating that XBian feels better/faster because it's higher default clocking. but from this it looks like RaspBMC is running important clock at 25% faster.

but unimportant for that case - if you don't want to match clocks at the beginning. for start change your XBian cmdline.txt to this:

Code:

dwc_otg.lpm_enable=0 quiet sdhci-bcm2708.enable_llm=1 dwc_otg.microframe_schedule=1 dwc_otg.fiq_fix_enable=0 dwc_otg.fiq_split_enable=0 dwc_otg.trans_backoff=3000 console=tty1 root=/dev/mmcblk0p2 rootflags=subvol=root/@,autodefrag,compress=lzo rootfstype=btrfs rootwait logo.nologo quiet noswap  mod_scsi.scan=sync partswap startevent=mountall splash nohdparm --startup-event mountall

for avoiding CEC updates there is much better approach in putting specific package on hold. then others will be updated automatically, CEC never.
you definitely have to update kernel & specially firmware. otherwise the test is useless.

BTW: core clock of 375 to Xbian's 270 is like comparing two different machines. coreclock specifically affects response times.

---

but if you are not afraid of a bit manual action, you can just match RaspBMC firmware & kernel by copying

Code:

/boot/start_x.elf -> /boot/start.elf
/boot/fixup_x.dat -> /boot/fixup.dat
/boot/bootcode.bin ->
/boot/kernel.img ->
/lib/modules/3.10.24 ->
/opt/ ->

then still without reboot run on XBian

Code:

sudo xbian-update-initramfs