Hi Khem, On Aug 2, 2012, at 2:37 AM, Khem Raj wrote:
> On Aug 1, 2012, at 9:18 AM, Elvis Dowson <[email protected]> wrote: > >> Hi, >> Perhaps the reason none of my root file system binaries are not working >> or running is because there is no >> >> GLIBCTARGETOS ?= "linux-gnueabi" >> >> in my machine/virtex5.conf or local.conf file? > > you don't need to set it. it should be automatically computed based on libc > and arch > your problem seems more like console related. Probably you don't have console > params > set correctly or securetty does not know about your console device. You're right. After rebuilding it, with that variable set, it made no difference in the generated binaries, (e.g. generate a tool chain powerpc-poky-linux-gnueabi-gcc) nor did it change the situation with my having no console login or bash prompt. The serial port that I am using is ttyS0. There is an entry for ttyS0 under /dev in my ramdisk , and my /etc/device_table also has an entry for ttyS. I have also checked that my securetty has an entry for ttyS0. I have tried all possible option, e.g. try to get inittab running first with S:2345:respawn:/sbin/getty 9600 ttyS0 then with S:2345:respawn:/bin/sh 9600 ttyS0 and then after that didn't work, tried kernel bootargs with init=/bin/sh or init=/sbin/getty I have even enabled verbose kernel driver debug messages and it appears to be correctly registering the driver, and doing everything correct at the kernel level, but the moment it hits init, it doesn't display anything on the console. This appear to work fine, displaying output on the ttyS0 console, as specified in the device tree upto the point just before it attempts to run init. As soon as init runs, I get no output on the console, in terms of a login prompt or a bash prompt. You can see detailed kernel bootlogs output from gdb here: http://forums.xilinx.com/t5/Embedded-Linux/PowerPC-kernel-fails-to-boot-with-linux-3-3-0-using-xps/td-p/251194/page/2 Best regards, Elvis Dowson _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
