I'm closing this bug because Ubiquity is not the server installer
anymore and the d-i based installer for server has been replaced by
subiquity.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Rushikesh Deore (rushi0205)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296883
Title:
Trusty server OEM mode hangs at first boot
** Description changed:
When doing a server install with the latest Trusty daily (2014-03-24) in
OEM mode, the boot hangs during the first boot after the install. Please
see the attached screenshot.
At the time when it hangs, this is the final output on the console:
* Starting
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296883
Title:
Trusty server OEM mode hangs at first boot
To manage notifications
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296883
Title:
Trusty server OEM mode hangs at first boot
To manage notifications
The attached patch should completely work around this issue.
** Patch added: switch to vt1 if not running oem-config
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1296883/+attachment/4201624/+files/oem-config.conf.patch
--
You received this bug notification because you are a
The attachment switch to vt1 if not running oem-config seems to be a
patch. If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user
@jderose
There's another bug you'll get bitten by, along with a workaround:
https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1362920
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296883
@jderose
Assuming the VT switch works for you, and assuming that you're not working with
a GUI, you'll end up getting bit by another bug:
https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1361595
The referenced bug report does have a patch that fixes the issue. Seems
that the upstart
Have you tried swtiching to other virtual terminals? I believe I was
experiencing the same issue, only to find that the display was stuck on
vt7 for some reason, but there were in fact logins waiting on vts 1-6.
Adding text to the kernel command line seems to mitigate this issue in
my case.
--
@jcollins... interesting, I'll give that a try. Thanks!
I'm installing into a VM (golden image mastering for Sytem76), so vt
switching is a bit less obvious there :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It renders the system temporarily or permanently unusable.
** Changed in: ubiquity (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296883
Title:
Trusty
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1296883
Title:
13 matches
Mail list logo
