Related
I have froyo with 2.6.32.9 kernel. I can't mount a remote nfs dir..
i can try this (with root privileges):
mount -t nfs remoteIPAdress:/remotedir /sdcard/mnt
i have got "No such device"
Maybe a kernel is not supported the NFS?
What can i do?
if you just need to read write from network drive use estrong file manager from market.
Solution
TiBiSMART said:
I have froyo with 2.6.32.9 kernel. I can't mount a remote nfs dir..
i can try this (with root privileges):
mount -t nfs remoteIPAdress:/remotedir /sdcard/mnt
i have got "No such device"
Maybe a kernel is not supported the NFS?
What can i do?
Click to expand...
Click to collapse
Look trough this thread: forum.xda-developers.com/showthread.php?t=761414
You need cifs.ko module to mount samba shares. Download it from forum.xda-developers.com/attachment.php?attachmentid=420072&d=1287150453, put files on your /sdcard and run these 3 commands:
su
insmod /sdcard/slow-work.ko
insmod /sdcard/cifs.ko
Of course, you need root. And after this you can mount your shares. I also recommend you forum.xda-developers.com/showthread.php?t=756158 this app to mount with nice GUI)
Alex073 said:
Look trough this thread: forum.xda-developers.com/showthread.php?t=761414
You need cifs.ko module to mount samba shares. Download it from forum.xda-developers.com/attachment.php?attachmentid=420072&d=1287150453, put files on your /sdcard and run these 3 commands:
su
insmod /sdcard/slow-work.ko
insmod /sdcard/cifs.ko
Of course, you need root. And after this you can mount your shares. I also recommend you forum.xda-developers.com/showthread.php?t=756158 this app to mount with nice GUI)
Click to expand...
Click to collapse
thx Alex!
but i haven't samba shares. I have nfs shares on the router (with tomato linux)
I think samba share it's very different with nfs share or i know it wrong?
We now have a working cifs.ko and nls_utf.ko. I was able to mount my win7 shares using cifs_manager and stream a few movies using mvideoplayer from the mounted share.
My initial problem seemed to be that I used the android ndk toolchain and the nook kernel is compiled with the codeSourcery toolchain.
After I re-compiled using the codeSourcery toolchain everything works (at least for now)
For those who want to try this.
Download the cifs.ko and nls_utf8.ko modules.
http://dl.dropbox.com/u/16190398/Nook Color 1.0/cifs.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.0/nls_utf8.ko
Mount /system as read write and create a directory under /system/lib called modules. Copy the cifs.ko and nls_utf8.ko modules under this directory.
Type the following from your windows or linux console
adb shell
#mount -o remount,rw /dev/block/mmcblk0p5 /system
#su
#cd /system/lib
#mkdir modules
#exit
#exit
Now you are back in your windows or linux command prompt
adb push cifs.ko /system/lib/modules
adb push nls_utf8.ko /system/lib/modules
adb shell
#su
#insmod /system/lib/modules/cifs.ko
#insmod /system/lib/modules/nls_utf8.ko
if everything went well you should see no errors.
#lsmod
(THis should give you a list of running modules)
You should see something like
nls_utf8 1856 0 - Live 0xbf153000
cifs 240060 0 - Live 0xbf113000
#exit
#exit
Download cifs_manager from the android market and follow the instructions from
http://forum.xda-developers.com/showthread.php?t=756158
If you have Astro file manager installed then tapping on the mounted share from cifs_manager will automatically launch Astro and list the folder/files under that share.
BTW, you can copy the modules anywhere you like even under /sdcard/modules but the default path used by cifs_manager is /system/lib/modules. You can edit the path from cifs manager to point to the location of your cifs.ko module.
---- 05/06/2011 Update ------------
New version of cifs.ko, slow-work.ko for the 1.2 update. This is for kernel version 2.6.32.9
Note, cifs.ko requires some symbols from slow-work.ko so you will need to load slow-work.ko first. If you use cifs-manager, under advanced settings
you can check load modules at startup via insmod and put the path to multiple modules for e.g /system/lib/modules/slow-work.ko:/system/lib/modules/cifs.ko.
Everything seems to be working fine for me. Let me know if you run into issues.
http://dl.dropbox.com/u/16190398/Nook Color 1.2/slow-work.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.2/cifs.ko
http://dl.dropbox.com/u/16190398/Nook Color 1.2/nls_utf8.ko
Alright! This is fantastic! I can even play my SNES roms over wifi. Thanks for sharing.
The only issue I have noticed is that you need to run the insmod commands every time you reboot the device, and I reboot a lot. For now I'm just using gScript to run the 2 commands whenever I need, but it would be great to have them run when the program starts. I know you're just sharing and this has been mentioned in the app thread, just wanted to make my observations known.
Edit: Found a nifty toggle in the settings of cifs managaer that runs the insmod command at startup. I guess I should look before I complain...
any chance you can provide your build environment, so that the rest of us can work on hacking the kernel.
thetoady said:
any chance you can provide your build environment, so that the rest of us can work on hacking the kernel.
Click to expand...
Click to collapse
Setting up the environment is ridiculously easy esp if you have access to a linux box. There is a very well documented wiki page which outlines the process of building your own custom kernel for the nook color.
http://nookdevs.com/NookColor:_Build_the_Original_Kernel
I downloaded the codesourcery tool chain and did the minimum install as I did not care about the IDE and added the path to my environment. THat was about it. Everything else I followed the wiki page.
Here is my .config file if you like. When you run "make menuconfig" you can choose to load an alternate config file instead of the default. Just put this .config (after renaming it to .config_myconfig or something) under your distro/kernel directory.
Let me know if you need anything specific and I'll try to help. I had to add the .txt extension to the config file for xda upload but you can rename it to anything you want.
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
Seems more like an error in configuring CIFS_Manager.
If the module doesnt load you get a different error from Cifs_Manager
"No such device".
Can you try using adb shell and use insmod to load the module manually.
CHeck with lsmod if the module is loaded.
Can you post you cifs_manager screen for the share that you are trying to mount.
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
I'm sure you noticed that there's an error in dascud instructions... the 2nd insmod command has a filename typo..
its should read
HTML:
#insmod /system/lib/modules/nls_utf8.ko
dascud.. thanks a ton... as mentioned in my previous post can you please make the change in your post
madrascafe said:
dascud.. thanks a ton... as mentioned in my previous post can you please make the change in your post
Click to expand...
Click to collapse
Done. Were you able to mount the CIFS shares ?
dascud said:
Done. Were you able to mount the CIFS shares ?
Click to expand...
Click to collapse
Yes. No problem at all. I even opened files from root explored & played some music. Thank you for this
firstly thanks dascud's great work! Awesome!
I found a problem when mount with option iocharset=utf8, cifsmanager report below error message then failed to mount
Mounting the share has failed with an error.
mount: Can not access a needed share library
When I remove iocharset=utf8, mount success but I failed to access any folder including non-western characters.
ctos said:
firstly thanks dascud's great work! Awesome!
I found a problem when mount with option iocharset=utf8, cifsmanager report below error message then failed to mount
Mounting the share has failed with an error.
mount: Can not access a needed share library
When I remove iocharset=utf8, mount success but I failed to access any folder including non-western characters.
Click to expand...
Click to collapse
CIfs_manager only loads the cifs.ko modules. You will need to load nls_utf8.ko manually or using a script to display non-western character set. I think you can use something like gscript for the purpose.
I've followed the instructions, but trying to launch the cifsmanager I get
Application not installed on Device
from reading the FAQ on the cifsmanager page, it says its a problem with the launcher. is this because I've updated the NC to 1.01? thanks
dascud said:
CIfs_manager only loads the cifs.ko modules. You will need to load nls_utf8.ko manually or using a script to display non-western character set. I think you can use something like gscript for the purpose.
Click to expand...
Click to collapse
gscript works for me. thanks a lot!
Sent from my LogicPD Zoom2 using XDA App
pezhore said:
Hrm, couldn't get that working on my system.
I'm getting this error:
Mountingthe share has failed with an error.
mount: Invalid argument
Thoughts?
Click to expand...
Click to collapse
I got this when I put the computer name in the share path. I switched to using IP address instead and it worked.
Hi,
Thanks for the files. I didn't follow the steps in the instructions because there is an easier way. Like mention before, ClifsManager only need cifs.ko.
I basically just copy cifs.ko to my sd card. In the CM setting, just change path to
/sdcard/cifs.ko
Setting up shares is easy too, share path is your ip/<sharefolder>, mount point /sdcard/<foldername> and your user/pwd. This worked with Windows 7.
ClifsManager is definitely one of the must have on the NC.
Is there any chance of getting an tun.ko driver built so that this can be used in conjunction with OpenVPN?
Thanks!
smlong426 said:
Is there any chance of getting an tun.ko driver built so that this can be used in conjunction with OpenVPN?
Thanks!
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/showthread.php?t=889736
Will this, or any software for that matter, allow me to openly share one or more folders on the NC device (SD card), so I can access that NC shared directory from a windows box and copy files back and forth?
KryptoNyte39 said:
Will this, or any software for that matter, allow me to openly share one or more folders on the NC device (SD card), so I can access that NC shared directory from a windows box and copy files back and forth?
Click to expand...
Click to collapse
What you need is a Samba server for Nook. Looks like this has already been accomplished. Maybe you can post a howto once you get this working.
http://forum.xda-developers.com/showpost.php?p=8239139&postcount=128
I have not seen this mentioned over here in the Vibrant sections at all, and sort of wonder why...
I found this thread by darkbyt3 while searching for cifs support a while back. I have tried the froyo module originally designed for the I9000 and it does work on the Vibrant. I am using the Stock + Voodoo kernel with Nero 3. You can use these modules (needs cifs.ko and slow-work.ko) along with Cifs Manager to mount your network shares.
Update:
Mount Manager (shameless plug) has been released and supports the loading of multiple modules. See the link for full details.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Astro file manager can sort of do this without the cifs module using its SMB plugin, but I've never been able to open anything directly using the Astro SMB. I have to copy it to the device first. With CIFS, I can open anything just like it is already on the device.
To use these modules you have to load them. I copied them to a folder called modules on my internal sdcard.
Code:
$ su
# insmod /sdcard/modules/slow-work.ko
# insmod /sdcard/modules/cifs.ko
You can check that the cifs module is loaded
Code:
# lsmod | grep cifs
cifs 257211 0 - Live 0xbf29c000
slow_work 12113 1 cifs,[permanent], Live 0cbf0bd000 (P)
Then you create the mount (or you can use cifs manager)
Code:
# busybox mount -t cifs //192.168.222.1/shares /sdcard/network/shares
The only thing I haven't figured out yet (haven't really looked either) is how/where to put the insmod commands so these modules automatically load when the device boots. Since slow-work.ko has to be loaded before cifs.ko, cifs manager cannot be used to load the cifs module since it only supports loading one module.
camalot said:
I have not seen this mentioned over here in the Vibrant sections at all, and sort of wonder why...
I found this thread by darkbyt3 while searching for cifs support a while back. I have tried the froyo module originally designed for the I9000 and it does work on the Vibrant. I am using the Stock + Voodoo kernel with Nero 3. You can use these modules (needs cifs.ko and slow-work.ko) along with Cifs Manager to mount your network shares.
Astro file manager can sort of do this without the cifs module using its SMB plugin, but I've never been able to open anything directly using the Astro SMB. I have to copy it to the device first. With CIFS, I can open anything just like it is already on the device.
To use these modules you have to load them. I copied them to a folder called modules on my internal sdcard.
Code:
$ su
# insmod /sdcard/modules/slow-work.ko
# insmod /sdcard/modules/cifs.ko
You can check that the cifs module is loaded
Code:
# lsmod | grep cifs
cifs 257211 0 - Live 0xbf29c000
slow_work 12113 1 cifs,[permanent], Live 0cbf0bd000 (P)
Then you create the mount (or you can use cifs manager)
Code:
# busybox mount -t cifs //192.168.222.1/shares /sdcard/network/shares
The only thing I haven't figured out yet (haven't really looked either) is how/where to put the insmod commands so these modules automatically load when the device boots. Since slow-work.ko has to be loaded before cifs.ko, cifs manager cannot be used to load the cifs module since it only supports loading one module.
Click to expand...
Click to collapse
Thanks a ton for the write up
As for the insmod commands on startup, I wonder if you can put them into init.rc, but I guess you need to create an update.zip like file to mod it and flash it via recovery.
Nero V3 will run /system/bin/userinit.sh on startup... you could put the commands in there.
Will this also work for NFS? I followed the steps in the OP, and the cifs modules are live, but I still cannot mount. I created the mount target directory as root with permissions set to all (777). It works on my computer. I tried typing these command into better term emulator:
busybox mount -t nfs 192.168.2.1:/my/mount /mnt/network
busybox mount -t nfs 192.168.2.1/my/mount /mnt/network
mount -t nfs 192.168.2.1:/my/mount /mnt/network
mount 192.168.2.1/my/mount /mnt/network
but I got this error for all of them:
mount: mounting 192.168.2.1:/my/mount on /mnt/network failed: No such[the
terminal gets cut off and I can't read the rest!]
CifsManager has this error:
mount:Invalid Argument
I'm running Axura 2.1 which uses JK6. Does the cifs.ko need to be compiled for specific kernels?
kslays said:
Will this also work for NFS? I followed the steps in the OP, and the cifs modules are live, but I still cannot mount. I created the mount target directory as root with permissions set to all (777). It works on my computer. I tried typing these command into better term emulator:
busybox mount -t nfs 192.168.2.1:/my/mount /mnt/network
busybox mount -t nfs 192.168.2.1/my/mount /mnt/network
mount -t nfs 192.168.2.1:/my/mount /mnt/network
mount 192.168.2.1/my/mount /mnt/network
but I got this error for all of them:
mount: mounting 192.168.2.1:/my/mount on /mnt/network failed: No such[the
terminal gets cut off and I can't read the rest!]
CifsManager has this error:
mount:Invalid Argument
I'm running Axura 2.1 which uses JK6. Does the cifs.ko need to be compiled for specific kernels?
Click to expand...
Click to collapse
AFAIK nfs is different then cifs. I don't think cifs will work with nfs shares.
lqaddict said:
Thanks a ton for the write up
As for the insmod commands on startup, I wonder if you can put them into init.rc, but I guess you need to create an update.zip like file to mod it and flash it via recovery.
Click to expand...
Click to collapse
ttabbal said:
Nero V3 will run /system/bin/userinit.sh on startup... you could put the commands in there.
Click to expand...
Click to collapse
Couldn't you also add them to init.d if you are running nero or using voodoo?
one more step in making the Mobile Phone a True Computer
Thanks for posting this CIFS Support, one more step in making the Mobile Phone a True Computer
Whitehawkx said:
Couldn't you also add them to init.d if you are running nero or using voodoo?
Click to expand...
Click to collapse
I got it to work by adding it to init.d but I had to move the two .ko files to a folder I created in /data. I think it is because the sdcard doesn't mount until late in the boot process. Other than that it works perfectly and I can read my NAS.
What is the slow work module for?
Sent from my SGH-T959 using XDA App
in which folder and which file?
grendel905 said:
I got it to work by adding it to init.d but I had to move the two .ko files to a folder I created in /data. I think it is because the sdcard doesn't mount until late in the boot process. Other than that it works perfectly and I can read my NAS.
Click to expand...
Click to collapse
roffee said:
in which folder and which file?
Click to expand...
Click to collapse
Doesn't matter, just point point the insmod cmd to where it is located in /data
roffee said:
in which folder and which file?
Click to expand...
Click to collapse
I just created a folder name CIFs in /data and put the two .ko files in it. Then in init.d I created a file that looked like :
#!/system/bin/sh
insmod /data/CIFs/slow-work.ko
insmod /data/CIFs/cifs.ko
But, just as dasunsrule32 stated, it doesn't matter what folder you use as long as your file points to the one you are using.
Awesomeness. Worked out great. Just as grendel905 stated I threw the .ko modules into a folder in /data and threw a script into init.d. They now load at boot. Just an fyi for ppl this method will not work if you are using a stock 2.2 kernel. You either need to be using voodoo or one of TW's kernels with the modified init.rc.
I've released Mount Manager on the android market that will allow you to load these modules on your device automatically (without having to edit any files). It can load them when the device boots, or when the app starts.
It also can manage your cifs/nfs shares too. Allowing you to mount/unmount them. You can also set them to auto mount when the device boots, when the application starts or when connected to wifi.
For more info you can see the thread for the app where I will maintain the changelog.
You have just become a friend to vibrant users everywhere!
So here's the problem im having. Both modules load fine and I've confirmed they are loaded, but when I try and mount anything, mount says cifs is an invalid argument for type.
Sent from my SGH-T959 using XDA App
What are you using to mount? An app or from the shell?
Sent via my Samsung Galaxy S
First I tried mount manager and when that failed I did it myself from a term.
Double checked that slow-work and cifs modules are loaded...
Here is terminal...
mount -t cifs //192.168.1.12/d /mnt/sdcard/sd
mount: Invalid argument
#
Doesn't matter where I try to mount to...
Chris
Nm, wasn't paying attention to case for my share name.. works. Thanks
Sent from my SGH-T959 using XDA App
hololight said:
First I tried mount manager and when that failed I did it myself from a term.
Double checked that slow-work and cifs modules are loaded...
Here is terminal...
mount -t cifs //192.168.1.12/d /mnt/sdcard/sd
mount: Invalid argument
#
Doesn't matter where I try to mount to...
Chris
Nm, wasn't paying attention to case for my share name.. works. Thanks
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
you should be able to do this and not have to worry about the case of your shares:
Code:
mount -t cifs //192.168.1.12/d /mnt/sdcard/sd -o nocase
nfs.ko
has anyone been able to create a nfs.ko module?
Thanks to the directions here I was able to create a loading cifs.ko for the Firebird SGS / GT-I9010 Kernel, but my nfs.ko built with the same process wouldn't load.
Don't want to flash a full kernel just need the modules if possible. Many thanks
SordFish said:
Don't want to flash a full kernel just need the modules if possible. Many thanks
Click to expand...
Click to collapse
This is currently one of the top google results for "cifs ouya;" please delete or rename this thread, as there had been zero progress on it, but everyone who wants cifs on ouya is getting steered to it.
huh? no one compile it?
here you are
What I need to do with this files? can you explain with more detail please.?
download and extract them
Code:
adb push md4.ko /data/local/tmp/md4.ko
adb push nls_utf8.ko /data/local/tmp/nls_utf8.ko
adb push cifs.ko /data/local/tmp/cifs.ko
adb shell
su
mount -orw,remount /system
cat /data/local/tmp/md4.ko > /system/lib/modules/md4.ko
cat /data/local/tmp/nls_utf8.ko > /system/lib/modules/nls_utf8.ko
cat /data/local/tmp/cifs.ko > /system/lib/modules/cifs.ko
mount -oro,remount /system
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/nls_utf8.ko
insmod /system/lib/modules/cifs.ko
then use something like "CifsManager" to mount smb share
P.S. those modules are for 1.0.393-r1 only, and if Ouya release a newer firmware, you will lost the cifs functions.
>s added
needed some >s. I inserted them below
i just pasted it without looking and MAD pc speaker beeping action when it cats to the terminal
Code:
adb push md4.ko /data/local/tmp/md4.ko
adb push nls_utf8.ko /data/local/tmp/nls_utf8.ko
adb push cifs.ko /data/local/tmp/cifs.ko
adb shell
su
mount -orw,remount /system
cat /data/local/tmp/md4.ko > /system/lib/modules/md4.ko
cat /data/local/tmp/nls_utf8.ko > /system/lib/modules/nls_utf8.ko
cat /data/local/tmp/cifs.ko > /system/lib/modules/cifs.ko
mount -oro,remount /system
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/nls_utf8.ko
insmod /system/lib/modules/cifs.ko
Thanks.
WonderEkin said:
huh? no one compile it?
here you are
Click to expand...
Click to collapse
Err, I guess I should have noted that possibility as well, haha. Thanks.
hi, anyone have working cifs.ko in ouya?, the library is missing. the only option is cifmanager but canĀ“t add at startup
I apologize for my ignorance, but what sort of practical applications would CIFS support offer on the OUYA? I side loaded an app called Samba Filesharing, and it seems to work fine, however the write speed is quite slow - under 3 MB/s from my laptop.
What would be the difference between following the steps above and just side loading the app I've mentioned? I'm very interested in using my OUYA as a file server in conjunction with a USB hard drive.
Thanks!
Sent from my iPhone using Tapatalk 2
So... figured I'd update this thread if anyone wants to test these...
Here's modules that should work on the current firmware ( OUYA 1.2.771 as of this writing ) as well as CIFSManager.
Install the same way as described by WonderEkin.
.. need some direction .. can't make this work .. "No such file or directory" .. share my directory from win8 with no security credential .. smb is working fine ..
realhuh said:
.. need some direction .. can't make this work .. "No such file or directory" .. share my directory from win8 with no security credential .. smb is working fine ..
Click to expand...
Click to collapse
Do these still work?
Hey to everyone
I downloaded MountManager onto my one, installed InsertCoin with Sense 6 and try to mount my server. But I cant create "/mnt/cifs/Server" - "read-only file system" - anyone knows why? When I try to use another software ("CifsMount" ???) I am able to mount but cant create any folders or files.
Hope I havent wrote in the wrong forum, but I think that its a rom specific issue because I was able to mount on my Nexus 4.
Greetings
That happened to me last night; I used Terminal Emulator (in Play Store) and entered "su" (minus quotes) to get root access and then used the "mkdir" command. So try this in Terminal Emulator:
su
mkdir /mnt/cifs/Server
I'm still trying to get CIFS support, unfortunately. Don't think I have it in my kernel