I had it working fine on RC3. Did the same exact thing and cant get it to work. Anyone get it to work? I am using P3's 900/125 kernel. Slayers "stock" kernel was causing boot loop, which it never did before.
Anyone get it working on RC4? If so, which setup?
Of course. I always do a fresh wipe, let it install and startup, then go into recovery and install kernel and w/e modules I am using.
Have you been able to get it working?
About moving the module, I dont have a dir called 2.6.32-P3Droid. Do I need to create one and then move the ramzswap module there?
That's what I had to do. Actually, now that I look at the compcache script, it is manually setting MODULES_DIR. Perhaps that could be edited to look in the correct location, instead of moving the module?
What do you get when you type "modprobe ramzswap"?
That's what I had to do. Actually, now that I look at the compcache script, it is manually setting MODULES_DIR. Perhaps that could be edited to look in the correct location, instead of moving the module?
What do you get when you type "modprobe ramzswap"?
modprobe: chdir(2.6.32.9-P3Droid): No such file or directory
Ok, that's exactly the same error I got when I did it.
If you create that directory (under /system/lib/modules) and put the module in it OR modify /system/bin/compcache to correctly set MODULES_DIR, that should fix it.
I created the dir and still nothing. I rebooted of course.
Nope, you need to do one or the other, not both. The file has a line:When I look at the compcache file you talk about, what should I edit the dir to? I am thinking I have to create the dir (like I already did) and then edit this file to reflect the new location?
MODULES_DIR=/system/modules/lib/modules/`uname -r`I created the dir and still nothing. I rebooted of course.
Did you put the ramzswap.ko file into that directory?
Yes I did.
Nope, you need to do one or the other, not both. The file has a line:When I look at the compcache file you talk about, what should I edit the dir to? I am thinking I have to create the dir (like I already did) and then edit this file to reflect the new location?
That `uname -r` bit is what generates the 2.6.32.9-P3Droid directory. You can either remove that bit from the MODULES_DIR definition OR create that directory and put the modules in it. Either one should work fine. I'm not sure which one is "correct"Code:MODULES_DIR=/system/modules/lib/modules/`uname -r`
I created the dir and still nothing. I rebooted of course.
Did you put the ramzswap.ko file into that directory?
Yes I did.
Nope, you need to do one or the other, not both. The file has a line:When I look at the compcache file you talk about, what should I edit the dir to? I am thinking I have to create the dir (like I already did) and then edit this file to reflect the new location?
That `uname -r` bit is what generates the 2.6.32.9-P3Droid directory. You can either remove that bit from the MODULES_DIR definition OR create that directory and put the modules in it. Either one should work fine. I'm not sure which one is "correct"Code:MODULES_DIR=/system/modules/lib/modules/`uname -r`
When I looked at my file, it never had the /`uname -r` in it. Should I add that to it?
Huh, maybe RC4 fixed it. RC3 still had that in there. I'll try out RC4 and see what I get tonight, perhaps, maybe something else changed.
And to add to this, I looked at my RC3 NAND and I never had the 2.6..... folder in /modules/ dir. I have copied over that compcache file to see if just copying it over will make any difference and moving the ramswap file back to the /modules dir. Other than that, I cant think of anything else.
EDIT: Still no workie. So its gotta be deeper I guess.