I tried CIFSmanager on v7beta Failsafe, but it didn't work. It does work on V6 (stock).
Is that a beta related problem, or did the Kernel change so it isn't compatible with Cifs.ko anymore?
Related
DO we have independent cifs.ko for P500? I'm using void#echo base on stock 2.2, i guess
TIA
at least, which custom rom that included with cifs.ko and tun.ko?
T.I.A
This should be posted in threads with custom roms, i am also interested in mounting my remote drives.
I tried a few cifs.ko for non-ATT SGS2 but they were not working.
Has anyone got the cifs working for ATT SGS2? As far as I can tell, entrophy ROM is the only one that has built-in support for cifs.
Afternoon all...
Apologies if this question has been asked. I've been searching but getting myself confused with all the info.
I downloaded cifsmanager from market place and tried to run it. I found that it wasn't working. After a little reading, I was told I need the cifs.ko module.
I downloaded what I thought was the correct module, made sure that within cifsmanager, I had the correct path and it still doesn't work.
I've read on few threads that this will not work on the stock kernel and that pershoot's kernel will do the job.
I found a link to pershoot's kernels http://droidbasement.com/db-blog/ but now confused as to which one I could use.
I have a 16gb WiFi and 3g model, do I use this kernel?
"10.1 3G, Touchwiz UX (HC 3.2 (stock); GT-P7500):
boot-cm_2636.4_p4_ux_hc32-oc-xtra-vfpv3-d16_fp-121111.zip:"
I've extracted the cifs.ko from lib-2636.4_ux_hc32.tar.gz - the droidbasement.com website says to push the module I desire to /data/local/modules
Where do I push it to, the kernel zip file?
Thanks in advanced....
Hi!
I can't find a way to mount smb shares. CifsManager and mount manager tells "no such device". As I found in xda and other places, it's all about cifs.ko module. I can't find it on phone. Usually it must be in /system/lib/modules/ but there is no such folder, only /lib/modules/ with few files there and no cifs.ko. I found cifs.ko and slow-work.ko somwhere on this forum, but it didn't work, even I pointed to that cifs.ko. Maybe not compatible with my device and CheckROM.
Can anyone help me with this? Maybe different ROM? I had problems with CyanogenMod - many items in market are not compatible with my phone, when using CyanogenMod.
My phone: Samsung Galaxy S2 GT-I9100
Android version: 2.3.5
Baseband version: I9100XXKI3
Kernel version 2.6.35.7-I9100XKI3-CL577579 [email protected] #2
Build number CheckROM V5.5
Thank You!
Ok, not actual for me anymore because I made to fix market problem in CyanogenMod rom.
But anyway, someone else might have the same problem. So if you have any ideas, please post!
Same Problem here.
Does anyone know a solution?
Using checkrom. It does not work with the Standard-Kernel nor with ninpo and dark Night Kernel. "No such device"
When using Miui it worked fine. Is it because of this .ko files?
I cant find compatible ones neither.
Hi guys , this is my first post here and i hope you could help me
Today i rooted my Galaxy s II so i could use droid vpn
after rooting i installed Tun.ko
But unfortunately when i press install it keeps telling me
" Cannot fin a compatible tun module for your device ...."
Then i tried doing this manually ..
i moved different tun.ko modules into
"/system/lib/modules"(( there was no folder there called "modules" so i created it ))
But it keeps saying " Path to tun.ko not found "
i'm using the kernel 3.0.15-i9100xxlps-cl294511 "Android 4.0.3 "
You can see the problem in the attached pic.
Help please !!
I got same problem, i think thats why you have a custom kernel, because i see to someone with stock kernel and he have no problem. Or maybe cuz isnt compatible with ICS.
for neak also the same thing.....its kernel compatibility issue.
you can connect without tun.ko moudle as it is supported by default
no nead for tun.ko installer just droidvpn and it will connect , but you will not get full iptable support because of missing of this moudle , it is a known problem since any kernel even for gb
I have the exact same problem. Kernel issue. Mine is kernel version 3.0.13. Someone??