Database Info

[Q] Sensation CIFSManager with TempRoot

Ok, so the latest temp-root has gone well, and things still work okay, which is a great improvement, and much kudos to the devs for this.
However, CIFs Manager seems to not work, and I like to watch stuff over my network - and I'm pretty sure it's something very simple to do with SymLinks and stuff, as to how it works.
"Mounting the share has failed with an error
mount: mounting //10.1.100.10/Films on /mnt/cifs/Films failed: No such device"
Same settings work fine on my Desire, so I know the network's good, must be something to do with where it's looking, or trying to work, and the symlinks etc. in the temp-root.
However, I haven't a clue where to start - maybe someone can help out?

Maybe you start with reading the CifsManager FAQs?
regards
Most Frequently Asked Questions:
Q: When trying to mount a share I only get an error message saying something like...
"Error running exec().Command: [su]"
A: Most probably your device is not properly rooted or the su command is missing.
"No such device".
A: Your current kernel or rom lacks the necessary CIFS support. Try to find a matching kernel module (cifs.ko) or use a rom with explicit CIFS support.
"mounting <yourshare> on <yourmountpoint> failed: No such file or directory"
A: Your "Mount Point" simply does not exist and CifsManager is not able to automatically create it for you. As automatic Mount Point creation is not done with su rights, CifsManager can only create Mount Points in directories with permissions 777 or on your SD-Card.
Q: I have installed CifsManager but launching the app fails with something like "Application not installed on your phone"
A: This is not a problem caused by CifsManager but a bug in your ROMs launcher. Look for an updated version of your launcher.
Q: I mounted my favorite share successfully but files with special characters are not displayed correctly.
A: Try to use a kernel with explicit UTF-8 support or try to find/load the kernel module nls_utf8.ko.
Click to expand...
Click to collapse

f3d0r said:
Maybe you start with reading the CifsManager FAQs?
regards
Click to expand...
Click to collapse
fed0r,
Great information there - thank you so much. I'll double-check the permissions, but I was sure I'd already altered the mount point to 777. If that doesn't work, I'll try using a mount point on SD too.
I never even thought that the issue could be something so simple - thanks agaiN!

I thought he was indicating:
A: Your current kernel or rom lacks the necessary CIFS support. Try to find a matching kernel module (cifs.ko) or use a rom with explicit CIFS support.

Yes, on reading it the second time over, that seems to be what is indicated. I actually had an error combining #2 and #3.
Ah well, back to waiting for S-OFF so I can flash a ROM with the right kernel, because I haven't got a clue when it comes to Kernel type things!!
So, Stock Sensation ROMs do NOT have CIFS support. Tested.

[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!

Cifs support for Infused 2.0.0

Have compiled cifs.ko and slow-work.ko for Infused 2.0.0.
Thanks to gtg465x for kernel sources on GitHub, Entropy512 for initial help and http://forum.xda-developers.com/showthread.php?t=837170&page=6 for help on slow-work.ko

[email protected] said:
Have compiled cifs.ko and slow-work.ko for Infused 2.0.0.
Thanks to gtg465x for kernel sources on GitHub, Entropy512 for initial help and http://forum.xda-developers.com/showthread.php?t=837170&page=6 for help on slow-work.ko
Click to expand...
Click to collapse
Thanks for posting!
I will be posting a Daily Driver kernel update that includes these when I get around to it. It'll probably be my last DD targeting Rogers firmware for a while as I'm running CM7 now.

[email protected] said:
Have compiled cifs.ko and slow-work.ko for Infused 2.0.0.
Thanks to gtg465x for kernel sources on GitHub, Entropy512 for initial help and http://forum.xda-developers.com/showthread.php?t=837170&page=6 for help on slow-work.ko
Click to expand...
Click to collapse
What do these do?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Looks like it lets you access samba shares. Not 100% on that however.

Yup. Lets you use the CifsManager app to access Samba shares

Entropy512 said:
Yup. Lets you use the CifsManager app to access Samba shares
Click to expand...
Click to collapse
Wat is samba shares?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

WeezyFBaby17 said:
Wat is samba shares?
Click to expand...
Click to collapse
SMB protocol, which is what Windows uses to share folders.

LinuxBozo said:
SMB protocol, which is what Windows uses to share folders.
Click to expand...
Click to collapse
Sweet
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Is this GB only or will it work on 1.5.3 as well? If so is it an install zip from CWM procedure to install?

Blackberrynomore said:
Is this GB only or will it work on 1.5.3 as well? If so is it an install zip from CWM procedure to install?
Click to expand...
Click to collapse
I've compiled it using Infused 2.0.0 kernel and it is Gingerbread. So it might not work with other ROMs.
Generally you do not need to install the modules. Just place them anywhere on sdcard and load them via insmod (root required). Please see CifsManager application description for more details.

How to install?
So, with this CIFS support, I can play my video files (AVI/DivX/RMVB...)
on local NAS via Wifi? (Just like use BuzzPlayer in iPhone)
Great!
The question is... how to install it? any document about install?

leedashone said:
So, with this CIFS support, I can play my video files (AVI/DivX/RMVB...)
on local NAS via Wifi? (Just like use BuzzPlayer in iPhone)
Great!
The question is... how to install it? any document about install?
Click to expand...
Click to collapse
Read [email protected]'s instructions, or use SGS Kernel Flasher to flash my 8-13 Daily Driver kernel (Note: For instructions on THAT, read the SGS Kernel Flasher docs. CWM can flash the zip too.)
modprobe the cifs module (Module autoloading MIGHT work in the daily driver kernel so this might not be needed, I haven't tested this much)
Install the CifsManager app from the market.

I attempted to install this via CWM and it installed so fast I wasn't sure if it worked or not. So I rebooted and installed CIFS Manager and ran it. I setup a test share on my laptop on the same network subnet and shared it out to everyone. I created a new share in CIFS Manager and then attempted to browse to the share and I get an error.
Share: 192.168.3.202/download
Mount Point: /mnt/cifs/download
Username: my username
Password: my password
Options: blank
I get an error stating:
Mounting the share has failed with an error.
{mount: No such device or address}
{mount: mounting the share failed the host is down}
Any help would be greatly appreciated.
I copied the cifs.ko and slow-work.ko to /system/modules and changed the mod path in CIFS manager. I also checked/changed permissions on those two files as well. Am I missing something???
NooB apologies extended to OP.

Since they're small files, it would flash fast.
Using ADB or Android Terminal Emulator, run lsmod - do you see cifs.ko in the list?

Entropy512 said:
Since they're small files, it would flash fast.
Using ADB or Android Terminal Emulator, run lsmod - do you see cifs.ko in the list?
Click to expand...
Click to collapse
I am not very familiar with Android terminal mode or commands but I did install terminal emulator from the market and typed: lsmod at the prompt. I did not see Cifs.ko in the output?

Blackberrynomore said:
I am not very familiar with Android terminal mode or commands but I did install terminal emulator from the market and typed: lsmod at the prompt. I did not see Cifs.ko in the output?
Click to expand...
Click to collapse
Hmm, it probably isn't loaded then. So you may need to run the following in a terminal:
Code:
insmod /wherever/you/put/cifs.ko

[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?

Add CIFS support to Moto G

Hi
Is it possible to add CIFS to stock UK ROM. Im rooted and looking at various guides over the internet with no such luck yet.
So far im getting this when running insmod
insmod /system/lib/modules cifs.ko - not executable: magic 7F45
Any ideas?

chuchuj said:
Hi
Is it possible to add CIFS to stock UK ROM. Im rooted and looking at various guides over the internet with no such luck yet.
So far im getting this when running insmod
insmod /system/lib/modules cifs.ko - not executable: magic 7F45
Any ideas?
Click to expand...
Click to collapse
Isn't this meant for the Q/A section?
Sent from my Moto G using Tapatalk

chuchuj said:
Hi
Is it possible to add CIFS to stock UK ROM. Im rooted and looking at various guides over the internet with no such luck yet.
So far im getting this when running insmod
insmod /system/lib/modules cifs.ko - not executable: magic 7F45
Any ideas?
Click to expand...
Click to collapse
wrong section bro also why do u want cifs anyways?

yeshwanthvshenoy said:
wrong section bro also why do u want cifs anyways?
Click to expand...
Click to collapse
I want to be able to permanently map my windows shares, so I can use an mp3 player of my choice. I don't like any of the players that have SMB support in them.

Thread moved, guys, if you see a thread being in the wrong section, please just report it and don't just leave a post "wrong section" or "this should be in Q&A". Either you leave a helping post or none at all, please.
Now, to your problem, you've got a typo, the correct command would be:
Code:
su
insmod /system/lib/modules/cifs.ko
you can skip the "su" if you add it to an init.d script, as init.d scripts are always being run as root

laufersteppenwolf said:
Thread moved, guys, if you see a thread being in the wrong section, please just report it and don't just leave a post "wrong section" or "this should be in Q&A". Either you leave a helping post or none at all, please.
Now, to your problem, you've got a typo, the correct command would be:
Code:
su
insmod /system/lib/modules/cifs.ko
you can skip the "su" if you add it to an init.d script, as init.d scripts are always being run as root
Click to expand...
Click to collapse
Sorry. I mistyped the command on here, I have typed exactly as you say and get the error as shown in the original post :S