10th Aug, 2014, 08:27 AM
10th Aug, 2014, 08:51 AM
(10th Aug, 2014 08:27 AM)CurlyMo Wrote: [ -> ]No config.txt means all defaults.
So that means I'm all good then!
If so that's great news. Thank you for your patience in trying to resolve the issue.
Fingers crossed I can go back to a trouble free experience! :-)
10th Aug, 2014, 06:37 PM
It means all raspberry pi defaults not XBian ones. Would be great to know why the XBian defaults don't work.
10th Aug, 2014, 07:35 PM
(10th Aug, 2014 06:37 PM)CurlyMo Wrote: [ -> ]It means all raspberry pi defaults not XBian ones. Would be great to know why the XBian defaults don't work.
Oh, ok.
Is there any log files I can send you that may track down the issue?
23rd Aug, 2014, 07:55 AM
I have exactly the same problem. Commenting out the initramfs line makes the rapsberry boot again.
I just ran apt-get upgrade:
=> So now I'm updating xbian-package-intramfs-tools, maybe this helps. Will report back
EDIT: Upgrade didn't help. However, changing the memory address to 0x00000000 did help, Xbian boots fine.
I only have one package not upgraded: libsystemd-login0, but I don't think it is related:
xbian@xbian ~ $ sudo apt-get install libsystemd-login0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libsystemd-login0 : Depends: libc6 (>= 2.14) but 2.13-38+rpi2+deb7u3 is to be installed
E: Unable to correct problems, you have held broken packages.
I just ran apt-get upgrade:
Terminal
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
libsystemd-login0 xbian-package-initramfs-tools
The following packages will be upgraded:
libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0 liblzo2-2 liblzo2-dev
Building dependency tree
Reading state information... Done
The following packages have been kept back:
libsystemd-login0 xbian-package-initramfs-tools
The following packages will be upgraded:
libgssapi-krb5-2 libk5crypto3 libkrb5-3 libkrb5support0 liblzo2-2 liblzo2-dev
=> So now I'm updating xbian-package-intramfs-tools, maybe this helps. Will report back
EDIT: Upgrade didn't help. However, changing the memory address to 0x00000000 did help, Xbian boots fine.
I only have one package not upgraded: libsystemd-login0, but I don't think it is related:
Terminal
xbian@xbian ~ $ sudo apt-get install libsystemd-login0
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libsystemd-login0 : Depends: libc6 (>= 2.14) but 2.13-38+rpi2+deb7u3 is to be installed
E: Unable to correct problems, you have held broken packages.
23rd Aug, 2014, 10:43 AM
I'm wondering if specifying the memory address is actually needed. Shouldn't this just work?
23rd Aug, 2014, 05:25 PM
+1
For days the login0 update has been failing, last night picked up another update and got flashing cursor lockup. Did a clean install and ran updates. Got flashing cursor lockup again.
Reflashed SSD image from May and awaiting fix(es) to this/these issues
For days the login0 update has been failing, last night picked up another update and got flashing cursor lockup. Did a clean install and ran updates. Got flashing cursor lockup again.
Reflashed SSD image from May and awaiting fix(es) to this/these issues
24th Aug, 2014, 04:58 AM
The same thing happened to me today when I updated. I've commented the intramfs line on config.txt and it finally booted, but I'm wondering, is that ok? It would keep working all ok with that line commented?
Thanks!
Thanks!
1st Sep, 2014, 10:46 AM
Has anyone reported this on github?
4th Sep, 2014, 06:18 AM
I just had the same issue.
So +1
So +1