• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Building kernel for kindle fire

Search This thread

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,731
Some interesting notes on the Kernel source posted by Amazon:
The version that was posted is TI's Tag L27.13.1 (Beta) for Gingerbred
You can grab the final release of source from omapzom:
http://omapzoom.org/?p=kernel/omap.git;a=commit;h=f61b5d3f352d07bf950eaf2da549b0e7c2db5e26

I did a comparision between the final L27.13.1 and the beta that Amazon used and sure enough there are VERY little differences.

Once my device comes, I'll poke around the devtree and confirm which devices are in the build. I don't think the source has the defconfig that was used for the KFire.
 

Hashcode

Senior Recognized Developer
Sep 3, 2011
3,426
23,731
just a thought.. may be plan for future ;)

since KF and galaxy nexus share the same chipset OMAP4430 we can try porting the 3.0 kernel for this device...

exiting repos for galaxy nexus:
https://bitbucket.org/paulobrien/android_kernel_galaxynexus/src
https://bitbucket.org/franciscofranco/galaxy-nexus/src

You could instead grab a 3.0 kernel from omapzoom (from which the GNex's was based) and go from there:
http://omapzoom.org/?p=kernel/omap.git;a=summary

You can see all of the 3.0 releasekernels in the tags.

The trick is we would need to establish the defconfig for how the kernel was built originally. And it doesn't look like we've done that.
 

ajq

Senior Member
Nov 22, 2011
59
7
Well, I think I've about given up. I cant get the bloody thing to boot anymore. I can use an insecure ram disk, and now my kindle has a nice black & white pink Floyd logo for about 3 seconds when it boots, but as for the kernel, I'm afraid I'm at wits end.

And my wife is starting to get anoyed at all the time I've been spending in the basement.

Sent from my Kindle Fire using xda premium
 

riverzhou

Senior Member
Dec 2, 2006
203
83
Shanghai
just a thought.. may be plan for future ;)

since KF and galaxy nexus share the same chipset OMAP4430 we can try porting the 3.0 kernel for this device...

exiting repos for galaxy nexus:
https://bitbucket.org/paulobrien/android_kernel_galaxynexus/src
https://bitbucket.org/franciscofranco/galaxy-nexus/src

android omap kernel (3.0.1) :

https://android.googlesource.com/kernel/omap
git clone https://android.googlesource.com/kernel/omap.git
git checkout android-omap-panda-3.0

linaro kernel from ti (3.1.0) :

http://git.linaro.org/gitweb?p=landi....git;a=summary
git clone git://git.linaro.org/landing-teams/leb/ti/kernel.git
git checkout android-release-2011-11-3

They all have SGX 540 driver.

http://forum.xda-developers.com/showthread.php?t=1376509

---------- Post added at 11:49 PM ---------- Previous post was at 11:47 PM ----------

I think the nexus has a 4460 but I might be wrong

Sent from my DROID Pro using XDA App

You are right. It's 4460.
 

randallu

Member
Dec 25, 2010
46
6
Palo Alto, CA
Well, I think I've about given up. I cant get the bloody thing to boot anymore. I can use an insecure ram disk, and now my kindle has a nice black & white pink Floyd logo for about 3 seconds when it boots, but as for the kernel, I'm afraid I'm at wits end.

And my wife is starting to get anoyed at all the time I've been spending in the basement.

Sent from my Kindle Fire using xda premium

So you had a working kernel build, but now you don't? Does it make any visible progress (blinking the LCD when it initializes, etc) or does it just hang?
 

ajq

Senior Member
Nov 22, 2011
59
7
Yeah, LCD blinks, brightens and dims. Some blinking of the led too. Doesn't. Look like it's getting to initrd.
 
  • Like
Reactions: emelie

JackpotClavin

Inactive Recognized Developer
Feb 27, 2011
1,024
3,814
New York
So I'm guessing adb shell is out of the question?

And have you tried powering off completely and taking the cord out, doing a fastboot command so it waits for the device, then plugging it in so it boots and seeing if it command executes?

Sent from my DROID Pro using XDA App
 
Last edited:

randallu

Member
Dec 25, 2010
46
6
Palo Alto, CA
Yeah -- it'd be great if you could post the .config -- my builds don't blink anything...

Maybe we could get the framebuffer console working and see where it's getting stuck, too.
 

intersectRaven

Senior Member
Mar 13, 2010
2,260
1,558
www.intersectraven.net
Hmmm...I think I'm getting close to this...page size is irrelevant...0x80000000 is correct....you need to create boot.img first so that fastboot boot works even without extra arguments (except the -i of course)...no modules in the kernel... :rolleyes:
 

DooMLoRD

Inactive Recognized Developer
Jul 27, 2010
13,191
39,703
Pune
Has anyone checked stock filesystem if there are additional modules loaded (like Samsung devices)... That would explain (partly) the incomplete booting...

Code:
adb shell find /. | grep ko

And

adb shell lsmod

Sent from my R800i using XDA App
 

randallu

Member
Dec 25, 2010
46
6
Palo Alto, CA
Hmmm...I think I'm getting close to this...page size is irrelevant...0x80000000 is correct....you need to create boot.img first so that fastboot boot works even without extra arguments (except the -i of course)...no modules in the kernel... :rolleyes:

Oh. I was always letting fastboot build the boot.img... Perhaps that explains some of my troubles.

Sent from my Nexus S using XDA App
 

intersectRaven

Senior Member
Mar 13, 2010
2,260
1,558
www.intersectraven.net
Has anyone checked stock filesystem if there are additional modules loaded (like Samsung devices)... That would explain (partly) the incomplete booting...

Code:
adb shell find /. | grep ko

And

adb shell lsmod

Sent from my R800i using XDA App

There are only two modules. One is the wireless lan driver (tiwlan_drv.ko) while the other is tiap_drv.ko which seems to be related to the wireless lan driver although I haven't looked at it yet. (more important to build a booting kernel first) :)

Oh. I was always letting fastboot build the boot.img... Perhaps that explains some of my troubles.

Sent from my Nexus S using XDA App

Yes. It is necessary to build boot.img first. Don't forget the base address though as that's important for the mkbootimg command and you don't have to do it through fastboot. :)
 

DooMLoRD

Inactive Recognized Developer
Jul 27, 2010
13,191
39,703
Pune
There are only two modules. One is the wireless lan driver (tiwlan_drv.ko) while the other is tiap_drv.ko which seems to be related to the wireless lan driver although I haven't looked at it yet. (more important to build a booting kernel first) :)



Yes. It is necessary to build boot.img first. Don't forget the base address though as that's important for the mkbootimg command and you don't have to do it through fastboot. :)

Yup, but with this cleared we can get a better idea about the correct config and that kernel version string won't matter that much, since there don't seem to be any dependent module (other than WiFi)...

Dumb thing but can someone check on stock kernel+stock Rom the supported file systems

adb shell cat /proc/filesystems

And then adjust them in config

Sent from my R800i using XDA App
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    great!

    so i have a few questions:
    1. did u flash the zImage or boot.img?
    2. if it was boot.img wht arguments did u use to create it (mkbootimg arguments)
    3. how did u flash it?

    oh btw i dont have the device with me but really curious on how the development goes :)

    thanks!

    I got the sound working now, though I had to fudge a line in omap4_panda_aic31xx.c to do it. Should probably figure that out, as I don't think it ought to be the way I made it, heh.

    I flashed boot.img; I used the ramdisk from the current 6.2 boot.img. I used the command-line from the current stuff as well, but put it in the .config

    I used fastboot with a factory cable (wow, did I do a butcher job on this cable, but it works).

    Code:
    mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz -o boot.img

    Code:
    $ fastboot -i 0x1949 boot boot.img
    downloading 'boot.img'...
    OKAY [  0.839s]
    booting...
    OKAY [  0.004s]
    finished. total time: 0.842s

    Need to leave the office, will get this stuff up on github after dinner. Glad I got this working, but now I have to work tomorrow to catch up on the crap I didn't do yesterday :)
    2
    Try this one. (working stock source with minimal changes)
    http://www.mediafire.com/?9ax9l479pt2ycwp

    Sorry, the config in the archive has yellow screen issue, please use the config in the attachment
    2
    Might you know what could be done to fix the display? Compiling the Amazon source (with a few modifications for compile errors) using otter_android_defconfig results in a weird display corruption. :confused:

    Try this one. (working stock source with minimal changes)
    http://www.mediafire.com/?9ax9l479pt2ycwp
    1
    good to see work has already started on kernel :)

    i might be getting this device, may be in 2-3 weeks time...



    try using 4.4.3 toolchain from CM repo... its the best to work with kernels...

    here is the toolchain at my git repo:
    https://github.com/DooMLoRD/android_prebuilt_toolchains

    clone it and use the arm-eabi-4.4.3 toolchain


    also if u guys are using 4.6.2 linaro then edit the makefiles and remove this flag "-Werror"
    1
    IT BUILT!

    Ill test soon!