Public bug reported: Compared to d-i - where parmfile modifications are not necessarily needed, the question is, if this can be again the same for subiquity?
At the very least, the current state definitely needs documentation - otherwise customers will try to install and it will fail without any indication what went wrong. On top of that, it would be nice if the installer could at least give a helpful message pointing out that the user will have to modify their parmfile for the installation to work. Of course the best solution would be to add code to the installer to prompt for the necessary information like before. Addl reference information: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1854513 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-185593 severity-high targetmilestone-inin2004 ** Tags added: architecture-s39064 bugnameltc-185593 severity-high targetmilestone-inin2004 ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875309 Title: [UBUNTU 20.04] Add notification in case subiquity got booted on s390x w/o a parmfile in place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875309/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
