Hi all,
I'm trying to rebuild the kernel for LG Optimus P500 with "IP: multicast routing" and "802.1d Ethernet Bridging" enabled (both under Networking support -> Networking options").
I used the NDK r5b to recompile and I successfully flashed the kernel with the multicast routing enabled using the mik9 kernel 2.6.32.9 sources and its template (http://forum.xda-developers.com/showthread.php?t=929941), so I suppose the entire process of reconfigure/rebuild/reflash the kernel should be correct.
The problem is that if I try to enable the ethernet bridge support in the kernel (either as a module or statically) and reflash it, when I turn on my P500, it stucks on the "ANDROID" splash and reboots after a while.
Is there anybody who has experienced something like that before? Do you have any suggestion to try to figure this out?
Thanks in advance.
You shiuld look into kernel messages (adb shellc at /proc/kmesg) and logcat (adb shell logcat) while its booting.
Related
The Story started when i wanted to install Drivers for USB OTG on my Droid, And now im ended up by a black hole, im completely lost
What i've Researched/Understand:
1.Kernel is a Bridge between Software and Hardware
2.Drivers must be included in Kernel
3.To Load Drivers, We Need to Extends The Functionality of the Kernel using Some *KO Files Through some Command-Line Commands
What i Have:
1.Source Code for my Phone Kernel
2.Driver for the Device that will be connected Over USB OTG
3.A Rooted Phone
4."Tenda W541U" Is the Device will be connected Through USB OTG and it's chipset is "RT2070L"
What I'm not understanding/Asking for:
1.How can i make these *KO Files?
2.Do i need to make them from Scratch?
3.How to Load them?
4.Will this modify My Kernel Permanently?
5.Do i need Unlocked bootloader?
Hi,
I initially started out debugging with GDB and got to a point where I wanted to be able to step into an android module/device driver. I could never successfully do it with it GDB so I did lots of searching and found out about KGDB which from all accounts is supposed to be the preferred way of debugging the kernel and modules in Linux based machines. I went through the exercise of getting KGDB cross compiled and inserted on my device and that part went ok. When I try to communicate to the device via GDB (target remote /dev/ttyHSL0) I get a device not found error message even though the file is there when I look at it via adb.
(gdb) target remote /dev/ttyHSL0
/dev/ttyHSL0: No such file or directory.
After doing more investigation and thinking about things a little we know that the way to communicate via an Android handset is with adb so this in itself is probably an indication as to why it's difficult to communicate to the device via KGDB.
Does anyone have any up to date or successful instructions on how to connect to a handset using KGDB?
Thanks
hello everyone, i'm trying to use tl-wn722n in my samsung gt-i9100. i downloaded the cm-10.2 source code, and modified the kernel config (add mac80211 and ath9k, kernel version 3.0.64).
during the compile, there are a lot of errors. i compared the kernel with original linux-3.0.64, made some changes, and succeeded getting the boot.img.
after flashing the kernel to my phone, i plug in the tl-wn722n, checked the kernel log, and it said: htc_9271.fw not found.
then i put the htc_9271.fw into /system/etc/firmware, and plug in tl-wn722n again, the phone rebooted. i tried many times, and the phone kept rebooting, and i couldn't even get the kernel log information.
i guess the ath9k driver didn't work correctly, but i don't know what to do, any one can help ?
Hi,
I'm wondering if anyone could help?
My device is a HTC Desire 620, single sim (a31lu).
I have managed to install a custom recovery, root, and flash lollipop using Patrik.KT's build (the only available custom ROM for this particular device).
When my phone is on it's stock firmware, (KK 4.4, Sense 6, I believe), USB tethering works flawlessly with my Asus rt56u, and I'm able to share my internet connection.
When I'm on Lollipop, the USB tethering option stays greyed out and it fails to connect. I've tried it on a PC, and it recognises the device, but it then makes the sound as if I have removed the USB cable.
I have tried modifying the build.prop for net.provisioning and the settings for settings.db for tethering_dun_required=0 that are available anywhere on the interweb, to no avail.
Could this be a kernel problem? I've had this happen on an old S3 and a change of kernel was able to resolve the issue, but there are no kernels available for this phone.
Could anyone please help?
Many thanks.
Is anyone able to help at all?
Hi guys i'm building LineageOS for the Razer Forge TV.
The rom build and run fine but with several bugs. For example, the led driver. This is the custom driver writen by Razer: Led Kernel Driver, works perfect on stock rom, but doesn't seems to work at all on Lineage.
The glow led has two instances, on and off nothing else. Is controlled by an proprietary app. The only job for this app it's write in the proc file system when the device sleep or wake up. When the device sleeps the app do this work "echo 1 > /proc/led_device" and when wake up this "echo 255 > /proc/led_device".
This command doesn't work in my custom rom (the led is always on), at all, even if i put manually via adb. No errors/selinux denials on logcat or dmesg.
Any clue or idea? Thanks
EDIT:
I just found out something. All Razer drivers included in the kernel, doen't work properly on LineageOS. So, the led doesnt shutdown the usb port doesnt switch into debug mode and hdmi edid doesn't collect the right information
https://github.com/gabrielgagz/android_kernel_pearlyn/tree/cm-14.1/drivers/misc
Another clue is that the kernel apearently comes from CAF. Razer publish the kernel in a compressed tgz instead some git repo.
So as far i see the sources comes from Code Aurora. I still can´t indentify the branch or tree...
BTW, the only things wich doesn't work properly are the drivers pushed by the vendor...