Details needed #6
Comments
|
mkbootimg is a tool built from android source code on a host machine and is run from the host. You might be able to build it independently of android but I have never tried. You should be using the mr1 branch of my kernel https://github.com/crondog/kernel_msm (I have been meaning to make that the default branch) |
|
Never heard of mkbootimg. Arch Linux (both arm and i686/x86_64) offer android-tools which has On Mon, Sep 8, 2014 at 2:46 PM, crondog [email protected] wrote:
|
|
So can abootimg do what i need or should i install the whole SDK from the AUR? I'm real bad at android development, but reading the documentation it looks like i can, simply using the --create flag. |
|
It can. By the way - extract the old boot.img from You can write your new kernel either there or to the recovery partiton, On Mon, Sep 8, 2014 at 3:52 PM, Jesper Jensen [email protected]
|
|
Now the kernel is failing to compile because python doesn't like commas in prints without parens (probably a python 2-3 thing) I think i'm just going to bed. I think i'll pass until this whole ordeal becomes more stable (i pray that it does). |
|
Just edit the Makefile - it's the stupid qualcomm GCC wrapper script. Search for wrapper and replace the line that sets CC with CC = $(REAL_CC)
|
|
Well, that solved that, but im having a very hard time actually getting it to cross compile from my x86_64 arch install (tried export ARCH=arm, and SUBARCH=arm, make flo_defconfig) but it's failing on make i'm assuming this is because it's trying to compile from arm to arm instead of from linux_x86 to arm. I don't know how to make it. |
|
You need to specify a cross compiler |
|
It worked! I've split (extracted) boot.img (i downloaded the original one from google for the razor) and compiled the new kernel. I'm guessing minimal.initramfs is just created from the system-initramfs as described here https://wiki.ubuntu.com/Initramfs. I made the boot image with EDIT: EDIT2: |
|
Nope, can't get it to work. I've tried booting it in every possible way, even leaving it for 3 hours to see if it just took a while. Is there any way to get some sort of debug output from it during boot? |
|
Ok so i keep forgetting that i set the kernel to build modules (this could be cuasing the issue because it might be missing a module) I updated the flo_defconfig so it builds everything in the zimage. This will hopefully fix things. To get some sort of output of what is wrong you need to reboot back into android right away and then cat /proc/last_kmsg to see what went wrong in the failed boot. |
|
I end up getting this error now: I should probably say that i did |
|
I just built it fine. Did you "make mrproper" first? |
|
Tried that as well, didn't work. I'll walk you through my entire compile flow this time:
This is where it errors out. |
|
Why are you removing wrapper.py? I dont think you should. Where are you setting your cross compiler? All i do is this. ARCH=arm make flo_defconfig The cross compiler is just from android |
|
I'm removing the wrapper since it doesn't work on my system. It's probably made for python2, i run python3. For the envars i do: |
|
You need that script. ... If you remove that then it is not receiving the correct compiler... Just install python2 |
|
I just changed I tried prefixing it with python2 (to force it). It made my build way slower, so i know it worked. Same error. |
|
I'm out of ideas. All i do to get it working is to use the android cross compiler and nothing else. Sorry |
|
I gave that a shot as well, just for completeness sake. Sadly it gave the exact same error. I can't find a single person talking about it on google. Nope, still crashed. just later |
|
I might be misunderstanding how this is supposed to work, but is my .config supposed to say |
|
Yes. Make sure that you have updated your branch so it should be included. |
|
When i run But then i look in kernel_msm/.config and it says |
|
That is all good then. That output is fine and that also means modules will not be built (which is what you want) |
|
Then i'm right back to having no idea. Looking at the code i don't see the problem :/ |
|
I used my brain, and disabled Sadly the other problem is still there i tried looking at last_msg: This was among all the other things from multirom and the msm kernel. Is the problem related to my trying to run with fastboot while having multirom installed? or is this unrelated to my problem (since most of the log mention cyanogenmod kernel and "internal" multirom) It prints a lot of stuff though, so it might be working? |
|
I tried making the boot image, and now i see the pattern: It just keep printing this until i force it to restart by holding down the power button. I'm also a little unsure of what i should see on the screen when it works. Since i can't install X from the chroot env (no internet connection) EDIT: turns out i have internet in chroot, I just didn't have a resolv.conf. I fixed it quite simply by adding the google dns to it.
|
|
I'm going to keep updating this, both for future record for myself, if anyone else has any problems, and to ask for help from anyone bothering to look... So, my problem is still the same as before, but i figured out i actually didn't have the packages correctly installed on my I now have the CHROOT working with a vnc connection! This leads me to wonder how Xorg is supposed be started without the framebuffer? Should i install lightdm or something? and what does the log above mean? |
|
You can start Xorg just by using startx or however you want. ie startx etc with a .xinitrc If you mean the framebuffer console, that is what fbterm is for. The kernel fbcon does not work but fbcon will do the job for you |
|
Freedreno compiles with xorg-1.16. I'm not sure if an old X server is About that dmesg - are you pressing the power key? it looks like it's
|
|
I should probably have told that the first kmsg log is just the power off. that was just me being stupid. But the second one is still unknown. The current git freedreno on the AUR requires X-ABI-VIDEODRV_VERSION == 15, the current xorg-server provides X-ABI-VIDEODRV_VERSION == 18. Those two conflict, so i just installed an old version from the ALARM. With that (and an old version of EVDEV since it requires the newest xorg-server) it compiled and i suppose it should still work, as long as i have the newest driver. I just followed the getty guide, and now i guess the kmesg looks more interesting, so here it is: is that good? it looks pretty decent. The screen still isn't changing from the fastboot screen. I have a very hard time figuring out how Xorg would start by itself (since noone is calling startx)/how i would run startx without a terminal to type it into. i guess fbterm will give me that, but what is getty and how will that start fbterm? |
|
The ABI can be changed by compiling for the new headers. That's there as a OTOH, if there's an API change you'd have to fix the source code. You'll
|
|
But that shouldn't affect it when the driver is updated to the latest revision should it? I'd think it would boot with xorg-server-1.5. There's not a single mention of xorg or fbterm in the log. It looks like it's suspending and resuming again and again from the log. |
|
Sadly, i can tell that nothing is booting. xorg never creates a log file... same thing goes for systemd, no journal file! |
|
SUCCESS i don't know what i did, but i recompiled the kernel, made a new bootimg and it's displaying the framebuffer terminal! The rendering is really sloppy, in that it seems to render in a band that moves down the screen, so it's completely unusable. It also seems to be printing something about "sleeping function called from invalid context (it looks to originate from a call from fbcon). At least it's something! Here's the log until i stopped waiting: http://pastebin.com/jxxxzxRi I want ahead and recorded the strange screen refresh problem: https://www.youtube.com/watch?v=7bSdv2Y5-LE I tried to disable the [email protected]. It's actually the linux kernel terminal, so i guess it is working. It just isn't very good... |
|
Woops i forgot that frambufferconsole was supposed to be a module and not built in. I have updated the flo_defconfig to disable framebuffer console. So when booting it will now not use the kernel framebuffer console. Make sure that you set up fbterm |
|
Woo! It's alive. It's prompting me for a login, which I obviously can't give it since I don't have a keyboard hooked up, but the screen is on and serial is working! Now I just need to hook it up with more space (since I'm already out) |
|
I also met the issue like below After disable the MSM_WCNSS_SSR_8960 in .config, it build successfully, but after boot up, I met the same issue in kernel. [ 8.569091] WARNING: at arch/arm/mach-msm/clock-local.c:313 rcg_clk_enable+0x20/0x40() |
I really don't get how makebootimg is ever supposed to run. Where am i supposed to find
~/android/system/out/host/linux-x86/bin/mkbootimgthat it's trying to run. Is it supposed to be run on the tablet in android mode? chroot? how about on the host.How about kernel_msm, am i supposed to get a specific version of that? from where?
I'm really stuck, and i am by no means a linux newcomer.
The text was updated successfully, but these errors were encountered: