expressatt: kernel building issues

Changing the include statement in io.h to #include "../../mach-msm/include/mach/msm_rtb.h" should do the job, although it's arguably quite ugly If you get more errors of this kind, it might be worth to investigate why arch/arm/mach-msm/include isn't put on the include path but if it's just this instance, just patch it out.

Also it might be quicker to get answers for your problems in the Matrix channel: https://wiki.postmarketos.org/wiki/Matrix_and_IRC

By Luca Weiss on 2019-08-23T08:20:44

I tried posting in Matrix, but it seems most people are active during my sleep time (which I should be doing right now :P). It's hard to scroll up and try to find where I asked my question and find the answer (unless I'm doing something wrong, so feel free to yell at me :P). Thanks for the answer though!

By Ghost User on 2019-08-23T08:34:30

After a few edits to the kernel (I had to fix a few more similar errors), it now gives me this error: log.txt. I guess I'll investigate tomorrow why they aren't including mach-msm, but I am a noob at this and would appreciate any help I can get.

Here is my github repo. There also seems to be a LineageOS kernel, but when I tried it, it seemed to give me the same exact errors.

By Ghost User on 2019-08-23T09:50:28

added category::device + 1 deleted label

changed title from pmbootstrap claims that I am missing msm_rtb.h to expressatt: kernel building issues

By Bart Ribbers on 2019-08-27T14:09:11

I'm still struggling to fix this. When looking at the source kernel config files though, I found that there are two def config files, one for the board (msm8960_defconfig) and the other for the device (express_defconfig). Would compiling the msm8940_defconfig first get me the msm_rtb.h file that I am looking for? If so, how would I get pmaports to do one defconfig and then the other?

By Ghost User on 2019-08-29T21:13:39

kernel config file is specified in kernel APKBUILD.

device-specific defconfig is usually better than SoC-generic

There also seems to be a LineageOS kernel

That LineageOS kernel has version 3.4, yours is 3.0, are you sure it's the same device?

Can't use 'defined(@array)' (Maybe you should just omit the defined()?) at kernel/timeconst.pl line 373.
make[1]: *** [/home/pmos/build/src/Samsung-expressatt-OpenSource-Kernel-00c0cb3b84a7c59142d4e7056cfb89a3f0a5783e/kernel/Makefile:140: kernel/timeconst.h] Error 255
make: *** [Makefile:953: kernel] Error 2
make: *** Waiting for unfinished jobs....

also see https://lkml.org/lkml/2012/11/18/159

By Alexey Min on 2019-08-29T21:15:22

I'm kind of confused on what you mean by the kernel APKBUILD. Is it the APKBUILD under device/linux-samsung-expressatt? If so, I put a config-samsung-expressatt.armv7 in the same directory, if that is what you mean. Sorry, I'm new to porting, so I barely have any idea of what I am doing.

device-specific defconfig is usually better than SoC-generic Ah alright. I'll just use what I was previously using.

I'm pretty sure the LineageOS kernel and the OpenSource kernel that I have are the same device. The cm.dependencies in LineageOS for expressatt showed that this was the kernel, and it also has the expressatt defconfig. I'm guessing people made some changes to the kernel. I'm going with what I got from Samsung's Open Source Software.

Also, thanks for the fix! I've been trying to learn how to port LineageOS simultaneously (It's going pretty bad), so I forgot I already fixed the msm_rtb.h problem. I got another error after applying this patch, but I think I need to implement symbolic links to fix them. The wiki said that there would be a couple of errors, but I'm getting a ton. Hope I'm not doing anything wrong.

By Ghost User on 2019-08-30T01:27:15

Actually, this error I'm confused about. I would like some help with this one. log.txt

The .tmp_vmlinux1 is not being made. I Googled "proc-arm926.o "get_l2_indirect_reg"" and got these two results: 1 and 2.

Are these the right patches? Again, thanks for your help.

By Ghost User on 2019-08-30T05:07:33

Is it the APKBUILD under device/linux-samsung-expressatt

Yes, it has config specified like this https://gitlab.postmarketos.org/postmarketos/pmaports/blob/master/device/linux-samsung-maguro/APKBUILD#L27 dependent on _flavor var above in the same file. So, you copied your express_defconfig to config-samsung-expressatt.armv7 and set all needed values in APKBUILD, right? BTW why are you sure that this defconfig is a correct one? Ususally you take LineageOS build for your device and see what defconfig it uses. It is usually located in lineageOS's device repo, the one named android_device_samsung-codename in BoardConfig.mk in a var named TARGET_KERNEL_CONFIG like for example for klte: https://github.com/LineageOS/android_device_samsung_klte/blob/lineage-16.0/BoardConfig.mk#L22

got these two results: 1 and 2.

I don't know how those 2 huge diffs can help you, each compile error must be explored individually. Linking errors like that usually mean that function body is not compiled (maybe it is hidden by some #ifdef / config option), so the place where it is called should be hidden by that define/config, too.

By Alexey Min on 2019-08-30T08:06:11

So, you copied your express_defconfig to config-samsung-expressatt.armv7 and set all needed values in APKBUILD, right?

Yes, I followed it to the letter. Should I have to set the _flavor variable? The wiki didn't do that, so I didn't either. Please let me know if I do.

BTW why are you sure that this defconfig is a correct one?

I'm not haha... I just thought it was expressatt's defconfig, since that is what the closest thing was to my phone's codename. I thought if the LineageOS kernel was giving me errors, the source code shouldn't. If you recommend me doing with LineageOS's kernel (samsung d2), I'll change to it.

It is usually located in lineageOS's device repo,...

Here is what it says. In the samsung_d2 kernel in the LineageOS repository they changed it. This device tree hasn't been updated since cm 12.

I don't know how those 2 huge diffs can help you...

Oh I see. So do you suggest to change to this kernel? I'll redo the kernel steps again with the change to the LineageOS kernel. Again, sorry for asking stupid questions and thanks so much for your help.

Edit: I'll add my old APKBUILD here. I'm going to update it with the LineageOS 14.1 kernel.APKBUILD

By Ghost User on 2019-08-31T22:08:55

Should I have to set the _flavor variable?

I think yes, if it is not set already. You can look at other kernel APKBUILDs in pmaports repo. Also can you share your APKBUILD somewhere?

recommend me doing with LineageOS's kernel

That's what I would do, take LineageOS's kernel with their defconfig, and don't use gcc8 on old downstream kernel like those, better to use gcc6 from the start, or even gcc4.

By Alexey Min on 2019-08-31T15:49:18

I edited my previous comment to include my old APKBUILD.

Alright, so I switched to the LineageOS kernel and I'm getting the original "mach/msm_rtb.h" missing error. I googled "msm_rtb.h missing" and found two links:

https://github.com/sonyxperiadev/kernel/issues/2 -> Tried to apply the patch, but it seems like a really old patch. What was interesting though was that that some of the lines in the patched files were commented out in the LineageOS kernel. I'm not going to fork the LineageOS kernel to make my changes because I have a tendency to mess things up really bad.

https://forum.xda-developers.com/showthread.php?t=2499423&page=3 -> Site says that they switched from Ubuntu to Linux Mint 15. Currently I'm on Ubuntu 14.04, but I'm unsure if I should switch to Mint.

Also, just curious, but why can't I extract the kernel that my device is currently using and use that instead of compiling a new kernel? Is it for mainlining?

By Ghost User on 2019-09-01T01:41:23

Alright, so I switched to the LineageOS kernel and I'm getting the original "mach/msm_rtb.h" missing error.

https://github.com/sonyxperiadev/kernel/issues/2 -> Tried to apply the patch, but it seems like a really old patch. What was interesting though was that that some of the lines in the patched files were commented out in the LineageOS kernel. I'm not going to fork the LineageOS kernel to make my changes because I have a tendency to mess things up really bad.

Try the fix @z3ntu mentioned here: #340 (comment 207218085)

It seems that you will have to patch your kernel to get it to compile. There is not much room for messing up with these include paths though, either it compiles or it does not. You also don't need to fork it. Try this guide:

https://wiki.postmarketos.org/wiki/Patching#Legacy_Guide

https://forum.xda-developers.com/showthread.php?t=2499423&page=3 -> Site says that they switched from Ubuntu to Linux Mint 15. Currently I'm on Ubuntu 14.04, but I'm unsure if I should switch to Mint.

This will not help, as we are not using the host distribution's compiler and toolchain, but every thing is running in an Alpine Linux chroot with pmbootstrap.

Also, just curious, but why can't I extract the kernel that my device is currently using and use that instead of compiling a new kernel? Is it for mainlining?

Because that does not really follow the free software spirit, of being able to modify everything and compile it from source. But also for practical reasons, you can't change the kernel config, and pretty much all Android kernels don't have everything enabled in their kernel configs, that is required to run postmarketOS. With that being said... using pre-built kernels might be somewhat useful for debugging, if you can't get anything else working. Related guide.

By Oliver Smith on 2019-09-03T21:23:14

Sorry for the late reply. I haven't done the steps that you recommended yet (planning to do it over the weekend), but I recently built Cyanogenmod 12.0 for my device. When I adb shelled into my device and did uname -a, it showed that my kernel was built the same day as well. Should I continue with the LineageOS kernel, not knowing if it works well, or switch to the 12.0 kernel?

Thank you all for your help.

By Ghost User on 2019-09-07T07:31:53

Use a kernel, that is known to be working. So Cyanogenmod 12.0 in your case. (You still need to build it from source with pmbootstrap of course, to make sure it has the right kernel config options enabled.)

You're welcome!

By Oliver Smith on 2019-09-07T14:14:28

Just wanted to let you know that I didn't give up on this project, but I have to take a detour and go with other projects. Hopefully I can get back to this in the future. Stay awesome!

By Ghost User on 2019-09-16T08:31:14

@ollieparanoid I don't know if I should continue here or create a new one. Let me know!

Alright, so today I decided to look into why msm_rtb.h was giving me a problem. I switched to Manjaro (from Ubuntu), and still got the same problem. The only thing I changed was that I switched to the latest kernel in the repo (from 12.0 to 14.1). I decided to check pmOS's devices to see if there were devices with my SOC, and I found these two: HTC_One_XL and HTC_One_SV (Hunting and pecking for the same SOC was a chore though :P). I think there is some problem with the defconfig conversion (Idk what it's actually called. I'm still a noob :P)

I'm going to lay out some of the differences here. I used (Diffchecker)[https://www.diffchecker.com/diff].

Key:

Original defconfig
Converted defconfig -> config-samsung-expressatt.armv7
HTC_One_XL. Didn't use HTC_One_SV because HTC_One_XL has the same GPU and SOC (so more similarities hopefully) and /arch/arm/include/asm/io.h (the place I was getting the error) wasn't modified, unlike HTC_One_SV.

1) CONFIG_ARCH_MSM8960=y
2) (was missing from the config file :/)
3) CONFIG_ARCH_MSM8960=y

1) CONFIG_CPU_V7=y
2) (was missing from the config file :/)
3) CONFIG_CPU_V7=y

1) CONFIG_CRYPTO_ECB=y
2) # CONFIG_CRYPTO_ECB is not set
3) CONFIG_CRYPTO_ECB=y

I'm sure there's more, but you hopefully get the idea. Something I also did was to switch to GCC4 which was mentioned on HTC_One_SV's page, but it still didn't work (I don't think it's neccessary to switch to GCC4, but I'll only switch back if it's giving me errors). HTC_One_XL's See More showed that Simon Utter had no trouble.

I had no issues what so ever building and compiling the kernel, then booting it.

Here's my log.txt (Realized the old one was slightly different). I think the config error starts on line 1463 and ends at 17182. I'm not sure what is causing it and would like some help. Thanks!

By Ghost User on 2019-12-08T20:23:18

Never mind... I was stupid and figured out the last problem. I was using wget wrong and getting the website instead of the text file...

Now that fiasco is done, I started compiling with gcc4 (the up to date gcc was giving me weird errors. I switched to gcc6 and gcc4 and they both stopped on the same error I think. I'll keep it on gcc4 to hammer out the problems out right now, but let me know if this is a bad idea.)

Here are the latest errors. I'm getting a weird error from drivers/usb/gadget/android.c that I don't know what to startpage for. I've looked into the devices with the same SoCs, but they didn't get this problem. This kernel is for 14.1 android. I'm going to try the CM 12.0 right now, but I'm having a bit of trouble trying to get the tar file from a branch. I'll update if I'm successful or not. Edit: figured it out :/ log.txt

By Ghost User on 2019-12-13T05:58:05

Actually, I think the 12.0 kernel with GCC4 compiled to Image (not ZImage )! I'm just getting this error now xz: unrecognized option: check=crc32

log.txt

Edit: I might try different branches of the kernel later to see if this error can be avoided. For now I'll be awaiting your reply as this is the farthest I've gotten :). Super excited!

By Ghost User on 2019-12-13T06:52:12

Seems like busybox's xz is not compatible. You can try to either use different comression method, or explicitly add normal xz to package dependencies

By Alexey Min on 2019-12-13T09:35:06

Holy moly, thanks it worked! Time to do the rest of the guide with my built kernel :)

By Ghost User on 2019-12-13T19:52:25

I'm now getting this error ERROR: Partition "KERNEL" does not exist in the specified PIT. I'm not sure what to do as Startpage isn't offering much. I installed heimdall, and decided to download the pit. Sure enough there was no KERNEL in the pit. I don't want to mess with it too much without help, as I don't want to brick my device.

pit.txt log.txt

By Ghost User on 2019-12-13T22:11:08

I think heimdall print-pit should output the list of partitions on device. In samsungs it is usually called BOOT? Well, yes, boot.img goes to BOOT partition

...
Partition Name: BOOT
Flash Filename: boot.img

You should setup kernel partition name in deviceinfo file like for example here: https://gitlab.postmarketos.org/postmarketos/pmaports/blob/master/device/device-samsung-klte/deviceinfo#L35

By Alexey Min on 2019-12-13T22:23:12

Thanks for your help!!! It works! There's a weird red tinge on the screen, and it boot loops after a while(Edit: seems to be when I press the power button. Means screen is on 24/7), but it boots! :) Thanks for your guys' help!

By Ghost User on 2019-12-13T23:40:47

closed

By Ghost User on 2019-12-14T01:11:30

expressatt: kernel building issues

Child items ...

Activity