[Q] cifs.ko for the Captivate - Captivate Q&A, Help & Troubleshooting

Hello all,
Forgive me if this has been asked/requested before. Is there a version of the cifs.ko module that is compiled for any of the current custom ROMs? I am looking for this file or would like to know how to compile it for a custom ROM. It is used to mount Windows SMB fie shares to our Captivate. I am currently using Cog's 2.2 Beta 9 ROM but it does not have the cifs.ko file.
Programs such as File Expert or Cifsmanager can handle the mounting once the cifs.ko file is present.
Any help would be appreciated,
Thanks in advance for any advice or direction to solving this issue.

I think not only cifs.ko. For double bytes characters support, nls_utf8.ko is also a must. If anyone can compile based on froyo source, it'll be awesome.

agreed on the double byte char
agreed that second file is required but as a start the cifs.ko is required. Fingers crossed someone can assist us,

Wow! Dead subject I guess
I thought this would be provide some great functionality to our Captivates but I guess it's just the two of us who are interested in such features. The adventure was fun while it lasted.
Juxtyce

http://forum.xda-developers.com/showthread.php?t=774321
peep this guys

I'm using Serendipity 5.12 with the Speedmod K13C kernel, and it definitely includes CIFS. There's an option in CWM to enable/disable it. I've been using it quite a bit with CIFSManager and Mount Manager.

juxtyce said:
Hello all,
Forgive me if this has been asked/requested before. Is there a version of the cifs.ko module that is compiled for any of the current custom ROMs? I am looking for this file or would like to know how to compile it for a custom ROM. It is used to mount Windows SMB fie shares to our Captivate. I am currently using Cog's 2.2 Beta 9 ROM but it does not have the cifs.ko file.
Programs such as File Expert or Cifsmanager can handle the mounting once the cifs.ko file is present.
Any help would be appreciated,
Thanks in advance for any advice or direction to solving this issue.
Click to expand...
Click to collapse
Most newer Speedmod and Voodoo based kernels include support for CIFS natively. In fact, with Speedmod it's simply a tweak enabled via recovery. I don't use Voodoo, so I won't say for certain, but I think it's enabled by default in most of the newer builds.
Also, it's worth mentioning, that cifs.ko, and associated helpers tend to only work correctly on a specific build of Android. So taking the cifs.ko from an older 2.1 version of Android will probably NOT work on any of the newer JPX-range or JSX-range of ROMs.

Shammyh said:
Also, it's worth mentioning, that cifs.ko, and associated helpers tend to only work correctly on a specific build of Android. So taking the cifs.ko from an older 2.1 version of Android will probably NOT work on any of the newer JPX-range or JSX-range of ROMs.
Click to expand...
Click to collapse
Exactly. The kernel module (.ko file) needs to be compiled against the source of the rest of the kernel or it will not load. I highly doubt that you will find a CIFS or TUN (for OpenVPN) module that is compiled against a generic source (JPX, KB1, etc) just floating around here. All of the CIFS and TUN support that I've seen are built in to the kernels themselves. If you want these features it's as simple as flashing SuckerPunch, SpeedMod, Firebird 2, or any other kernel for the Captivate that has that support built in. I use Firebird 2 v0.8.
If you don't want to flash a kernel, you have another route. You need to figure out what kernel source you are running (the version, such as 2.6.32.9, will likely not be good enough - you'll need to know if it's JPX or KB1 or something else), find a Captivate kernel that is based on that version, and either download the kernel and extract the zImage file to get the modules or PM the author and they might be kind enough to give you just the modules that you are looking for. This route is way more work and not guaranteed to work, but Linux is all about choices and that is what makes it fu*king awesome.
Good luck!

Related

[kernel][testing]Unhelpful Kernel (from Captivate)

I'm trying to get the kernel I've been working on for Captivate working on Vibrant. This poses a bit of a problem, because while I have access to a Vibrant kernel and initramfs, and a known-working config for Vibrant, I lack access to a phone.
I've forked a test branch based on what I have so far. I would appreciate pretty much any of the following:
a volunteer to build this kernel or test a binary
a volunteer to help with Vibrant development
any other Vibrant-specific details that don't apply to Captivate or to SGS in general
I have already built a binary, but it is mostly untested. I want to make it very clear that this is a testing kernel. It should work, it should not break anything... but it might not boot, it might wipe data, I haven't heard of it happening to anybody yet but it's certainly not impossible that it might damage hardware. These are unlikely, except for not working, but are all possible outcomes of trying this kernel. If you want to test this, read the OP in the thread for the Captivate version, have backups of your data ready, preferably duplicated to a hard drive or an SD card that is removed before testing. Have Odin3 and a stock Vibrant kernel on hand, and have ClockworkMod recovery installed.
If it hangs starting up, wait a bit, then pull the battery and start in recovery without trying to start up normally. Then, start clockworkmod, mount /system, and use adb to pull /system/user.log - this should contain a log of what happened when the user init scripts ran, and may provide clues as to what went wrong. You can make sure it doesn't include anything you don't want to reveal, and just PM it to me or join #sgs_dev on freenode and talk to me or some other developers there - perhaps a dev with a Vibrant will have a better idea where to start.
In the long term, I would not mind somebody forking the github repository to work on any Vibrant-specific issues. I can then try to pull changes from a fork and do builds for both phones, if somebody doesn't want to do the Vibrant builds themselves.
Good luck, and thank you.
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
ill be more than happy to test the binary
I too will be more than happy to give any sort of help possible. Should this be a start from a stock kernel and build deal, ie stock kernel stock rom just rooted with clockwork?
Sent from my Vibrant using tapatalk pro
If you're using a lagfix with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
EDIT: "lagfix", thx swype.
Unhelpful said:
If you're using a ladies with the playlogos hack you should undo it first, or set up your user init script to run in the new early user init. Other than that anything that works with a stock kernel should still work.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm about to build from your source i just forked to see whats diff then mine. They look though to be about the same except for nilFS
I will probably fork and maintain a vibrant tree with ivan who also has a Vibrant. That way we can get the best of both worlds. And being that we are in the same IRC we pretty much have identical mods to our kernels.
So most likely any changes you make to your captivate Kernel will end up in the vibrant branch as well and I also have the device to test with
See ya in IRC
anomalous3 said:
if no one volunteers by the time I finish installing openSUSE I'll give it a whirl. the binary that is.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
haha if ur talking about the linux distro i know what u mean
Excellent news! I have some things in my tree I think you could use here, too, but it's much easier to have a developer with a Vibrant who can build them and test immediately.
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
rei165 said:
What advantages does the captivate kernal have over the vibrant kernal, if any?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The stock captivate kernel doesn't have any "advantages" and wouldn't really work. Unhelpful, however, has added nilfs support to the captivate kernel as well as some other tweaks, and has now made these changes available to the Vibrant community. As I understand it, NILFS mounts, reads, writes, and unmounts faster on our devices than any of the other filesystems he tested, so there's hope for a permanent lagfix.
I tried this kernel, it does boot but my existing lagfix scripts don't work with it, so I lose all my data. No big deal to fix from recovery, just revert to stock before messing with it if you want to test it. As mentioned, no real advantage either way, but it's nice to have options.
If there is interest, I'll fix my lagfix scripts to run on this kernel. Reverting back to JAC OVv4 works without hassle via clockwork.

Cifs Manager, tool to automount shares. Droid X CIFS.KO??

http://forum.xda-developers.com/showthread.php?t=756158
Is this possible on the Droid X? I linked a thread from the XDA Droid X forum providing a tun.ko (OP created without Moto config file.)
http://forum.xda-developers.com/showthread.php?t=740030&highlight=tun.ko
yeah i'm with you on that, just got a new dx, got rooted, installed cifsmanager just to find that i need a cifs.ko file specially for the droidx..... anyone compile one of those yet? or a different kernal that supports cifs?
greenacratic said:
yeah i'm with you on that, just got a new dx, got rooted, installed cifsmanager just to find that i need a cifs.ko file specially for the droidx..... anyone compile one of those yet? or a different kernal that supports cifs?
Click to expand...
Click to collapse
We cant change the kernel.
I had it working on the fascinate using a cifs_3.ko. I was wondering if a flavor of droid could provide the same results. A cifs.ko that would work with the droid.
I'm using AndroStream Pro, Gmote and andmote(sp?). I cant find something produces the same results. I know the Fascinate is better at handling codecs, but I'm hoping a solution that mounts samba shares might be a good workaround.

[Q] Kernel, Rom, Firmware. Some noob questions

Hi there! I'm new to the forum and to android as well.
As you can guess I'm a proud owner of SGS
Since my SGS sucks a bit (random crashes, reboot, RFS) I'm interested in taking the maximum out of it, and I have some questions.
What is the difference between kernel and a rom? As far as I know from Linux and OS theory, kernel is the layer between the user (applications) and the hardware. I also know that most of the ROMs have kernel in them. Then what else the ROM contains?
What is firmware? Is it used a synonym for kernel/rom?
Is it worth installing custom kernel/rom on SGS? I'm a bit paranoid in those things and have some fears about the issue.
Is there a way to install some good kernel (like speedmod) and naked ROM (not someones mod, i.e. a stock android ROM without any additions from third party developers)? Is it hard to make my own ROM based on stock ROM (without touching the kernel, even tough I looked at the code and read books about the linux kernel, I dont yet consider my self a guru to be able to make my own kernel for android), just the modification and custom applications?
Thanks a lot guys!
Everyone has a kernel - even if you don't mod your phone at all. It wouldn't work without one!
Now, if you flash a ROM, you change the whole system including the kernel. If you flash a kernel, you're only changing the core piece of your system.
Sent from my GT-I9000 using XDA App
A rom is a full firmware .
A kernel is the bit at the base level between processors and OS .Or just as you said .
Is it worth installing custom kernel/rom on SGS? I'm a bit paranoid in those things and have some fears about the issue.
YES but its at your risk though SGS is relatively un brick able .
Simplest upgrade would be via Rom Kitchen and build your own rom .
Choose base rom kernel modem and CSC to suit plus themes and apps .
http://forum.xda-developers.com/showthread.php?t=817703
jje
The kernel in android is essentially just a customized Linux kernel. The ROM is basically the application layer and the framework. Usually ROMs include kernels, but you can flash a different compatible kernel.
Firmware usually refers to either all the basic software on your phone (minus the apps) or the ROM, csc and modem.
You can definetly flash a custom kernel onto a stock ROM, which will improve performance a great deal even without a custom ROM. Find instructions aplenty here on XDA.
Sent from my GT-I9000 using XDA Premium App
Thanks for the replies guys!
YES but its at your risk though SGS is relatively un brick able .
Click to expand...
Click to collapse
By un brick able you mean that its hard to brick it, or if I brick it its hard to un brick (fix) it then?
Also I'm having a hard understanding, if kernel is the thing that manages the hardware and also responsible for lagfix then kernel is really what matters for the performance of the phone. How a ROM could improve phones performance?
Also one more questions:
As I understand CSC and modem are connectivity related files (3G internet, APNS etc) right? So its better not to touch them when flashing custom ROM/kernel?
Thanks a lot again!
JJEgan means it's really hard to get to brick your SGS.
The kernel is responsible for the proper functionality and cooperation between hardware parts. As for SGS, it is a common belief that Samsung's RFS is not as robust or "agile" as ext4 FS. Thus, converting RFS to ext4 should increase device's performance (the time needed for the read/write operations to take place is decreased). BUT, in order for the device to function properly, the kernel MUST support ext4 as a file system format otherwise it won't work anymore (This could happen after installing a stock kernel on a device that uses some filesystem apart from rfs). Samsung's stock kernel does not, so you have to replace it, if that's the case.
(E.g. If you format a USB drive under Windows 7 with "exFAT" as its filesystem, you won't be able to access it through Windows XP for example, because XP does not support "exFAT" - Different kernels & Different OS version ).
Yes, CSC and modem.bin are what makes your device a TELEPHONE, too Connectivity issues between your operator and your handset depend on those files. If you can find the latest COMPATIBLE modem file, then go for it.
Thanks for the explanation!
As for CSC and modem, by compatible you mean the same version (XXJPY for example)? How do I know they are compatible with my phone?
Thanks a lot again!
the CSC doesnt have to match the baseband. for exapmle, you can have XXJPY baseband and XXJQ1 modem. (thats what i used to run)
its all about finding the right modem for your region, you want to make sure you get good connections dont ya ? modems affect SMS, Calls, Data, WIFI, so on.....
so you want the right one. If you go to rom kitchen, you can see all the modems and what region they cover
Thanks!
But is there a way not to touch the CSC/modem when flashing custom kernel/ROM? I'm really afraid to mess with those.
Also could someone refer to this question:
Also I'm having a hard understanding, if kernel is the thing that manages the hardware and also responsible for lagfix then kernel is really what matters for the performance of the phone. How a ROM could improve phones performance?
Click to expand...
Click to collapse
Thanks a lot again, and sorry for a bunch of questions!
So is the pda is the kernel then if you are flasing pda/modem/csc?
Yes, PDA is a kernel
skwo said:
Thanks!
But is there a way not to touch the CSC/modem when flashing custom kernel/ROM? I'm really afraid to mess with those.
Also could someone refer to this question:
Thanks a lot again, and sorry for a bunch of questions!
Click to expand...
Click to collapse
Think of the kernel as the drivers and the ROM as the OS. If your drivers are from 1987, windows 7 wont run well, if at all. However, you can have the newest 2011 drivers installed on Windows 95....same thing. Kernel and ROM must be well suited and work together for a good experience.
Sent from my GT-I9000 using xda premium
X-GoD said:
So is the pda is the kernel then if you are flasing pda/modem/csc?
Click to expand...
Click to collapse
Actually if you are flashing a three file firmware with odin, PDA is the ROM, which in this case usually includes a kernel.
If you are flashing a kernel alone onto an already installed ROM, then the kernel is put in the PDA field.
Sent from my GT-I9000 using xda premium
Gingerbread needs a different kernel than Froyo, right?
every firmwarerelease (JVQ, JVP, JVR, JVS, etc..) has its own kernel version.
but with talondev im not sure, cuz there is no distinction between the kernel versions.
with all other custom kernel releases you have specific kernel versions.
yep 10 charrrrr
Terranigmus said:
Gingerbread needs a different kernel than Froyo, right?
Click to expand...
Click to collapse
Yes, be sure to read the kernel's thread to check the version it is made for.
Sent from my GT-I9000 using xda premium
thehackman said:
every firmwarerelease (JVQ, JVP, JVR, JVS, etc..) has its own kernel version.
but with talondev im not sure, cuz there is no distinction between the kernel versions.
with all other custom kernel releases you have specific kernel versions.
Click to expand...
Click to collapse
Actually most custom kernels can work with any firmware build for the same version, froyo or gb. Some devs may base a kernel on a specific firmware, but they usually work on all.
Sent from my GT-I9000 using xda premium
I found the following link that briefs the options that you are looking for. I know this is an old post but thought posting here would help others as well.
donandroid.com/understanding-odin-a-beginners-guide-on-odin-buttons-checkboxes-629
Thanks,
Uresh
skwo said:
Hi there! I'm new to the forum and to android as well.
As you can guess I'm a proud owner of SGS
Since my SGS sucks a bit (random crashes, reboot, RFS) I'm interested in taking the maximum out of it, and I have some questions.
What is the difference between kernel and a rom? As far as I know from Linux and OS theory, kernel is the layer between the user (applications) and the hardware. I also know that most of the ROMs have kernel in them. Then what else the ROM contains?
What is firmware? Is it used a synonym for kernel/rom?
Is it worth installing custom kernel/rom on SGS? I'm a bit paranoid in those things and have some fears about the issue.
Is there a way to install some good kernel (like speedmod) and naked ROM (not someones mod, i.e. a stock android ROM without any additions from third party developers)? Is it hard to make my own ROM based on stock ROM (without touching the kernel, even tough I looked at the code and read books about the linux kernel, I dont yet consider my self a guru to be able to make my own kernel for android), just the modification and custom applications?
Thanks a lot guys!
Click to expand...
Click to collapse
uresh.kuruhuri said:
I found the following link that briefs the options that you are looking for. I know this is an old post but thought posting here would help others as well.
donandroid.com/understanding-odin-a-beginners-guide-on-odin-buttons-checkboxes-629
Thanks,
Uresh
Click to expand...
Click to collapse
thats quite old link u brought up here..........
Sent from my GT-I9000 using xda app-developers app

OC script or kernel for stock rooted 3.2 on Streak 7?

As the title implies I would like to continue using stock 3.2 ROM but would love a script or kernel that allows me to OC the CPU and GPU. I have seen firsthand all the amazing work that the community of pros here at XDA seem to deploy at regular intervals so I figured this would be an easy one. I wish I was as good at software as I am at hardware. Anyways, thank you in advance for your consideration, your time, and possibly your effort. I used to overclock my Iconia A500 all the time via nofrills and a custom kernel so I'm familiar with overclocking at least.
That doesn't make any sense. You cant have STOCK and CUSTOM at the same time.
In order to have a over-clockable device, you need a custom ROM.
giveen said:
That doesn't make any sense. You cant have STOCK and CUSTOM at the same time.
In order to have a over-clockable device, you need a custom ROM.
Click to expand...
Click to collapse
Just a custom kernal should do.....atleast android phones in my exp, new to the streak so maybe im wrong
if you think it will work, use our custom working in my thread.
I've used several custom kernels to overclock (the most popular one was thor2002's kernel) with the stock ROM on the Acer Iconia running 3.0-3.2. Unless the Streak is very different it should run the stock ROM with a custom kernel as long as the kernel was written for 3.2. The problem I face is that the OC kernel I see was made for froyo and I didnt see a zipped folder with the kernel in that repository so I guess you want me to build it? I'm running windows so I am not familiar with that process. Thor would just list the newer versions as a .zip file, we'd download the zipped folder, go into recovery, seek, flash, reboot, and done.
i was doing the same but i moved to honeystreak its almost identical to stock with a few inporvments and i can say my ds7 is one of the lucky 1.8oc capable ones lol

help with gamepad support and loading xpad.ko

Hi all,
I have a rooted sm-t810 running stock marshmallow kernel 3.10.9.8374498 and I have been trying for a long time to add support for my xbox 360 wireless dongle and controllers.
I read a lot online about it and it seems that I need to load a specific module (xpad.ko) that is not available by default in my kernel.
However I have no idea where to find one that is compiled and compatible with my kernel and I have absolutely zero experience with compiling the kernel and/or the module from source, I wouldn't know where to begin or what to do about it.
From what I understand I should download the source of my kernel in a linux desktop, compile the module in it, copy the compiled module to my decide and run insmod it, but again, I have zero experience in all this.
Could somebody help me by giving me the compiled xpad.ko for my kernel?
If not, could you tell me step by step what should I do it to do it myself assuming im a total ignorant in kernels,modules, their compilation, the specifics about android, and everything around it ?(before yesterday I didn'teven ever rooted my tablet )
Thank you in advance if anybody is willing to help!
Cheers,
Mastro

Categories

Resources