compiled kernel but no Image.gz-dtb ,only vmlinux

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

[mibry]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

[mibry]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

Can I ask if you can share you boot.img with bindmt_support, I have been trying to compile a kernel with same and namespaces without much success. Thanks in advance.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

Can I ask if you can share you boot.img with bindmt_support, I have been trying to compile a kernel with same and namespaces without much success. Thanks in advance.

I've compiled the kernel wjth module support for bindmt . I will put the boot.img and the module(.ko ). Unfortunately , like the kernel from repository it has no support for wifi. I had to make a lot of changes in files and  links to compile the kernel. I will place the files here in a few  of minutes.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

Can I ask if you can share you boot.img with bindmt_support, I have been trying to compile a kernel with same and namespaces without much success. Thanks in advance.

I've compiled the kernel wjth module support for bindmt . I will put the boot.img and the module(.ko ). Unfortunately , like the kernel from repository it has no support for wifi. I had to make a lot of changes in files and  links to compile the kernel. I will place the files here in a few  of minutes.

This type of files are not permitted . I am at work. I will try later at home. I think I will have to ask the administrator to put here.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

Can I ask if you can share you boot.img with bindmt_support, I have been trying to compile a kernel with same and namespaces without much success. Thanks in advance.

I've compiled the kernel wjth module support for bindmt . I will put the boot.img and the module(.ko ). Unfortunately , like the kernel from repository it has no support for wifi. I had to make a lot of changes in files and  links to compile the kernel. I will place the files here in a few  of minutes.

This type of files are not permitted . I am at work. I will try later at home. I think I will have to ask the administrator to put here.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

Can I ask if you can share you boot.img with bindmt_support, I have been trying to compile a kernel with same and namespaces without much success. Thanks in advance.

I've compiled the kernel wjth module support for bindmt . I will put the boot.img and the module(.ko ). Unfortunately , like the kernel from repository it has no support for wifi. I had to make a lot of changes in files and  links to compile the kernel. I will place the files here in a few  of minutes.

This type of files are not permitted . I am at work. I will try later at home. I think I will have to ask the administrator to put here.

[cam1965]

Hi,
after a long journey compiling kernel inside cosmo ( I did a lot of changes to compile it , really a pain ) , the kernel was compiled.
But only vmlinux was generated . Not the Image.gz-dtb.
Please see the error in the attached photo.
( dtc_overlay exec format error ).
Please developers help me.
I think Adam Boardman can help me.
Thank you all.

Updated : the error persists inside cosmo, but if compiled in my mac ( with dual  boot mac and linux ) the image was generated correctly.

There was a comment I read somewhere stating that compiling kernel on the cosmo was not work at present due to MISC_BINFMT was not enabled in the initial kernel. This in turn effects when the kernel compiles as it tries to call some x86 functions during compile time. I think this is correct.

Ok. Thank you so much.

Compiled a kernel in my mac with linux  (with binfmt_misc support ) and tried to compile a new  kernel in cosmo ( booting the kernel with binfmt_misc support enabled ), but the problem persists. The kernel was compiled generating vmlinux, but not  generating Image.gz-dtb.

Anyway thank you

Can I ask if you can share you boot.img with bindmt_support, I have been trying to compile a kernel with same and namespaces without much success. Thanks in advance.

I've compiled the kernel wjth module support for bindmt . I will put the boot.img and the module(.ko ). Unfortunately , like the kernel from repository it has no support for wifi. I had to make a lot of changes in files and  links to compile the kernel. I will place the files here in a few  of minutes.

This type of files are not permitted . I am at work. I will try later at home. I think I will have to ask the administrator to put here.

files in zip finally here

[mibry]

Ok I see what you mean. No wifi is worst than not having the other modules. We will have to wait on Nokit and Adam for full kernel. Thanks for the files.

[cam1965]

Ok I see what you mean. No wifi is worst than not having the other modules. We will have to wait on Nokit and Adam for full kernel. Thanks for the files.

Yes. It is true.
The kernel update from repository also has no wifi support.
I've asked here the sources for vendor modules. No answers yet.
Please see
https://www.oesf.org/forum/index.php?showtopic=36163

[mibry]

Ok I see what you mean. No wifi is worst than not having the other modules. We will have to wait on Nokit and Adam for full kernel. Thanks for the files.

Yes. It is true.
The kernel update from repository also has no wifi support.
I've asked here the sources for vendor modules. No answers yet.
Please see
https://www.oesf.org/forum/index.php?showtopic=36163

Silly question, when you compiled the kernel did it compile the modules correctly? Did you try compiling a monolithic kernel?

[cam1965]

Ok I see what you mean. No wifi is worst than not having the other modules. We will have to wait on Nokit and Adam for full kernel. Thanks for the files.

Yes. It is true.
The kernel update from repository also has no wifi support.
I've asked here the sources for vendor modules. No answers yet.
Please see
https://www.oesf.org/forum/index.php?showtopic=36163

Silly question, when you compiled the kernel did it compile the modules correctly? Did you try compiling a monolithic kernel?

The kernel config has support for modules. But it has only 2 modules enabled and also this binfmt module that I have enabled .
This module was compiled  correctly. When I boot with my compiled kernel it loads the binfmt module correctly. I don' t have time to dedicate to cosmo. I will not compile a monolithic kernel ( for the reasons below ).
As my other question, the vendor modules are not in the kernel source  tree ( this modules are necessary to wifi support ). Please see below:

https://www.oesf.org/forum/index.php?showtopic=36163

Note : these vendor modules work only with the kernel image provided by Planet. The updadted kernel from repositories ( apt-get update and apt-get upgrade ) don't load them correctly.

[mibry]

Ok I see what you mean. No wifi is worst than not having the other modules. We will have to wait on Nokit and Adam for full kernel. Thanks for the files.

Yes. It is true.
The kernel update from repository also has no wifi support.
I've asked here the sources for vendor modules. No answers yet.
Please see
https://www.oesf.org/forum/index.php?showtopic=36163

Silly question, when you compiled the kernel did it compile the modules correctly? Did you try compiling a monolithic kernel?

The kernel config has support for modules. But it has only 2 modules enabled and also this binfmt module that I have enabled .
This module was compiled  correctly. When I boot with my compiled kernel it loads the binfmt module correctly. I don' t have time to dedicate to cosmo. I will not compile a monolithic kernel ( for the reasons below ).
As my other question, the vendor modules are not in the kernel source  tree ( this modules are necessary to wifi support ). Please see below:

https://www.oesf.org/forum/index.php?showtopic=36163

Note : these vendor modules work only with the kernel image provided by Planet. The updadted kernel from repositories ( apt-get update and apt-get upgrade ) don't load them correctly.

Looking at the latest posting from Planet hopefully a new kernel will be forthcoming that will allow a kernel to be compiled.