Kernel newbie here. I've been looking for instructions on how to add netfilter support to the android kernel (2.6.29 in kernel/msm from android.git.kernel.org), but coming up dry. I've asked around before but all I've heard is "you have to add a lot of lines of code" basically saying I need to do copypasta for the netfilter module to get it enabled in the kernel. I read somewhere else that I should use toolchain arm-eabi-4.3.1 and the option to enable netfilter support should be in the kernel's .config and it's just a matter of saying 'Y' to it.
I tried it, but I still couldn't get wifi-tether to work once I had built the kernel and wlan modules.
I haven't much experience in the linux kernel (actually, other than building it, this is the first time I've tried to modify anything, so I'm tackling it head-on), so I need some guidance.
Any experienced linux-heads willing to help?
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!
I would like to compile several different sets of modules for the stock kernel. I can't seem to get a straight answer on this. If I can, can someone point me to a guide that I can use. If I cannot, can someone point out a tutorial on how to run a kernel with kexec? I asked in another thread, but after several months I didn't get an answer. I would appreciate it, and will post all the modules I compile for all to use. Please educate me.
Hello,
I searched through a lot of threads on how to compile CM, also checked CM wiki, but I want to compile AOSP, not CM. I want to compile it and maybe add some little tweaks to it. How do I compile it? I mean the device-specific part - which repositories, where do I put them (device, kernel,...) and so on?
I'm new to this, and also there's a problem with Ubuntu in VirtualBox, I cannot get my Galaxy S recognized via ADB in the virtual machine (Ubuntu). Just VirtualBox fails at connecting. So I want to ask also if there is any way to get proprietary vendor stuff from phone without using the extract-files.sh script? (another repository for this?)
I'm sorry if I'm starting a question that has been discussed before, but I couldn't find a thread about compiling AOSP for the galaxysmtd. I also checked malcho's thread for building unofficial nightlies and I'm lost there. Still don't know how...
Thanks in advance.
Welcome to the first custom kernel for the KitKat Shield.
This thread is for the development and building of the Shield Portable kernel.
This is not intended to download a build, post issues, and return when fixed.
Kernel Source:
https://github.com/StarKissed/starkissed-kernel-roth
Kernel Downloads:
https://goo.im/devs/playground/shieldroth
The kernel can be built using the commands below or the included script.
Code:
make tegra11_android_defconfig -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make tegra114-roth.dtb -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).
[Kernel] Shield Kernel Development
The included ramdisk is for update 98. If you are on 72, this will most likely result in a bootloop. Using the 72 ramdisk will not work with this kernel, as the source is specific to "OTA 5" according to the Nvidia gitweb.
I recently updated the source and changed a few commands that may explain why current source resulted in non-working builds. I will be testing builds soon and then begin modifying the kernel once the core build is verified working.
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
rylen said:
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
Click to expand...
Click to collapse
All the code is there, it just loops. I'm not sure what's going on with it. The shield tablet version works.
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
bakageta said:
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
Click to expand...
Click to collapse
Won't do much good until it boots
True enough, just thought I'd bring it up since it's a fairly easy fix. In the meantime, I threw together a stock kernel with an updated driver to get by. I had one problem after another with the latest official driver, but the good folks at LKML had already put some work in on v4.1.0 several years ago. Using drivers/net/usb/asix.c and usbnet.c from the 3.4.106 source built without problems.
Beginning to think I may have to settle for building against the full source on this one. It boots fine when doing that, but not built alone. The shield tablet builds fine alone, so there's no explanation for it.
you are going to make a new build of your kernel? if you need help with the tests i can help.
YamazakiRobert said:
you are going to make a new build of your kernel? if you need help with the tests i can help.
Click to expand...
Click to collapse
Things are a bit crazy, but once I can get all of the changes fixed up and it'll build clean, I'm going to try to run it over night.
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
bakageta said:
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
Click to expand...
Click to collapse
It shouldn't be related. You may need to check the proprietary drivers. I believe HDMI is one.
Didn't bother to find out what the problem was, it just stuck around because I was doing dirty builds as I tested. Once I got a few other tweaks and had some time, I did a clean build and it resolved itself. Did you manage to get your kernel booting when building it by itself? I'm sure I'm doing something wrong there too, but I've been grudgingly building the entire device, since that at least works reliably.
What is so special about this kernel compared to stock ? goodjob already btw, you're one of the few who actually have a kernel
It's really sad how not much development is going on, it's such a good device there is only like 1 release at the original section :/