OESF Portables Forum
Model Specific Forums => Cosmo Communicator => Cosmo Communicator - Linux => Topic started by: cam1965 on February 28, 2020, 06:16:28 pm
-
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.
-
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.
-
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.
-
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
-
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.
-
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.
-
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.
-
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.
-
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.
-
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
-
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.
-
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 (https://www.oesf.org/forum/index.php?showtopic=36163)
-
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 (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?
-
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 (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 (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.
-
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 (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 (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.
-
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 (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 (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.
I am in doubt about this. I think they are working most in android. But let's wait. Who knows. keep the faith.
-
Reconfigure your kernel to set CONFIG_MODULE_FORCE_LOAD=y and recompile. Boot the newly compiled kernel, then force-load the wifi module like this:
modprobe --force wlan_drv_gen3
In general this is a bad idea, but where you're not changing the kernel source (I assume), it should be safe. I was able to boot my custom-compiled Linux kernel for my Cosmo and load the wifi module in this manner without issue. The wifi worked fine. But I agree, the source code for the droid-hal-cosmopda package should be published to avoid nonsense like this. There's a chance, though, that these are closed-source binaries from MediaTek.
-
Reconfigure your kernel to set CONFIG_MODULE_FORCE_LOAD=y and recompile. Boot the newly compiled kernel, then force-load the wifi module like this:
modprobe --force wlan_drv_gen3
In general this is a bad idea, but where you're not changing the kernel source (I assume), it should be safe. I was able to boot my custom-compiled Linux kernel for my Cosmo and load the wifi module in this manner without issue. The wifi worked fine. But I agree, the source code for the droid-hal-cosmopda package should be published to avoid nonsense like this. There's a chance, though, that these are closed-source binaries from MediaTek.
Thank you so much !
Worked like a charm.
My previous module binfmt_misc loaded automatically after boot.
And wlan_drv_gen3 as you explained
Note : uname -a shows Linux cosmopda 4.4.146 #14 SMP PREEMPT .
The Planet kernel shows #28.
Again, thank you very much !
-
Reconfigure your kernel to set CONFIG_MODULE_FORCE_LOAD=y and recompile. Boot the newly compiled kernel, then force-load the wifi module like this:
modprobe --force wlan_drv_gen3
In general this is a bad idea, but where you're not changing the kernel source (I assume), it should be safe. I was able to boot my custom-compiled Linux kernel for my Cosmo and load the wifi module in this manner without issue. The wifi worked fine. But I agree, the source code for the droid-hal-cosmopda package should be published to avoid nonsense like this. There's a chance, though, that these are closed-source binaries from MediaTek.
Thank you so much !
Worked like a charm.
My previous module binfmt_misc loaded automatically after boot.
And wlan_drv_gen3 as you explained
Note : uname -a shows Linux cosmopda 4.4.146 #14 SMP PREEMPT .
The Planet kernel shows #28.
Again, thank you very much !
Compiling the kernel with my new boot kernel generates the Image.gz-dtb , without dtc_overlay exec format error.
Problem solved.