Author Topic: compiled kernel but no Image.gz-dtb ,only vmlinux  (Read 1365 times)

cam1965

  • Sr. Member
  • ****
  • Posts: 331
    • View Profile
    • http://
compiled kernel but no Image.gz-dtb ,only vmlinux
« Reply #15 on: March 07, 2020, 11:51:55 am »
Quote from: mibry
Quote from: cam1965
Quote from: mibry
Quote from: cam1965
Quote from: 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.

I am in doubt about this. I think they are working most in android. But let's wait. Who knows. keep the faith.

shuntcap

  • Jr. Member
  • **
  • Posts: 79
    • View Profile
compiled kernel but no Image.gz-dtb ,only vmlinux
« Reply #16 on: March 12, 2020, 04:26:00 am »
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.

cam1965

  • Sr. Member
  • ****
  • Posts: 331
    • View Profile
    • http://
compiled kernel but no Image.gz-dtb ,only vmlinux
« Reply #17 on: March 12, 2020, 09:24:04 am »
Quote from: shuntcap
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 !

cam1965

  • Sr. Member
  • ****
  • Posts: 331
    • View Profile
    • http://
compiled kernel but no Image.gz-dtb ,only vmlinux
« Reply #18 on: March 13, 2020, 11:58:11 am »
Quote from: cam1965
Quote from: shuntcap
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.