beta2

[mk01]

(19th Sep, 2013 01:16 AM)IriDium Wrote:  I did have a panic when it failed to boot (Stuck on loading), but that was because somewhere in the upgrade process it changed cmdline.txt and removed root=/dev/sda1 in favour of root=/dev/mcblk0p1. This might be worth checking as some users will be booting off of a Flash Card or similar.

this will be a bug and I have a feeling where. Until I fix it, just to inform you I'm almost sure, when you reboot, mmcblk will be there again.

give me a minute.

also the kept packages. first I though it's just one shot issue going from Alpha version to Beta but then I went through documentations and simply apt-get will never count packages with CHANGED dependencies (in the meaning of new packages to install because of dependency changed) as packages to upgrade.

so this was clear bug in xbian-config for ages. with the packages you have now it is fixed and also such packages will go into list of packages to update.

btw: I had a little extra today went through all possible processes running apt-get update & relevant and found a rarely happening case when other processes could run the dpkg database updates in not quite effective scenario. Hopefully fixed this as well.

---

@IriDium

please update /xbian-package-initramfs-tools . it should be 1.0-2.14 . retest. it should be fine.

---

(18th Sep, 2013 08:25 PM)Airwolfuk Wrote:  I can confirm i am on the 3.10.12 kernel and still have wifi issues

ok, then let's try as I proposed before. I will re-bundle kernel from B1.1 to match B2 version string, so you would be able to reinstall it.

then you can test the wifi.

are you ok with this ?

---

(19th Sep, 2013 01:16 AM)IriDium Wrote:  8) xbian-bridge still respawning - no determinable reason.

Iri,

and can you check if it is at least catching events from XBMC?

look into /var/log/upstart-xbmc-bridge.log