Database Info

[Q] CIFS Manager says it's not installed

CIFS Manager says it's not installed if I try and run it from the apps screen with VEGAn-Tab Beta 5. However, if I run it from Market it runs. Any ideas?
Also, how do I get it to connect to anything? I did a search for CIFS.KO with root explorer (once with CIFS and another with CIFS.KO) as the search term. The only thing that shows up is CifsManager and it's correndponding dirs. I thought CIFS was part of VEGA-N.
BTW - newbie here so I'm trying to remember my Liniux stuff from years ago.

gksmith said:
CIFS Manager says it's not installed if I try and run it from the apps screen with VEGAn-Tab Beta 5. However, if I run it from Market it runs. Any ideas?
Also, how do I get it to connect to anything? I did a search for CIFS.KO with root explorer (once with CIFS and another with CIFS.KO) as the search term. The only thing that shows up is CifsManager and it's correndponding dirs. I thought CIFS was part of VEGA-N.
BTW - newbie here so I'm trying to remember my Liniux stuff from years ago.
Click to expand...
Click to collapse
You need to run it from a different launcher. Something like Launcherpro. It does not like the stock launcher...
You set up the shares from the cifs manager app. ipaddress/sharename....

I tried but I know I not doing it right. If you say we set up everything in CIFS Manager, does that mean we don't need to do anything at all with my computer?

xmr405o said:
I tried but I know I not doing it right. If you say we set up everything in CIFS Manager, does that mean we don't need to do anything at all with my computer?
Click to expand...
Click to collapse
Only thing you need on your PC is the folder you want to use be shared and accessible on your network.

Super Newb alert.
Thank you for your response. I think it's the way I'm inputting the details in CIF Manager. I think I got far as my IP address but I'm not sure if I'm putting the right share path. The mount point should point to the folder I created on my internal sd card, right?
Also, Username and password - Do I need to fill that out?

xmr405o said:
Super Newb alert.
Thank you for your response. I think it's the way I'm inputting the details in CIF Manager. I think I got far as my IP address but I'm not sure if I'm putting the right share path. The mount point should point to the folder I created on my internal sd card, right?
Also, Username and password - Do I need to fill that out?
Click to expand...
Click to collapse
You need a user name and password if that is how the shared folder on your PC is setup. Pretty much if you need a password to get into your computer, you need it for the shares.
Set up the mount point something like this but use your computers IP and folder name.... 192.168.0.109/share
The other part depends on what rom you are using. Stock TnT, vegaN, which one? Not all of them have CIFS built into them. TnT, and TnTLite require a kernel patch that is located in the forum. vegaN should already have it.

xmr405o said:
Super Newb alert.
The mount point should point to the folder I created on my internal sd card, right?
Click to expand...
Click to collapse
I just noticed what you wrote.. The shared folder is on your PC, not on your tablet.. If you leave everything at default in cifs manager it will create a cifs folder under /mnt/cifs in a file manager. The shared folder on your pc will show up inside this folder.
Once you have the share setup on cifs manager you need to tap on the name and see if you get a little green indicator. That is mounting the share. You won't see your folders until you do.

Need custom ROM or Kernel for CIFSMANAGER?

Title says it. I"m on the just updated 3.1. Installed CIFSMANAGER, but don't seem able to map a drive. Get 'Error running exec'.
Just to verify, do I need a custom ROM or Kernel to use it?
[EDIT]
Or maybe I need to be rooted?

definitely need root.... also need the cifs.ko lib, not sure if that is included in stock 3.1 or not.... i just chose to go with primordial 3.1, since i knew it had it and it was working.... had to downgrade to .9, wipe, root, and install.

xformulax said:
definitely need root.... also need the cifs.ko lib, not sure if that is included in stock 3.1 or not.... i just chose to go with primordial 3.1, since i knew it had it and it was working.... had to downgrade to .9, wipe, root, and install.
Click to expand...
Click to collapse
I may end up doing something like that. Holding off for a while to see if the thing is solid enough to not have to return.
I don't know about that lib either. Just went to the site for the app, and it did indicate it needs root. Haven't read much yet over there. Will read some more on it.

ewingr said:
I may end up doing something like that. Holding off for a while to see if the thing is solid enough to not have to return.
I don't know about that lib either. Just went to the site for the app, and it did indicate it needs root. Haven't read much yet over there. Will read some more on it.
Click to expand...
Click to collapse
if you want to check for the lib, it's location should be /system/lib/modules/cifs.ko
also not sure if there's an easy way to root 3.1, but rooting .9 was pretty simple, just need adb (miniadb is fine, no need for the entire SDK)

xformulax said:
if you want to check for the lib, it's location should be /system/lib/modules/cifs.ko
also not sure if there's an easy way to root 3.1, but rooting .9 was pretty simple, just need adb (miniadb is fine, no need for the entire SDK)
Click to expand...
Click to collapse
Thanks for that. Just checked, and it is not there. I would think that if all that is 'required' is root, then installing CIFSMANAGER would install that lib. But who knows. I presume if that is the case then the reason I don't have it is because I am not rooted.
Interestingly, I can get to the server I want to with ES Filemanager. But I think it is using SMB. Also, I cannot get to it via other apps, which is what I presume CIFSMANAGER does for us.
I suspect I'll hold off with root until one comes out for 3.1. But I will likely be applying a ROM one of these days. I've been on custom ROMS on my Captivate for quite a while.

[Q] Cisco AnyConnect for Rooted Devices

Has anyone got the Cisco Any Connect for Rooted Devices App to work on the TF??? I keep getting the "This device does not meet minimum requirements to run this software (TunTap driver could not be located)" error. Anyone find a workaround?

I'd root my TF in a sec if it will work. I've been trying to get this to work on my D2G but it also doesn't have a TunTap driver. I found tun.ko in one of the forums but have to had the chance to see how one might install it. I know some custom ROMs have it included.

works fine rooted prime + clemsyn 16

It seems that it is not able to load the tun.ko if it is present as a module. I had to use insmod /system/lib/modules/tun.ko to make it work. I have a stock kernel with just added tun.ko module.

Woah, didn't know this came out...thanks. Will give it a shot.
Edit: Appears to work fine, but I need get get my ASA license.

Awesome! Finally!

The app installs fine but when you try to connect is when you get that error. @ljs_cz, does the stock 3.1 come with the tun.ko module? If not where can I find one? I found a post with a module but its for 3.0.

Totally wasn't aware this existed. Works flawlessly on my TF running prime and clemsyn. This combined with RemoteRDP means I don't need to carry round my laptop when I'm on call!
Thank you OP, life-changer.

For those who are on stock 3.1 root, copy tun.ko to /system/lib/modules and
install it from a terminal, command "insmod tun.ko".
Check with command lsmod, you should see tun.ko loaded.
Install cisco anyconnect for rooted device and you are set.
Note, you will need to load tun.ko again after a reboot.
tun.ko, http://db.tt/ad4m1qB
Sent from my Transformer TF101 using Tapatalk

Thanks ill give that a try!!!

Ok its works great but when i restart the device the module isn't installed anymore and i have to insmod again. Any way to keep is installed after device boots???

help
gpmg762 said:
For those who are on stock 3.1 root, copy tun.ko to /system/lib/modules and
install it from a terminal, command "insmod tun.ko".
Check with command lsmod, you should see tun.ko loaded.
Install cisco anyconnect for rooted device and you are set.
Note, you will need to load tun.ko again after a reboot.
tun.ko,
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
i tried copying the tun.ko to /system/lib/modules but i got Permission Denied.
Is there another way to make this work?
I am rooted with build model 8.4.4.11

You need to mount the /system as RW before you can copy it. I am not sure of the ADB command, but you can do it through total commander (file manager) which is how I did it.

is it possible that you could give me a step by step guide as to how to accomplish this? i am trying but seem to be failing.

Bump, I could also use some help with ssretz's problem.

hmm..on ICS, tried your solution anyway. copied the file over to the location you specified, but when i run the command in the terminal it says no such file or directory.
Edit...i ran su -c insmod /system/xxx/xxx/tun.ko
i ran su earlier, but not on the same line.
that seems to register it. will test later.

still failing to copy files
Hi,
im running the TF PRIME 2 with ICS 4
im trying all of the suggested aboe and still failing to copy a file to the system/library/modules folder
any help?
i think it's a permission issue, my device IS rooted and i CAN copy files to the other SD folders

zipper9 said:
Hi,
im running the TF PRIME 2 with ICS 4
im trying all of the suggested aboe and still failing to copy a file to the system/library/modules folder
any help?
i think it's a permission issue, my device IS rooted and i CAN copy files to the other SD folders
Click to expand...
Click to collapse
I've done it via command line (you must mount the system directory in RW mode) using multiple iteration of the proper switches until it finally worked, but if you're struggling, just spend a couple bucks to buy Root Explorer. The aggravation you'll save will be well worth it.
Root Explorer has a button that will eliminate the command line instructions necessary to mount the system directory in RW mode and return it to R only, along with allowing you a simple copy/paste interface to move the files.

connects but does not route over tunnel with CM9/Megatron 1.0.1
Current system with issue: Megatron 1.0.1 with stock kernel.
Details:
I am able to connect using Rooted anyconnect, and I see my route table getting updated but when I try to access a resource on the vpn network it can not reach. I am not able to ping, ssh, rdc to any resource thru the tunnel. Local lan resources such as my own computer work fine or internet resources
I see the following interfaces get created after I connect:
-csctun0
-droptun0
My route table displays updated routes after vpn connects showing to use the iface of the cscotun0 for the resources that need to be routed thru. (192.*, 10.*, etc)
Funny thing is that I am able to use the stock 4.0 ICS and/or older honeycomb releases and it works fine. It's just with Megatron 1.0.1 or any CM9 rom. I tried using update-cm-9-20120329-NIGHTLY-tf101-signed.zip, still a nogo. Leads me to believe could be related to the CM9 trunk.
The logs between stock and CM9 flavored roms look the same on anyconnect. Nothing glaring.
lsmod doesn't show the tun module in as I believe now tun is compiled directly in the kernel (can someone confirm this?) (Running lsmod with stock doesn't show tun, nor in CM9/Megatron).
I love me some cyanogen and really like ricardopvz work especially the quick apps, but I need my vpn working for production support as its nice to work off the tablet when I am not near a computer.
Any help or direction will be greatly appreciated. Thanks in advance.

Confirmed that my problem only exists with CM9/Megatron roms
AOKP and stock based roms work fine. Any one else have this issue?
Sent from my Incredible 2 using XDA

[Q] help with cifs after flash update

Hookay so I know your thinking hey it's his first post he hasn't looked around for a solution. I tried?
Anyways I've got a mz604 model wifi xoom that I flashed to the 3.1 stock kernal and then updated to 3.2 root from here http://forum.xda-developers.com/showthread.php?t=1165998
I was pretty pumped until I tried pushing the cifs.ko that I found from here http://forum.xda-developers.com/showthread.php?t=974343
I checked it out and I know a few people who previously had it installed seem to be having good luck with it on 3.2 unless they were lying. But every time I try to insmod cifs.ko I get insmod: init_module 'cifs.ko' failed (Exec format error)
I tried the cifs.ko that I found in Tiamat-Kernel-2.0.0-Katana-stockgpu.zip under the /system/lib/modules folder but when I pushed that or any of the *.ko files from there I got the same error. It's like I'm loading it up for the wrong kernal.
So am i loading the wrong cifs.ko file for the wrong kernal? is there something I can do? I checked the permissions on the files before running insmod with no luck.
Thanks if you can help if not thanks for looking.

slapjaw said:
Hookay so I know your thinking hey it's his first post he hasn't looked around for a solution. I tried?
Anyways I've got a mz604 model wifi xoom that I flashed to the 3.1 stock kernal and then updated to 3.2 root from here http://forum.xda-developers.com/showthread.php?t=1165998
I was pretty pumped until I tried pushing the cifs.ko that I found from here http://forum.xda-developers.com/showthread.php?t=974343
I checked it out and I know a few people who previously had it installed seem to be having good luck with it on 3.2 unless they were lying. But every time I try to insmod cifs.ko I get insmod: init_module 'cifs.ko' failed (Exec format error)
I tried the cifs.ko that I found in Tiamat-Kernel-2.0.0-Katana-stockgpu.zip under the /system/lib/modules folder but when I pushed that or any of the *.ko files from there I got the same error. It's like I'm loading it up for the wrong kernal.
So am i loading the wrong cifs.ko file for the wrong kernal? is there something I can do? I checked the permissions on the files before running insmod with no luck.
Thanks if you can help if not thanks for looking.
Click to expand...
Click to collapse
I was having similar problems. I'm running the Tiamat 2.0 OC kernel.
From your explanation it appears that you upgraded to 3.2 with a stock kernel and then tried to push a different cifs.ko module to your xoom. Then did the same with the Tiamat cifs.ko module.
You need to flash the Tiamat Kernel before you try to use the cifs.ko module that goes with it. (you can't use a cifs.ko module that was compiled with another kernel if my understanding is correct).
Anyway, try flashing one of the tiamat kernels (they already include the cifs module) and then open cifs manager. Set up your new share.
Now inside cifs manager, go to settings, and check both "Load cifs module" and "Load via insmod".
Happy sharing!

[Q] CIFS Manager compatibility?

Just got my A700 and it appears the kernel is not CIFS-compatible. I understand there are modules which can be used with CIFS Manager to make it work with non-compatible kernels. Does anybody know if one exists that will work with the A700?

Funny timing, I was researching this last night! I ran out of time, but essentially if you grab the kernel source, you should be able to compile the needed module, which we can then load.
I'll update this post later this morning when I dig up that URL.
--
Here are the two sources that I was referring to:
http://facti.net/drupal/node/151
http://facti.net/drupal/node/150
These articles were written for the TF101, but with the A700 kernel source available (go to Acer's Support site), there's no reason anyone cannot do this as well.
I'm going to try and find some time tonight, but we'll see.

Is this something that requires recompiling the whole kernel, or can you load the module into CIFS manager separately? If you manage to compile the module, can you post it here?

candre23 said:
Is this something that requires recompiling the whole kernel, or can you load the module into CIFS manager separately? If you manage to compile the module, can you post it here?
Click to expand...
Click to collapse
If I'm reading/researching everything correctly, all we need is a cifo.ko module from our kernel source. You should not have to recompile and install a completely new kernel.
Work is really busy today, but I've already downloaded the kernel source to a machine at home. Hoping to get time tonight to get it set up and run some tests. I'll post updates here for sure.

Thank you. I'm sure I'm not the only one who would appreciate it.

Alright, please try this file.
I cannot test myself, since I have not yet rooted (another topic entirely). Please let me know if this works for you.

No joy. Stuck the file where it wanted it, but I'm still getting "no such device".

candre23 said:
No joy. Stuck the file where it wanted it, but I'm still getting "no such device".
Click to expand...
Click to collapse
You're rooted, right?
Can you execute the following command, to "force" the module to be loaded?
insmod /system/lib/modules/cifs.ko
You can use either ADB SHELL or Terminal Emulator. Be sure you're root when you do this too (sorry, not sure what your current knowledge level is).

Thx for your effort. Unfortunately i get the following error:
# insmod /system/lib/modules/cifs.ko
insmod: init_module '/system/lib/modules/cifs.ko' failed (Exec format error)
Regards,
Dos

dosboot99 said:
Thx for your effort. Unfortunately i get the following error:
# insmod /system/lib/modules/cifs.ko
insmod: init_module '/system/lib/modules/cifs.ko' failed (Exec format error)
Regards,
Dos
Click to expand...
Click to collapse
Thank you for posting this. I think I might know what I goofed. Hopefully will get another one compiled and posted tonight.

when you compile the modules are they tablet specific? i tried the cifs.ko and md4.ko from the a500 thread in my a510, and they would load up fine with insmod, but when i used cifsmanager to mount a windows share, or tried to mount from adb shell, the tablet would reboot.

Rusty_Gunn said:
when you compile the modules are they tablet specific? i tried the cifs.ko and md4.ko from the a500 thread in my a510, and they would load up fine with insmod, but when i used cifsmanager to mount a windows share, or tried to mount from adb shell, the tablet would reboot.
Click to expand...
Click to collapse
They are specific to the kernel source code, yes.
I most likely did not have the correct kernel configuration in place, when I attempted my recompile. But since I'm returning the A700, I didn't feel like delving into it further. The articles I linked to earlier should be a good start if you wish to give it a go.

Any idea how to make CifsManager work on A510?