Training

When: Every first Sunday of every month -get a ticket- from $15 (Click Here).

Monday, January 12, 2015

Ubuntu 14.10 installation failure

There is a bug report for that:

https://bugs.launchpad.net/ubuntu/+s...r/+bug/1325801

And it's mentioned in the Release Notes:

https://wiki.ubuntu.com/UtopicUnicor...d_post-install

Boot, installation and post-install

The amd64 (Intel x86 64bit) images specifically targeted at Apple
hardware (amd64+mac) are no longer produced. Most Apple computers are
now capable of booting the amd64 image directly using the EFI (not
legacy) boot method so long as their firmware is up to date. If for
some reason your hardware doesn't boot properly using the amd64 image,
make sure you don't have a pending EFI update and if that still
doesn't work, then patch the 64-bit ISO using the software in bug
#1298894 (tested working on Macbook 2,1). Alternatively, simply use
the i386 (32bit) image instead.

Due to changes in syslinux, it is not currently possible to use
usb-creator from 14.04 and earlier releases to write USB images for
14.10; we believe that it is also not possible to use usb-creator from
a 14.10 system to write USB images for earlier releases. For now the
workaround is to use a matching release of Ubuntu to write the images,
but we intend to issue updates soon to work around this
incompatibility. 1325801

Machines with ATI/AMD video cards may be getting blank or entirely
turned off screen at boot. The screen will switch on when the X server
starts. If you need it to turn on prior to that, for example to unlock
an encrypted harddisk hitting ESC twice should reset the video card to
a working state.

An update to shim in 14.10 introduces a bug where, when booting on a
UEFI system with SecureBoot disabled, the boot is delayed for two
seconds and a message "Booting in insecure mode" is displayed on the
screen. This message does not indicate a security problem with Ubuntu
and does not interfere with the operation of the system except for
introducing this boot delay. As a workaround to avoid this boot delay,
users can enable SecureBoot if enabled on their hardware, or if they
do not intend to use SecureBoot at all they can uninstall the
shim-signed package and then rerun the grub-install command. 1384973

No comments: