Hi, I'm seeing this when booting up the iMX6 board with the current build (strangely enough, the first build didn't do this):
<6>mmc0: new high speed SDHC card at address e624 <6>mmcblk0: mmc0:e624 SD32G 29.7 GiB <6> mmcblk0: p1 p2 p3 p4 < p5 p6 p7 > <6>EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) <6>EXT4-fs (mmcblk0p5): recovery complete <6>EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null) <6>EXT4-fs (mmcblk0p6): recovery complete <6>EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null) [ Up to here, this is expected and just given as context ] <4>Disabling lock debugging due to kernel taint <3>init: service 'console' requires console <3>init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' <3>init: service 'console' requires console <6>warning: `rild' uses 32-bit capabilities (legacy support in use)
After that, it goes on and boots Android fine, everything works nicely. But there is no console on the serial port. Has anyone run into that "init: service 'console' requires console" thing before?
ttyl bero
2012/2/14 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org
Hi, I'm seeing this when booting up the iMX6 board with the current build (strangely enough, the first build didn't do this):
<6>mmc0: new high speed SDHC card at address e624 <6>mmcblk0: mmc0:e624 SD32G 29.7 GiB <6> mmcblk0: p1 p2 p3 p4 < p5 p6 p7 > <6>EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) <6>EXT4-fs (mmcblk0p5): recovery complete <6>EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null) <6>EXT4-fs (mmcblk0p6): recovery complete <6>EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null) [ Up to here, this is expected and just given as context ] <4>Disabling lock debugging due to kernel taint <3>init: service 'console' requires console <3>init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' <3>init: service 'console' requires console <6>warning: `rild' uses 32-bit capabilities (legacy support in use)
After that, it goes on and boots Android fine, everything works nicely. But there is no console on the serial port. Has anyone run into that "init: service 'console' requires console" thing before?
Please double check "androidboot.console" bootarg.
Regards, Amit Pundir
ttyl bero
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
2012/2/16 Amit Pundir amit.pundir@linaro.org:
[ Up to here, this is expected and just given as context ] <4>Disabling lock debugging due to kernel taint <3>init: service 'console' requires console
After that, it goes on and boots Android fine, everything works nicely. But there is no console on the serial port.
Please double check "androidboot.console" bootarg.
Looks right... console=ttymxc0,115200n8 rootwait ro earlyprintk rootdelay=1 fixrtc nocompcache di1_primary tve init=/init androidboot.console=ttymxc0
John,
Have you seen this?
2012/2/14 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org:
2012/2/16 Amit Pundir amit.pundir@linaro.org:
[ Up to here, this is expected and just given as context ] <4>Disabling lock debugging due to kernel taint <3>init: service 'console' requires console
After that, it goes on and boots Android fine, everything works nicely. But there is no console on the serial port.
Please double check "androidboot.console" bootarg.
Looks right... console=ttymxc0,115200n8 rootwait ro earlyprintk rootdelay=1 fixrtc nocompcache di1_primary tve init=/init androidboot.console=ttymxc0
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On 15 February 2012 14:27, Zach Pfeffer zach.pfeffer@linaro.org wrote:
John,
Have you seen this?
2012/2/14 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org:
2012/2/16 Amit Pundir amit.pundir@linaro.org:
[ Up to here, this is expected and just given as context ] <4>Disabling lock debugging due to kernel taint <3>init: service 'console' requires console
After that, it goes on and boots Android fine, everything works nicely. But there is no console on the serial port.
Please double check "androidboot.console" bootarg.
Looks right... console=ttymxc0,115200n8 rootwait ro earlyprintk rootdelay=1 fixrtc nocompcache di1_primary tve init=/init androidboot.console=ttymxc0
In Ubuntu uboot configs, sabre-lite uses console ttymxc1
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android
On Tue, 2012-02-14 at 22:27 -0800, Zach Pfeffer wrote:
John,
Have you seen this?
2012/2/14 Bernhard Rosenkränzer bernhard.rosenkranzer@linaro.org:
2012/2/16 Amit Pundir amit.pundir@linaro.org:
[ Up to here, this is expected and just given as context ] <4>Disabling lock debugging due to kernel taint <3>init: service 'console' requires console
After that, it goes on and boots Android fine, everything works nicely. But there is no console on the serial port.
Please double check "androidboot.console" bootarg.
Looks right... console=ttymxc0,115200n8 rootwait ro earlyprintk rootdelay=1 fixrtc nocompcache di1_primary tve init=/init androidboot.console=ttymxc0
This isn't ringing any bells to me, but did you make sure you've got the relevant console-over-serial options enabled? For example, on omap there's SERIAL_OMAP_CONSOLE (why this is a board specific option, i don't know...)
thanks -john
linaro-android@lists.linaro.org