线索一 ：
引用老外的一段话：
Job control will be turned off since your shell can not obtain a controlling terminal. This typically happens when you run your shell on /dev/console. The kernel will not provide a controlling terminal on the /dev/console device. Your should run your shell on a normal tty such as tty1 or ttyS0 and everything will work perfectly. If you REALLY want your shell to run on /dev/console, then you can hack your kernel (if you are into that sortof thing) by changing drivers/char/tty_io.c to change the lines where it sets "noctty = 1;" to instead set it to "0". I recommend you instead run your shell on a real console...
线索二：
还是老外的：
Add androidboot.console=ttySn to your kernel commandline, where n is
the number of your console serial port.
The regular console= is
needed by the kernel, and the androidboot.console= probably sets some
property used by the usermode components. It might be possible to use
setprop in init.rc to accomplish the same thing, but I'd have to check
the sources.
现象：触摸屏上是一张左上角为鸭嘴兽的图像，触摸屏上还有显示字母：android，然后就不动了，请教了一位同事，同事说android还没有启动起来，让看下logcat ，结果logcat 也不能看，启动logcat时显示：
unable to open log device "/dev/log/main"……
查看/sys/kernel/logger这个目录，
因为网友说有一个日志开关：
echo 1 > /sys/kernel/logger/log_main/enable
发现根本没有这个目录，
然后看启动信息，从其他网友的资料看到正常android启动时kernel启动信息里应该有这几行：
logger: created 64K log 'log_main'
logger: created 64K log 'log_events'
logger: created 64K log 'log_radio'
OK，我的启动信息里没有这几行，看来这个内核没有编译进去 log 支持，他**的，难道要我重新编译内核？
阅读(2715) | 评论(0) | 转发(0) |
