Originally Posted by don_falcone

@pali: pre-release kp49 flashed, working, ramzswap working, testing wl1251 now.

@all: use modprobe from now on (it's better/safer than insmod anyway), procedure:

Code:

modprobe ramzswap num_devices=1 disksize_kb=98304
swapon /dev/ramzswap0
swapoff /dev/mmcblk0p3
swapoff /dev/mmcblk1p2

(with second partition on SD being a swap partition)

EDIT: wl1251 also confirmed working (used fAircrack for checking)

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.

Originally Posted by dignified

thanks..f... u

Originally Posted by Carlito

When I turn off the phone and charge it with the wall connector it keeps showing me the nokia logo than the 5 dots showing up. They disappear than the logo shows up again and so on . . . very strange. When turning the phone on it doesn't charge at all.

Originally Posted by don_falcone

Code:

modprobe ramzswap num_devices=1 disksize_kb=98304
swapon /dev/ramzswap0
swapoff /dev/mmcblk0p3
swapoff /dev/mmcblk1p2

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.