[DEVs] Firmware Summary - Page 6

knc1 · 02-24-2013, 12:08 PM

Quote:

Originally Posted by baf

There should be more info on version magic mismatch in dmesg.

Yeah - good point,
Install the dmesg -> doc DevHelper button
Use once before you try the insert (will transfer and clear buffer)
Use a second time after you try the insert
Post the second document as a compressed attachment.

I knew I wrote that button for a reason!

In fact, I intend to add to the collection of DevHelper buttons as the need arises.

twobob · 02-24-2013, 12:15 PM

okay I have that button (of course

)

will do that now.

twobob · 02-24-2013, 12:32 PM

eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=18C:from pmic
binfmt_misc: no symbol version for struct_module

baf · 02-24-2013, 12:42 PM

Quote:

Originally Posted by twobob

binfmt_misc: no symbol version for struct_module

Missing Module.symvers file in the root of the kernel source?

knc1 · 02-24-2013, 12:57 PM

Quote:

Originally Posted by baf

Missing Module.symvers file in the root of the kernel source?

Code:

core2quad linux-2.6.26-rt16 $ grep 'struct_module' Module.symvers
0xae785729    struct_module    vmlinux    EXPORT_SYMBOL

Got that, will go back to grepping the source catalog for the missing loader script.

Hmm... Might be in the Freescale repo - I have a clone of that already to look at.

Yeah, need one of these things:

Code:

arm-none-linux-gnueabi-ld -EL  -p --no-undefined -X  -o .tmp_vmlinux1 -T arch/arm/kernel/vmlinux.lds .... ..... ..... ....

Hmm....
Have that:

Code:

./work/linux-2.6.26-rt16/arch/arm/kernel/vmlinux.lds

Have to think about this during lunch break.

In case I am mis-reading the command and the message (in all its glory):

Code:

  arm-none-linux-gnueabi-ld -EL  -p --no-undefined -X  -o .tmp_vmlinux1 -T arch/arm/kernel/vmlinux.lds arch/arm/kernel/head.o arch/arm/kernel/init_task.o  init/built-in.o --start-group  usr/built-in.o  arch/arm/kernel/built-in.o  arch/arm/mm/built-in.o  arch/arm/common/built-in.o  arch/arm/mach-mx3/built-in.o  arch/arm/nwfpe/built-in.o  arch/arm/vfp/built-in.o  arch/arm/plat-mxc/built-in.o  kernel/built-in.o  mm/built-in.o  fs/built-in.o  ipc/built-in.o  security/built-in.o  crypto/built-in.o  block/built-in.o  arch/arm/lib/lib.a  lib/lib.a  arch/arm/lib/built-in.o  lib/built-in.o  drivers/built-in.o  sound/built-in.o  net/built-in.o --end-group 
arm-none-linux-gnueabi-ld: no machine record defined

knc1 · 02-24-2013, 03:08 PM

The linker is doing its thing (see attached), the object files do not have anything in the __versions section.

??Bad macro expansion somewhere??

More, after a nap to think on this one.

twobob · 02-24-2013, 03:08 PM

am testing now

knc1 · 02-24-2013, 05:39 PM

After macro expansion (attached).
The winning line is line number 6,601
(For anyone who thinks that Linux does not use Macros.

)

Those blank, quoted, fields in that line's expansion should not be blank.

Hmm....
Guess I need to find a similar situation where it does expand properly, then figure out why the difference.

twobob · 02-24-2013, 10:41 PM

Quote:

static const char __mod_vermagic5[] __attribute__((__used__)) __attribute__((section(".modinfo"),unused)) = "vermagic" "=" "2.6.26.8-rt16-lab126" " " "" "" "mod_unload " "modversions " "ARMv" "6" " ";

hmmm... I see. Interesting stuff. and utterly beyond my comprehension.

NullNix · 02-25-2013, 07:16 AM

Quote:

Originally Posted by twobob

hmmm... I see. Interesting stuff. and utterly beyond my comprehension.

static const char __mod_vermagic5[] __attribute__((__used__)) __attribute__((section(".modinfo"),unused)) = "vermagic" "=" "2.6.26.8-rt16-lab126" " " "" "" "mod_unload " "modversions " "ARMv" "6" " ";

means

"An initialized constant char array variable named __mod_vermagic5, symbol named "vermagic", in the .modinfo section, included even if unused, we declare that it is used even if it doesn't seem to be, contents "2.6.26.8-rt16-lab126mod_unloadmodversionsARMv6 "."

The significance of that content is that it includes, uh, not everything, but *most* things that might make this kernel ABI-incompatible with other kernels, so that you can compare the contents of this section in a module with the content of the same in the kernel to see if they might be compatible.

This is very definitely a kludge: lots of things can cause ABI incompatibilities which are not included in that string, but everything in the string is relatively certain to, except perhaps minor changes to the version number (but there's no way to tell if a core kernel change didn't change some structure somewhere, so best to rule such changes out too).

knc1 · 02-25-2013, 09:00 AM

Quote:

Originally Posted by NullNix

static const char __mod_vermagic5[] __attribute__((__used__)) __attribute__((section(".modinfo"),unused)) = "vermagic" "=" "2.6.26.8-rt16-lab126" " " "" "" "mod_unload " "modversions " "ARMv" "6" " ";

means

"An initialized constant char array variable named __mod_vermagic5, symbol named "vermagic", in the .modinfo section, included even if unused, we declare that it is used even if it doesn't seem to be, contents "2.6.26.8-rt16-lab126mod_unloadmodversionsARMv6 "."

The significance of that content is that it includes, uh, not everything, but *most* things that might make this kernel ABI-incompatible with other kernels, so that you can compare the contents of this section in a module with the content of the same in the kernel to see if they might be compatible.

This is very definitely a kludge: lots of things can cause ABI incompatibilities which are not included in that string, but everything in the string is relatively certain to, except perhaps minor changes to the version number (but there's no way to tell if a core kernel change didn't change some structure somewhere, so best to rule such changes out too).

The point is, those empty fields.

That is the list of symbol signatures and symbol version ID that is missing in the expansion.

The kernel will not load a module unless the symbol signatures and version ID of each symbol match what it provides (which is why you shouldn't strip the symbol table off of the kernel binary).

But the other point made is also valid -
Just because the external code interfaces correctly (by the above tests) to provide a "wash foobar" function does not mean that the code actually washes foobars. It might churn butter instead.

knc1 · 02-25-2013, 10:21 AM

Maybe if I asked these people for their Linux, dot-config file ? ?
http://www.top500.org/system/177975

No mention of problems loading modules (into 1/2 million cores):
http://www.olcf.ornl.gov/titan/

knc1 · 02-25-2013, 05:15 PM

My Kindle Koding partner (twobob) and I have what seems to be working modules now.

Six time zones apart, but we both have the same /Kloud directory mounted in our file systems. Makes tossing files back and forth a lot easier.

bad .config, bad source archive, wrong compiler - - nothing too major wrong.

PS: Amazon took down the 3.4 source archive for a damn good reason!

knc1 · 02-26-2013, 12:52 PM

Group 3 (K4, K5touch, K5paperwhite): https://www.mobileread.com/forums/sho...2&postcount=38

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

Group 1 (K2, DX): https://www.mobileread.com/forums/sho...5&postcount=90

Both of the uploads above have been updated, now includes depmod files.

A few of each archive have been loaded and tested to actually run as intended.

We may never have any use for all of these, but the archives will serve as a "master copy" of everything for each group of KUAL devices.

knc1 · 02-26-2013, 03:49 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
Sorry folks, no: CIFS or SAMBA driver in this lot.

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 414 of them in the tar-ball:

Spoiler:

02-25-2013, 10:21 AM	#87
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Maybe if I asked these people for their Linux, dot-config file ? ? http://www.top500.org/system/177975 No mention of problems loading modules (into 1/2 million cores): http://www.olcf.ornl.gov/titan/ Last edited by knc1; 02-25-2013 at 10:28 AM.

02-25-2013, 05:15 PM	#88
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Progress My Kindle Koding partner (twobob) and I have what seems to be working modules now. Six time zones apart, but we both have the same /Kloud directory mounted in our file systems. Makes tossing files back and forth a lot easier. bad .config, bad source archive, wrong compiler - - nothing too major wrong. PS: Amazon took down the 3.4 source archive for a damn good reason! Last edited by knc1; 02-25-2013 at 06:55 PM.

02-26-2013, 12:52 PM	#89
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	2 done, 1 to go Group 3 (K4, K5touch, K5paperwhite): https://www.mobileread.com/forums/sho...2&postcount=38 Group 2 (K3): https://www.mobileread.com/forums/sho...5&postcount=47 Group 1 (K2, DX): https://www.mobileread.com/forums/sho...5&postcount=90 Both of the uploads above have been updated, now includes depmod files. A few of each archive have been loaded and tested to actually run as intended. We may never have any use for all of these, but the archives will serve as a "master copy" of everything for each group of KUAL devices. Last edited by knc1; 02-26-2013 at 03:50 PM.

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-24-2013, 12:15 PM	#77
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	okay I have that button (of course ) will do that now.

02-24-2013, 12:32 PM	#78
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	eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=18C:from pmic binfmt_misc: no symbol version for struct_module

02-24-2013, 03:08 PM	#82
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	am testing now

Advert

Advert