Unable to install from text mode interface

Status changed to 'Confirmed' because the bug affects multiple users.

The workaround from https://github.com/boxcutter/ubuntu/issues/22 works.

Instead of pressing escape twice and enter to enter text mode do select your language and push F6, enter and escape to enable expert mode and then remove everything from Boot Options and then add the above line:

  /install/vmlinuz auto url=http://10.0.2.2:8081/ubuntu-15-04.cfg debian-installer=en_US locale=en_US kbd-chooser/method=us hostname=myhostname keyboard-configuration/modelcode=SKIP keyboard-configuration/layout=USA keyboard-configuration/variant=USA initrd=/install/initrd.gz --

This is still an issue on Xenial, I'm setting this to high and targeting to 16.04 milestone as per Robie's triage of the dupe (bug 1537252)

Hope to see this fixed for 16.04! Happy hacking guys! :-D

Just confirmed that this bug is still present in xenial-server-* builds as of March 2.

And it is not even assigned, no one is working on this?

Just tried building http://cdimage.ubuntu.com/ubuntu-server/daily/current/xenial-server-amd64.iso (dated 14th March) and it still has this bug.

The workaround posted by "andrewsomething" at: https://github.com/boxcutter/ubuntu/issues/22 still works.

Ian

It will be a shame to release Xenial with this bug opened... =/

This really seems to be an issue with packer, and not the Ubuntu installer.

May I suggest a better alternative. Instead of using packer why not use the ubuntu cloud images available
http://cloud-images.ubuntu.com/

or use virt-install and the netboot installers a.la.
virt-install \
        --connect qemu:///system \
        --virt-type kvm \
        --name demo \
        --ram 2048 \
        --disk size=10 \
        --graphics vnc \
        -l ftp://ftp.utexas.edu/pub/ubuntu/dists/trusty/main/installer-amd64/ \
       --os-variant ubuntutrusty

The ubuntu text mode installer is a pretty pristine fork from debian, and as such I don't think we should be fixing this in Ubuntu.

Ubuntu has version 20101020ubuntu445 of debian-installer while Debian has 20160106. That seems to imply that it it was forked years ago without re-syncing on Debian.

Yes, it hits Packer users but it certainly isn't limited to Packer. As I mention in the original report, I can reproduce it booting the ISO manually as well.

I can confirm this is a bug with Ubuntu and is perfectly reproducible without Packer.

Dave Chiluk, you're wrong, this problem is perfectly reproducible without Packer.

This is an Ubuntu BUG, for sure. Might be present on Debian as well but, I didn't tested it on Debian.

What I know is that "install from text mode interface" does not work anymore on Ubuntu, with or without Packer.

It may be true that this represents a bug in the syslinux package. But from an Ubuntu user experience POV, this is undocumented behavior - I didn't know that hitting 'esc' at that screen did anything, and we have never had a 'text mode interface' as part of the supported UI. The supported interface is the F6 "extra boot options" interface which is being described here as a "workaround".

A quick bit of testing shows that this regressed between ubuntu-15.04-server-amd64.iso and ubuntu-15.10-server-amd64.iso .
So:

WORKS: ubuntu-14.04.4-server-amd64.iso
WORKS: ubuntu-15.04-server-amd64.iso
FAILS: ubuntu-15.10-server-amd64.iso
FAILS: xenial-server-amd64-daily-20160411.2.iso

Thats good, because it means if the regression was in syslinux, then it was between 3:6.03+dfsg-5ubuntu1 and 3:6.03+dfsg-8ubuntu2 (there was a major version bump in syslinux between trusty and but it still seems to work in vivid. so that is good):

$ rmadison syslinux
 syslinux | 2:4.05+dfsg-2 | precise | source, amd64, i386
 syslinux | 3:4.05+dfsg-6+deb8u1 | trusty | source, amd64, i386
 syslinux | 3:6.03+dfsg-5ubuntu1 | vivid | source, amd64, i386
 syslinux | 3:6.03+dfsg-8ubuntu2 | wily | source, amd64, i386
 syslinux | 3:6.03+dfsg-11ubuntu1 | xenial | source, amd64, i386

There was some conversation on irc yesterday.
 http://irclogs.ubuntu.com/2016/04/11/%23ubuntu-devel.html#t20:18
cjwatson suggested likely gfxboot-theme-ubuntu as the bug component.

Status changed to 'Confirmed' because the bug affects multiple users.

just for some more info, I asked for clarification from cjwatson.
 $ rmadison gfx-boot-theme-ubuntu
 gfxboot-theme-ubuntu | 0.13.2 | precise | source, amd64, i386
 gfxboot-theme-ubuntu | 0.13.3 | precise-updates | source, amd64, i386
 gfxboot-theme-ubuntu | 0.16.1 | trusty | source, amd64, i386
 gfxboot-theme-ubuntu | 0.18.0 | vivid | source, amd64, i386
 gfxboot-theme-ubuntu | 0.18.0 | wily | source, amd64, i386
 gfxboot-theme-ubuntu | 0.20.0 | xenial | source, amd64, i386

Even though gfx-boot-theme-ubuntu did nto change from vivid to wily where the regression occurred, cjwatson suggests that it still may be the cause of the issue as gfxboot-theme-ubuntu and syslinux are very tightly related.

16.10 this works as expected.

Status changed to 'Confirmed' because the bug affects multiple users.

Per former comment by Rickard we can consider Dev fixed, yet one might want to look into Xenial.

Status changed to 'Confirmed' because the bug affects multiple users.