Hi,
Mika Westerberg has implemented kdump for OMAP3430 based arm architecture. I want to use kdump in Nexus 4.
I have config the command line as "root=/sdcard maxcpus=1 [email protected] [email protected] ", then I compile the first kernel and the crash capture kernel.
I also cross compiled the kexec-tools for nexus4. However, when I use the kdump tool, I got the error "Cannot find the start of the core dump". Can anyone help me? Thanks!
Related
can anybody tell me how to compile tun.ko for any rom? what would i need to download/install etc? any help would be appreciated. thanks!
get the kernel soruce and check config file for tun
in .config file search for "TUN" keyword, change Y to M, run make menuconfig, save, compile.
slow down guys absolute noob here. how/where do i run makeconfig? what software would i need? sorry if stupid questions :c
Sent from my GT540 using XDA App
daggerxXxsin said:
slow down guys absolute noob here. how/where do i run makeconfig? what software would i need? sorry if stupid questions :c
Sent from my GT540 using XDA App
Click to expand...
Click to collapse
First, you need the kernel source code for your device. The Linux GPL requires that OEMs provide the kernel source so you should be able to find it.
You'll need a linux machine with a development environment. You'll also need the Android NDK for the ARM toolchain.
Once you've got all that lined out, you'll need a kernel config. You can usually get this from your device's proc directory as /proc/config.gz.
Now gunzip the config.gz in your kernel source directory, rename it to ".config" and run "make oldconfig". If it is from an identical source tree, then it should run without prompting.
Now run make menuconfig and drill down to the tun options and enable it as a module. Now you can "make" your kernel and "make modules" for the modules.
okay so first thing is to setup a build environment. gotcha. will work on that.
Sent from my GT540 using XDA App
Gene Poole said:
First, you need the kernel source code for your device. The Linux GPL requires that OEMs provide the kernel source so you should be able to find it.
You'll need a linux machine with a development environment. You'll also need the Android NDK for the ARM toolchain.
Once you've got all that lined out, you'll need a kernel config. You can usually get this from your device's proc directory as /proc/config.gz.
Now gunzip the config.gz in your kernel source directory, rename it to ".config" and run "make oldconfig". If it is from an identical source tree, then it should run without prompting.
Now run make menuconfig and drill down to the tun options and enable it as a module. Now you can "make" your kernel and "make modules" for the modules.
Click to expand...
Click to collapse
Hi Gene, i want to ask, if we cannot find the config.gz file from the device, is it imposibble to get the tun.ko working?
Or if it possible, can you tell me how to gain some configuration, that used by the tun.ko, so we can set the config from menuconfig correctly?
I`ve tried to compile tun.ko for a device, the insmod working fine, but when the vpn try to use the tun, it is crash, it raise segmentation fault.
Hi to all, i'm new in the forum . I want debug android kernel for samsung s3 plus , so i downloaded it from
opensource.samsung.com , i've compiled with this configurations lines :
CONFIG_KGDB (for KGDB)
CONFIG_HAVE_ARCH_KGDB (for KGDB)
CONFIG_CONSOLE_POLL (for Android USB support)
CONFIG_MAGIC_SYSRQ (use sysrq to invoke KGDB)
CONFIG_USB_ANDROID_ACM
KGDB_TESTS_ON_BOOT
CONFIG_DEBUG_KERNEL
CONFIG_DEBUG_INFO
So i try to run kernel compiled using emulator-arm but the emulator is offline.
Where i wrong?
How to launch original kernel in emulator?
Thank you all.
I found some guides online to enable the Linaro Ranchu device, but no matter what I try I can't seem to get it to work in an emulator.
I'm attempting to port a ROM over to the Nexus 5x, which uses an Arm64 processor. However, I'm currently lacking a USB A-to-C cable so my only bet right now is ARM64 emulation. I first read about the possibility using Ranchu on the Linaro website. I understand that the code referenced in that article (and, indeed. the whole ARM64 emulator formerly known as emulator64-arm64 from what I've seen) has since moved to qemu-android.googlesource.com. So, I downloaded the Linaro devices tarball and dropped it into the Android source. This gave me a 'ranchu-eng' lunch combo.
I then used the following process to build the kernel and images:
Code:
cd kernel/goldfish
../../prebuilts/qemu-kernel/build-kernel.sh --arch=arm64 --out=../../prebuilts/qemu-kernel/arm64 --cross=aarch64-linux-genu- --config=ranchu -j8
croot
lunch ranchu-eng
make -j8
This builds without issue, but I can't seem to emulate it for the life of me. Using the commands from that Linaro article, qemu crashes saying something along the lines of "bad address 0x00000024". Trying to run emulator-arm64 results in an error along the lines of '-cpu: option not found'. How can I emulate an ARM64 system? Also, since there are no Arm64 system images any longer (apparently, there used to be there), I can't use an AVD device for the emulator.
How can I do Arm64 emulation for Android development?
Hi,
I'm working on a native application that display the chipsetID.
When i test with a simple application HelloWorld and compile using ndk-build, it work and i found the apk under system/bin. But when i include nexus header,it generate errors "File not found" .
Best Regards.
Hello!
I was trying to port Vanilla Android to a tablet, but am finding it will not launch the kernel that would be required.
I have 3 kernels:
Kernel 3.19 (Aarch64, Gzipped, 2K pages, 7.8 MB, extracted from a lineage build from online) - Launches
Kernel 5.15 (Aarch64, Gzipped, 4K pages, 21.8 MB, from android/kernel/prebuilts/5.15) - Fails
Kernel mainline(Aarch64, Gzipped, 4K pages, 12.0 MB, built from source) - Fails
The 3.19 kernel successfully launches (but is too old to run the OS, and therefore libprocessgroup panics at exec)
Neither the 5.15 kernel nor the mainline kernel launch (they simply hang for a while then reboot, and fail to generate kmsg logs)
This is really confusing me, because all of the kernels target the same architecture, but only one of them actually launches. And the only differences in the generated boot image are the kernel and the page size header.
My only possible idea is maybe they have different built-in drivers? I can't tell because there are no kmsg logs.
The device's processor is a cortex-a7, if that info is of any use.
EDIT: Also, while gzipped Kernel 3.19 launches, it does not launch if it is gunzipped. Which makes me think maybe it's something to do with how much space it takes up? Or maybe the device is very particular about the format?
EDIT 2: Unzipping and re-zipping Kernel 3.19 with max compression and not keep name causes it not to work, making me think maybe it needs to be compressed in some weird method
Also, sorry if this is not the right place to get help with this. XDA is kind of hard to navigate