[Bug 1611921] Re: no serial console after reboot in do-release-upgrade (14.04)

[Leroy Tennison]

Clarifying "Connected to console port (RJ45) via minicom using 115200
8N1" since it may be confusing.  The connection to the device's console
port (an RJ45 physical connector) was via a USB-to-serial converter
cable connected to a serial-to-RJ45 cable provided by Axiomtek.  The
connecting laptop used minicom with serial port /dev/ttyUSB0 with 115200
8N1 for communication parameters.  This connection worked before reboot
(it was used to launch do-release-upgrade).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1611921

Title:
  no serial console after reboot in do-release-upgrade (14.04)

Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Hardware: headless device (Axiomtek NA-330)
  Connected to console port (RJ45) via minicom using 115200 8N1
  In Ubuntu 14.04 LTS run do-release-upgrade (to Ubuntu 16.04.1 LTS)
  At end, confirm reboot
  No serial console after that (fortunately the network connection came up allowing ssh access)
  Debugging/work-around:
     /etc/default/grub contained GRUB_TERMINAL=serial and
       GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1"
       which was reflected in /boot/grub/grub.cfg
     dmesg | grep tty produced
        [    0.000000] console [tty0] enabled
        [    1.612175] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
        [    1.632768] 00:03: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
     systemctl enable console-getty.service
     systemctl enable serial-getty at ttyS0.service
     systemctl start console-getty.service
     systemctl start serial-getty at ttyS0.service
     Ctrl-A F in minicom returned the login prompt which hadn't worked previously

  After the work-around the console port turned out to be ttyS0 so some
  of the above may not be necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1611921/+subscriptions