Related
Hello all. I was wondering whether it'd be possible to put a 2.6.27 kernel into a 2.1 rom so that it can be made faster for the time being.
For now, i can boot up the image using
fastboot boot zImage
but i want it to be the default kernel it boots not the .29 one. Whenever i try to flash the 2.6.27 kernel from recovery mode, the phone will refuse to start up. Is there any way around this?
Yes I have the 2.6.27 working on the 2.1 ROM. (With Brain **** Scheduler Patches)
How?
10char
Compile your 2.6.27 kernel, create the required libs. unpack boot.img mv zImage as your new kernel repack it and boot.
This post has helped me a lot!
http://forum.xda-developers.com/showthread.php?t=551711
what do you mean by create the required libs? I already have a zImage file.
And the wlan.ko (loadable module)?
Did you compile this with most of it static in the kernel?
i have that as a seperate file which i'll push to the system after i flash the kernel
Well then go ahead
The last couple of hours I've been frantically trying to cook together a working ROM.
So far, this is what i've done:
*Replacing 2.6.33 kernel with Paul's "Custom Kernel" which is 2.6.29.
*Replacing&editing init scripts
Especially with the init scripts, my question is, are these the main parts of concern regarding a port?
In other words, am i on the right track, or is this much harder than i think? :S
Btw i don't think i'll get done with this before a ROM gets released, its just for interests sake
I thought the main problem was Froyo needing a 2.6.33 kernel and having to port Desire specific code into a 2.6.33 kernel so replacing it with 2.6.29 wouldn't work
Se the other froyo thread, I posted some quick instructions on how to boot a semi-working rom. There's no service and graphics are glitchy, also no wifi but that is just a matter of copying the right module, I didn't bother doing that.
There should be no dependency on a specific kernel version, but 2.6.33 is faster. I have also been trying to port cyanogen's 2.6.33 kernel but it's not as easy as it seems, there are many caveats and it did not boot yet.
deovferreira said:
Se the other froyo thread, I posted some quick instructions on how to boot a semi-working rom. There's no service and graphics are glitchy, also no wifi but that is just a matter of copying the right module, I didn't bother doing that.
There should be no dependency on a specific kernel version, but 2.6.33 is faster. I have also been trying to port cyanogen's 2.6.33 kernel but it's not as easy as it seems, there are many caveats and it did not boot yet.
Click to expand...
Click to collapse
Could the fact that MoDaCo's boot.img from rootedupdate.zip works, be related to it having an extra stage attached besides kernel and ramdisk?
I tried unpacking & repacking the boot.img you mention. And it doesn't boot
deovferreira said:
Se the other froyo thread, I posted some quick instructions on how to boot a semi-working rom. There's no service and graphics are glitchy, also no wifi but that is just a matter of copying the right module, I didn't bother doing that.
There should be no dependency on a specific kernel version, but 2.6.33 is faster. I have also been trying to port cyanogen's 2.6.33 kernel but it's not as easy as it seems, there are many caveats and it did not boot yet.
Click to expand...
Click to collapse
Could you post a link to this kernel?
I have managed to make it boot other kernels, by writing my own boot.img packing scripts.
edit: uploaded wrong file -_-
froyo kernel is 2.6.32
i'm almost sure this is the source code http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
cyanogen have also used 2.6.34
Kali- said:
froyo kernel is 2.6.32
i'm almost sure this is the source code http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
cyanogen have also used 2.6.34
Click to expand...
Click to collapse
Thanks for the link.
So, as the Desire source code is available, it's mainly a matter of porting kernel code? What about RIL and "acoustic" libraries htc ? hmm.... When i booted Froyo with r1.1 MCR custom kernel, 3G/EDGE and calling worked fine. There was graphic glitches though. Framebuffer port?
gr0gmint said:
Thanks for the link.
Click to expand...
Click to collapse
i made a mistake,
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
this is "probably" the right kernel (with few patch to bcm 4329 wifi) i have just compared to the nexus config.gz (2.6.32.9, CFQ Scheduler ...)
sorry but there is no froyo tag in the git
Dear all,
Did anyone succeed extracting kernel configuration from I9000XXJP3? Kernel version is 2.6.32.9, the vermagic is "2.6.32.9 mod_unload ARMv7"
extract-ikconfig doesn't work on it.
I succeeded extracting a zImage gzipped payload, but it seems not to contain any configuration in it (see attached).
/proc/config.gz doesn't exist, Samsung open source package (downloaded from Samsung open source site) contains only Android 2.1 Eclair or previous versions.
My target is to build tun.ko and, eventually, ext3/ext4 modules to make them working in Samsung Galaxy S I9000 with rooted I9000XXJP3.
Any idea?
Without froyo source code or a good Samsung Kernel (es. for himem capable) I think is impossible to play good with theses beta roms.
Ciao
Any news? I need tun.ko for jp3 too..
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
redsh said:
I have tried to compile the 2.6.32.9 kernel editing the .config in 2.6.9, the module tun.ko is accepted by the device, but I get a kernel panic!
Click to expand...
Click to collapse
Did you use the stock linux kernel? Or the common from android.kernel.org?
I'm trying the same thing actually. Isn't there any default config for the processor that might work? I tried with the config from .29 but when loading the module it says wrong format.
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
bilboa1 said:
try to build 2.6.32 with the 2.6.29 config ("yes" all missing stuff)
turn on your galaxy, adb push the tun.ko
try to load it, it will say "missing symbols" blabla
find the config options that match those symbols, enable them, recompile, try again
Click to expand...
Click to collapse
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
miki4242 said:
Great to see some people who are hacking the kernel! Keep it up!
But I'm afraid it is not going to be as easy as dropping aries_rev03_defconfig as .config in a 2.6.32 kernel tree and doing 'make oldconfig'. That's because many of Samsung's changes have not been included in the newer mainline kernel versions yet.
Samsung added quite a lot of low-level board support for their dev boards (and for the SGS, of course), did some customization and added a few drivers which you will need to forward-port to the newer kernel.
Please have a look at this thread, in which I've started a breakdown of the Samsung patches against Android Eclair's 2.6.29 kernel.
The best course of action I think is to git clone Android's kernel from AOSP, checkout the android-2.6.29 branch, apply Samsung's patches to that, then attempt to rebase your tree to a newer kernel version. (Note, you may want to start with small steps, to get a feel for what you're up against )
Note that there probably will be lots of merge conflicts which you need to resolve, and after dealing with all those, you also have to make sure that everything else that's merged still works as expected, but at least that will show you the amount of work involved. You will basically be doing all the work that Samsung is doing right now for their kernel for FroYo. It will be interesting to follow their progress on the mailing lists and on IRC.
Click to expand...
Click to collapse
Yes that would be a lot of work. Maybe its better to just wait until they release the kernel from froyo. I read that they release their opensource stuff rather fast. But just for adding a module like ext4 I don't think you need those patches, because imho they didn't touch the fs of the kernel. We just need an adaquate kernel config and adding modules should be possible.
Phlogiston said:
Thats exactly what I did, but I got wrong module format... which is a fatal error. I need to invest further in the used config... maybe i did not pick up the right one properly..
Click to expand...
Click to collapse
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Yes i've set the subversion as well but without the patches from samsung its impossible it seems. We need to wait and hope that they release the froyo kernel sources soon....
bilboa1 said:
Make sure you're using the same kernel version number and build number, because samsung kernels do not have the option to load incorrect module versions
Click to expand...
Click to collapse
Are you sure they set CONFIG_MODVERSIONS? It's off in the downloadable sources.
Just compare the output of `modinfo -F vermagic <yourmodule>` to `modinfo -F vermagic <modulewhichloads>` or to /proc/version .
did this get solved yet? I google'd for the tun.ko file for my i9000 using jp3 but nothing yet... if you have a proper one for the MoDaCo version here please attach it! ~
I think I saw someone's post with tun.ko for FroYo beta somewhere in these forums, I mean i9000 Android Dev. One of the guys here has found a way to compile kernel for jp* here. I am sure.
I actually found it attached somewhere in the forum and it was 1,5447 mb big I think it was... but it still didn't work for me so I presumed the kernel or something must have been wrong.
Dear all,
I ask around in the past days if anyone was doing it, but no luck, I even try to look myself if it was easy to do starting from CM kernel, but then, looking better on sourceforge.net the androidhtc project... in the git repo I've seen the htc-vogue-2.6.32 branch!!! Obviously started by dzo.
To get it I've done:
mkdir androidhtc
cd androidhtc
git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/kernel
cd kernel
git checkout -b htc-vogue-2.6.32 origin/htc-vogue-2.6.32
Click to expand...
Click to collapse
Than to configure and compile it (I have a crossdev environment)
cp arch/arm/configs/vogue_defconfig .config
make ARCH=arm menuconfig
# need to be adjusted the config...
make ARCH=arm -j3 CROSS_COMPILE=arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Or you can take the nbh in DZO site and edit with NBH editor.
Everything is working right now:
wifi http://forum.xda-developers.com/showpost.php?p=7869029&postcount=5586
GPS, 3g, touch screen, camera, 3d... bluetooth.
In two days I didn't have any trouble.
Can't wait for the new compcache
Original thread on HTC Vogue by DZO
This is GOOD NEWS!!! I bet theres a shed load of work to be done yet though but it'll be good to get things up to date!
WOW.. nice keep your good work Dude..
I'm just newbie, only can hope and waiting
this confused me when i saw it. according to the internet the google foryo release already is .32
blindguyinanorgy said:
this confused me when i saw it. according to the internet the google foryo release already is .32
Click to expand...
Click to collapse
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
This thread is kind of confusing. dzo said in the Fresh Froyo thread that he was pretty busy at the moment and what he meant with that is very likely that he is spending his available time on getting 2.6.32 ready for our devices.
It's very obvious if you keep an eye on the repo: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
The very best thing to do right know is propably to not disturb dzo more than necessary. I'm sure he'll let us know when it's has evolved to a somewhat useable state.
loserskater said:
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
Click to expand...
Click to collapse
You are correct that we are using an older kernal. .25 is from before cupcake, wow.
I guess what I saw on the web was that new devices with froyo are also going to already come with .32
I wonder if there is much difference for any phone
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
new kernal
voyteckst said:
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
Click to expand...
Click to collapse
Used kernel 2.6.32 after using nbheditor, boots fine running fine so far. Shows kernel version 2.6.32.9 in android settings using Fresh Froyo. Taking it to work tomorrow to test it more.
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
handle223 said:
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
From my tests:
- had to reinstall whole system because of force close errors after changing nbh...
- 3g works, camera works, bt probably works (it enables, so probably it works ;-) )
- cannot even enable wifi
- probably location don't work (I wait about 15 minutes without results)
- didn't check gps
for me on pola200 camera doesnt work... bt activates, but wlan as with all devices - not working. feeling pretty smooth with this kernel...
Wifi fix - new 26/08/2010 kernel
dzo said:
I've fixed wifi on the 2.6.32 kernel. Attached is the new module, put it in /system/lib/modules. You'll also need the very latest kernel. I made some very big changes to the sd driver so this could break other things..
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
tiagoclc said:
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
Click to expand...
Click to collapse
Thanks, now wifi can be enabled ;-)
hello all
maybe a stupid Question how can I put the wlan.ko in the lib module
kisses
Rose Red
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
vArrow said:
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
Click to expand...
Click to collapse
No, You don't have to reinstall. You can mount /system partition rw and replace old one wlan.ko in /system/lib/modules/
Use this android update
thx all for your help
kisses
Rose
haret
Did someone try haret already? I've problems with zimage 2.6.32 ...it hangs on startup...can someone drop here the haret.exe, initrd and default.txt ?
Hugs
Hello
Someone can post
alecuba16 said:
Hello
Someone can post
Click to expand...
Click to collapse
LOL someone can Google?
Someone can sniff around the forums?
Kind of lazy don't you think?
syntax1993 said:
LOL someone can Google?
Someone can sniff around the forums?
Kind of lazy don't you think?
Click to expand...
Click to collapse
There are a lots old posts telling about the latest but isn't.
This is why i'm asking
You should probably check out the Kaiser Kernel Thread around page 9 or 10 for the latest kernel being worked on by clemysn.
Also check out the Gingerbones build of android. It is Android 2.2.1 (Froyo) just so you're aware. In my opinion it's the most stable of them all, but extremely stripped down.
As far zImage and Panel... zImage is if you're using Haret to run Android, the link above I mentioned is if you're installing on NAND. Panel, well you'll need to use aTools to configure your kernel for your device (Kaiser, Vogue, Polaris), but Panel 2 seems to be the most common type (I actually have panel type 3, so I have to use that)
There is a latest zImage kernel by l1q1d you can try, it's under the same thread on the first page first post.
Many thanks!!!
EDIT:
I'm using the clemsy's modified kernel(prevents reboots page 15 from kernel's thread)
-Wifi works on all froyo's (scoots,barebones,super froyo,best froyo)+donut from myn's
-Flashed radio 1.65.24.36
-I modified the kernel nbh to run @490mhz and 2160mha on advanced settings
-latest initrd and zImage-2.6.32-froyo-09-10-10_23 that i founded until yesterday for haret users.
I uploaded there if someone wants the clompletely flashing pack (haret and NAND)
http://www.megaupload.com/?d=0GPGOZRJ
alecuba16 said:
Many thanks!!!
EDIT:
I'm using the clemsy's modified kernel(prevents reboots page 15 from kernel's thread)
-Wifi works on all froyo's (scoots,barebones,super froyo,best froyo)+donut from myn's
-Flashed radio 1.65.24.36
-I modified the kernel nbh to run @490mhz and 2160mha on advanced settings
-latest initrd and zImage-2.6.32-froyo-09-10-10_23 that i founded until yesterday for haret users.
I uploaded there if someone wants the clompletely flashing pack (haret and NAND)
http://www.megaupload.com/?d=0GPGOZRJ
Click to expand...
Click to collapse
thanks man thats of great use for a lot of ppl...
alecuba16 said:
Many thanks!!!
EDIT:
I'm using the clemsy's modified kernel(prevents reboots page 15 from kernel's thread)
-Wifi works on all froyo's (scoots,barebones,super froyo,best froyo)+donut from myn's
-Flashed radio 1.65.24.36
-I modified the kernel nbh to run @490mhz and 2160mha on advanced settings
-latest initrd and zImage-2.6.32-froyo-09-10-10_23 that i founded until yesterday for haret users.
I uploaded there if someone wants the clompletely flashing pack (haret and NAND)
http://www.megaupload.com/?d=0GPGOZRJ
Click to expand...
Click to collapse
think you man
thinks again for your upload
& thinx for ur help
excuse my bad english