On 02/10/2014 15:21, Michel Stam wrote:
> Early during bootup, kmodloader is started which loads the drivers
> in /etc/modules.d. Unfortunately at this time the system script has
> not run yet, which is supposed to set the console log level.
> Having the S10system script moved to an earlier time is not an
> option, as this in turn will not work because the system script
> will try to register itself with ubusd, which is not running
> either. This only happens after S12log is run.
we actually want to see these messages.
procd is supposed to wait for ubusd which it apparently did not do, so i
just wrote a patch to fix this problem.
>
> As a quick fix, temporarily show only errors and more severe
> messages. S10system will quickly fix that shortly after,
> at least the bootup is more sane (and readable).
>
> Signed-off-by: Michel Stam <m.s...@fugro.nl>
> ---
> package/base-files/files/etc/init.d/boot | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/base-files/files/etc/init.d/boot
> b/package/base-files/files/etc/init.d/boot
> index f10db13..9223807 100755
> --- a/package/base-files/files/etc/init.d/boot
> +++ b/package/base-files/files/etc/init.d/boot
> @@ -35,6 +35,9 @@ boot() {
> grep -q debugfs /proc/filesystems && /bin/mount -o noatime -t debugfs
> debugfs /sys/kernel/debug
> [ "$FAILSAFE" = "true" ] && touch /tmp/.failsafe
>
> + # Prevent module load messages from flooding the boot process; 'system'
> service will fix this
> + /bin/dmesg -n 3
> +
> /sbin/kmodloader
>
> # allow wifi modules time to settle
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
