Develop Bugs

[REF] cifs.ko for samsung galaxy s [including froyo 2.2]

This is the kernel module for smb/cifs mount.(windows shares)
You need it for example for this: hxxp://forum.xda-developers.com/showthread.php?t=756158
I didn't found a compatible cifs.ko for samsung s anywhere so I had to compile it.
[recommended] cifs.zip - Eclair(2.1)
[recommended] froyo.zip - Froyo(2.2) - cifs.ko & slow-work.ko (insmod slow-work.ko first)
cifs_froyo_slow_work.zip - Froyo(2.2) - cifs & slow_work in one .ko Do NOT use this because its buggy (slow, reboots when rmmod)

could you pls explain what is this for? Experts needn't, but there're lots of newbies hangin aroud here, like me . Thanks

It's a kind of file system like ext2/3/4, for example.
Sent from my GT-I9000 using Tapatalk

This is the kernel module for smb/cifs mount.(windows shares)
You need it for example for this: hxxp://forum.xda-developers.com/showthread.php?t=756158
I didn't found a compatible cifs.ko for samsung s anywhere so I had to compile it.

Awsome. We can now mount samba shares! Freakin awsome
Sent from my Apple Newton 2100

You have my gratitude

Very usefull! thank you!

i'm back, when i'm trying an insmod i have cifs.ko : invalid module format
i use a jm5 samset 1.9f roms.

I use jm5 (mimocam's fix + root) and I've compiled the module from source-code provided by samsung (opensource.samsung.com) using arm-none-eabi-(Sourcery G++ from codesourcery.com). Maybe samset used something else which is incompatible.

ickyboo said:
Sent from my Apple Newton 2100
Click to expand...
Click to collapse
Bwahahahaha

ethanfel said:
i'm back, when i'm trying an insmod i have cifs.ko : invalid module format
i use a jm5 samset 1.9f roms.
Click to expand...
Click to collapse
Setenza said he'll add Cifs in the next SamSet release.

can you make one that is compatible with the Vibrant version? Either stock Vibrant kernel or any working kernel compatible.
Greatly appreciated

I've tried the module, but also get the "invalid module format" message.
However, I'm using JM5 + root using kernel 2.6.29 built on Fri Jul 30 15:12:44 KST 2010 armv71 GNU/Linux
Can you tell us for which kernel you've build this module?

thoriam said:
I've tried the module, but also get the "invalid module format" message.
However, I'm using JM5 + root using kernel 2.6.29 built on Fri Jul 30 15:12:44 KST 2010 armv71 GNU/Linux
Can you tell us for which kernel you've build this module?
Click to expand...
Click to collapse
I've compiled for kernel 2.6.29.2 using samsung's sources
my phone says he has kernel 2.6.29 [email protected] #1
I'm attaching the module compiled with latest toolchain I could find(binutils-2.20.1, gcc-4.5.1,newlib-1.18.0)

ctran81 said:
can you make one that is compatible with the Vibrant version? Either stock Vibrant kernel or any working kernel compatible.
Greatly appreciated
Click to expand...
Click to collapse
No idea if will work bc I don't have a Vibrant.

In the mean time I've also compiled my own version of the cifs.ko module.
I've used the Samsung sources and used the Sourcery G++ Lite 2010q1-188 for ARM EABI toolchain.
I've only enabled cifs in the kernel config and compiled the module.
I've attached the compiled result.

Thanks for your effort. I'm using JM5 +samset1.9f and couldn't get the cifsmanager to work with all 3 of your cif.ko . I've just dont know why the size the last 2 versions are huge compare to the first one? Thanks anyway. Hope you can come up with something.
thoriam said:
In the mean time I've also compiled my own version of the cifs.ko module.
I've used the Samsung sources and used the Sourcery G++ Lite 2010q1-188 for ARM EABI toolchain.
I've only enabled cifs in the kernel config and compiled the module.
I've attached the compiled result.
Click to expand...
Click to collapse

darkbyt3 said:
no idea if will work bc i don't have a vibrant.
Click to expand...
Click to collapse
thank you very much. It's working on my stock vibrant kernel! YOU ROCK SIR! (using attached vibrant.zip)
Now I can stream all my media files!
(I'm vary curious how you did this, if you can point me to some guides that would be awesome, (I can write some C/C++ code))

Works great for me - had been looking around to see if anybody had compiled the CIFS module for the Galaxy S. I started reading up on how to cross compile kernel modules myself but didn't get very far.
Anyway; I have a slight problem. while mounting and browsing from the terminal as root and through adb as non-root work, I can't seem to browse in any mounted folders actually on the device using either the stock 'My Files' or Astro which was what I was aiming to do.
What I do to mount said:
\\\\192.168.0.0\\Directory /sdcard/smbshare -o user=Username,pass=password,uid=1000,gid=1015
Click to expand...
Click to collapse
Without setting the user and group settings I can't browse unprivileged as everything in the share is 'owned' by root.
I also tried using mount -t smbfs //192.168.0.0/Directory /sdcard/smbshare with the same result.
Anybody else having a similar problem? Maybe it's just something obscure about my setup.

thoriam said:
In the mean time I've also compiled my own version of the cifs.ko module.
I've used the Samsung sources and used the Sourcery G++ Lite 2010q1-188 for ARM EABI toolchain.
I've only enabled cifs in the kernel config and compiled the module.
I've attached the compiled result.
Click to expand...
Click to collapse
Sorry for the noob questions:
- Can you please give more details on how to enable cifs in the kernel config?
- Is there a specific plate to copy the cifs.ko module?
- Is there a simple (one-click) way to install this?
- is the module dependent on the kernel version? has to be exactly the same?
- is there a easy way to check if it's working (I'm using cifsmanager and get some error saying cannot access device / folder not found -not sure about the exact message text)
Thanks in advance

[Q] cifs.ko for 2.6.32.21-gd2764ed kernel on DesireZ

Hi,
originally I wanted to post to the
"[KERNEL] Stock Sense 2.6.32.21-gd2764ed [Mod Ramdisk, CPU governors, CIFS, OC]" thread but since i've just signed up I'm not allowed to post there.
I've taken the cifs.ko module from there but when i try to insmod it I get the error Message "insmod: init_module "/system/lib/modules/cifs.ko" failed (No such file or directory"
Im using the stock kernel (2.6.32.21-gd2764ed on my DesireZ (PermRoot and S-off) and want to use "CifsManager" App to mount my shares after I have established my OpenVPN connection to my ubuntu home server. By the way openvpn works fine I just want to mount my shares since DLNA does not work through the VPN tunnel (broadcast problems trough the tunnel)
Is there someone who can provide a working cifs.ko for that kernel or at least some hints how I can get the kernel sources to compile it by myself?
Thanks in advance!

[Q] 'TUN' Support in a CM7 ROM? Kernel?

Hi everyone, I use CM7 roms (keep switching between various flavours, just about to flash CM7 RC3 by kali http://forum.xda-developers.com/showthread.php?t=957336
My question is this. How do I get 'TUN' module support in a CM7 ROM. The reason I (think) I need it is because OpenVPN asks for it. I want to use OpenVPN to connect to my work. I've seen at least 3 kernels which support TUN, but they all work with Sense ROMs.
So, at present stage, would it not be possible for me to get TUN support in a CM7 ROM?
TIA.

Bump...
Anybody? Any other solution to connect to an openvpn server?
Sent from my Desire HD using Tapatalk

Tun Support for Gingerbread on Galaxy Tab
Hi everybody,
i have installed Gingerbread with CF-Root from Chainfire and everything is fine. But i need TUN support in the Kernel or by Module. So it is possible to make this running on that CF-Root-Kernel ?
I have start to build my own Kernel but when i load the zImage the Tab always restart with no funktion... When i load only the Build tun.ko module in then CF-Root-Kernel i got the message from insmod:
insmod: can't insert 'tun.ko': invalid module format
dmesg:
tun: exports duplicate symbol tun_get_socket (owned by kernel)
TAB-DATA:
Mod= GT-P1000
Firmware= 2.3.3
Basisbandversion=P1000XXJPZ
Kernel=2..3.7 [email protected] #2
Buildnumber=Gingerbread.XXJQ1
Hope anybody can help me.
Thanks

Xperis S: cifs support?

Does XS has a cifs.ko in stock rom to use samba shares? If not, as I assume, is there a way to get this module for an rooted XS? Or are there any custom kernels with cifs support, which I can use on a stock rom?

stm999999999 said:
Does XS has a cifs.ko in stock rom to use samba shares? If not, as I assume, is there a way to get this module for an rooted XS? Or are there any custom kernels with cifs support, which I can use on a stock rom?
Click to expand...
Click to collapse
If you gain root access to your XPERIA S(LT26i) you should be fine.
You can then use CIFS Manager and Samba Fileshaing as is your want.
I chose to use RaymanFX' ELiTE V2 Kernel on my XPERIA S in case that is a factor in making CIFS and Samba share operational, but I don't think it's required.
I'm using CIFS and Samba file sharing without any problems, no *.ko downloads required.

CIFSManager is only a manager, it needs cifs support in kernel.
But I will have a closer look at your kernel, at first sight it looks interesting.

I'm am using an SXAS and I've been looking into this, tool.
After some trying with different kernel modules I downloaded the kernel sources from Sony's developer webpage. And then it became very clear:
Theoretically our 6.2.B.0.200 firmware's kernel has integrated cifs support. The kernel config says so.
So I connected with adb and tried to mount via command line and looked at dmesg. It says: "CIFS VFS: Connecting to DFS root not implemented yet". This means: The kernel should be able to handle cifs, but there is a bug. Either it is the mount utility from the busybox I've installed or it is a bug in the kernel. Since our firmware uses a 3.4.0 Linux kernel and due to some googleing, I assume this to be a kernel bug.
You can find some source code patches in the internet. Maybe I'am patient enough to try building my own kernel.
stm999999999 said:
CIFSManager is only a manager, it needs cifs support in kernel.
But I will have a closer look at your kernel, at first sight it looks interesting.
Click to expand...
Click to collapse

mattes13 said:
Maybe I'am patient enough to try building my own kernel.
Click to expand...
Click to collapse
I did build the kernel with the applied patch, but it didn't solve the problem. I guess I have to do some more research within the kernel forums. So no cifs yet.

mattes13 said:
I'm am using an SXAS and I've been looking into this, tool.
After some trying with different kernel modules I downloaded the kernel sources from Sony's developer webpage. And then it became very clear:
Theoretically our 6.2.B.0.200 firmware's kernel has integrated cifs support. The kernel config says so.
So I connected with adb and tried to mount via command line and looked at dmesg. It says: "CIFS VFS: Connecting to DFS root not implemented yet". This means: The kernel should be able to handle cifs, but there is a bug. Either it is the mount utility from the busybox I've installed or it is a bug in the kernel. Since our firmware uses a 3.4.0 Linux kernel and due to some googleing, I assume this to be a kernel bug.
Click to expand...
Click to collapse
Okay, for anybody, who is interested: I have not tried the following using the stock kernel of .200 or .211 since I'm on Forzaferrarileo's JB kernel at the moment. However, after a lot of internet research I found out how to configure the cifs manager app to mount Samba shares again.
Share Path: //<ip>/<share>
Mount Point as you like it
Username as needed
Password as needed
Options: sec=ntlm,iocharset=utf8,unc=\\\\<ip>\\<share>
It appears that the Samba developers changed their mounting syntax. Although the app states to start the share path with the ip, you need the double slash. And although the share path is already defined, they want it again in the options with the unc option. There you need to double all backslashes. If you have spaces in the unc path, use double quotation marks around your path.
Additional info: currently, I'm using busybox version 1.20.2.

Cifs is enabled and the module is built in kernel . Need only right use of cifs manager
Sent from my LT26i using xda app-developers app

Forzaferrarileo said:
Cifs is enabled and the module is built in kernel . Need only right use of cifs manager
Click to expand...
Click to collapse
Forgot to mention that explicitly, thx.

Anyone got CIFS working?????

Hi all
Just wondering if anyone has got Cifs working on their Tab 3 10.1 x86 ??
Think its a 4.2.2 issue not sure
i have latest bin droid kernel (with cifs support i think)
just cant get it to load the cifs.ko file (which might not be compiled for x86)
really not sure and a it stuck
any help would be great

really... no one uses/wants CIFS support.
any help from anyone...pleeeeease