** Changed in: ubiquity (Ubuntu Xenial)
Status: Confirmed => Incomplete
** Changed in: ubiquity (Ubuntu Yakkety)
Status: New => Incomplete
** Branch unlinked: lp:~jsmith-hongduc/+junk/thesun...@yahoo.com
--
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:~jsmith-hongduc/+junk/thesun...@yahoo.com
** Changed in: ubiquity (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: ubiquity (Ubuntu Yakkety)
Status: Incomplete => New
** Changed in: ubiquity (Ubuntu Xenial)
Status: Confirmed => Incomplete
Even simpler than that, could you boot on a LiveCD/DVD (as above; trying
to boot in UEFI mode); and tell us what are the contents of
/sys/firmware/efi/efivars, and if it exists?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As stated partway through the thread, after submitting the bug report
through the automated tool, I wiped the boot partition & performed a
clean install of 16.04, during which I did not select the option for 3rd
party drivers (which I had selected previously). The resulting
installation ran
Following your reinstallation, do you still get that error on
boot/login?
What does running 'archdetect' report?
Also, could you please attach /var/log/installer/syslog on this bug
report, in case we can get any information from it that would help in
fixing the bug for others?
Thanks!
--
You
dmesg shows the bios e820 memory map and the dpkg history shows that
grub-pc is currently installed, so yea, it is booting in bios mode and
for some reason, is trying to switch to efi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh, good point. I was operating under the false assumption that we did
ship two separate copies of the kernel as on the installed system.
Still, there is no reason for the system to ever try to run efibootmgr /
install grub-efi-amd64 unless it detects being booted in EFI mode, and
where
On Mon, May 16, 2016 at 08:15:29PM -, Mathieu Trudel-Lapierre wrote:
> I'm not convinced that this isn't an EFI system.
> The CD used here looks like it was booted in EFI mode:
> [0.00] Command line: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/ubuntu.seed boot=casper
When you select to install 3rd-party drivers, you do not *have to*
disable Secure Boot. We just recommend it because it is likely to be
necessary for the 3rd-party drivers to work correctly.
So it sound like you've uncovered an issue in the installer for the
third-party drivers case when we try
>From taking a look at the motherboard manual, this is an EFI system (UEFI
BIOS). The system was built by a local independent integrator. The
motherboard is ASUS Q87M-E.
On Mon, May 16, 2016 at 1:15 PM, Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> I'm not convinced that this isn't
I'm not convinced that this isn't an EFI system.
The CD used here looks like it was booted in EFI mode:
[0.00] Command line: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
And that there was some EFI data available to the system
Thank you for looking into this. To clarify, I had attempted an in-place
update from 15.10 to 16.04. The update experienced some errors along the
way, but on reboot I was nonetheless in 16.04. But now I got a series of
error reports upon login (it never showed me the details).
In an attempt to
What I can see in the logs is this request for packages from the
ubiquity installer:
Start-Date: 2016-05-16 09:28:12
Requested-By: ubuntu (999)
Install: intel-microcode:amd64 (3.20151106.1), iucode-tool:amd64 (1.5.1-1,
automatic)
End-Date: 2016-05-16 09:28:19
Followed 5 seconds later by a
Sorry, when you say "upgrade or reinstall", what do you mean? You mean
you saw this error on an upgrade, and also again after reinstalling the
system?
The error message shows that you are installing the shim-signed package
on a system that is not booted in EFI mode. We should fix this to not
14 matches
Mail list logo
