Hi, Danke Thanks for reply.
I'm porting the kernel-msm-.32 on my Tattoo. It has msm7225 board with QVGA screen, which is not supported by android. The board driver was written by HTC for 2.6.29-msm kernel. It seems that to use 2.6.32 kernel on this device, I must port the board driver to kernel-msm. So minimal changes is impossible for my case. Now the result is the ported kernel got stuck on booting and I couldn't get the dmesg from it. The other way I can try is to make the msm7x25/7x27 driver from codeaurora project work on my Tattoo. But right now I have no spare time to realize it. Or would you like to give me some key points of porting? Very appreciated. Regards, On Jul 29, 10:55 am, Danke Xie <[email protected]> wrote: > Hi Jie, > > There are indeed some kernel CONFIG options to enable console support > for a serial tty device. For example, there is one for the serial port > for sure. A serial device usually means it can be used as a tty > terminal, but to be used as a "console", there is additional work on > the driver. So you will see some kernel flags like CONFIG_NETCONSOLE > or CONFIG_SERIAL_MSM_CONSOLE -- they just control the 'console' part > of the driver. Some serial drivers don't have console support, > including some versions of the USB serial driver. If this is the case, > you might not be able to use the USB to get kernel messages -- unless > you add the console support in it. This is probably more work than > getting your current kernel to boot. > > There is no generic way to troubleshoot early boot hangs. I think the > quickest way might be reducing the complexity of the new changes, and > make sure the kernel can boot before adding new features. If there is > still problem with minimal changes, or even the original kernel, I > really don't know... You may just need to double check if the kernel > was compiled and flashed correctly, and if you could get the LCD as a > console, that might help too. > > Thanks, > Danke > > On Jul 28, 7:08 pm, Jie <[email protected]> wrote: > > > > > > > > > Hi, > > > In my case, no way to run 'adb shell' because the kernel got stuck > > before adbd started. > > > As for USB serial port method, I'm not sure whether some special > > CONFIG for the kernel needed or not. What are the detailed steps? > > > On Jul 29, 9:35 am, andrew_esh <[email protected]> wrote: > > > > Download the SDK Toolkit form > > > here:http://developer.android.com/sdk/tools-notes.html > > > > ... and run ddms. Connect the phone via USB, and click on it when it > > > appears in the upper left corner. Watch the colored logcat messages > > > appear in the lower window pane. The messages may give you some > > > indication what's wrong. There are other dumps that can be done from > > > the "Device" menu. > > > > You can also run "adb shell" from the toolkit, and do a "dmesg" to > > > dump the kernel message list. While that would be lower level > > > information, it may help isolate malfunctioning hardware. > > > > Chances are one of the system files has become corrupt, and you will > > > have to wipe the data off the phone and reflash the system. Your > > > service provider should be able to safely step you through that. > > > > On Jul 27, 1:38 pm, doug <[email protected]> wrote: > > > > > Hello, > > > > > My N1 hung on the cross "X" screen after I flashed it with a new boot > > > > image. How do I debug this boot problem? Is there a way to read the > > > > boot sequence off the device to see where it gets stuck? > > > > > Thanks, > > > > doug -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
