EDIT 2: too early... after another reboot, modprobe with disksize_kb parameter supplied results ALWAYS in instant reboot. I've seen this behavior with colin.stephane's kp48 builds too. Some ideas where to check? I've sysklogd installed. So, it works the first reboot after kernel flashing, but never after that. Every time a spontaneous reboot during which the custom kernel settings are not loaded. EDIT 3: Confirmed. Compcache works only if: - i freshly dpkg'd -i kernel, modules, and flasher (in that sequence, kernel-settings were retained from kp47) AND - performed a reboot. And only then it works after this first reboot. From each consecutive reboot onwards. i observe the instant reboots after ramzswap0 initializing with disksize_kb. If i solely insert the module, no reboot occurs, but of course i cannot initialize it separately.
ramzswap's interface has changed and now requires an 'rzscontrol' tool to initialise devices. I don't believe that's packaged right now. However: * It's changed yet again upstream, is now called 'zram', and its disk size is controlled by writing to files in sysfs. * rzscontrol is a trivial ioctl caller. * compcache's licence is compatible with that of initramfs-tools.
This bug was fixed in the package initramfs-tools - 0.98ubuntu2 --------------- initramfs-tools (0.98ubuntu2) maverick; urgency=low * The ramzswap device changed its interface so that the disk size needs to be given using an ioctl rather than as a module parameter. Incorporate the rzscontrol tool from the compcache project (http://code.google.com/p/compcache/) so that we can control current ramzswap devices (LP: #600782). This is a strictly temporary measure, as recent versions of compcache change the interface (and module name) again to involve writing to sysfs files, which won't require any special tools.