[SOLVED] CIFS support - Desire HD General

A noob question support. Is there a CIFS support in the 2.6.32.21-gbe90714 kernel or a suitalbe cifs.ko file that one could use with the Cifsmanager app?
I am a bit lost here. I downloaded the DHD kernel source released, but had no luck locating the cifs.ko file. And I have no idea how to compile one myself. Can someone pinpoint me in the right direction?
update:
found some instructions here http://forum.xda-developers.com/showthread.php?t=783117 so I will see if I can get it working
update 2:
i have been able to build cifs.o (no cifs.ko was produced ) from the kernel provided by HTC, but it fails with insmod. The problem might be (besides that I have only a vague idea what am I doing) that the downloaded kernel is 2.6.32-g5ed1769 and my phone is running kernel 2.6.32-gbe90714.
Also compiling the kernel ends with this error
make[3]: *** No rule to make target `drivers/input/touchscreen/ntrig.o', needed by `drivers/input/touchscreen/built-in.o'. Stop.
Thats where I got stuck.
I have attached the file cifs.o produced.
Updare 3: Solved - see attachment in post http://forum.xda-developers.com/showthread.php?p=8865419#post8865419

Support/Troubleshooting forum sub section is needed, this Desire HD general is becoming a Desire HD trashcan..

M_T_M said:
Moved to general. Not a DEV thread.
Cheers,
Click to expand...
Click to collapse
I placed in DEV since it deals with kernel compilation. Maybe it should be moved to theme and apps as I am trying to get Cifsmanager app working on DHD.

Small update: I have managed to get a cifs.ko from kernel 2.6.32.17 from G2 partially working. I have HEX edited the file and changed to my kernel version.
I can insmod the file and mount drive without a problem. I can than access the mounted drives a browse the folders, but when I try to open the file I get an error.
I do not seem to be able to find a 2.6.32.21 kernel compiled cifs.ko which I believe might work with HEX updating "-gbe90714".

*push*
looking for the right cifs.ko as well :\ would be really nice to be able to mount cifs shares without custom rom...

anyone got CIFS working on stock ROM?

CIFS working on 2.6.32.21-gf3f553d
here is a working cifs.ko for DHD kernel 2.6.32.21-gf3f553d
Code:
su
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Works fine on my DHD (samba access and video playback with V Player).

nxtwrld said:
here is a working cifs.ko for DHD kernel 2.6.32.21-gf3f553d
Code:
su
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Works fine on my DHD (samba access and video playback with V Player).
Click to expand...
Click to collapse
Thanks for this, it works fine when I insmodded all the .ko's you zipped (that I placed in system/lib/modules/). On reboot though I cannot use cifs manager unless I insmod again. Do I need to insmod everytime i reboot?
Sent from my Desire HD

nxtwrld said:
It's a hex edited and --strip-debug cifs to educe file size of the version from MikeMelbourne. http://forum.xda-developers.com/showpost.php?p=9780217&postcount=7
Click to expand...
Click to collapse
I understand the hex edit - would you mind telling me how you did the --strip-debug - I'd like to do the same.
They were compiled on a headless PII 400 MHz running Ubuntu Edgy Eft server.
-Mike-

You just need to have the android ndk, which I supposed you have since you have bee able to compile the kernel. So just run
Code:
/path/to/android-ndk-r4b/build/prebuilt/linux-x86/arm-eabi-4.4.0/bin/arm-eabi-strip --strip-debug /path/to/cifs.ko
you have to modify the path to cifs.ko a and android-ndk-r4b
I have bee trying to compile the kernel my self on kubuntu, but always finished with an error, so I just ended up hexediting other files.
Thanks for your files. I have been waiting for a working samba mount to stream my videos from NAS!!

keemyb said:
Thanks for this, it works fine when I insmodded all the .ko's you zipped (that I placed in system/lib/modules/). On reboot though I cannot use cifs manager unless I insmod again. Do I need to insmod everytime i reboot?
Sent from my Desire HD
Click to expand...
Click to collapse
I am afraid it has to be insmoded every time on boot. You can automate it with Gscript or Tasker apps.

Thanks @Nxtwrld for the strip-debug advice. The HTC kernel never compiled with my phone's config.gz - after each failed compile I would have to edit .config and disable the item responsible for the build failure. I ended up compiling the module by itself.
Sent from my Desire HD using XDA App

Final compile - optimised versions against NDK R5.
Against the new Android NDK R5 I have just compiled:
* tun.ko - 18 KB
* slow-work.ko - 16 KB
* cifs.ko - 269 KB
* nls_utf8.ko - 4 KB
I have also debug stripped them - resulting in a total module size of 304 KB instead of 3.2 MB.
This time I compiled them on Ubuntu 10.10 instead of the ancient Ubuntu 6.10 I had been compiling on.
Again, these are for 2.6.32.21-g66cfb7a - feel free to hex edit them. I have tested both tun & cifs and they work.
Thanks again nxtwrld for the strip-debug advice.

Can you do the same for kernel 2.6.32.21-g3d0aaf ?

here you go.

thank you! Works very good!
nxtwrld said:
here you go.
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App

I've tried for hours so far to understand more about the android and how to install the files inside 2.6.32.21-gf3f553d.zip.
I have the Desire HD with stock Orange rom and that kernel, i literaly have no idea how to install thease moduals onto the phone.
My desire hd is rooted and is S-on I've tried things like Kernel Update Utility and also just trying to simply copy and paste the files into system/lib/modules didnt work since astro didnt let me paste.
If it wasnt nearly 1am and i wasn't trying for the past 3 hours i would have done more reading. I know its something simple im missing, just can't figure out what the process is to installing thease modules is. First Android phone, first day with it as you can probebly tell.
Any help will be apreciated.
Thanks

arielc said:
I've tried for hours so far to understand more about the android and how to install the files inside 2.6.32.21-gf3f553d.zip.
I have the Desire HD with stock Orange rom and that kernel, i literaly have no idea how to install thease moduals onto the phone.
My desire hd is rooted and is S-on I've tried things like Kernel Update Utility and also just trying to simply copy and paste the files into system/lib/modules didnt work since astro didnt let me paste.
Click to expand...
Click to collapse
There's a free app in the market called "mount /system (rw / ro)" that can make your /system read-write (rw) or read-only (ro). After setting rw - you should be able to copy the *.ko files into /system/lib/modules.
Another alternative is to copy the *.ko files onto your sdcard (/mnt/sdcard).
You can then use an app (i.e. "Terminal Emulator") to enter these commands:
Code:
su
insmod /mnt/sdcard/slow-work.ko
insmod /mnt/sdcard/cifs.ko
insmod /mnt/sdcard/nls_utf8.ko
Alternatively, you can open CifsManager, open the Settings and specify a custom path to your kernel modules (i.e. in /mnt/sdcard). The recent version allows you to specify multiple modules, separated by colons. e.g:
Code:
/mnt/sdcard/slow-work.ko:/mnt/sdcard/cifs.ko:/mnt/sdcard/nls_utf8.ko
Hope this helps.

You should also check you kernel version and verify, that you are really running pin this kernel. I have no idea what the kernel for Orange branding is....

Amazing thanks, i did it with the terminal emulator method. First time i tried it, it wouldnt work. A restart later and i've rentered the comands and my computer drive is mounted. Works like a dream, thanks loads for th hex edited files and the walkthrough with diffrent options was so very helpful.

Related

Debian working niceley on Desire.

Debian for Desire.
If you are able to try this on another android device, please do as I will be very interested in the results.
Download
http://www.multiupload.com/79TSI1AAF9
You will need.
-Root access.
-Busybox (included in most custom roms)
-1.4gig free on SDCARD
-VNC Client (ie. AndroidVNC)
-Terminal Emulator (ie. ConnectBot)
-7zip
Instructions
-Extract the file deSIREbian.7z on your PC using 7zip.
-Copy the contents (debian.img and deboot) to root directory of SDCARD.
-On your phone in terminal emulator type
su
sh /sdcard/deboot
Click to expand...
Click to collapse
You should get a blank screen showing "localhost:/#" after a couple of seconds.
-On your phone in your VNC client log in using these details
Password - password
Port - 5901
Click to expand...
Click to collapse
Nickname and Address are not needed, call it what you want though.
Changing the colour to 24bit and enabling local mouse pointer and full screen bit map are not neccesary but reccomended.
-Thats it.
Notes.
-You can log in via ssh, (gives a much better terminal, ie works properly with aptitude). Use [email protected] and password "toor"
-The version of Debian is Armel Lenny, installed using debootstrap.
-It is just the base package with LXDE on top, you only get a desktop, a file browser, an internet browser, and a pic viewer.
-If you want more packages there's tonnes of room on the image. eg apt-get install openoffice.org or apt-get install abiword or apt-get install any flipping thing u want
-You can access the SDCARD from Debian at "root/sdcard" (read-write)
-You can access Debian filesystem from Android (When Debian is running) at "sdcard/debian" (read only)
-debian.img is mounted at "sdcard/debian" using "dev/block/loop5"
-So far the only rom i have come accross that this dont work with is one of the cyanogen nightlies from last week. apart from that, working on opendesire, cyanogen, defrost, leedroid, official 2.2 with busybox...
Issues.
Debian cannot be shut down. You need to reboot the phone to do this. (You can kill the VNC server with "vncserver -kill :1" there is an icon on the festoons to do this.)
Update log.
deSIREbain.
-First release.
deSIREbain2
Fixed
-Loading a second terminal no longer breaks vnc.
-You no longer need to create the folder debian on sdcard.
Added
-ssh server (login with root and toor)
Removed.
-The image has been downsized from 2 gig to 1.4
Hey,
thank you for your work, i will test it so far and will tell you the results
got this error:
Code:
# su
su
# sh /sdcard/deboot
sh /sdcard/deboot
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or di
rectory
net.ipv4.ip_forward = 1
chroot: can't change root directory to /sdcard/debian: No such file or directory
#
If you have the same problems try out
su
mkdir /sdcard/debian
losetup /dev/block/loop3 /sdcard/debian.img
mount -t ext2 /dev/block/loop3 /sdcard/debian
ls /sdcard/debian
thx to mercianary for help
greetings
I found this guide quite helpful at getting a bootstrapped Debian setup running.
http://www.saurik.com/id/10
I didn't need to insert the ext2 module as it's already loaded for me, I guess G1s didn't have that convenience back then.
blackstoneuser5 said:
I found this guide quite helpful at getting a bootstrapped Debian setup running.
www . saurik.com/id/10
I didn't need to insert the ext2 module as it's already loaded for me, I guess G1s didn't have that convenience back then.
Click to expand...
Click to collapse
I used parts of this for reference too. Its a great guide, explains things really well.
i've just updated this. link is in the first post.
Fixed
-Loading a second terminal no longer breaks vnc.
-You no longer need to create the folder debian on sdcard.
Added
-ssh server (login with root and toor)
Removed.
-The image has been downsized from 2 gig to 1.4
debian for desire--help please
hi
I spent much time for searching debian or ubuntu for desire, but nothin worked
know i found this and i have download everything and start to install over the terminal
but the " sh /sdcard/deboot" is not workin to
there's only this answer:
# su
su
# sh /sdcard/deboot
sh /sdcard/deboot
[: not found
losetup: not found
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
busybox: not found
sysctl: not found
chroot: not found
may somebody help me?
i really want to have it on the desire
thanks
It looks like you had not installed busybox
Which ROM do you use ?
oh i'm sorry
i'm a newbie and don't really know what a rom is
but i had problems with busybox and there was a somebody who said i can get the app titanium and let it install the busybox
could you please show me a tut how to install busybox
maybe a german tut
thanks
Getting error at: sh /sdcard/deboot
line 5: syntax error near unexpected token `else'
Rosi1337 said:
Getting error at: sh /sdcard/deboot
line 5: syntax error near unexpected token `else'
Click to expand...
Click to collapse
dont know why that happened.. works on mine. syntax looks ok to me.
try with this one (attatched), it's the same but without the bit that's not working for you.
what rom are you using, i shall try to replicate the error so I can try to fix properly.
thepuechen said:
could you please show me a tut how to install busybox
maybe a german tut
thanks
Click to expand...
Click to collapse
There should be a guide on installing busybox somewhere if you want to search for it, i know i remember seeing one a while ago.
Too be honest, your better off just flashing a rom that includes busybox, it would be MUCH easier.
have a look here and see what takes your fancy, I would recomend defrost, because it is stable and easy to overclock.
Thanks mercianary,
It works fine!,
I use customised DeFroST_0.9b_uvonly with USB-host patch.
By the way I would like to add more options to kernel line.
Where can I find like a menu.lst file ? or How to add it to kernel line.
There is no /dev/graphics/* in running Debian console.
I would like to use FrameBuffer on running Debian.
thanks,
Android VNC won't connect Trying to get a handshake, but then says that VNC connection failed
please paste at that time log
jacobtc said:
Android VNC won't connect Trying to get a handshake, but then says that VNC connection failed
Click to expand...
Click to collapse
Please paste at that time log.
Maybe vnc server does not running.
tknv said:
Thanks mercianary,
It works fine!,
I use customised DeFroST_0.9b_uvonly with USB-host patch.
By the way I would like to add more options to kernel line.
Where can I find like a menu.lst file ? or How to add it to kernel line.
There is no /dev/graphics/* in running Debian console.
I would like to use FrameBuffer on running Debian.
thanks,
Click to expand...
Click to collapse
You should understand that this is not a really booted native linux. Instead you are working in a chroot environment. So there is no kernel running that can get parameters. Only the the stock kernel of your DeFroST. Also there is no FrameBuffer as the graphic hardware ist not accessible. Instead this approach uses a vnc-server to which you can connect via a local viewer.
The advantage of this approach is clear:
- run almost any linux package available in the debian repository
- use your phone as before with the nice android
The disadvantage:
- no graphic output, so no 3D-games (which are rare under linux on the arm platform ;-)
- you can crash your android by eating up to much ram (not such a problem - it restarts on its own and if not you just have to reboot)
Thread is dead?
It seems this thread is dead. The problems many users seem to have come from a dirty setup. The image is broken in many terms:
- wrong file permissions on important binaries, like su
- wrong file permissions on many device files under /dev, so the ttys are only accessible by root
- wrong permissions on other places so there are always errors when installing additonal software (e.g. with the man pages)
- wrong setup that uses the root user for the desktop - instead an unprivileged user should be used
- missing packages for timezones and locales so the time is only right, if you are in a UTC region and console programs having trouble displaying anything else then plain english
I can not recommend using this setup image. It is better to use one of the instructions available online to get a clean setup.
Su doesn't work because your allready root.
Getting anything but root to work would be a real pain.
As you said its a chroot environment, its never going to be perfect.
The image was made using debootstrap just like all the other 'clean' ones.
Yep, it is broken as hell, but it works for what most people would need it for...make,gcc,python,a proper web browser,torrents, and some emergency word processing on the train to work.
The problem most people have is not being able to mount the image, this is due to fro-yo a2sd taking up all the loop devices.
Just thought I'd add my 2 cents.
I tried this on a MIUI rom and the scripy didnt do anything - ie i ran it using:
"# sh /sdcard/deboot"
.....and all it said was:
"#"
I entered all the lines in the shell script but the last one said it failed to launch VLC and no commands registered property (not even ls)
So i tried it on Defrost 5.1, and the script still didn't work.
But when i entered everything manually, it did work. Not too sure about the green theme though.
But thanks alot! Saves me spending a few hours trying to coax a working debootstrap out of my computer.
Thanks!
Josh.
mercianary said:
Su doesn't work because your allready root.
Click to expand...
Click to collapse
Nope. Actually su works only for root. It's missing the setuid root flag like all other binaries that should have it set.
mercianary said:
Getting anything but root to work would be a real pain.
Click to expand...
Click to collapse
Nope. I am always working as a normal, unprivileged user in my chroot. You just have to be in the proper groups. No need to work as root. Android works also with an unprivileged user.
mercianary said:
As you said its a chroot environment, its never going to be perfect.
The image was made using debootstrap just like all the other 'clean' ones.
Yep, it is broken as hell, but it works for what most people would need it for...make,gcc,python,a proper web browser,torrents, and some emergency word processing on the train to work.
Click to expand...
Click to collapse
This is what I do not understand. There is no need that it is broken, as mine works without any errors. So I think something went wrong in creating yours. For sure a chroot is no running OS but you can server almost any service with it and run anything you want (if your ram does not get exhausted ;-).
mercianary said:
The problem most people have is not being able to mount the image, this is due to fro-yo a2sd taking up all the loop devices.
Click to expand...
Click to collapse
Yes. Everyone with a good rom should have a2sd+ (aka the old a2sd) which saves more space than the froyo one and leaves your loop devices for you.
jo

VPN over android on HD2 ?

I wonder if there is anyone that tried to use any type of VPN over recent android builds for HD2?
Actually the problem resides in a missing kernel module "tun.ko".
I have tried to get the file from the internet to the same kernel and load it using "modprobe tun" or "insmod tun.ko" command but it is always giving me the same error: "modprobe: 'tun.ko' : invalid module format.
If anyone has a working module, that will be great.
hhhawasly said:
I wonder if there is anyone that tried to use any type of VPN over recent android builds for HD2?
Actually the problem resides in a missing kernel module "tun.ko".
I have tried to get the file from the internet to the same kernel and load it using "modprobe tun" or "insmod tun.ko" command but it is always giving me the same error: "modprobe: 'tun.ko' : invalid module format.
If anyone has a working module, that will be great.
Click to expand...
Click to collapse
I will update the kernel to include tunneling
EDIT:
http://git.linuxtogo.org/?p=groups/...it;h=17b1cb194c76267cae097241aea7a9f47ced7283
done.
tun.ko is present in all module autobuilds from today on.
check http://forum.xda-developers.com/showthread.php?t=719646#2 for the official GIT autobuilds
please let me know if it works for you
thanks
dcordes said:
I will update the kernel to include tunneling
EDIT:
http://git.linuxtogo.org/?p=groups/...it;h=17b1cb194c76267cae097241aea7a9f47ced7283
done.
tun.ko is present in all module autobuilds from today on.
check http://forum.xda-developers.com/showthread.php?t=719646#2 for the official GIT autobuilds
please let me know if it works for you
thanks
Click to expand...
Click to collapse
Thank you very much, with this module it should then be possible to have openvpn functionality.
Update: Ok, I am now using latest kernel with tun support.
With this kernel I am able to load the module tun.ko with insmod.
There are no errors and lsmod shows me the module as active.
Where to put an entry to load this module by default on boot?
I have tried the latest kernel build, on SHUBCRAFT CM6 froyo build, the module is loaded successfully and the device /dev/tun is also created successfully.
Thanks a lot.
Anyway I couldn't try the VPN functionality since the Wireless/3G didn't work after kernel upgrade! although I have successfully loaded the wireless modules.
--------
BTW, it didn't work with mattc Leo android build.
After some time of trying my openvpn is running very well with the new kernel and tun module. Thanks once again.
Downy said:
After some time of trying my openvpn is running very well with the new kernel and tun module. Thanks once again.
Click to expand...
Click to collapse
What Andriod build are you using?
Can you please tell us how did you manage to run the WIFI on the new kernel?
hhhawasly said:
What Andriod build are you using?
Can you please tell us how did you manage to run the WIFI on the new kernel?
Click to expand...
Click to collapse
try 1.3. VPN is enabled - not tested.
hhhawasly said:
What Andriod build are you using?
Can you please tell us how did you manage to run the WIFI on the new kernel?
Click to expand...
Click to collapse
I am running mattec release version 1.5 with the most current kernel (zImage) and the most current modules bcm4329.ko and tun.ko extracted from http://oe.netripper.com/files/htcleo_autobuild/modules-htcleo-latest.tgz.
For wifi it is very important to always use the correct bcm4329.ko according to your currently used zImage file.
So when I update a new kernel I also always download the newest modules and extract bcm4329.ko.
To get wifi working, I have extracted the bcm4329.ko out of the modules-htcleo-latest.tgz file and then used adb (I am using ADB Magic GUI to make things easier) to push the file to /system/lib/modules. Changed permissions at the end.
So
step 1:
I boot to wimo and replace zImage in my android folder.
step 2: boot back to android and connect via adb
step 3: extract bcm4329.ko out of modules-htcleo-latest.tgz
step 4: using adb I push this bcm4329.ko file to /system/lib/modules (command: adb push bcm4329.ko /system/lib/modules)
step 5: last but not least I change permissions, but dunno know if its really neccessary. (command: adb shell chmod 777 /system/lib/modules/bcm4329.ko)
Thats it. And thats what I am always doing when I am using a new zImage.
If you have further questions, just ask!
Currently I am running the latest kernel from today, 08/13/10 without any wifi or openvpn problems.
Unfortunatly the kernel module "tun" was not included with the 1.3!
Anyway I have managed now to run the new kernel and the tun module with 1.3.
And OpenVPN and wireless are now working fine.
hhhawasly said:
Unfortunatly the kernel module "tun" was not included with the 1.3!
Anyway I have managed now to run the new kernel and the tun module with 1.3.
And OpenVPN and wireless are now working fine.
Click to expand...
Click to collapse
vpn module is in first post
shu8i said:
vpn module is in first post
Click to expand...
Click to collapse
Oooops
I need a glasses for my eyes
I have tried the ROM and the module and everything was running smoothly.
Thank you all very much
Sorry To Bump This Post Up
But I AM NOt Able To Connect To Vpn PPTp On Any ANdroid Cyanogen Mod
What Should I DO Is There Update Or Solution Or ANything Around ?

.config for android 2.3.3 nexus S

Hi, i am trying to compile tun.ko and cifs.ko for my stock android kernel.
i have trouble getting the .config.gz from the phone as its nolonger available.
can someone share a workable .config.gz with me? i will share the tun.ko and cifs.ko if i am successful in creating it.
this is for stock kernel 2.3.3
i just need a similar .config of 2.3.3 from the custom rom community.
thanks. (i am new to this custom rom and i am trying hard to learn)
Just do a 'make herring_defconfig' and voila!
P
paulobrien said:
Just do a 'make herring_defconfig' and voila!
P
Click to expand...
Click to collapse
hi, i've tried "make msm_defconfig" and make "defconfig", but not working.
will defo try your suggestion.
thanks.
qwerp_ said:
hi, i've tried "make msm_defconfig" and make "defconfig", but not working.
will defo try your suggestion.
thanks.
Click to expand...
Click to collapse
Yeah, you need the herring one.
P
hi, i manage to create tun.ko and working for stock 2.3.3
but however i am still getting error on cifs.ko.
based on my understanding, i am missing out some pre-requisit for the module.
what other settings do i need to add to/remove from .config to make a workable cifs.ko?
thanks.
this is the tun.ko that i manage to complie for stock android 2.3.3 nexus s.
the MD5 of the tun.ko is
e2859858eb1e5d8ab1e69d1d9ffc4594 tun.ko
to whoever who wants it.
similar trouble for me...
trying to compile cifs/nls_utf8 for stock 2.3.3, too
I followed the steps like:
make herring_defconfig
make menuconfig (check cifs & nls_utf8 options)
make modules_prepare
make M=fs/cifs
make M=fs/nls
adb push fs/cifs/cifs.ko ...
adb push fs/nls/nls_utf8.ko ...
adb shell
$su
#insmod cifs.ko
#insmod nls_utf8.ko
and this is what I got....
insmod: init_module 'cifs.ko' failed (Exec format error)
insmod: init_module 'nls_utf8.ko' failed (Exec format error)
really need help. thanks.
p.s.
my environment includes:
. android.git.kernel.org/kernel/samsung.git
. ubuntu-10.10-desktop-i386.iso
. arm-2009q3-67-arm-none-linux-gnueabi-i686-pc-linux-gnu
success finally.
here is the attached file
slow-work.ko
cifs.ko
nls_utf8.ko
the catch is that cifs.ko requires slow-work.ko as a dependency.
so,
insmod slow-work.ko
insmod cifs.ko
insmod nls_utf8.ko
and volia..
thanks for all for the help.
this is for stock android build
2.6.35.7-g1d030a7 only.
wonderful~~ it does works!
could you introduce your operation?
I wanna know how I screwed it up
withinsea said:
wonderful~~ it does works!
could you introduce your operation?
I wanna know how I screwed it up
Click to expand...
Click to collapse
you will need to compile slow-work as module.
i found the guide somewhere on the xda forums under galaxy tab. there is a post where it shows you whats need to be done.
as i say before. cifs is dependent on slow-work.
without slow-work, it will complaint during init that file is not found.

[How to] CIFS after 4.1.83 update

Anybody who wants to get CIFS working after 1.8.3 update (assumes you have cifs.ko and slow-work.ko from 1.5.7)
1) adb
2) su
3) mkdir /lib/modules/2.6.32.9-00007-g527fe10
4) cp <slow-work.ko location>/slow-work.ko /lib/modules/2.6.32.9-00007-g527fe10
5) cp <cifs.ko location>/cifs.ko /lib/modules/2.6.32.9-00007-g527fe10
6) depmod -a
7) modprobe slow-work.ko
8) modprobe cifs.ko
9) reboot
This will load up CIFS automatically after every boot.
-F
I will move this to development when you reach the posts limit so you can have the chance to discuss overthere.
Thanks,
Can you upload these two files
I don't have them from 1.5.7
Thanks much,
Foogl said:
Anybody who wants to get CIFS working after 1.8.3 update (assumes you have cifs.ko and slow-work.ko from 1.5.7)
1) adb
2) su
3) mkdir /lib/modules/2.6.32.9-00007-g527fe10
4) cp <slow-work.ko location>/slow-work.ko /lib/modules/2.6.32.9-00007-g527fe10
5) cp <cifs.ko location>/cifs.ko /lib/modules/2.6.32.9-00007-g527fe10
6) depmod -a
7) modprobe slow-work.ko
8) modprobe cifs.ko
9) reboot
This will load up CIFS automatically after every boot.
-F
Click to expand...
Click to collapse
Anybody who wants to get CIFS working after 1.8.3 update (assumes you have cifs.ko and slow-work.ko from 1.5.7)
Click to expand...
Click to collapse
Can you explain how to get CIFS if we don't have cifs.ko and slow-work.ko from 1.57? Not new to linux, but new to working with android so step-by-steps are apprecaited.
Thanks
ibscum said:
Can you explain how to get CIFS if we don't have cifs.ko and slow-work.ko from 1.57? Not new to linux, but new to working with android so step-by-steps are apprecaited.
Thanks
Click to expand...
Click to collapse
Well, you can build them from the source. But here are some useful ko's build for 1.57
Sorry for the noon question but what is cifs
Sent from my MB860 using XDA Premium App
CIFS ...
... is a network protocol for sharing various thinks (files, printers, ...).
See http://en.wikipedia.org/wiki/Server_Message_Block
You are using in Windows to share folders on network. Linux implementation is called Samba. If you have that capability on your phone, you can mount your home network shares, watch movies directly from your phone without actually copying them on the phone and all sort of good thinks.
It is absolutely essential service, if you want to use your phone more extensively.
Do you know how to get nls_utf8.ko working with cifs?
Insmod nls_utf8.ko says "error inserting 'nls_utf8.ko': -1 Invalid module format
Foogl said:
... is a network protocol for sharing various thinks
Click to expand...
Click to collapse
Grr, hopefully this doesn't cause a double post - having user error even getting a quick reply in...
I followed your directions above but had some issues. When copying the files over, I kept getting 'cannot stat ..." I gave it the full path, it was under the c directory, I even tried placing the files directly under C but no matter what it kept giving the same issue. I then just copied them onto the phone using mass storage method and then did a cp from adb shell to put them in the modules directory. I assume it needed to be copied using the shell as su in order for permissions to work out?
Then I did depmod -a, which worked fine. However, modprobe .. did not. It only retuns FATAL cannot find module etc. I tried giving it the full path to the files with no success. So a google search showed some people saying to try insmod instead. I treid that giving the full path to the files and it didn't return any errors. So I ASSUME it worked?
Not sure why this didn't go as smooth as your instructions. I feel like I hacked my way through it and it's likely gone awry. I wont be able to test this out with CIFS manager until later tonight. Any suggestions on where I went wrong or what I might need to redo?
Thanks!
Well, it worked like a champ. Thanks for the quick how-to and help. Now if I could find an app that will play .iso format movies it would all be perfect...
Update:
Not only does it work, it works great. Had some time to really play with it and I couldn't be happier. No more streaming from PC to phone (except for iso formats) via apps like VLC S&C. Simply browse to the mount which looks just like any other folder on my phone and open and play my media, or open my docs. Quality is excellent, can seek/skip whatever without any hesitation. In short, it acts just as though it's a local folder. I know this is old news to most of you. Just thought I'd share for those who aren't familiar with CIFS. I swear, this connects/mounts to my windows server and plays better than my windows PC.
Just to clarify, for those who my run into the same issues I did.
If it refuses to copy the files from your pc to phone under adb shell, just copy them to your phone via the usual usb mass storage drag/drop method. I placed them in a temp folder. then back to the adb shell, do the cp commands just adjust the path where the files live to the path on your phone (i.e. in the temp dir). I suppose you might be able to just move these into the modules dir using a file explorer w/ root privs but I wanted to be sure the correct file permissions existed by doing it with adb shell as su.
Then if, after doing depmod -a the modprobe doesn't work, use insmod. I gave the full path to where you copy these files in (/lib/modules/2.6.32.9-00007-g527fe10/<filename>). Again, not sure if thats needed or if it's smart enough to scan the full modules hierarchy for the file names.
This doesn't seem to work for me anymore after the GB OTA update. Anyone has it working for them?
norm688 said:
This doesn't seem to work for me anymore after the GB OTA update. Anyone has it working for them?
Click to expand...
Click to collapse
Me either..
Cifs.ko for 4.5.91 would be awesome.
Me either..
Cifs.ko for 4.5.91 would be awesome.
Click to expand...
Click to collapse
Agreed! Any help on getting Cifs running would be greatly appreciated.
Been searching for something and found this:
http://forum.xda-developers.com/showthread.php?t=1113191
Is there any harm in using a cifs.ko intended for a different device? I'm at work now, but might give this a shot when I get home to see if it's functional for Atrix. There's another thread under the development section asking the same question of where we can get a Gingerbread friendly module.
Any direction is appreciated.
theres a bunch of kernels (some included in ROMs) with baked in CIFs support such as the popular faux123's overclock/undervolt kernel.
Flash a kernel via clockwork, no muss no fuss.
theres a bunch of kernels (some included in ROMs) with baked in CIFs support such as the popular faux123's overclock/undervolt kernel.
Flash a kernel via clockwork, no muss no fuss.
Click to expand...
Click to collapse
Hmm. Haven't taken the leap to unlock the BL. Haven't had a need for a custom ROM yet. Really, the only functionality missing for my purposes is this cifs module. I'd rather not have to unlock and bake a custom ROM just for a cifs module if possible.
fair enough. I figure if I'm rooting around system files (pun intended) might as well go the whole hog.
Then again I've run custom ROMs on all 3 droids I've owned so I'm kinda used to the assumption that whatever stock is, I can get it much faster/better
ibscum said:
Is there any harm in using a cifs.ko intended for a different device?
Any direction is appreciated.
Click to expand...
Click to collapse
There shouldn't be... but I'm pretty sure the Module (cifs.ko) needs to be compiled for the specific kernel version. (2.6.32.9-00001-g41bc3e0 [email protected] #2) The Actual Android version (GB 2.3.4) does not matter.
So if you find a cifs.ko for THAT kernel version (or a Kernel thats close enough) it might work. It's trial and error.
There are lots of folks (far smarter than I am), who can grab the kernel source and compile a cifs.ko... I'll have to learn one of these days.
fair enough. I figure if I'm rooting around system files (pun intended) might as well go the whole hog.
Click to expand...
Click to collapse
True. I have the official OTA 2.3.4 update and haven't seen any clear direction on whether I can unlock - looks like most of the information is related to those who unlocked with the leaked update. Granted, I haven't put much time into it since I've been content up until now. Might be time to start digging for info.
So if you find a cifs.ko for THAT kernel version (or a Kernel thats close enough) it might work. It's trial and error.
There are lots of folks (far smarter than I am), who can grab the kernel source and compile a cifs.ko... I'll have to learn one of these days.
Click to expand...
Click to collapse
I believe the module I linked was from a Samsung device so I'm guessing it's a no go. Appreciate the info guys!
wintermute000 said:
theres a bunch of kernels (some included in ROMs) with baked in CIFs support such as the popular faux123's overclock/undervolt kernel.
Flash a kernel via clockwork, no muss no fuss.
Click to expand...
Click to collapse
Took this advice and flashed faux123's kernel.
Not only does cifs work... my data speeds went from 300k average.. to 2mb average.
Thanks for the advice

CIFS Mount on Tablet Z working! (stock 4.1.2 confirmed, 4.2.2 testers wanted)

Hello,
since I have my Tablet Z I was searching for a solution to be able to mount CIFS directories (e.g. from a NAS) on my Tablet Z, since certain media apps (especially music players with own database like GoneMad or Poweramp) only work with local directories.
Unfortunately no dev seems to be interested in compiling the necessary kernel modules or making a custom kernel with the functionality included. And myself I'm no dev.
But today - hooray - I saw this thread http://forum.xda-developers.com/showthread.php?t=2260831 and thought: "There are more programs from other phones, especially the very similar Xperia Z, that work on the Tablet Z, so just let's try!"
I downloaded the package linked in the first post of the thread - the .350 one. (The .423 one didn't work). Then I unpacked it and copied the contents of the folder (some .ko and config files) to /system/lib/modules.
Then I opened a terminal, cd'ed to /system/lib/modules and entered "insmod cifs.ko". Worked!! :good::cyclops:
Next I mounted my network share with the totally normal command (not with the "unc:\\\\"-stuff suggested in the above thread to get it working on the Xperia Z):
Code:
busybox mount -t cifs -o iocharset=utf8,username=xxxxx,password=yyyyy //x.x.x.x/[my share] [mount point]
Voila!
(NFS doesn't work, insmod gives an error.)
But now I can use GoneMad Music Player with my Intenso WiFi Harddisk :good::good::good:
Since I am still on 4.1.2 (with no plan to update to higher versions yet, because for me 4.2 or 4.3 has drawbacks on this device), I don't know whether one of the two module packages from the Xperia Z thread would also work on 4.2.2.
It would be great if someone who has this version running could test it.
Best Wishes,
Hasenbein
Perfect! This was the my last missing function on Tablet Z
Successfully tested on SGP321 (LTE) 10.1.1.A.1.307
Hi,
I have a Sony SG311 over 4.2.2 stock rom. If I copy these files on my tablet, Can i use CIFS manager app to mount directly my NAS share folders ?
Thansk for help
Yes, if it would work on your ROM then of course you could use CIFS manager.
But up to now nobody has got it working on 4.2.2, only on 4.1.2.
It would be great if you could test it by following my instructions. Thanks!
hasenbein1966 said:
Yes, if it would work on your ROM then of course you could use CIFS manager.
But up to now nobody has got it working on 4.2.2, only on 4.1.2.
It would be great if you could test it by following my instructions. Thanks!
Click to expand...
Click to collapse
Hasnt worked for me on 4.2.2
Always get "invalid argument" error whether I do it manually in terminal or using Cifs manager. It wont mount my network drive.
Hope someone has a solution soon.
sneakymise said:
Hasnt worked for me on 4.2.2
Always get "invalid argument" error whether I do it manually in terminal or using Cifs manager. It wont mount my network drive.
Hope someone has a solution soon.
Click to expand...
Click to collapse
Same to me
hasenbein1966 said:
(NFS doesn't work, insmod gives an error.)
Click to expand...
Click to collapse
You can try brute-force loading it via punchmod instead of insmod, that usually works if the module isn't compiled for a completely different device.
Some info here: http://forum.xda-developers.com/showthread.php?p=41920265#post41920265
OK, could you 4.2.2 users try insmod -f first (normal force loading via -f parameter), then look with lsmod whether the module has been loaded, and if it didn't work, try punchmod? That would be great! Thanks!

Categories

Resources