@crispyoz
Yeah, I find it weird too. Don't know the reason, will try to figure it out eventually. I will just work around it for now.
Thank you for your time. I did not know about logread, which is being super helpful to me right now. So, thanks for that
@crispyoz
Thank you for your reply. I did end up figuring out the problem. I connected to wifi and reboot it loaded a lot faster. Is there some sort of bug or is there something else that causes onion to load faster when wifi connection is present? I tried with a dummy wifi name and password, it was loading equally as fast.
@crispyoz
No, I do not. Does it have something to do with block-mount? I believe pAd is partition disk?? And its partitioning or reading all blocks on each boot?
I use the USB to power. But I have not noticed any difference even by powering up through other way. Omega firmware loads faster so there must be something that I am missing right?
@crispyoz
I am sorry, I will try to make my problem clearer to understand. Normally when the kernel finishes loading the modules,the ethernet is up and running (which I really need for this project). I removed all the modules one by one, got the module loading time faster but the ethernet loading time is literally the same.
For example:
module gets loaded at 95 seconds.
ethernet is up and running.
modules gets loaded at 45 seconds.
ethernet is still not up till 95 seconds.
Quite a few times I have noticed that module load faster, even with all the modules present. One certain period, I was able to replicate was when I disabled ra0 and restarted the system. Coincidentally I took out power and got same module loading time repeatedly and once I reboot, it went back to long loading time. This of course, I have not been able to replicate it since.
@crispyoz
Yes, I have tested on other devices, its still the same. I am sorry, I am new to linux. So, how do I use logread? or did you mean to see more of the log message.
@crispyoz
Thank you for your reply. I removed the module and it was still the same. I tried removing the wifi driver as in mt7628_init and it still did not load the module faster. Again, I need the wifi driver so it does not help my overall situation. Is there perhaps caching issue because some times it does load a lot faster like in onion. I once disabled the ra0 in config/wireless and restarted it loaded a lot faster a couple of times but I have not been able to replicated it ever since.
Thanks
Hi I have a custom firmware built for omega but it takes too long to load I have specifically found the following between ip6 table and === pAd =, where it takes too long to load. Does anyone have any idea? I have noticed that on the onion binary it takes less than second to go through these. I would appreciate any help on this
Hi everyone,
I have a custom firmware build with which needs wifi support. I build the firmware using WIFI warp core, but there is an error which states modules linked in: MT_WIFI when wifi warp core starts. We also have can support. I removed the Can bcm but it still gives modules linked in: MT_WIFI error when wifi warp core starts.
To give a little background, the custom firmware, which already works, has a lot of functionalities disabled such as wifi, usb, sd card at the moment. So I am now trying to add wifi support back. We want to be able to upgrade our firmware using wifi which needs to connect to the internet. We have set omega to use spi to connect to can and modified the dtsi accordingly. As it seems wifi warp core requires more than just what is included when we select it for build. I would really appreciate if anyone has any answers.
