Related
Has anyone got the fbcon framebuffer console to work on the Atrix ?
I have sucessfully compiled an atrix tegra kernel from source and booted on my 4.5.91 (2.3.4) Atrix.
I have 'sucessfully' set the frame buffer console and enabled fbcon via menu config.
These were compiled as builtin modules and built a zImage without any issues.
However, the new kernel fails to boot where the 'default .config' built kernel will boot.
I was hoping to get lucky and override the /dev/graphics/fb0 limitation on these devices. I need the framebuffer to run a framebuffer applictaion proir to starting up android after the kernel boots. I have the capability working on the nexus one just having trouble porting to the Atrix.
Does anyone know a simple kernel trick to fix the framebuffer?
Thanks in advance.
Maybe this will be of help
https://github.com/epsylon3/kernel-MB860/commit/17d7beda6baf7fdee731863ef0ae03785f30eb7b
turl1 said:
Maybe this will be of help
https://github.com/epsylon3/kernel-MB860/commit/17d7beda6baf7fdee731863ef0ae03785f30eb7b
Click to expand...
Click to collapse
It sure was. Thank you very much for the shove in the right direction.
I grabbed that git tree and configured tegra_olympus_cm7_def_config and set that switch. So I can read the framebuffer but have yet to be able to display what I right. Thanks again.
SOLVED
turl1 said:
Maybe this will be of help
Click to expand...
Click to collapse
Thanks again turl1.
there was one more hitch where you actually have to swap buffers using an ioctl found in system/device/motorolo/olympus/recovery/graphics.c:
FBIOPUT_VSCREENINFO
General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).
Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.
For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:
[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion
As someone already might know, I'm streambinder, from MoltenMotherBoard team.
I have already followed some projects for the GT-S5300, but especially kept in contact
with some of the events related to the porting of ROM and Kernel sources for BCM21553 chipset based devices.
In this precise moment, the sources in my possession allow you to be able to compile
a bugfree CWM 5.0.2.8 (based on CyanogenMod 7 code) with a kernel based on the Samsung stock one.
The only - fundamental - problem was due to the fact that unless I hadn't used the prebuilt INIT binary
token in the Samsung stock firmware boot.img, the phone would not work - or, better, boot up.
This means that until the situation - regarding this issue - doesn't change, our access to the porting of custom ROM
would be barred.
Recently, I decided to give Cori another chance and rework my sources, looking at the wonderful work brought
by the BroadcomCM team on CyanogenMod 9 (in particular, thanks to @bieltv.3 and @Alberto96) and @psyke83 on CyanogenMod 11.
They've not only been able to run these two ROMs in a more or less crude way, but this developer has been able to write
the necessary strings to make the INIT binary of some of these BCM21553 devices opensource.
Strong of this informations, I readjusted some of the sources of BroadcomCM's CyangenMod 9, which includes
all the progress carried out by both the team and psyke83, in order to make them work even on Cori,
and am now next to the first test of the CWM 6.X.X.X, based on IceCreamSandwich code.
At the same time, @akhbh is working on the KitKat code based CWM.
I hope I can give more information about any progress as soon as possible.
The General Discussion thread for non-development issues is here:
*.[DISCUSSION] CyanogenMod 11 For Galaxy Pocket GT-S5300 Discussion Thread
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
streambinder said:
Made a first test of CWM based on CyanogenMod 9 code.
It seems it cannot flash it as it weighs so much compared to its partition configuration value: in fact, the maximum boot partition size is set up to 5.0MB, but the compiled boot.img weighs 5.3MB.
Will have to resize its weight in order to make it fill into the partition.
@akhbh, have you had any complication in these terms, with CyanogenMod 11 sources?
@psyke83, what do you suggest to do? Do you think an increasement of boot partition would be a better idea?
Click to expand...
Click to collapse
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
akhbh said:
No, I didn't faced those complications. My boot.img weighted around 4.5 MB in lzma compression mode. In gzip, it increased to more than 5 mb.
Click to expand...
Click to collapse
Perfect.
Which kernel have you based your build on?
streambinder said:
Perfect.
Which kernel have you based your build on?
Click to expand...
Click to collapse
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
akhbh said:
Well, I took the GeTux kernel for cori, had to change the board name though and then compile it. CWM was booting even before changing the board name but there was no reaction from the phone on trying to boot cm9/cm11
And after changing board name, a black screen on trying to boot
Another info: When tried to merge cori source into the bcm21553 common one, it did compile but gave bootloop of GT-S5300 logo on trying to boot as well as when trying to go in CWM.
Bieltv.3 recommended to use cori source instead of the bcm21553 common one so we used cori sources
Click to expand...
Click to collapse
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
streambinder said:
I suggest to use our Kernel sources for now, too: it will automatically bypass few errors/issues/bootloops that we cannot now fight with.
The most important thing is to make INIT working from sources (hope it will be working
on my CM9 sources, too) and check that every our configuration is correctly working and
making Cori boot into recovery.
Once we'll make it perfectly working without any kind of issue, will be the right time to try
to make Cori supported with the BC21553-common kernel.
Click to expand...
Click to collapse
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
akhbh said:
Okay, I will use your kernel sources and try if something is changed once I reach home. For now, I neither have this device nor a PC, as I'm in another city.
Will be keenly watching your work. Will start after reaching home around the end of September
Click to expand...
Click to collapse
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
streambinder said:
No problem, mate.
Here you have every source in my possession:
platform_kernel_samsung_cori | github.com
platform_device_samsung_cori
Keep in contact with me, as I will need some informations by you.
Anyway I'm now making another build, keeping some not so much important binaries excluded, so that I can make the compiled boot.img fill into our little Cori's boot partition. I know it's a dirty workaround, but if it works, I'll use it untill @psyke83 will suggest me a better way to do.
Click to expand...
Click to collapse
have u tried to build cwm v6 from cm9 source ??
cleverior.ipul said:
have u tried to build cwm v6 from cm9 source ??
Click to expand...
Click to collapse
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
akhbh said:
I think we didn't had significant changes. Perhaps the same as totoro. But, that resulted in the internal_sd not mounting error in cwm.
Sadly, as said before, I am away from my home city and can't provide the files to you and can't do the boot.img diffs as well
Try to ask psyke83, he might have a solution for that
Click to expand...
Click to collapse
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
streambinder said:
Then, if you didn't make any massive change upon the sources, then I'll only try using your kernel.
Can you give me your kernel sources, mate, please?
Click to expand...
Click to collapse
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources coz as said earlier, his kernel is used. Well, we were working together to bring cm11 but weren't successful
akhbh said:
Currently, I can provide you the boot.img only. For the sources, @cleverior.ipul can provide the kernel sources.
Click to expand...
Click to collapse
Ok, please send it to me, will compare it with my package.
streambinder said:
Ok, please send it to me, will compare it with my package.
Click to expand...
Click to collapse
Here it is:
http://www.4shared.com/zip/1nKFbOJ2ba/ccccGetux_CM11.html
streambinder said:
Of course, mate. I'm working on it, right now.
It doesn't seem to boot, strange if the same INIT binary sources are working for @akhbh.
#UPDATE
In order to troubleshoot, I'll give you some info.
For his build I used these sources:
platform_kernel_samsung_cori
platform_device_samsung_cori
android_device_samsung_bcm21553-common
Applied some lines on our bcm21553-bootimg.mk, too, in order to exclude parted and mke2fs and make the compiled boot.img weigh less.
@cleverior.ipul, can you link me your kernel sources, as akhbh said he used your ones for CM11.
@akhbh, which modifies have you applied in order to compile CWM based on CM11 code? Which device tree?
#UPDATE 2
Attached my compiled boot.img.
If anyone of you would extract it (you can easily use this tool: bootimgtools - read how to use it in the README) and make a diff with the CM11 one (just extract the ramdisk of both boot.imgs and - in the terminal - use this command: diff -urN /path/to/cm9/ramdisk /path/to/cm11/ramdisk > diff.patch), would make to me a huge favour.
Let me know.
Click to expand...
Click to collapse
here the link source https://github.com/cleverior/android_kernel_samsung_cori
i've changed the board name. If your device can not boot after using the zImage from this source, then rename init.bcm21553.rc to init.gt-s5300.rc.
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
akhbh said:
@streambinder, what is grom? As bieltv.3 said that init built grom for cori is required to fix adb over cwm recovery. If adb gets working, then possibly the black screen while booting cm11 might get fixed
Click to expand...
Click to collapse
Sincerely don't what are you talking about.
Anyway, have to try to understand where's the problem with the not-booting CWM.
Will try with your sources and let you know.
USB Driver
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE550ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip.secure
ZE551ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip.secure
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/zenfone2_2_12_40.zip
Great!! Looking forward for great dev support..
Fire code said:
USB Driver
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE550ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip.secure
ZE551ML ROM
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip.secure
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/zenfone2_2_12_40.zip
Click to expand...
Click to collapse
Links for ZE551ML and ZE550ML ROMs are broken.
BACKUP
Quote:
Originally Posted by Fire code
USB Driver
https://drive.google.com/open?id=0B-1_qo5woThsQkNWQnVwZG9CVzA&authuser=0
ZE550ML ROM
N/A(sorry ~i didn't backup this~ )
ZE551ML ROM
https://drive.google.com/open?id=0B-1_qo5woThsTnM3bjQxaHJoUzg&authuser=0
Kernel source
ZE550ML/ZE551ML
http://dlcdnet.asus.com/pub/ASUS/Zen...e2_2_12_40.zip
https://drive.google.com/open?id=0B-1_qo5woThsOHhkTUNEUFItdFU&authuser=0
I can't wait tell I get this device. Nothing but good old cyanogenmod and aosp roms.
Sent from my SM-T230NU using XDA Free mobile app
Anyone rip any apps out and had success with them running on AOSP yet?
Do you guys think there will be an Ubuntu Touch edition for the ZenFone 2? It has an Intel CPU, I really wish that.
update link
USB Driver:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
ZE500CL
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/UL-ASUS_Z00D-WW-12.16.4.3-user.zip
ZE550ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.11-user.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE550ML/UL-Z008-WW-2.12.40.9-user.zip
ZE551ML
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.11-user.zip
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-2.12.40.9-user.zip
hp420 said:
Anyone rip any apps out and had success with them running on AOSP yet?
Click to expand...
Click to collapse
You can get some ZenFone 2 apps From :-
I have deodexed rom.
and ported some apps and they are working flawlessly on CM11 without any bug.
http://forum.xda-developers.com/and...enfone-2-apps-port-root-t3073195#post59906345
ThunderSky7 said:
You can get some ZenFone 2 apps From :-
I have deodexed rom.
and ported some apps and they are working flawlessly on CM11 without any bug.
http://forum.xda-developers.com/and...enfone-2-apps-port-root-t3073195#post59906345
Click to expand...
Click to collapse
Deodexed rom meaning you have a zenfone 2 stock deodexded rom? Do you have a link to it or the rom is private?
You should add screenshots.. :good:
thanks for drivers
sooo much repo'ing to get AOSP before the compiling even begins. There's gotta be a better way for them to maintain the repository. :/
Edit:
After downloading around 40 gigs of files from AOSP, won't compile on our phones. Looks like build tools are only 64-bit and the Debian Jessie chroot I'm using on the phone isn't allowing the 64-bit tools to execute. Our kernel reports that it IS in fact x86_64, but I can't seem to find the phone's /lib64 directory to map to the chroot. So, something that could be fun is now a huge headache -- may need to put together a pc just to build this kernel & hope I still have enough bandwidth from my ISP to repo another 40 gigs.
ycavan said:
sooo much repo'ing to get AOSP before the compiling even begins. There's gotta be a better way for them to maintain the repository. :/
Edit:
After downloading around 40 gigs of files from AOSP, won't compile on our phones. Looks like build tools are only 64-bit and the Debian Jessie chroot I'm using on the phone isn't allowing the 64-bit tools to execute. Our kernel reports that it IS in fact x86_64, but I can't seem to find the phone's /lib64 directory to map to the chroot. So, something that could be fun is now a huge headache -- may need to put together a pc just to build this kernel & hope I still have enough bandwidth from my ISP to repo another 40 gigs.
Click to expand...
Click to collapse
It's already several years ago Android build tools migrated to x64-only. So, you cannot build Android (even 32bit version) on x32 machine.
Zenfone 2 kernel is 64bit. But Android itself is 32bit. You still can start 64bit binaries if you want. I'm using 64bit busybox and some other utilities I've made.
I didn't try to compile Zf2 kernel yet because there is no unlocked bootloader exist, so you simply can't boot your own kernel.
I was able to apt-get lib64 on debian jessie ( was called libc6-amd64 ) & that moved things along until the assembler refused to load libz.so. No amount of looking around helped figure that one out since libz.so did exist.
This is just something fun to do while waiting for the unlocked bootloader. Wouldn't it be nice to be able to just compile your own kernel on your phone?
Compilation requires a lot of typing in command line. I cannot imagine doing this on phone. It's simply crazy. I'm not even talking about time needed for compilation.
I'm using PC (with linux VM) to compile everything.
sorg said:
Compilation requires a lot of typing in command line. I cannot imagine doing this on phone. It's simply crazy. I'm not even talking about time needed for compilation.
I'm using PC (with linux VM) to compile everything.
Click to expand...
Click to collapse
@sorg..so currently is there anything that you have produced for zenfone 2? and is it possible for this phone to be developed once asus release and unlock the BL?
cangcan said:
@sorg..so currently is there anything that you have produced for zenfone 2? and is it possible for this phone to be developed once asus release and unlock the BL?
Click to expand...
Click to collapse
Yes, i've compiled many binaries already.
Of course it's possible to develop for ZF2. There is ASUS Nexsus Player (fugu) device in CM12 repository which is basically very close to ZE550/ZE551. So, there is already a lot of code in Cyanogenmod. But, i prefer stock ROM anyway.
sorg said:
Yes, i've compiled many binaries already.
Of course it's possible to develop for ZF2. There is ASUS Nexsus Player (fugu) device in CM12 repository which is basically very close to ZE550/ZE551. So, there is already a lot of code in Cyanogenmod. But, i prefer stock ROM anyway.
Click to expand...
Click to collapse
That's good news sorg, great to know you've been getting some code flowing while waiting for the bootloader unlock tool.:thumbup: I'll have to check out your repositories when I get the chance, especially since I wanted the device tree for my rom projects.
Sent from the Ace's MB865 using Tapatalk
edit: nvm
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
sk806 said:
Hi All,
I have been building permissive kernels for my own use for a while now, but the Note 5 kernel (both the "C" and "I" versions from Samsung open Source) is giving me fits. As you can see from my terminal output, I get through the creation of the image, the modules build fine, but when the firmware install makefile starts, I get an error I've never seen before, even if I have made no changes at all to the source code:
Code:
OBJCOPY arch/arm64/boot/Image
GZIP arch/arm64/boot/Image.gz
Building modules, stage 2.
MODPOST 2 modules
CC net/ipv4/tcp_htcp.mod.o
LD [M] net/ipv4/tcp_htcp.ko
CC net/ipv4/tcp_westwood.mod.o
LD [M] net/ipv4/tcp_westwood.ko
[B]/home/parallels/ANDROID/KERNEL/920c_kernel/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule[/B].
I have looked at the cited section code, but don't see anything obvious. I have also google searched for this error way too thoroughly and PM'd some who have successfully compiled this kernel, but alas...
I am running Ubuntu 14.04 via Parallels on a Macbook Pro running Yosemite. As noted above, I am compiling from the Samsung OpenvSource files for The 920I and have also tried the 920C version, as well. As for toolchains, I have tried the Android NDK aarch64 4.9 toolchain, linaro aarch64 4.9 and linaro aarch64 5.2, all to no avail. I have tried make clean, make mrproper, deleted .ccache, etc., as well as using/not using -jX.
Here is a link to a repo with the untouched source code: https://github.com/sk806/N5_Kernel.git
ANY HELP IS GREATLY APPRECIATED!!!
Thanks!
Steve
Click to expand...
Click to collapse
That is Samsung for ya. Maybe @g.lewarne could provide some insight
mikeyinid said:
That is Samsung for ya. Maybe @g.lewarne could provide some insight
Click to expand...
Click to collapse
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
sk806 said:
I hope so! Thanks.
It's weird, as i've gotten the same error on both a virtual box and parallels setup. I am going to try boot camping it and then I'm done, unless someone knows what is going on.
Click to expand...
Click to collapse
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
elesbb said:
Have you resolved this issue? I am running into it too trying to compile S6 Kernel for 5.1.1
Click to expand...
Click to collapse
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
sk806 said:
I haven't. I can get every kernel to compile for my current devices, except this one. Strange.
Click to expand...
Click to collapse
It is related to modules compiling from what I can gather. If I use Ktoonsez source, I don't get that error. However, I notice it doesn't compile any modules. I still get an Image in my boot directory. Do you? I think the kernel itself is safe to use. You could probably ignore this error.
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
sk806 said:
HA! I googled the error a million times and never saw your repo! I wasn't sure if removing "stm_z1.fw tsp_stm" from the makefile would screw anything up, but apparently it doesn't. Many thanks, sir!
It's odd that others have built with the same sources (920C, mainly, from what I have seen), and have not changed that section of the makefile, but still succeeded in their build. I wonder what it is about my setup that caused this error. Anyway, not an issue now. Thanks again.
Steve
Click to expand...
Click to collapse
There are others I've seen using my commit (no credit) and didn't cherry-pick keeping the history. I believe the Image still flashes with or without though
I am having the same issue can you explain what was the issue ?
UpInTheAir said:
You guys just need to read what the error exactly refers to and then search for it in your source.
Would have brought you to. ....
https://github.com/UpInTheAir/SM-N920/commit/ad77e0333fbdccf5e0e1485e5a65ae47a062b235
Easy
Click to expand...
Click to collapse
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
elesbb said:
I don't have anything like that in my makefile.fwinst file. Here is what is at line 45, which is where terminal is telling me the error is at:
$(installed-fw): $(INSTALL_FW_PATH)/%: $(obj)/% | $(INSTALL_FW_PATH)/$$(dir %)
$(call cmd,install)
Here is the actual terminal error message:
/home/seth/S6-Kernel_Parent/Extracted_S6_Source/Kernel.tar/scripts/Makefile.fwinst:45: target `/lib/firmware/tsp_stm/stm_z1.fw' given more than once in the same rule.
So I'm confused.
EDIT: Nevermind I'm an idiot. I found it. Thank you so much!! Finally solved
Click to expand...
Click to collapse
Can you tell me what you did? I have the same error and i cant fix it ????
minealex2244 said:
I have the same problem as OP with my S6. This link would help me but it is broken. Can you please provide some info about the commit or another link or whatever?
Click to expand...
Click to collapse
Did you figure it out?
EncryptedCurse said:
Did you figure it out?
Click to expand...
Click to collapse
Uhm somehow. I used a script which ignored that error as your kernel image is already built and you shouldn't care about modules. But if you still want a fix then see my commit: https://github.com/minealex2244/AldeXus/commit/e89301766b3d251b285649a38ee4dea4f2871b99
This commit shows you what to remove (it may be the perfect fix or just an example of what you should do in your code).
Tell me if it helped.
Broken link
Hey, I'm having the same issue but I can't find your commit, could you please fix the link?. Thanks in advance.
4.9 was released and Nexus 5 it's support by mainline kernel
http://www.phoronix.com/scan.php?page=news_item&px=Linux-4.9-ARM-Pull
Interesting. This might bring development back to the phone. Also 4.8 and 4.9 have some amazing features and speed improvements.
Will any dev merge and update our kernel? will this function with our android latest version?
santi1993 said:
Will any dev merge and update our kernel? will this function with our android latest version?
Click to expand...
Click to collapse
No, it's probably not even functional in many aspects, there will be a lot of patching/fixing needed to get it to work.
There is already been discussed about his.
Yes, it's impossible use 4.9 without patch related to panel, exc exc
So what does exactly the "Nexus 5 support" on this kernel mean if you can't run Android on it without patching? Would it potentially help running Linux distros on our devices or?
TheReduxPL said:
So what does exactly the "Nexus 5 support" on this kernel mean if you can't run Android on it without patching? Would it potentially help running Linux distros on our devices or?
Click to expand...
Click to collapse
There is support for the kernel, so yes, you could now run Arch, Debian, OpenWRT, or DD-WRT much more easily.
Android utilizes old libraries that are not compatible with new kernels (that's at least my understanding of the matter), so you would need to patch it to run a newer kernel, and that could only get you so far.
The newest kernel version that anyone had managed to boot Android with is the latest 4.4.x LTS release.
I wonder if someone could backport the necessary changes from 4.9 to the latest 4.4.x release though, that would already be something.
Thank you! I really like the concept of running *WRT on Nexus - I wonder how would functionality like network booting work like...
Could the mainline kernel also be used for other non-Android OSs like Ubuntu (Touch) or Sailfish OS?
TheReduxPL said:
Thank you! I really like the concept of running *WRT on Nexus - I wonder how would functionality like network booting work like...
Could the mainline kernel also be used for other non-Android OSs like Ubuntu (Touch) or Sailfish OS?
Click to expand...
Click to collapse
I don't think so, as they rely on Android bits to work with the bootloader and recovery.
But perhaps there is a chance with the new OS that KDE are cooking, which is supposed to be completely independent of Android.
The 4.10 kernel brings in mainline support for the Nexus 6P and the Nexus 5X.
I wish that mainline support would arrive for the Nexus 4.
moriel5 said:
The newest kernel version that anyone had managed to boot Android with is the latest 4.4.x LTS release.
Click to expand...
Click to collapse
Update: Apparently Android 6.0.x and up can now utilize kernel 4.9.x.
As there is a build of Android 7.1.x for the x86 platform (I have no idea whether it is an official build of Android-x86, nor do I know the precise Android version, though) with a 4.9.x kernel (again, I have no idea precisely which version).
My source is a newly thread opened in the Remix OS forum, in which the OP asks for the possibility of updating the kernel in Remix OS, and mentions that he/she managed to boot it (only in debug mode, though) with the aforementioned kernel.
The source: https://forum.xda-developers.com/remix/remix-os/remix-3-0-207-kernel-t3546057
anyone managed to boot a hh from any kind of 4.9 compilation?
Sent from my Nexus 5 CAF using Tapatalk
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
santi1993 said:
anyone managed to boot a hh from any kind of 4.9 compilation?
Click to expand...
Click to collapse
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
Linux version 4.9.27 ([email protected])
Wow, you are one of the coolest users on there! i doubt anyone could boot it up!
You rock! hope we can get a public release to test it out!
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
Hey that's amazing. I've been working on this too. So where exactly did you enter the command line parameter for console? Can you list out that command?
Sent from my Nexus 5 using XDA Labs
santi1993 said:
Linux version 4.9.27 ([email protected])
Wow, you are one of the coolest users on there! i doubt anyone could boot it up!
You rock! hope we can get a public release to test it out!
Click to expand...
Click to collapse
Thanks for appreciation, but what do you expect from "public release"?
As many other already posted here, this kernel is far away from the 3.4 Images for daily use.
So this is just for fun of course :angel:
Icyphox said:
Hey that's amazing. I've been working on this too. So where exactly did you enter the command line parameter for console? Can you list out that command?
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
Have a look at the tool abootimg.
You could use a bootimg.cfg fle and change the cmdline for your boot image individually.
E.g.:
Code:
bootsize = 0xe48800
pagesize = 0x800
kerneladdr = 0x8000
ramdiskaddr = 0x2900000
secondaddr = 0xf00000
tagsaddr = 0x2700000
name =
cmdline = console=ttyMSM0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 androidboot.selinux=permissive
The other parameters are fixed values for hammerhead... and the bootsize value depends on the size needed for your image.
In this case it's just the default value used for TWRP.
Then use the tool like this:
abootimg --create hammerhead-kernel4.img -f bootimg.cfg -k zImage-dtb -r initrd.img
Best regards,
scholbert
scholbert said:
Thanks for appreciation, but what do you expect from "public release"?
As many other already posted here, this kernel is far away from the 3.4 Images for daily use.
So this is just for fun of course :angel:
Have a look at the tool abootimg.
You could use a bootimg.cfg fle and change the cmdline for your boot image individually.
E.g.:
The other parameters are fixed values for hammerhead... and the bootsize value depends on the size needed for your image.
In this case it's just the default value used for TWRP.
Then use the tool like this:
abootimg --create hammerhead-kernel4.img -f bootimg.cfg -k zImage-dtb -r initrd.img
Best regards,
scholbert
Click to expand...
Click to collapse
Wonderful! The heads-up I needed was the bootimg.cfg. Thanks a bunch. Also, is your ROM usable with this kernel?
Sent from my Nexus 5 using XDA Labs
Icyphox said:
Wonderful! The heads-up I needed was the bootimg.cfg. Thanks a bunch. Also, is your ROM usable with this kernel?
Sent from my Nexus 5 using XDA Labs
Click to expand...
Click to collapse
No far away from any use together with a ROM or even anything the TWRP image uses inside.
No graphics... no usb...
This is just a proof of concept, playing around with the dts files and kernel. Nothing more.
If someone would create a console based ramdisk with some tools included, you may dig a little deeper into the soc or check which parts are responsive or not.
Cheers,
scholbert
It has been quite some time.
Does anyone think that using PostMarketOS's kernel as a stepping stone may help get at least kernel 4.4 to a daily-driver ready status?
Update: Perhaps it would also be a good idea to use the Nexus 7 (2013)'s sources to try porting the newer kernel there to the Nexus 4 (as they share the same SOC).
scholbert said:
Hey folks!
I'm playing around with one of my nexus 5 devices for a while now... right now i got Maru OS installed and it's nice
But anyway this is another story.
Yeah i did!
Used this kernel (which is 4.9.27):
https://git.linaro.org/landing-team...rnel-debian-qcom-dragonboard410c-17.04.tar.gz
... and used Linaro GCC 4.8-2014.04 toolchain (had to use the 32Bit version here).
Then:
make qcom_defconfig
make
make qcom-msm8974-lge-nexus5-hammerhead.dtb
Then later on:
cat arch/arm/boot/zImage arch/arm/boot/dts/qcom-msm8974-lge-nexus5-hammerhead.dtb > arch/arm/boot/zImage-dtb
Then i took twrp-3.0.3-0-hammerhead.img and extracted it with abootimg.
Changed the cmdline parameter for console to console=ttyMSM0,115200,n8
Took the new kernel and rebuild the recovery image to be my test image (just quick'n'dirty)
Then via adb:
reboot bootloader
... and afterwards injected the boot image (e.g.):
fastboot boot hammerhead-kernel4.img
See the attached file for the output.
This log was taken with a serial console cable attached to the earphone plug.
Cheers,
scholbert
Click to expand...
Click to collapse
From the logs, it looks like the reason the boot stops is because of init.rc errors. I might be able to help with that, but my nexus 5's battery is toast.