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.
Related
I am trying to get the get-a-robot-vpnc (http://code.google.com/p/get-a-robot-vpnc/) working on my vogue. I am running from nand, using the donut ASOP build.
The first step would be to get tun.ko installed. I downloaded the one included on the google code page and pushed it to /system/lib/modules via adb. When I try to insmod it, i get:
Code:
# pwd
pwd
/system/lib/modules
# insmod tun.ko
insmod tun.ko
insmod: can't insert 'tun.ko': unknown symbol in module or invalid parameter
I am thinking that I need to compile my own tun.ko for vogue. But I am pretty lost. Can anyone suggest any resources to get the kernel cross compiling for vogue set up? A while back when I was hanging out in vogue IRC channel craig0r gave me some good links.. but I have since lost those.
EDIT: found a link for compiling kernel: http://www.androidonhtc.com/get_involved . In the process of doing this now..
EDIT: built a copy of tun.ko that will properly insmod on the vogue. Now the problem is that I can't specify the port through the software! It seems to be assuming 62465. Looks like this is already marked as an issue: http://code.google.com/p/get-a-robot-vpnc/issues/detail?id=34
If anyone wants the tun.ko I built for vogue just PM me.
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 ?
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.
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
Is it possible for someone with Linux experience to compile a cifs kernel module for use with the stock 4.0.3 kernel? I would like to be able to mount smb shares and know nothing of Linux compilation ...obviously I am rooted......and also, why doesn't a business class device come with cifs support? Lenovo...I'm looking at you....
Thanks to anyone who may help our with insight on this issue.
lmbea4 said:
Is it possible for someone with Linux experience to compile a cifs kernel module for use with the stock 4.0.3 kernel? I would like to be able to mount smb shares and know nothing of Linux compilation ...obviously I am rooted......and also, why doesn't a business class device come with cifs support? Lenovo...I'm looking at you....
Thanks to anyone who may help our with insight on this issue.
Click to expand...
Click to collapse
Here it is. Compiled from the official Lenovo ICS sources. Needed to setup my build system anyway.
Edit:
If it doesn't work please post your precise kernel-version (setting->info) with all the characters and numbers and everything.
(exec format error)
I tried the file you made, placed it in the /system/lib/modules directory...Insmod /system/lib/modules/cifs.ko and got the (exec format error) ...am I doing something wrong...and also, thank you so much for helping! Awesome work
2.6.39.4-g9b8008b-dirty
[email protected]#1
lmbea4 said:
I tried the file you made, placed it in the /system/lib/modules directory...Insmod /system/lib/modules/cifs.ko and got the (exec format error) ...am I doing something wrong...and also, thank you so much for helping! Awesome work
2.6.39.4-g9b8008b-dirty
[email protected]#1
Click to expand...
Click to collapse
Next try. If it doesn't work this time please post the last lines of dmesg
yes...but
Yes! the new module loads wonderfully ....now as for getting cifs manager to work,I keep getting "mount: no such file or directory" ...and yes I have the latest busybox, and yes I made the mount point rw...strange....also I noticed that other kernel modules have the cifs.ko and a md4.ko...could the problem lie in not having a md4.ko? Also, you are awesome at this, thank you so much for your continued help!
What I'm trying to accomplish
I'm trying to get the Cifs Manager application to function on my thinkpad tablet. I thought it might help to give out that information so you can see where I'm heading with all of this. Thanks again
lmbea4 said:
I'm trying to get the Cifs Manager application to function on my thinkpad tablet. I thought it might help to give out that information so you can see where I'm heading with all of this. Thanks again
Click to expand...
Click to collapse
A logcat might tell you whats wrong. Try to start searching there, most times its something simple.
Edit: You might be right, a md4.ko seems to be necessary. Will build it as soon as i find out what md4 exactly is.
Edit2: And here it is. Its a crypto module.
awesome!!
That did the trick, cifs manager works great now!! Thank you so much!
lmbea4 said:
That did the trick, cifs manager works great now!! Thank you so much!
Click to expand...
Click to collapse
Hi, could you share your process to mount cifs on thinkpad tablet? I have followed on one tutorial on thinkpadtabletforums. But failed unfortunately. Could you give me a hint? Thanks in advance!
cifs manager
kpf190 said:
Hi, could you share your process to mount cifs on thinkpad tablet? I have followed on one tutorial on thinkpadtabletforums. But failed unfortunately. Could you give me a hint? Thanks in advance!
Click to expand...
Click to collapse
Sure, first download the cifs manager from the play store. (none of this works of you don't have root). then download the two files (in one zip file,2 posts up) and place the two files in the system/lib/modules/ directory. now, open the cifs manager app and go to settings. you need to check the "use insmod" and then in the option below that you need to put /system/lib/modules/cifs.ko:/system/lib/modules/md4.ko that whole thing, no spaces, the : will make it run the second command which is a required modules for the cifs one to work.
good luck
lmbea4 said:
Sure, first download the cifs manager from the play store. (none of this works of you don't have root). then download the two files (in one zip file,2 posts up) and place the two files in the system/lib/modules/ directory. now, open the cifs manager app and go to settings. you need to check the "use insmod" and then in the option below that you need to put /system/lib/modules/cifs.ko:/system/lib/modules/md4.ko that whole thing, no spaces, the : will make it run the second command which is a required modules for the cifs one to work.
good luck
Click to expand...
Click to collapse
Noted and tried but still get msg as "mount: No such device".
I think I have no luck with CIFS...
Thanks Koshu and all. Mounted my NAS shares with no problems.