12952 2018-10-05 07:30:42 +0000 [QA 2.6.M3 rc1 ][BSP/Mturbot] Not able to see login prompt when using serial 2018-11-20 04:08:13 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration 2.6 x86 Multiple RESOLVED WONTFIX Medium+ normal 2.6 M4 1 pankaj-y anuj.mittal yp.bsp.watcher yp.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 81765 0 pankaj-y 2018-10-05 07:30:42 +0000 Information : Able to see BIOS Page using serial connect but not able to see login prompt for serial communication USB, SD and HDD. Steps to reproduce 1) Download the image from following link http://centaurus01.png.intel.com:8080/workspace/andromeda02/yocto-2.6_M3.rc1/genericx86-64/core-image-sato-sdk-genericx86-64.hddimg 2) Create a yocto project image in a HDD example <dd if= core-image-sato-sdk.hddimg of =/dev/sdb> 3) Verify the MTubro board is connected to the host, Connect Minnowboard Turbot board to host machine using serial cabel ( Any linux machine ) 4) Boot the Minnowboard Turbot board using bootable pendrive. 5) Host machine check in /dev/ which device name serial connected. ( default is coming on ttyUSB0 ) 6) Establish connection using "sudo screen /dev/ttyUSB0 115200 on terminal 7) After this serial connection is done successfully, Check the IP In Terminal type $ifconfig" Note : Tried on 2 different setup and rebooted host machine 3 times, observed same issue. Status for 2.6M2RC1 : Pass Bugzilla link for 2.6M2RC1 : https://bugzilla.yoctoproject.org/show_bug.cgi?id=12666 (Pass) Debug information : 1) Issue is not reproducible core-image-sato-sdk.wic image. 2) Debugged by providing console=ttyS0,115200 and console=tty0 in kernel boot line in hddimg image same as mentioned in core-image-sato-sdk.wic image in kernel boot line but not able to see login prompt. 81962 1 anuj.mittal 2018-10-26 01:37:54 +0000 This should work if you add the console on first boot. Else you will have to add the getty entry manually in inittab. Can you check that that works? 82165 2 pankaj-y 2018-11-12 04:18:40 +0000 Issue is not reproducible after adding getty entry manually in /etc/inittab as mentioned below : #1:12345:respawn:/sbin/getty 38400 tty1 1:12345:respawn:/sbin/getty 115200 ttyS0 Should we need to change everytime (ttyS0) or these changes will be merged in further release. 82185 3 anuj.mittal 2018-11-13 09:33:57 +0000 (In reply to comment #2) > Issue is not reproducible after adding getty entry manually in /etc/inittab > as mentioned below : > > #1:12345:respawn:/sbin/getty 38400 tty1 > 1:12345:respawn:/sbin/getty 115200 ttyS0 > > Should we need to change everytime (ttyS0) or these changes will be merged > in further release. Did you also check if this works on first boot after you have flashed the image? 82274 4 anuj.mittal 2018-11-20 04:08:13 +0000 genericx86-64 uses SERIAL_CONSOLES_CHECK on purpose. And that means that if you don't specify a console on first boot, then you will have to do it manually in inittab later. Since the console actually works, I am closing this.