[Bug 192184] New: [uefi] fresh install of 2014-07-14 11.0-CURRENT amd64 snapshot doesn't boot

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jul 28 09:41:33 UTC 2014


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192184

            Bug ID: 192184
           Summary: [uefi] fresh install of 2014-07-14 11.0-CURRENT amd64
                    snapshot doesn't boot
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: dch at skunkwerks.at

Created attachment 145067
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145067&action=edit
dmesg

# Objective

install FreeBSD 11.0-CURRENT to 80Gb external USB drive

# Expected Result

After standard UFS install, system boots into FreeBSD.

previous snapshot
http://ftp.at.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/FreeBSD-11.0-CURRENT-amd64-VT-20140614-r267488-memstick-uefi.img.xz
works as expected.

dmesg from working boot attached, see
https://gist.github.com/dch/22c28211c539a6d612a4 for further info x11 related
info being discussed in x11 issue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191206

# Actual Result

Installing via burned ISO from current snapshot
http://ftp.at.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/FreeBSD-11.0-CURRENT-amd64-20140714-r268622-disc1.iso.xz
completes installation successfully but is unable to boot the kernel from the
resulting system.

It is possible to get to the loader, e.g. and run:

    mode 2
    set boot_verbose="YES"

However no additional output is received with this flag on.

Last successful message is:

Booting… Start @ 0xffffffff802db000 …

The previous snapshot's next message starts with "EFI Framebuffer", hopefully
that helps.

It's not just a video / display issue, the network port / IP doesn't come alive
either.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list