This thread is now obsolete.
Kernel sources for build 5.26.0 have been released:
https://opensource.motorola.com/sf/go/projects.milestone/frs.milestone_source_froyo
I've pushed some new pre-compiled modules to github, though beware, I haven't had time to test all of them on device yet:
https://github.com/nadlabak/android...mmit/b300803348705d3fc5ce76d8c88d57186748a370
As the kernel sources are not yet available from the Motorola's open source project, here is an outline how I compiled the overclock and cpufreq governor modules. (Btw., the overclock module needed a substantial adaptation, see the source here: http://android.doshaska.net/2.6.32oc )
I'm using the sources from this AOSP repo:
Code:
git clone git://android.git.kernel.org/kernel/omap.git
git checkout --track -b android-omap-2.6.32 origin/android-omap-2.6.32
Use the sholes config:
Code:
make sholes_defconfig
flags that need to be disabled:
CONFIG_LOCALVERSION_AUTO
CONFIG_MODVERSIONS
CONFIG_DEBUG_MUTEXES
CONFIG_SCHEDSTATS
CONFIG_SCHED_DEBUG
[updated on 17.01.2011, thanks go to Skrilax_CZ]
At least the ext2 will work without panics when compiled using this config.
For tun, cifs and nfs there is still some additional config mismatch that prevents the modules to work without null pointer dereference oops.
Also, even when no custom kernel module is used, you can get the kernel panic very easily, try to enable wifi and do:
Code:
cat /proc/kallsyms
If you're interested in a more detailed android kernel compilation guide, you can e.g. roughly follow this Droid kernel guide: http://www.droidforums.net/forum/rescue-squad-guides/31452-how-compile-your-own-kernel.html
Thanks for starting this thread kabaldan! It is a great starting point in tackling the issue of adding tun support to the new kernel (tun.ko module). I am not as good as many others in this, but trying won't hurt. Meanwhile if someone else is working on tun support - share experience here!
If kernel seems to be ok, sometimes mounting with new version of busybox won't work.
I used to get kernel panic when use newer version of busybox (not Android kernel but my own embedded linux)
Hey Nadlabak can you add DLNA function of CM6?
same problem using droidx kernel sources. insmod ok, mount reboots the phone
yantz
I tried droid2 kernel module - doesn't work either
I noticed OpenVPN included in CM6 also relies on this kernel module. Hence doesn't work. I guess we won't (ever) see kernel sources for that leaked kernel we are now using. I assume Motorola will release the sources sooner or later, but not before official Froyo layout. The waiting is killing me! kabaldan, can't you try to do some magic as you did with the overclock module? The beer is from me!!!
Can you test this attached tun.ko?
Insmod is OK, but I currently don't have time for any further tests...
EDIT: don't bother, kernel panic as usual
Module loads fine, but when attempt to use it, phone reboots, just like with the module compiled from DroidX sources..
leobg said:
Module loads fine, but when attempt to use it, phone reboots, just like with the module compiled from DroidX sources..
Click to expand...
Click to collapse
So, I got it loaded - insmod works just great, just like it did on the 2.1 kernel.
I'm trying to use the CM6 built-in OVPN settings, but I can't find any documentation on the setup. How did you get it set up?
I have
/sdcard/openvpn/
cert.crt
ca.crt
config.conf
config.ovpn
pem.key
I realize that config.conf and config.ovpn are the same file- but I use this VPN on windows and on Mac, and I wasn't sure the requirements on Linux.
If I can't find some documentation I'll try downloading the OpenVPN settings app from the market and playing with that.
Also, I don't know if it's true or not, but I heard the Milestone2 source compiled driver could work.
Are you trying the module kabaldan provided? It doesn't seem to work, at least for me. Loads fine, but phone crashes when setting up tun interface. I couldn't get OpenVPN in CM6 0.3 to work so far. I am testing the tun.ko with the cisco vpn package (which worked great on the old kernel with CM6 0.2) vpnc. When I initiate the connection, phone reboots if the attached here tun.ko is used. I also tried with tun.ko compiled from DroidX sources - same thing - phone reboots. I am not sure where did kabaldan take/compile this module from.
Sent from my Milestone using Tapatalk
I was using the same one, I was thinking maybe he could use the info from more than one phone. I'll try get-a-robot or OpenVPN Installer, but I won't hold my breathe. I was just hoping to use the built-in functionality of the ROM.
*edit* Just saw he removed it because it doesn't work yet, oh well.
the kernel doesnt seem to like any other fs not built into it. i've tried several, ext2, ext3, ext4, cifs, jffs, reiserfs etc. all modules would load without a problem but system will reboot during mount. heck i even tried creating logical volume on the partition. volume created fine, but when time to mount, it reboot
i ended up using a 2nd vfat partition for apps2vfat, on top of native froyo move to sd. moved my debian arm there and manually, yes manually, replace many symlinks in libs to copied files
hopefully next froyo release for other regions would provide a different kernel
yantz
hey kabaldan wondering if you've had another chance to look at an updated tun.ko
Finally some breakthrough. The great Skrilax_CZ has made some hard debugging and one very good guess:
CONFIG_DEBUG_MUTEXES must be disabled in the kernel config.
At least the ext2 module compiled this way is working without panics now.
Congrats to Skrilax!
EDIT: Tun nor nfs not tested yet..., cifs unfortunately still not working.
kabaldan said:
Finally some breakthrough. The great Skrilax_CZ has made some hard debugging and one very good guess:
CONFIG_DEBUG_MUTEXES must be disabled in the kernel config.
At least the ext2 module compiled this way is working without panics now.
Congrats to Skrilax!
EDIT: Tun nor nfs not tested yet..., cifs unfortunately still not working.
Click to expand...
Click to collapse
This means that now the app2ext work?
Where are the modules for we test?!
Thanks for the news!
Modules for testing:
ext2 - http://code.google.com/p/cyanogenmod4milestone/issues/detail?id=197#c19
tun - http://code.google.com/p/cyanogenmod4milestone/issues/detail?id=222#c4
Hi sort of a newbie here... So does this mean that data2ext will work?
Sent from my Milestone using XDA App
Hi Nadlabak...maybe you already know.
For the cifs module, how about slow-work is made available as a module.
as is done at this link
http://forum.xda-developers.com/showpost.php?p=9271775&postcount=4
after further testing:
ext2 mounting now works, reading from ext2 partition too, but writing still causes panic
tun causes panic too
Let's hope for a soon kernel source release, as it looks like we won't get much further without it.
edowar: thanks for the link
@kabaldan
Could it be possible to create a swap module for milestone ?
It seems that running kernels does not have this feature yet and i'm not sure motorola to implement it for next 2.2 release so .... well just wondering !
I'm looking for NFS support on my SGT (Network file system, NOT the game...).
Tab has been rooted, running Paul's MoDaCo kernel & rom (amazing BTW), busybox and what not.
At home I'm running Ubuntu workstations and servers and know my way around linux.
However, I can't figure out how to mount my Tab to my NFS shares.
I've tried CIFS manager, ES filemanager and Mount manager, all without success. It seems to me I might be missing the correct modules. So the question is; is NFS supported in the first place? And if so, what am I overlooking?
(and could someone please post in the Modaco Kernel thread, as I don't have permission to post in dev-threads untill I spam at least 10 posts...)
[EDIT 2011-02-01]
Paul has indicated he might include NFS support in R4 of his kernel, no support in R3.
Hi
Editing post as I saw you are already on MoDaco's ROM.
Not sure about NFS but you mentioned Ubuntu..meaning you should have no trouble getting your samba server running.
With samba and MoDaCo custom Kernel you just need to pull down its "kernel modules.zip" It's a separate file containing the cifs.ko module.
Use CIFS manager (download from market) and specify where you extracted the module to (/sdcard/cifs or anywhere you want to place it).
Once cifs manager is able to load the cifs.ko module, you should be able to mount the shares
@bullyfrog Using the smb server and the cifs.ko modules is an alternative indeed, and for the time being a suitable workaround. Thank you for this tip. However, it's not what I was hoping on...
BTW NFS support will be included in next kernel, so hopefully by that time I've figured it out and will post as a Howto...
Hi I looked for sometime for answers but could not find anything relevant.
Looking to get the ftdi VCP drivers to install on Xoom. Which means I either have to compile a kernel or add them as a module. I can not for the life of me find the correct source tree.
I downloaded kernel 2.6.36.3 from google which matches my kernel version.
My kernel version on the tablet is 2.6.36.3-gb899258 .
When I cross compile the module and try to do an insmod its complaining about the magic version is different which leads me to believe that I have the wrong kernel.
Where can I get the right stock kernel?
If i can not find it there is another option to download the config.gz from the device and recompile another version of the kernel with native support for the ftdi drivers.. How do i just install just the kernel on the device? Is it a uImage bzImage and how do I just flash that?
cd
Thanks
edit:
scrap that ...
sorry, not really helpful in your case
I'm assuming you got your source from here? This is the link from the Android website:
git clone https://android.googlesource.com/kernel/tegra.git
If you decide to go the route of compiling another kernel source, the easiest way (and a good way to keep snapshots of various configs) would be to use Koush's AnyKernel to flash the kernel. I don't know anything about what you're trying to do but I hope that helps some.
Yep the code comes from there.....
I finally got it to work , I downloaded the stock kernel from google then when I make the modules I had to modify the Makefile to get it to match the kernel versions.
It seems to work for now...
Thanks for your help
I'm trying to get Ubuntu installed on my phone using the chroot/vnc method. Please don't refer me to the official Ubuntu for Android page.
The issue I'm running into it seems is that the kernel on my ROM (Glorious Overdose with Platypus Egg Kernel) does not support loop device, so I've hit a wall.
If there is a kernel available for our phone which does support loop devices a link would be highly appreciated, since it seems that virtually all of the existing links to ROMS, kernels and mods are 404ing.
This kind of sucks because my last phone, an LG Optimus was able to run Ubuntu, but it was too slow to really be useful. I'd really like to be able to get more out of my new Sidekick.
bump. Seriously, not a single response? Stock kernel doesn't have it. Bali kernel doesn't have it. Platypus Egg Kernel doesn't have it. Any way to incorporate it into the kernel?
This may be the wrong place to ask, but how does one go about building/modding an Android kernel? I've compiled Gingerbread to run on a netbook successfully before and I've modded the regular Linux kernel (added drivers for odd hardware, etc) many times before so it shouldn't be that different. Maybe it's time to get into ROM cooking.
Download the source from opensource.samsung.com, extract the ramdisk from a working kernel, rebuild with whatever changes you want.
As of now, no kernels that are released for the Sidekick include loop support.
Noob-un-2: I took a look again at this, and found that loopback is already enabled, but the mount is an actual binary, rather than being linked from busybox. you should be able to mount an image to a dir through loopback with the following command:
busybox mount -o loop /sdcard/myimage.img /mnt/mount_dir
(assuming that /mnt/mount_dir already exists, if it doesn't, create it).
Hi all
This post will hopefully serve two purposes, one to help me find what Im looking for and the second to help other find similar.
Im looking for an N5 kernel that supports both CIFS and NFS, either built in or in the form of loadable modules. I have so far tried Faux and Franco, latest versions of both. I cant mount CIFS or NFS using the mount command with either of them. Are there any kernels on the N5 that support this properly?
If anyone knows any perhaps we can compile a list here so its clear which kernels support which features, searching high and low and trawling through kernel changelogs to find what I need is becoming quite laborious. Kind of makes me wonder why most kernel devs dont seem to want to publish a comprehensive feature list for their kernels, some do but most unfortunately dont.
Thanks in advance.
From what I can see there are kernels that support cifs - look in /system/lib/modules/ for cifs.ko.
[
I have not yet found a viable nfs module for the stock nexus, nor have I found a way to get the mount command to work.
It looks as if CM based roms may be able to deal with this, though.
Could you compile your own? If you want just to be able to simply transfer files ES File Explorer supports at least CIFS.
Sent from my Nexus 5 using xda app-developers app
Thus far I've found that Faux supports NFS, I'm able to mount directly via the busybox mount command, it just required a slight modification to the syntax. Unfortunately I've still not found any that support CIFS not even one that has the loadable modules for it. And I need these for shell scripts I'm using, which operate independently of apps so the usual file manager apps are of no use.
Sent from my Nexus 5 using Tapatalk
phobox360 said:
Thus far I've found that Faux supports NFS, I'm able to mount directly via the busybox mount command, it just required a slight modification to the syntax.
Click to expand...
Click to collapse
@phobox360 could you please post your command for NFS mount? I installed hammerhead-lp-faux123-024u kernel, tried both 'mount' and 'busybox mount' , with and w/o su, but still not able to mount NFS exports. Thanks in advance.