I saw some folks talking about messing with fuse on atrix. Since I already had a kernel build environment set up, I figured I would post these modules as well. Dunno if they will be useful for anyone, but they might save a few hours of time if someone wants to experiment...
Just out of curiosity: isn't this effectively the same as the fuse.ko for 4.1.27/4.1.54 (i.e. for kernel 2.6.32.9)? afaik, there's only been the one kernel released so far....
I'm not trying to shoot you down, just trying to figure out if there's a difference.
Kernel did change in the update
For whatever reason (updated drivers, psneuter exploit fix), they had to bump the version. I expect that since the version magic is different so you need a new binary... I actually didn't try the old ones... I should have... because they do work .
wrldsuksgo2mars said:
For whatever reason (updated drivers, psneuter exploit fix), they had to bump the version. The version magic is different so you need a new binary. Maybe you can force the old one though (which would have the same effect, as I built this with a corrected magic string but using the old kernel sources).
module for stock
vermagic: 2.6.32.9 SMP preempt mod_unload modversions ARMv7
module for 4.1.57
vermagic: 2.6.32.9-00005-gde8e6dc SMP preempt mod_unload modversions ARMv7
Click to expand...
Click to collapse
Yeah, somebody successfully insmod-ed the other module. I did as well, for that matter. But hey, if this'll make it easier to autoload it, that's all that matters!
Related
Hey all,
I am just curious as to if anyone knows whats all involved in porting the 2.6.29 kernel over to Hero. Obviously this is necessary for Android 2.0 and I'm just plain curious how to go about it. I mean, I'm assuming you download the Android source and take the kernel source code and inject it into the Hero source code. Then compile the drivers for use with the new kernel. Now, I may be totally off. That's just what I'm curious about.
Well just be sure to sharpen your Skenuevieator Pen..
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!
look im a n00b(still learning android stuff),
so this question is just out of curosity
why cant we have kernel 2.6.32 ??
well google said froyo needs atleast 2.6.32 to run
but we here are running gingerbread smoothly on 2.6.29(thnaks to all the awsoms devs )
can someone knowledgble reply
thank you ;p
Simply because the kernel drivers needed for the X8 only exist in Linux 2.6.29 as published by Sony Ericsson.
If you would want to use a newer Kernel release (i.e. the ones Google is using for their Android builds) you need to port the drivers to that kernel version - read: make them fit the kernel.
That's a very tedious process, so it's easier for the ROM and Kernel developers to base their work upon the original SEMC Linux 2.6.29 sources.
on short: its easier to port drivers from 2.6.32 or 35 or 38 than make the base 2.6.32.... working on our phone
as b.jay said, porting kernels takes a long time, and if you recive only a couple of errors in the middle of it, BOOM, you gotta go back to the sart and track what wrong command you typed or what code is wrong etc. thats why no one has ported 2.6.32 kernel.
to many drivers to cope with, to much errors that you will recive. porting roms is easyer
thanks guyz for the answers....in short it is possible to have kernel 2.6.32....maybe nAa can port it....he has already backported some stuff.
It is possibe given someone wants to spend an insane amount of time (edit: we're talking several weeks to several months here) in forward-porting the Shakira specific drivers and additions to the ARM Linux code base.
I don't see it happen as it's a enormous undertaking for a single developer to port the whole stuff - that would require a medium-sized team of coders a) knowing what to port / b) well versed in Linux Kernel hacking / c) knowing how to code for ARM (edit: as the existing sources most likely need to be adapted to the Kernel ABI (in this case 2.6.3.x), which is not exactly stable in Linux and changes erratically as Linus' maintainers see fit. Also, don't forget that the changes need to be tested to see if the kernel boots and works flawlessly).
Don't hang your hopes too high.
need to much time to update linux version of kernel
But for instance lg optimus p350 has almost same specs but runs .32 kernel.it has same qualcomm 600 mhz cpu,ardeno 200,and 140 mb ram.so x8 has even better specs.so i dont se why this wouldnt be possible.
Sent from my GT-I5800 using xda premium
Since nobody seems to check the Q&A forum [Q] Kernel compiled in Ubuntu 12.04 fails
So i havent worked on a kernel in a while and decided id start workin on one again. Well I recently updated to 12.04 lts and no changes to my old source I just did a test compile and it wont boot. Same toolchain, source, ramdisk, etc.
Is there some sort of issue with compiling on 12.04?
Even redownloaded the source from my github and tried the toolchain recommended by samsung, stock tool chain, and 3 others and i still get nuthin. Just trying to compile a 2.2 kernel for the vibrant. No source i download works am i missing something?
does ANYONE have any ideas? I dont care who you are just something! I been at this for a freakin week and cant figure it out, ......i've changed nuthing but the OS and i really dont want to have to redo my entire setup because it is such a huge pain
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
trailblazerz11 said:
Are you sure the kernel works? What is causing it to not boot?
I build ICS kernels just fine.
Check this and update tools for 12.04 http://source.android.com/source/initializing.html
Click to expand...
Click to collapse
100% sure it works, its the same source as my old nightly# 3 kernel which i can flash and works fine. Its a 2.2 kernel so thatd be the main diff there, and I've already done the setup of the build environment. I dont get past the vibrant logo so i have no idea what the problem is >.< its driving me nuts
i tried the linaro TC, 2 diff code sourcery, google toolchain even, and no luck
I even started a fresh kernel from scratch and added just the EXT4/voodoo stuff and my ramdisk and still nuthin
so i remade my voodoo ramdisk and that still doesnt work.
I'm out of ideas, I've quadruple checked to make sure all my tools and erthing are installed......idk what the issue is
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
helikido said:
Not a developer but wouldn't downgrading to an older Ubuntu fix the problem? Btw I loved your gingerbread kernels and I hope you can get back to the top again Aim for 400mb ram with 720p and you will achieve something high
Click to expand...
Click to collapse
Id rather not but it seems that might be the case -_- I gotta look into how well older versions of ubuntu suppport the BullDozer cores before i do i guess.....
also I only made GB kernels for the NS4g i think ? o .o Vibrant I had been workin on it but I like being able to have MSAA in my games and what felt like greater stability, so i scrapt the new projects in favor of specific features i use :3
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
hurtz777 said:
Ecotox I really wish you or another dev could make an updated CM7.2 kernel with Voodoo Color, OC/UV, and performance tweaks since Glitch is outdated and probably won't be updated for CM7.2. I know most devs have gone to ICS kernels, but CM 7.2 is still snappier and better for gaming then ICS.
Click to expand...
Click to collapse
I've been gone working on a game project, so I really haven't been doing much android stuff in months. If I get some time I might but can't make promises. Don't take this the wrong way but I'm looking for some help if anyone has any ideas not requests or compliments on previous work (though both are appreciated)
Sent from my Galaxy Nexus using Tapatalk 2
Can you use windows xp to compile kernels?
helikido said:
Can you use windows xp to compile kernels?
Click to expand...
Click to collapse
no
10 char
No but ty for the try....looks like imma have to revert back to 11.10...so let it be known for best results on compiling android use Ubuntu 11. If u have Ubuntu 12 and it works fine then leave it and good for u
Sent from my Nexus S 4G using Tapatalk 2
Hey there! Try downgrading gcc and g++ to version 4.4. If that doesn't work you can always just set up a dev VM in xen or vmware instead of blowing away the whole box. Hope that helps.
And if so, how much longer do you think? Have you seen any hints or rumors plastered on the net? Do you have any links to evidence of 3.10 coming? Are we missing out on anything of importance that 3.10 brings?
Does anyone know why we are still on 3.1, which was released in 2011? I thought Nexus devices got all the good stuff first... Or are only custom roms and kernels using 3.1?
Android devices rarely get new kernel versions anyway since the kernels tend to be customized to work with a specific device, and the binary drivers are built for a specific version of the kernel. This is not as bad as it sounds tho, since a lot of stuff can be backported meaning you get functionality from a newer kernel without the actual kernel version changing. Even more common with custom kernels. For example there's ROMs for our device that uses the F2FS file system which first appeared in the 3.8 kernel and gotten big changes every version after that, and it runs just fine backported to the 3.1 kernel.
hencke said:
Android devices rarely get new kernel versions anyway since the kernels tend to be customized to work with a specific device, and the binary drivers are built for a specific version of the kernel. This is not as bad as it sounds tho, since a lot of stuff can be backported meaning you get functionality from a newer kernel without the actual kernel version changing. Even more common with custom kernels. For example there's ROMs for our device that uses the F2FS file system which first appeared in the 3.8 kernel and gotten big changes every version after that, and it runs just fine backported to the 3.1 kernel.
Click to expand...
Click to collapse
Ok, so this quote here from Linux.com about commits that look like they are made for Nexus 7 2012, is just wishful thinking? I hope not because 3.10 is a massive jump in technology, and possibly even in performance for our device.
there are architecture-specific commits for 3.10 in the kernel/tegra project, which points to development for the 2012 Nexus 7.
Click to expand...
Click to collapse
http://www.linux.com/news/embedded-...roid-will-be-updated-to-the-v310-linux-kernel
EDIT: Ok, I see now, so many new things from 3.4 and 3.8 may already be in our 3.1 custom kernels? If Google releases a 3.10 for the N7 I hope our devs take advantage of it, instead of porting things over to 3.1. I'd like to see our device get Android 5.0 and kernel 3.10, that would really make me feel like this was one of the best investments I have ever made.
As I said, lots of the improvements from newer kernels have already been backported so there wouldn't be as big a difference in performance as you might think. The tegra commits are interesting, but sadly does not confirm anything. For example, the android police article on those same commits mentions that screenshots from the nexus 4 and 5 with the new android version still show them on kernel 3.4. The chance that the 2012 nexus 7 would get a kernel update while the nexus 5 seems awefully slim. I hope I'm wrong tho, since I think it would make things simpler for the custom kernel developers to base stuff on a newer kernel but I wouldn't get my hopes up...
hencke said:
As I said, lots of the improvements from newer kernels have already been backported so there wouldn't be as big a difference in performance as you might think. The tegra commits are interesting, but sadly does not confirm anything. For example, the android police article on those same commits mentions that screenshots from the nexus 4 and 5 with the new android version still show them on kernel 3.4. The chance that the 2012 nexus 7 would get a kernel update while the nexus 5 seems awefully slim. I hope I'm wrong tho, since I think it would make things simpler for the custom kernel developers to base stuff on a newer kernel but I wouldn't get my hopes up...
Click to expand...
Click to collapse
Ok, thanks for making it a little more clearer to me. I kept thinking our 3.1 kernel from 2011 was holding us back from getting one last great update. I think features are no longer needed and I just want them to push performance as far as this thing can be taken. So with ART and F2FS finally coming, I was hoping a better kernel would grace us as well. lol, but it looks like a newer kernel wouldn't do much that the devs haven't already done.
Thanks buddy for jumping in and clearing some of that up for me. :good:
Nvidia released their kernel 3.4.35 for tegra3