Have a new NC running quite well using dalingrin's kernel and latest CM7 nightly. Have everything working on it smoothly but can't seem to get CIFSManager working -- would love to use this to stream videos (using Mobo) with this.
I set everything up as indicated on this site as well as on iamafanof.wordpress.com/2010/12/27/streaming-epub-books-media-to-nook-color-with-cifsmanager. I keep getting the error "Mounting the share has failed with an error.mount: Mount not found". Does anyone have any idea how to fix this? CifManager was able to create the mount folder on the SD card that I am using so I assume it has the correct permissions and was able to find it in the first place. Also, since I use dalingrin's kernel, I assume the cifs.ko is built into CM7, which combines the .ko into tiwlan_drv.ko by dalingrin. I also assume I don't have to check any of the settings boxes as tiwlan_drv.ko is loaded on boot.
Anybody with any ideas or help? Would be much appreciated! THanks.
Related
Hi all,
Have any of you been able to get a Cifs share mounted under android 4.3 on the N10.
I've tried various kernels and managers like Cifs manager but with no joy, they complain of invalid argument.
It seems like there has been success on the N7 according to this thread http://forum.xda-developers.com/showthread.php?t=2107224&page=7 but I can't see anything for the N10.
If it does work for you could you let me know what ROM / Kernel combo you use?
Not only 4.3. I haven't managed to make it work on 4.2.2 either
Sent from my GT-I9505 using Tapatalk 4
http://forum.xda-developers.com/showthread.php?t=2430056
^^^^^^^ What zod said. Working fine for me
I tried several combinations to mount CIFS shares with mountmanager:
Trinity + Carbon Rom, Sentinel, CM10.2 = works without problems
Flaming Monkey + Carbon Rom, Sentinel, CM10.2 = works - but without UTF-8 (for special characters like öäü...)
KTManta + Carbon Rom, Sentinel, CM10.2 = doesnt work.
Any Kernel + Purity Rom, AOKP, PA = doesn't work.
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
andreasy said:
Could someone please confirm if CIFS is finally dead on Android? I haven't seen a single user manage to make it work. I even asked kernel developers to patch their kernel with this only solution provided here and even though they were happy in the beginning they never wanted to talk about it later which makes me think it was a hell or them.
I'd really like to know if I should just uninstall all CIFS related staff and just forget about it.
Edit:
Sorry I think it's wrong threat
Click to expand...
Click to collapse
Google sure seems to be trying really hard to kill CIFS (and any network filesystems for that matter) on Android. As it stands now (in 4.3) there is no possible way to get CIFS working properly on the stock ROMs with a stock kernel. This is because the geniuses at Google removed loadable module support from the stock kernel and because of the way they implemented the multi-user stuff (using filesystem namespaces). The thing that kills me is that there is absolutely no reason for Google to make this so difficult. They could have simply compiled support for network filesystems into the kernel if they wanted to remove modules for "security". It would also be trivial for them to add a mount point which propagates to the user namespaces. They did this crap on purpose. And that is exactly the reason why my next tablet will not be an Android one. You shouldn't have to hack your tablet to get basic functionality that should just work out of the box. I'm done being scroogled.
Anyhow, I did manage to get CIFS working on my Nexus 7 which is running 4.3. See my post here for details. Now, I don't think my kernel will work on your Nexus 10. But, if you flash someone else's custom kernel (or compile your own) for the Nexus 10 which does have CIFS support/modules you should be able to use my update.zip which does not contain the kernel. I don't have a Nexus 10 to test on, so I can't promise anything but I don't see why it wouldn't work.
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
cien12 said:
With new 4.3.1 Rom Versions I have troubles with CIFS Mount.
I can mount my NAS without problems with Terminal command, and I can see all mounted Files and Folders in Terminal.
But any App (like ES Fileexplorer, Solidexplorer, Power-Amp....) can't see any files. The Folder always keeps empty.
I have tried several mount points: /sdcard/cifs, storage/emulated/legacy/cifs, /data/media/cifs. Always the mount is visible in Terminal but not in all apps.
I have tried many mount options like: noperm, rw, file_mode, dir_mod, gid.....
Click to expand...
Click to collapse
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
pkfox said:
Hi there, could you post the command line you use to mount your NAS drive ? I keep getting "Invalid argument", this is what I've tried
Code:
mount -t cifs //192.168.1.3/music /mnt/music
Click to expand...
Click to collapse
You have to get su access first with "su"
mount -r -o noperm,rw,file_mode=0777,dir_mode=0777,uid=1000,gid=1000,unc=\\\\192.168.0.10\\music,username=***,password=*** -t cifs none /sdcard/cifs
Thanks that worked, do you know of a way to mount automatically at boot time on Android ? I notice there is no /etc/fstab
Thanks again.
Hi all, if your goal is simply to play music and video from your NAS to your android device, you can use Kodi (xbmc) that can access cifs path directly!
i', using BTU MGA rom rooted, and adam kernel 1.6. i'm having no luck whatsoever getting a cifs mount to work. anybody got it working? i've tried it using cifs manager, and also in terminal. always comes back with "invalid argument"...
CIFS mount troubleshoot
whatsisnametake2 said:
i', using BTU MGA rom rooted, and adam kernel 1.6. i'm having no luck whatsoever getting a cifs mount to work. anybody got it working? i've tried it using cifs manager, and also in terminal. always comes back with "invalid argument"...
Click to expand...
Click to collapse
Hi,
there are several threads about CIFS debugging. I have also issue with CIFS mounting, but you can have different issue, so try this:
1) check "ls /proc/fs/cifs" ... it should show CIFS modules. If not existing, your trouble is even deeper
2) increase debug for CIFS: "echo 1 > /proc/fs/cifs/cifsFYI"
3) after you run your mount command, run "dmesg > outerror.txt" and search lines containing text "cifs". You can see more.
This link might help:
http://forum.xda-developers.com/showthread.php?t=756158&page=53
... see the link in the post from victorhooi 21st December 2013 12:41 AM
I'm currently running an OMNI build for everest, which is working delightfully well. The only thing I can't seem to achieve is to mount a CIFS directory. Actually, it can be mounted, but its contents are only visible to root.
While doing some research I found this thread. For what the description says, I assume this fix has been applied in CM, since I was able to mount CIFS (outside of /storage) before switching from CM to OMNI.
Would these patches be applicable for OMNI? If so, I would try to ask the everest ROM creator to apply them, or even try myself. But I'm afraid I may be lacking the knowledge to judge whether it'd just be a waste of time.
Thanks in advance for any tips on this matter.
Any update on the topic? I've tried Omni on my Nexus 10 and it runs perfectly well but this is the last thing that stops me from using the ROM. After mounting the data from my CIFS or NFS share the data is only available from the app performing the mount. The patches in the link from the previous post seems to work around this issue, is there any chance it could be applied to OmniROM?
Try to mount your folders manually (or by GScript) with Superusers --mount-master switch to make the mounts available to all processes. Something like this.
The su binary now also has a "--mount-master" option that connects you to a su session in the main mount namespace. Mount commands in this session should affect all processes. This is still a bit experimental, and getting it working requires a reboot after upgrading the binaries from a pre-1.93 version. This feature has been asked for a lot by devs, and it escapes the need to hijack system services to affect system-wide mounts, which is becoming more complicated with every Android release. A new version of StickMount will be released in a few days as well, taking advantage of this feature, and thus avoiding a number of issues some are seeing.
https://plus.google.com/+Chainfire/posts/hLKytCwUm6k
Click to expand...
Click to collapse
Alternatively, there is still the possibility to hijack a system service (like SSH one) to point to a script instead that will bring up your mounts. I'm personally using this so i haven't checked the SU method yet.
Good Luck!
DualJoe said:
Try to mount your folders manually (or by GScript) with Superusers --mount-master switch to make the mounts available to all processes. Something like this.
Alternatively, there is still the possibility to hijack a system service (like SSH one) to point to a script instead that will bring up your mounts. I'm personally using this so i haven't checked the SU method yet.
Good Luck!
Click to expand...
Click to collapse
Thanks, --mount-master works like a charm!
I updated from CM10 to the latest CM11 nightly and noticed that I the system/lib/modules appears to be missing? I use mount manager to mount and access my home server shares, but CM11 seems to missing the modules?
I even copied them over from my wifes tablet yet mount manager still doesn't seem them either.
Anyone have any ideas?
ptmuldoon said:
I updated from CM10 to the latest CM11 nightly and noticed that I the system/lib/modules appears to be missing? I use mount manager to mount and access my home server shares, but CM11 seems to missing the modules?
I even copied them over from my wifes tablet yet mount manager still doesn't seem them either.
Anyone have any ideas?
Click to expand...
Click to collapse
yep, i got the same bug. Hope you found a solution!?!
smoschi said:
yep, i got the same bug. Hope you found a solution!?!
Click to expand...
Click to collapse
I actually did find a solution or work around. I copied the cifs.ko module to my storage/sdcard0/downloads location and then was able to see and add the module.
It did seem to be hit and miss in loading at first, but seems to be holding and mounting the shares. Have had no issues in the last week or so.
I also updated to the SnapShot-M8 the other day, but unsure if made a difference or not.
ptmuldoon said:
I actually did find a solution or work around. I copied the cifs.ko module to my storage/sdcard0/downloads location and then was able to see and add the module.
It did seem to be hit and miss in loading at first, but seems to be holding and mounting the shares. Have had no issues in the last week or so.
I also updated to the SnapShot-M8 the other day, but unsure if made a difference or not.
Click to expand...
Click to collapse
Thats great to hear,
cant believe that nobody use cifs. Im on cm11and cant find cifs.KO and i think its not included in cm kernel. Plesse give a link for cifs.KO files fr nexus10 ... Thank you
will this module work on stock rooted 5.1.1 ?
Hi all
As the title says, i want to mount a networkpath to my nexus 10 for using "normal" musicplayer like Mort player to play the music stored in the network.
I searched a little around but only found solutions for JB. (Cifs and stuff)
I already tried myself to mount it with Mount manager from the playstore but always get a "failed to mount"
I am using an usb-stick on my Router (Asus RT-N56U). I have access to it with my fileexplorer.
Used ROM and kernel are shown in my signature.
Hopefully someone can give me a hint.
Greetings
Cua.
A little brainstorming:
An user in our german forum found out, that for the moment mounting seems only to work with thunderkat-kernel. But the folder is empty when trying to access. Maybe a problem with the correct rights.
Still in hope someone can help solving this problem.