[PATCH] Remove loglevel from default kernel boot arguments to let kernel using it's default configuration.

Paul Fertser fercerpav at gmail.com
Wed Jun 10 18:55:57 CEST 2009

Yorick Moko <yorickmoko at gmail.com> writes:
> I can confirm this (bootin shr-unstable from SD)
> root at om-gta02 /proc $ cat /proc/cmdline
> loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro
> mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(depr-ub-env),0x00800000(kernel),0x000a0000(depr),0x00040000(identity-ext2),0x0f6a0000(rootfs)
>  g_ether.dev_addr=00:1F:11:01:08:10
> g_ether.host_addr=00:1F:11:01:08:11  root=/dev/mmcblk0p1 rootdelay=1
> loglevel=1 quiet splash
> it doesn't seem to make sense passing loglevel twice
> as a result, my splash screen is disturbed by a blinking cursor

AFAICT passing loglevel twice is ok and worked in the past.

Those extra messages disturbing splash screen are mostly left from
debugging. I'm going to take care of those i see running with
loglevel=4. I'm not sure what to do with g_ether messages when g_ether
is compiled as a module though.

Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav at gmail.com

More information about the openmoko-kernel mailing list