Got stuck at verifying modules being built into the kernel for Hybris HAL
Linux - MobileThis forum is for the discussion of all topics relating to Mobile Linux. This includes Android, Tizen, Sailfish OS, Replicant, Ubuntu Touch, webOS, and other similar projects and products.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Got stuck at verifying modules being built into the kernel for Hybris HAL
I'm working on porting Sailfish OS to my Samsung Galaxy S10 Plus (SM-G975F) using the HADK which stands for Hardware Adaptation Development Kit (I added the PDF for it as an attachment to this thread) and I use Lineage 17.1 as a base.
After coming to page 15 and running make hybris-hal droidmedia I use the mer-kernel-checker verify script to verify that the kernel that was built doesn't have any warnings or errors anymore and here's where I got stuck.
I know for a fact that I have changed the defconfig to solve the warnings and errors that's displayed so hybris-hal should show no warnings or errors.
I compared with the .config in /obj/KERNEL_OBJ/ and they don't look the same and I have no clue as to why.
I have looked in the FAQ-HADK and the hot-hadk if the issue is reported (at the time of this writing), but I can't see that anyone else experiences this.
I'll also add the summary of the HADK to show you how far I've come and what steps I've finished.
Copy paste the content of fixup-mountpoints.txt to /hadk/hybris/hybris-boot/fixup-mountpoints before building anything.
Your thread has had 255 views so far, but no replies. Let me try. I also note in passing your 4 attachments have had one view between them. Folks are willing to help if they can, but we are volunteers, not unpaid workers.
My first advice is that if you don't know what you're doing, stop. Porting is not for the faint of heart. If you are a software engineer, you will laugh scornfully at that, and that's ok. But be ready to sort things out and burn midnight oil as needed. Secondly, you need not necessarily cut out warnings and errors - they are your guidance at the moment. Why not leave them, and pipe them to file or /dev/null?
The configs don't look the same because they are not the same. There's many starting questions which bring in their own menu. If you don't want bluetooth, for example, all bluetooth questions and bluetooth drivers are skipped, etc. Why not try the .config in /obj/KERNEL_OBJ/, if your own doesn't work? Why not debug your config, or make your own??
Last edited by business_kid; 06-25-2021 at 11:16 AM.
Kristoffer G, all this is way over my head, and I didn't want to spoil your zero reply status by giving such a near-useless reply, but now I can:
Have you checked more Sailfish-OS specific channels like https://forum.sailfishos.org/ and https://talk.maemo.org/ (TMO) ?
I think you will get at least some on-topic input there.
I know on TMO there's a few threads for so-called community ports to other Android devices. Check it out.
My first advice is that if you don't know what you're doing, stop.
Thank you for your reply!
Well, I live my life by trial and error to learn and to improve the next time I get this problem.
The thing is, Samsung seems to be harder to port Sailfish OS to (at least devices past the Galaxy S7)
With some help I did manage to port Sailfish OS to the Sony Xperia 10 Dual as Sony is more friendly to sharing source code and guides and whatever is needed.
No, I'm not a developer. I'm mostly a translator and packager for my distribution called Mageia, but that's not the same platform.
Quote:
Originally Posted by business_kid
Secondly, you need not necessarily cut out warnings and errors - they are your guidance at the moment. Why not leave them, and pipe them to file or /dev/null?
I definitely don't mean to offend you in any way by writing this, but if you look in the HADK pdf you'll see that on page 15 it clearly states and I quote:
"If you are in a rush, get rid only of ERROR cases first, but don’t forget to come back to the WARNING ones too."
Your idea is good, but the HADK does not have that instruction........... YET, so here's where I feel like I've come to a dead end.
If I can build the kernel and get at least no ERRORS and maybe no WARNINGS I can continue myself.
Sidenote: My wish is that in the future Sailfish OS would have an installer like an interactive setup guide asking you what kind of hardware you want to use (if it detects it properly) during the setup process just like you would with a desktop Linux system, but that's just me thinking to much.
Like this:
"I found the following modem, would you like me to enable use of it for you?"
Of course the user might not be so sure if that's correct, but I hope you get my point.
With some help I did manage to port Sailfish OS to the Sony Xperia 10 Dual as Sony is more friendly to sharing source code and guides and whatever is needed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.