[mk01]

(4th Jul, 2013 02:11 PM)niftydude Wrote:  Ah I hadn't realised. This could explain why mine is feeling slow. I have one of the early rpis, which only has 256mb ram. With the current split of 128 gfx mem, this means I have only 128 mb system ram, and zram is being run on ALL of that, so memory access is slow.

of course. I really don't know what blackout I had keeping default 128, probably forgot again, that the other 128 is video memory.

so as I said, I'm doing the development now with 384 video mem, what keeps 128mb ram as those with model A. and guess what. even the default 128 is BIGGER as free mem (124) so the very first time I was installing debs I created few second before, I got swap error, then then second, then kernel tried kill processes and then freeze. of course this is not the way.

in the update which is already been posted, default is still there, and is taken, but only if it is 1/3 of memory available to kernel (so total - video). otherwise, is it 1/3.

anyhow, did you try the swappart parameter? it resizes root, creates 256 mb swap at the end of the device. zram-swap - if finds ANY swap partition (even on other usb disks), uses them instead of file.

---

(4th Jul, 2013 05:29 PM)alfredo Wrote:  As usual I'll get back as soon as I get more info, but wanted to report early on current findings. Thanks a lot for your support... and patience with my issue!

put "debug" in cmdline.txt. you should see all the output, including mountall and upstart.

second option is put "rescue_late" in cmdline, it will drop you to shell after "Moving root" and before switch_root. root is under /rootfs folder, /dev, /proc, /run and /sys moved already. so the best is right go to "chroot /rootfs". practically you are at your root (of course without /var and /usr mounted).

third option is to put "init=/bin/bash" into cmdline, it will drop you after switch root. / is your root. if you manage to mount /var and /usr manually, you can put "exec /sbin/init" and upstart (and immediately mount all) will be launched.

in option 2 and 3 you can ifup your lan, you can fully access filesystem and do necessary changes to fstab or /etc/init/mountall.conf.

NOTE: during switch_root, udevd is killed and re-launched, even with udevadm trigger --action add, than means, your disk will have to take again some time to reappear (/dev is recreated for devices not already in use). parameter for mountall is --dev-wait-time=value (in seconds).