This shows you the differences between two versions of the page.
update_issues [2014/05/30 00:22] CurlyMo |
update_issues [2014/11/11 20:56] (current) palswim Updated patch to alter script to set runlevels instead of commenting lines. |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | **Common update issues** | + | ===== Common update / installation issues ===== |
- | //Python upgrade// | + | ==== XBian RC 2 not booting ==== |
+ | |||
+ | If your fresh install of Xbian 1.0 RC 2 won't boot (only blinking cursor + red light on the pi), follow these steps. Put sdcard back in your PC and edit cmdline.txt: | ||
+ | |||
+ | Replace | ||
+ | <code> | ||
+ | root=LABEL=xbian-copy | ||
+ | </code> | ||
+ | |||
+ | with | ||
+ | <code> | ||
+ | root=/dev/mmcblk0p2 | ||
+ | </code> | ||
+ | |||
+ | ==== Python upgrade ==== | ||
When upgrading, you can encounter this issue: | When upgrading, you can encounter this issue: | ||
Line 33: | Line 47: | ||
Now continue your upgrade as did before. | Now continue your upgrade as did before. | ||
- | //AutoFS issues Beta 2// | + | ==== AutoFS issues Beta 2 ==== |
If you are getting autofs errors trying to upgrade from Beta2 to RC1 just reboot and start the update process again. | If you are getting autofs errors trying to upgrade from Beta2 to RC1 just reboot and start the update process again. | ||
+ | |||
+ | ==== dpkg errors on 256mb pi ==== | ||
+ | |||
+ | This can happen when running any 'apt-get upgrade' and dpkg gets killed because OOM | ||
+ | <code> | ||
+ | E: Sub-process /usr/bin/dpkg exited unexpectedly | ||
+ | </code> | ||
+ | |||
+ | * remove /etc/sysctl.d/xbian.conf | ||
+ | * reboot | ||
+ | * try again | ||
+ | * if still not, try creating /etc/sysctl.d/xbian.conf with only one setting vm.min_free_kbytes = 16384 | ||
+ | * if 16384 still crashes dpkg, try 32768 or even 65536. (you have to reload setting from this file by "sudo sysctl -p /etc/sysctl.d/xbian.conf" | ||
+ | |||
+ | ==== plymouth upgrade error ==== | ||
+ | |||
+ | The problem looks like this when upgrading the XBian installation on a CuBox-I or Raspberry Pi device: | ||
+ | <code> | ||
+ | Setting up plymouth (0.8.8-16) ... | ||
+ | update-initramfs: deferring update (trigger activated) | ||
+ | update-rc.d: error: expected NN after start | ||
+ | usage: update-rc.d [-n] [-f] <basename> remove | ||
+ | update-rc.d [-n] <basename> defaults [NN | SS KK] | ||
+ | update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...] . | ||
+ | update-rc.d [-n] <basename> disable|enable [S|2|3|4|5] | ||
+ | </code> | ||
+ | |||
+ | The solution is to apply this patch (manually): | ||
+ | <code> | ||
+ | --- /var/lib/dpkg/info/plymouth.postinst.old 2014-07-01 21:38:49.947752101 +0200 | ||
+ | +++ /var/lib/dpkg/info/plymouth.postinst 2014-07-01 21:39:11.359011460 +0200 | ||
+ | @@ -51,14 +51,14 @@ | ||
+ | fi | ||
+ | # End automatically added section | ||
+ | # Automatically added by dh_installinit | ||
+ | -if [ -x "/etc/init.d/plymouth" ]; then | ||
+ | - update-rc.d plymouth start . 2 3 4 5 . stop . 0 6 . >/dev/null || exit $? | ||
+ | -fi | ||
+ | +if [ -x "/etc/init.d/plymouth" ]; then | ||
+ | + update-rc.d plymouth start 41 2 3 4 5 . stop 41 0 6 . >/dev/null || exit $? | ||
+ | +fi | ||
+ | # End automatically added section | ||
+ | # Automatically added by dh_installinit | ||
+ | -if [ -x "/etc/init.d/plymouth-log" ]; then | ||
+ | - update-rc.d plymouth-log start . S . >/dev/null || exit $? | ||
+ | -fi | ||
+ | +if [ -x "/etc/init.d/plymouth-log" ]; then | ||
+ | + update-rc.d plymouth-log start 40 S . >/dev/null || exit $? | ||
+ | +fi | ||
+ | # End automatically added section | ||
+ | # Automatically added by dh_makeshlibs | ||
+ | if [ "$1" = "configure" ]; then | ||
+ | </code> |