[DEVs] Firmware Summary - Page 3

knc1 · 02-21-2013, 06:20 PM

The search continues for dot-config files with a little bit of prep work.

Spoiler:

So we have a config file in this "old school" style of a kernel image.

Code:

core2quad dxg $ mv ku-2.5.8-dc dot-config-2.5.8
core2quad dxg $ gzip dot-config-2.5.8

Strip the known dot-config off the end of the image.

Code:

core2quad dxg $ dd if=ku-2.5.8-kimg bs=1 count=2660060 of=ku-2.5.8-trim
2660060+0 records in
2660060+0 records out
2660060 bytes (2.7 MB) copied, 10.7579 s, 247 kB/s

See if any sense can be made of that earlier gzip signature in the file.

Code:

core2quad dxg $ dd if=ku-2.5.8-trim bs=1 skip=84448 of=ku-2.5.8-trim-unk.gz
2575612+0 records in
2575612+0 records out
2575612 bytes (2.6 MB) copied, 10.566 s, 244 kB/s

core2quad dxg $ gzip -l -v ku-2.5.8-trim-unk.gz
method  crc     date  time           compressed        uncompressed  ratio uncompressed_name
defla 46434b49 Feb 21 17:01             2575612          1414750023  99.8% ku-2.5.8-trim-unk

core2quad dxg $ zcat ku-2.5.8-trim-unk.gz >ku-2.5.8-trim-uk
gzip: ku-2.5.8-trim-unk.gz: decompression OK, trailing garbage ignored

core2quad dxg $ file ku-2.5.8-trim-uk
ku-2.5.8-trim-uk: ASCII cpio archive (SVR4 with no CRC)

Ah, so - A compressed initramfs archive.
Keep a copy of that also.

Spoiler:

Both files are attached here.
A DX(G) has two copies of the same kernel image, so no distinction is made here between 'main' and 'diags'.

knc1 · 02-21-2013, 06:21 PM

Until I get my hands on a K2 binary to fondle, this post will remain blank.

twobob · 02-21-2013, 07:33 PM

Quote:

Originally Posted by knc1

Until I get my hands on a K2 binary to fondle, this post will remain blank.

I fully intend to abuse Niluje into fessing some up...
ANYONE ELSE?

I know for a FACT that there are users with k2's on here. SHOUT UP!

And from everyone. Thank you.

knc1 · 02-21-2013, 09:50 PM

Quote:

Originally Posted by twobob

I fully intend to abuse Niluje into fessing some up...
ANYONE ELSE?

I know for a FACT that there are users with k2's on here. SHOUT UP!

And from everyone. Thank you.

At one time, we had a larger selection of kernel binaries in our kindle repair collection.

I am willing to take those apart, if anyone still has a copy of something I did not already take apart.

Since the kernel is GPL and everything staticly linked to them is therefore also GPL, your copy can be attached here.
OR, PM me a link if you would prefer.

I just may move all of this stuff over to MiniModding.com - which is more development oriented than this single forum that we have here.

twobob · 02-21-2013, 10:07 PM

I tend to agree.

I was eyeballing minimodding for shifting the bulk of the 100+ zips (pared down to the useful stuff) earlier today? was it today? anyways. yeah.

I agree.

The k2 is hardly critical I have had no actual feedback reports yet on the k2 so I think - as you said - this can be listed as "MIA" till a pressing need comes along.

knc1 · 02-22-2013, 08:41 AM

One of the objectives of this research thread was to learn what the module version strings where on all KUAL supported devices.

This in turn determines how many different builds of kernel modules it would require to support all KUAL devices.
(Ans: 3)

After a few days of fondling the bytes of the kernel binaries the results (read by modinfo, from irfs modules) is:

Group-1: https://www.mobileread.com/forums/sho...5&postcount=90

K2: MIA

DXG: vermagic: 2.6.22.19-lab126 preempt mod_unload ARMv6

Spoiler:

Group-2: https://www.mobileread.com/forums/sho...5&postcount=47

K3: vermagic: 2.6.26-rt-lab126 mod_unload modversions ARMv6

Spoiler:

Group-3: https://www.mobileread.com/forums/sho...2&postcount=38

K4: vermagic: 2.6.31-rt11-lab126 mod_unload ARMv7

Spoiler:

K5(touch): vermagic: 2.6.31-rt11-lab126 mod_unload ARMv7

Spoiler:

K5(paperwhite): vermagic: 2.6.31-rt11-lab126 mod_unload ARMv7

Spoiler:

knc1 · 02-22-2013, 09:41 AM

If the over-whelming desire strikes you to replicate an Amazon kernel . . . .

You will need:

Vendor's kernel source (posted by Amazon)
Vendor's configuration file (posted here)
Vendor's initramfs (posted here), or one of your own invention
Cross-compile toolchain(s) (posted in the KeK resource pool)
Knowledge of how to run the kernel without burning it to the flash memory.

Note: As things stand at the time of this post - you will have to invent a version 5.2 or 5.3 dot-config file from the Amazon provided version 5.1 dot-config files.

A noobie reference: http://gumstix.org/basic-cross-compilation.html

Get after it people.

knc1 · 02-22-2013, 06:12 PM

Totally untested - at least until someone tests a few of these and reports back here.

This first attempt was a brute force, if it stood still long enough to build, wasn't already there, then build it as a module approach.

Probably a lot of useless stuff here for a Kindle, but then again, maybe a few hidden nuggets of gold.

Like: NBD driver, NFS-3 server driver, CIFS driver, OSS driver, .....

You will need knowledge of how to manually determine dependencies (modinfo), manually insert (insmod) and manually remove (rmmod) modules from a running kernel.

Tar-ball has a base directory of 'lib/modules/version' (just like your work station would have).
You **must** be 'root' to get these things properly un-packed.

The lib/firmware sub-tree was accidentally included in the first tar-ball, that is now corrected.

For the curious, there are 328 of them in the tar-ball:

Spoiler:

baf · 02-23-2013, 06:56 AM

Quote:

Originally Posted by knc1

Note: As things stand at the time of this post - you will have to invent a version 5.2 or 5.3 dot-config file from the Amazon provided version 5.1 dot-config files.

Config files are provided in Amazon kernel sources in arch/arm/configs/. I used imx50_yoshi_defconfig for KT.

knc1 · 02-23-2013, 07:20 AM

Quote:

Originally Posted by baf

Config files are provided in Amazon kernel sources in arch/arm/configs/. I used imx50_yoshi_defconfig for KT.

You must not have diff'd it with the one shipped as part of the kernel binary during the kernel build process.

Next your going to tell me you believe in

because Amazon included a gift certificate with your Kindle.

Before I am done here, I will bundle up the collection as an arch/arm/configs addition.

This is a "post often, post early, consolidate later" sort of thread.

dsmid · 02-23-2013, 08:29 AM

Wow, NBD:

Code:

nbd-client home_pc 2000 /dev/nbd0
mount /dev/ndb0 /mnt/us/documents/home_pc
dbus-send --system /default com.lab126.powerd.resuming int32:1

baf · 02-23-2013, 09:45 AM

Quote:

Originally Posted by knc1

You must not have diff'd it with the one shipped as part of the kernel binary during the kernel build process.

I did. The only difference is initramfs/initrd support turned off (CONFIG_BLK_DEV_INITRD is not set) in published config, probably because it would not build without initramfs source.

twobob · 02-23-2013, 10:00 AM

Quote:

Originally Posted by dsmid

Wow, NBD:

Code:

nbd-client home_pc 2000 /dev/nbd0
mount /dev/ndb0 /mnt/us/documents/home_pc
dbus-send --system /default com.lab126.powerd.resuming int32:1

You don't mention the device... 4 or 3?

twobob · 02-23-2013, 10:02 AM

Quote:

Originally Posted by baf

I did. The only difference is initramfs/initrd support turned off (CONFIG_BLK_DEV_INITRD is not set) in published config, probably because it would not build without initramfs source.

I guess that is knc1's point.

This project was about dredging the "true" guts.

Though the differences may be tiny identifying them could prove all-important for certain activities

knc1 · 02-23-2013, 10:03 AM

Quote:

Originally Posted by twobob

You don't mention the device... 4 or 3?

Well, it wasn't a 3 - - those are still putting up a good fight about getting built.

02-21-2013, 06:21 PM	#32
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	K2 bin info Until I get my hands on a K2 binary to fondle, this post will remain blank.

02-22-2013, 09:41 AM	#37
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Kindle kernels If the over-whelming desire strikes you to replicate an Amazon kernel . . . . You will need: Vendor's kernel source (posted by Amazon) Vendor's configuration file (posted here) Vendor's initramfs (posted here), or one of your own invention Cross-compile toolchain(s) (posted in the KeK resource pool) Knowledge of how to run the kernel without burning it to the flash memory. Note: As things stand at the time of this post - you will have to invent a version 5.2 or 5.3 dot-config file from the Amazon provided version 5.1 dot-config files. A noobie reference: http://gumstix.org/basic-cross-compilation.html Get after it people. Last edited by knc1; 02-22-2013 at 06:47 PM.

02-23-2013, 08:29 AM	#41
dsmid Linux devotee Posts: 598 Karma: 2069047 Join Date: Feb 2011 Device: Kindle 3, Kindle 4B, Kindle PW2	Wow, NBD: Code: nbd-client home_pc 2000 /dev/nbd0 mount /dev/ndb0 /mnt/us/documents/home_pc dbus-send --system /default com.lab126.powerd.resuming int32:1

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Unbearable Oversight of the [Original] Nook Tablet Devs!	sarahmelissa	Nook Color & Nook Tablet	9	08-28-2012 06:51 PM
Why don't we just signup as Active Content Devs?	nathansuchy	Kindle Developer's Corner	4	06-16-2012 09:31 PM
Touch [Question devs] Will we ever get Custom library?	danskmacabre	Kobo Reader	4	04-02-2012 06:29 PM
Suggestions for Kindle Devs	jxh11215	Kindle Developer's Corner	5	03-28-2010 07:35 AM

02-21-2013, 10:07 PM	#35
twobob ( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr Posts: 6,586 Karma: 6299991 Join Date: Jun 2012 Location: uti gratia usura (Yao ying da ying; Mo ying da yieng) Device: PW-WIFI\|K5-3G+WIFI\| K4\|K3-3G\|DXG\|K2\| Rooted Nook Touch	I tend to agree. I was eyeballing minimodding for shifting the bulk of the 100+ zips (pared down to the useful stuff) earlier today? was it today? anyways. yeah. I agree. The k2 is hardly critical I have had no actual feedback reports yet on the k2 so I think - as you said - this can be listed as "MIA" till a pressing need comes along.