I faced the same issue. I have built my rootfs using buildroot. The kernel image, MLO, and UBoot were built externally. And also the toolchain were used externally.
In my case, after the kernel boots(NFS-boot), before the login prompt, the serial terminal fails and the error is printed continuously "Can't open /dev/ttyO0. No such file or directory". And I coudnt operate the system with my terminal(minicom). Luckily I installed ssh, so I could log in to the system using ssh. Then I used dmesg to see some logs: # dmesg | grep tty I found this message: WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0' So I just tried to rename my ttyS0 with ttyO0 back again. Magically my serial terminal was back to control. I don't know the details of how it worked but it did work. All I have to find out is to let the kernel identify the appropriate tty device file correctly. FYI, I am a beginner in Embedded Linux and Linux kernel as a whole so please bear with me. Thank you. On Friday, 5 August 2011 19:31:39 UTC+5:30, gerard_mp wrote: > > Hello, > > I've successfully built Kernel 3.0, using the patches provided in meta- > texasinstruments GIT repo. I've also built U-boot 2011.06 (also with > some patches from the same repo). Finally, I've build a base file > system using build-root. Everything seems to work well, Kernel shows > all messages, network turns up, but when it is to launch getty for > login prompt, it stucks forever showing each second: > > can't open /dev/ttyO2: No such file or directory > can't open /dev/ttyO2: No such file or directory > ... > > Is there a known solution for that? May I should attach more details? > > Thanks! -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/754d959c-169a-424f-9213-a1fecf66d2c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
