Database Develop

Compatible cifs.ko

Can some one compile or point me to a cifs.ko that is compatible with the incredible. The ones I can find do not seem to be. Thanks in advance.

Interesting
http://linux.die.net/man/8/mount.cifs Not that I can help but if anyone wanted a quick reference.

Alot of the roms for other phones have it but its not compatible with out kernel. Is there a guide how to compile kernels? I made a couple in linux that worked. long ago..

here ya go...what app are you using to browse CIFS shares? I haven't tested this module, but just compiled it now.

Forgive me as I haven't actually tried this, but here is the 10,000 foot view:
At a minimum, you will need a linux system, with a gcc-arm cross compiler set up. I believe the android-sdk provides one. The version used by current kernels is gcc-4.4.4.
Then you will need the sources of the kernel you are running. The hydra kernel git tree is here: http://github.com/ejhart/Hydra-kernels.git , and the stock kernel sources are here: http://member.america.htc.com/download/RomCode/Source_and_Binaries/incrediblec_cc1c2268.tar.bz2
The hydra git tree doesn't seem to have a a working .config included, but this isn't so important if you are only building and installing kernel modules. From there, you'll need to configure the kernel in cross compiler mode, add the modules you want, and you will need to make sure the version magic string is identical to the kernel you are using. From there run make, and once the compile is finished, find the .ko 's you want, and push them to the /system/modules folder where you can insmod them.
Edit: You can use the .config from /proc/config.gz, didn't see it in there before.

mattwood2000 said:
here ya go...what app are you using to browse CIFS shares? I haven't tested this module, but just compiled it now.
Click to expand...
Click to collapse
I got one from another user but thanks do you still want me to try it? I mounted my share in a directory on the SDCARD so i can browse it with any file manager. I think any app that scans the sd card will also scan my server with about 8TB so that is a minor issue.

kernel compile guide
A guide for compiling kernels can be found here :
http://code.google.com/p/android-serialport-api/wiki/Htc
I not a techie and a newbie at any android development.
Since the guide is more or less a a set of instructions with no theory.
Got it to run, but not sure what I was doing.
Any assistance in provide either cifs.ko for the HTC Aria w/ kernel version :
liberty-2.6.29-21f066a6 or instructions on how to compile the module would be greatly
appreciated.
BTW - there an app on the store for automating the CIFS mount (CIFSManager
Regards,
-d

veli69 said:
I got one from another user but thanks do you still want me to try it? I mounted my share in a directory on the SDCARD so i can browse it with any file manager. I think any app that scans the sd card will also scan my server with about 8TB so that is a minor issue.
Click to expand...
Click to collapse
Could you please post the cifs.ko file that you have that works. Thanks.

OOMatter said:
Could you please post the cifs.ko file that you have that works.
Click to expand...
Click to collapse
Note that the post you quote was from before the 2.2 OTA, and hence that cifs.ko would be incompatible with the current kernel.

elborak said:
Note that the post you quote was from before the 2.2 OTA, and hence that cifs.ko would be incompatible with the current kernel.
Click to expand...
Click to collapse
Thanks for pointing that out. So does anyone have a compatible cifs.ko for the current DINC kernel?

OOMatter said:
Thanks for pointing that out. So does anyone have a compatible cifs.ko for the current DINC kernel?
Click to expand...
Click to collapse
I do. Check my blog. http://adrynalyne.us
Sent from my ADR6300 using XDA App

veli69 said:
Alot of the roms for other phones have it but its not compatible with out kernel. Is there a guide how to compile kernels? I made a couple in linux that worked. long ago..
Click to expand...
Click to collapse
http://marakana.com/forums/android/examples/111.html
GOOOOOOOOOOOOOOOOOOOOOOOOOOOGLE!!!!!!!!! YEAH!

Thats all fine and dandy except our source isn't on any git.
developer.htc.com

philips w732 vermagic '3.0.13 preempt mod_unload armv7' working cifs.ko and md4.ko modules
narod.ru/disk/63766749001.47b679339538b050028c3c7d87506dd2/md4.ko.html
narod.ru/disk/63743140001.693272f3661d5aac547ecc760f04db05/cifs.ko.html

[MODULE] Cifs module for the official kernel of GT-P3113

I have compiled cifs.ko, md4.ko and nls_utf8.ko for the stock android 4.0.3 on GT-P3113
Kernel Version: 3.0.8-378347-user
Build Number: IML74K
These modules are required to use CifsManager (or any other mount managers for cifs/windows shares) for stock android 4.0.3.
To use it with CifsManager, you should enter
Code:
/mnt/sdcard/cifs/md4.ko;insmod /mnt/sdcard/cifs/nls_utf8.ko;insmod /mnt/sdcard/cifs/cifs.ko
to CifsManager -> Settings -> Path to cifs.ko
(Replace paths accordingly to your device)
Kernel source is from http://opensource.samsung.com/
and many thanks to bcanli's thread in Nexus S, who saved me few hours of debugging why cifs.ko is not enough

Excellent work. I was using Cifsmanager on the Kindle Fire and was assuming I would have to find another way on the Samsung.
http://forum.xda-developers.com/showthread.php?t=1397461

very noob question, but what is the functionality of the Cifs modules?
regards
JP

To access network shares as local folders. Gives some flexibility with media players and other apps.
send from the forgotten one (gt-p7100)

thanks, do you know how to enable ad-hoc on galaxy tab 2 7.0?
regards
JP

any chance of this for the offical 4.0.4 version? i've just updated and it does not work for me

I 've switched to CM9/10 builds a long time ago, but if you send me what official 4.0.4 give as output on "uname -a" command in Terminal emulator or "adb shell uname -a" via adb, i can try to rebuild it

im getting uname not found

XaMaB said:
I 've switched to CM9/10 builds a long time ago, but if you send me what official 4.0.4 give as output on "uname -a" command in Terminal emulator or "adb shell uname -a" via adb, i can try to rebuild it
Click to expand...
Click to collapse
the kernel version is 3.1.10
thanks in advance
shaju

XaMaB said:
I 've switched to CM9/10 builds a long time ago, but if you send me what official 4.0.4 give as output on "uname -a" command in Terminal emulator or "adb shell uname -a" via adb, i can try to rebuild it
Click to expand...
Click to collapse
Could you please post the cifs.ko, md4.ko and nls_utf8.ko that you are using in CM9/10?
Greatly appreciated
Thanks

shajvarg said:
the kernel version is 3.1.10
thanks in advance
shaju
Click to expand...
Click to collapse
This is not enough. This is the example what i need as version
Code:
adb shell uname -a
[B]Linux localhost 2.6.32-ics_tytung_HWA_r3.3_JB #4 PREEMPT Thu Aug 23 22:09:50 CST 2012 armv7l GNU/Linux[/B]
meimeifung said:
Could you please post the cifs.ko, md4.ko and nls_utf8.ko that you are using in CM9/10?
Greatly appreciated
Thanks
Click to expand...
Click to collapse
You can find them in system\lib\modules of any nighlty/stable zip of CM9/10

XaMaB said:
This is not enough. This is the example what i need as version
Code:
adb shell uname -a
[B]Linux localhost 2.6.32-ics_tytung_HWA_r3.3_JB #4 PREEMPT Thu Aug 23 22:09:50 CST 2012 armv7l GNU/Linux[/B]
You can find them in system\lib\modules of any nighlty/stable zip of CM9/10
Click to expand...
Click to collapse
Thanks for your answer. I tried cm9 and cm10 nightly build posted in this forum, and I cannot find nls_utf8.ko nor md4.ko while I can find the cifs.ko.
I guess I am out of luck unless I compile from source myself...

meimeifung said:
Thanks for your answer. I tried cm9 and cm10 nightly build posted in this forum, and I cannot find nls_utf8.ko nor md4.ko while I can find the cifs.ko.
I guess I am out of luck unless I compile from source myself...
Click to expand...
Click to collapse
In CM9/10, nls_utf8 and md4 modules already integrated in the kernel.

This stil requiers root*?

Hello,
please can you build it for me. Now, I have a mobistel cynus t1 with:
OS Version: 3.0.13
OS architecture: armv7l
Processor: ARMv7 Processor rev 0 (v7l)
1st CPU type + ABI: armeabi-v7a
I hope this is enough, because I also get: uname not found.
Thank you very much.
Best regards
Georg

Hey dude could you please made the cisf module for my Galaxy Tab 2 3110??
Here the output
3.0.31 - 523998 #1 SMP PREEMPT thu nov 22 22:01:24 KST 2012 armv71 GNU/Linux
I will really appreciate your help!
Thx

pecana said:
Hey dude could you please made the cisf module for my Galaxy Tab 2 3110??
Here the output
3.0.31 - 523998 #1 SMP PREEMPT thu nov 22 22:01:24 KST 2012 armv71 GNU/Linux
I will really appreciate your help!
Thx
Click to expand...
Click to collapse
It was not possible without replacing the entire kernel. Samsung protects the kernel so we could not use our own kernel module.

OP, can you put something like [MODULE] in topic? So we can be more organized

ketut.kumajaya said:
It was not possible without replacing the entire kernel. Samsung protects the kernel so we could not use our own kernel module.
Click to expand...
Click to collapse
I don't care if I need to flash a new kernel If there is a working one let me know and I'll give it a try
I installed cyanogen 10.1 where cisf module is included and it 's working fine, but I cannot find a way to let it working on a Stock /Modded ROM. Any suggestion?

For stock 3.0.31 kernel: http://forum.xda-developers.com/showthread.php?t=2088515&page=2
Replace the entire kernel JB 4.1.1/4.1.2: http://www.mediafire.com/?7an00ezlgxwbkpe

[KERNEL] Building additional modules for JB stock kernels

Some background info:
I'm the author of PPP Widget which is an app that enables mobile data connections on Android devices with USB host capabilities - even if they are WiFi-only.
It turned out that many Android devices have the drivers for 3G sticks already on board, included with the stock kernel. The one large exception are Samsung devices ...
I started to provide the missing drivers as modules (mostly "ppp_async" and "option" which depends on "usb_wwan"). That worked well for some Google devices and also for Samsung devices running ICS, using the source packages from
http://opensource.samsung.com/
In their JB kernels though, Samsung enabled the "MODVERSION" option. Furthermore, compiling the modules with the officially recommended toolchain resulted in a different "module_layout" checksum than in the modules provided in the firmware.
This prevents using any additonal modules on the devices. "insmod" refuses to load these modules.
The only explanation for this problem is that the custom device configuration provided in the source packages does not match the configuration of the device kernel.
This is the case for all GT-P31xx and GT-P51xx models as far as I can tell.
My take is that Samsung is required to provide the correct kernel configuration under the rules of the GPL. Maybe anyone else wants to contact Samsung on this behalf; I already did several times - still waiting for an answer ...

That's the reason why I build everyting from source including the GPU driver and lost exFAT support http://forum.xda-developers.com/showthread.php?t=1859227 and the boot image result http://forum.xda-developers.com/showthread.php?t=1855700 .

ketut.kumajaya said:
That's the reason why I build everyting from source including the GPU driver and lost exFAT support
Click to expand...
Click to collapse
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...

JFDee said:
Unfortunately, replacing the kernel is no option for end users. The modules I provide are going into a folder on the sdcard, and can be "insmod'ed" from there with no problem - once their magic string and the "modversions" are matching the kernel on the device. The latter is the wall I'm hitting ...
Click to expand...
Click to collapse
Thanx alot for such a great development. ...
Adi™
Creator Of Sungsonic™HD

I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.

JFDee said:
I have received a reply from Samsung. They have updated the JB open source package for GT-P3110, GT-P5110 and GT-N7100 (which previously included a config file from 3.0.15 for a kernel version of 3.0.31 !!).
Unfortunately, the modversions of the compiled kernel are still different and incompatible. I have replied with these finding.
Waiting again ...
BTW, the only recent kernel config consistent with the actual device kernel that I have found is for the GT-N8000 (3.0.31). So it is possible to provide a matching configuration.
Click to expand...
Click to collapse
If You will start to work with kernel I'm willing to beta test with my P5110. Only issue for me is that I need to know what 3G dongle to buy (well need it anyway so would prefer an advice from someone who know something about it). I'm living in Poland and Ireland (once here once there) so I can even test LTE modems (well donations here, myself can spend up to ~50€ on 3G one) because in Wroclaw, Poland I heard it's quite good, also I got H+/H on SGSII here. While in Ireland signal is not THAT strong due to fact most of places are quite remote (except Dublin, Galway etc). Hope I can help in either way

This is what I wrote to Samsung concerning the botched configuration file provided with the latest GT-P3110 kernel source:
Thank you for the source code update.
However, I have asked for the kernel configuration that matches exactly the kernel on the GT-P3110.
I have compiled the kernel from the provided update, but the module layout checksum does *not* match the one from the kernel running on my device.
On the device: module_layout 0xb5a27644
From source: module_layout 0x143474f1
I have used the recommended toolchain "CodeSourcery 2010q1" and the unchanged config file provided with the source ("android_espresso_omap4430_r04_user_defconfig").
Please be aware that you are obliged by the GPL to provide the correct config file for the binary kernel that you are distributing.
As a side note: the configuration provided with the kernel source for the GT-N8000 *does* match the kernel on the device, so there is no doubt that it is possible to get the configuration right.
Other Android vendors are just enabling the "embedded" config file in the kernel, so that the correct configuration is simply available on the device as "/proc/config.gz". This is so much less trouble. I suggest that you enable this option for Samsung kernels too.
Regards,
...
Click to expand...
Click to collapse

The GT-N8010 is also in the same situation you describe - config for 3.0.15 and jb stock kernel at 3.0.31, can't build working modules for stock.

davp, there seems to have been some activity at the Samsung open source center after my messages.
I suggest you make yourself heard as well. Use the "Inquiry" button next to the package download link in the table for your device.
To be able to add working modules to the device, the kernel configuration for the source has to be 100% compatible. It does not matter if any closed drivers are missing as we don't want to replace the kernel - but all those general debugging config options should be correct.
BTW, there is a history of similar issues:
http://forum.xda-developers.com/showthread.php?t=1123643

The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).

JFDee said:
The kernel source for the GT-P3110 has been updated once more, and this time they have fixed the configuration.
With the latest JB update we can actually build working modules for the current firmware.
I confirmed this to the Samsung people and reminded them of the other devices in need of this fix: GT-P3100, GT-P5100, GT-P5110, GT-N7100 and probably more (like the GT-N8010).
Click to expand...
Click to collapse
So for now we might get stock kernel which will support 3G modems via USB OTG? How about other kernels such as CM10.1?
I'm looking for good 3G dongle then Any advices?

Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.

FTDI Single Port Serial Driver added.

cifs.ko not working on P3100 JB 4.1.2 (stock rooted)
ketut.kumajaya said:
Additional kernel modules for stock JB P31xx (tested) and P51xx (untested), contains:
- usb_wwan, ppp_async, and option module for PPP Widget
- dns_resolver, md4, and cifs module for cifs/samba filesystem support
- sunrpc, lockd, and nfs module for nfs filesystem support
Kernel config file attached.
Click to expand...
Click to collapse
Hi ketut.kumajaya,
I'm trying to use cifs.ko but i get:
/system/lib/modules # insmod cifs.ko
insmod: can't insert 'cifs.ko': unknown symbol in module or invalid parameter
I have:
/system/lib/modules # uname -a
Linux localhost 3.0.31-1084989 #1 SMP PREEMPT Mon Mar 25 14:53:07 KST 2013 armv7l GNU/Linux
I tried other cirs.ko with same result.
Can you give me some clues of what can I do?
Thank you.

Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.

ketut.kumajaya said:
Try insmod in order:
insmod dns_resolver.ko
insmod md4.ko
insmod cifs.ko
If something goes wrong, see the kernel messages using dmesg.
Click to expand...
Click to collapse
Great!!!
That's the solution.
In my Tab 10.1 4.0.4 I'm loading (different kernel and different modules, of course):
insmod cifs.ko
insmod md4.ko
insmod nls_utf8.ko
So I was not thinking I should use a different order.
Thank you.

[Q] tun.ko for CM11

Hi,
Does anyone have tun.ko compiled for CM11? Specifically, I have the kernel version "2.6.35.7-androidarmv6+mardon" with build number "cm_cooper-userdebug 4.4.4 KTU84Q d5267ea7c2 test-keys" installed.
The tun.ko installer (from the play store) does not seem to have this version (yet).
This would help to make work VPN clients like the built-in IPsec, which now only leads to a reboot when I try to use it.
Thanks a lot for your help!
Matthias

[Q] Trying to compile novafusion's kernel

Hi guys,
I'd like to compile a kernel for my running ROM, which is the latest released by novafusion (cm11.0_janice.nova.20141011.zip).
I bougth an i9070 after seeing st-ericsson released their sources, to later find out not all of them were, but that's fine, I just want to play arround with it.
So I download it's source from their repository (not sure if it is `Samsung_STE_Kernel' or `android_kernel_samsung_ux500', so I got both), and set `ARCH' and `CROSS_COMPILE' on the running terminal.
The first thing I notice is that a `uname' on my device reports this:
Linux localhost 3.0.101-CM-g7da4c21-dirty #1 SMP PREEMPT Sat Oct 11 19:56:11 CEST 2014 armv7l GNU/Linux
While downloaded kernels' `make kernerlversion' throws `3.0.31'. Setting this appart for a moment, I do an `ls arch/arm/configs/', and finally, a `make cyanogenmod_i9070_defconfig'.
Inspecting the generated `.config', I change `CONFIG_INITRAMFS_SOURCE="source/usr/i9070_initramfs.list"' to `CONFIG_INITRAMFS_SOURCE="usr/i9070_initramfs.list"' and notice from within the that file, that I don't have `../../ramdisk.cpio', neither `../../ramdisk-recovery.cpio', but I guess this could be somehow pulled from my device or the original ROM, so I just `touch' them by now.
To make the versions match, in the hope one of these is the same kernel my device is actually running, I comment `CONFIG_LOCALVERSION_AUTO', and set `CONFIG_LOCALVERSION' to `-CM-g7da4c21-dirty' from within `.config'.
From within kernel's top-level `Makefile', I change `SUBLEVEL' to `101'.
Modify `scripts/setlocal' to not output a `+', so the string version matches.
Then type `make oldconfig', and now my version should be the same as the one my phone runs, though I obviously can't do anything with it, unless I'd reverse my running kernel to find out symbol-table entries.
So my questions are:
Why migth be the reason for my kernel having been compiled without `/proc/config.gz' support in fist place? or `Module.symvers' or similar having been made available so users can reproduce it?
Which of both source trees should I compile to replace my phone's kernel?
How can I obtain `ramdisk.cpio' and `ramdidsk-recovery.cpio'? I've been looking at `boot.img' on my ROM, and while I'm still dealing with it on my own (none of the scripts I've found in here or the internet seems to work with it in particular), I couldn't either find the script novafusion uses to pack it from within their repository (either I missed it, or perhaps it's a cyanogenmod tool).
While I've done previous embedded development, not much at the level of kernel, though, but I did post a message asking this on the novafusion's blog-post related to the ROM I'm using. It got silently discarded and not published, I guess because it doesn't actually pertain to there, where one would expect seeing messages and reports about things not working with such ROM version in particular.
So, if somebody could tell me something about, I'd really appreciate.
Regards,

Sync CM11 source adding janice & u8500-common device tree+Samsung_STE_Kernel and build using standard build commands: .build/envsetup.sh && lunch cm_janice-userdebug && make bootimage
Inviato dal mio GT-I9505