I guess I have already tried out this yesterday, with no bootup logs 
printed on console. Although at later stage after logging into buildroot, I 
can use dmesg.

Below was the bootargs, I tried:

setenv bootargs root=/dev/nfs rw ip=192.168.0.100 console=ttyS0 
nfsroot=192.168.0.1:/home/xxx/nfsroot

I've triggered a build to recheck it.

BTW, I'm on a slow machine(almost biblical era... 1GB ram) and a single 
change starts 1 hr of module building. Which I do not use anyway :-(
Is there anyway I can avoid and just build the kernel. A small defconfig 
like omap2plus_defconfig. 

Cheers
nagla
 

On Thursday, November 26, 2015 at 12:30:52 AM UTC+5:30, RobertCNelson wrote:
>
> On Wed, Nov 25, 2015 at 12:53 PM, gnu gnu <[email protected] 
> <javascript:>> wrote: 
> > Thanks Robert. 
> > 
> > But I do not quite follow it. You mean I should switch back my bootargs 
> to 
> > ttyO0 while /etc/inittab should be ttyS0 ? 
> > While in omap2plus_defconfig case I had ttyO0 at both places(bootargs 
> and 
> > inittab). Why this has to be this way ? 
>
> Ah crap, sorry: 
>
> U-Boot# setenv bootargs console=ttyS0,115200n8 root=/dev/nfs rw 
> ip=192.168.0.100 nfsroot=192.168.0.1:/home/xxx/nfsroot 
>
> ( i had to deal with the 2.6.33: ttyS2 -> ttyO2 migration so my head 
> will never be sane again with omap serial drivers... ) 
>
>
> CONFIG_SERIAL_8250_OMAP=y needs "ttyS0,115200n8" 
> CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=y  replaces old u-boot/bootloaders 
> "ttyO0,115200n8" -> automatically to "ttyS0,115200n8" 
>
> CONFIG_SERIAL_OMAP=y needs "ttyO0,115200n8" 
> CONFIG_SERIAL_OMAP_CONSOLE=y (this just special for 
> CONFIG_SERIAL_OMAP=y  as CONFIG_SERIAL_8250_xyz just assumes) 
>
> systemd will span a console based on /proc/cmdline 
>
> non-systemd/udev will need this rule: 
>
> https://github.com/rcn-ee/repos/blob/master/bb-customizations/suite/jessie/debian/60-omap-tty.rules
>  
>
> which will automatically create /dev/ttyOx based on /dev/ttySx for 
> compatibility: 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to