Hi Nandi, Are you sure you have ttyS0 port available on your hardware? Also in serial port parameters, number of bits is missing, generally we give, console=ttyS0,115200n8
-br Arun On Thursday, 25 October 2012 04:49:05 UTC+1, Nandi wrote: > > I am not able to get into tty shell. > > I have the proper kernel commandline parameters: > console=ttyS0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 rw rootdelay=2 > loglevel=8 panic=10 > > And also init.rc has the console service: > service console /system/bin/sh /dev/ttyS0 > class core > console > > But I am unable to open tty shell. What am I missing? > > (I have the Rx connection wired properly) > > Thanks > -N > > On Wednesday, October 24, 2012 3:39:27 AM UTC+5:30, Weston Weems wrote: >> >> On my hardware I've got serial tty, I was able to get a tty shell, and >> issue logcat once I was in. I made me realize that the latest head has >> changes to timezone file generation that caused issues. >> >> Also in init.rc you can change loglevel 3 to loglevel8, and you'll get a >> bit better output. >> >> >> Weston >> >> >> >> On Tuesday, October 23, 2012 3:21:38 AM UTC-7, Nandi wrote: >>> >>> I am battling a similar issue and one of the method I am using is to >>> boot with a minimal init.rc and see which is one is contributing to the >>> issue by doing >>> further debugging on the adb shell. >>> >>> However in my case, I am unable to get to adb shell since the adbd >>> itself is exiting :(. Let me know if you have any success and I would like >>> to learn >>> from your experience. >>> >>> -N >>> >>> On Monday, October 22, 2012 9:09:37 AM UTC+5:30, Weston Weems wrote: >>>> >>>> With the exception of earlyprintk and logwrapper stuff, is there >>>> anything I can do to diagnose a booting problem? I am getting "an >>>> untracked >>>> pid exitted" and get stuck at the android logo. >>>> >>>> Any ideas? >>>> >>>> Weston >>>> >>> -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
