On 11/29/18 14:12, Udit Kumar wrote: > Thanks Laszlo, > > >> I can only think of some terminal control sequences that are *not* printed to >> the terminal when you don't enter UiApp manually. I don't understand how that >> could cause the exact symptom you describe, but I have no better explanation. >> >> Can you try other serial communication programs on your desktop? Such as >> "minicom" or "screen"? > > Screen didn't help. > Moreover , using different OS distributions show same similar behavior !! > >> Also, can you try changing your "console=..." kernel param(s)? > > You meant baud-rate ?
Yes, and more. The options that the "console=" kernel parameter takes. > > On uefi side, could you help me if there is some extra information passed to > OS in path > UiApp -> BootDevice, I don't think so. Nothing comes to my mind anyway. > I could see , some of additional protocols are installed in above path, I am > not sure if those are > used by OS or OS Loader (grub in my case) somehow. Well, UiApp generally connects all drivers to all devices -- normally a platform BDS would not want to do this, for the sake of booting quickly --, which likely results in more protocol instances being installed in the system. That shouldn't cause a difference for how serial behaves once the OS has booted. Thanks Laszlo _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
