Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 01 Sep 2015 10:05:01 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 202811] FreeBSD can't boot on UEFI with AMD hardware
Message-ID:  <bug-202811-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202811

            Bug ID: 202811
           Summary: FreeBSD can't boot on UEFI with AMD hardware
           Product: Base System
           Version: 10.2-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: simonthoby@gmail.com

Hi,

I currently can't install FreeBSD on my computer because UEFI seeems to doesn't
work with FreeBSD (while It works well with many Linux distros). I ran into
this: http://i.imgur.com/YnT2Wr9.jpg. (You could also find a video of my
problem here: http://www.dailymotion.com/video/x33uid3_bootup-bsd_tech).
This is the same bug that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193672 but it's marked as
corrected.

After viewing the issue on bugzilla, I also tried to start FreeBSD on UEFI in
Virtualbox and it give me almost the same issue:
http://i.imgur.com/I9b1R3O.png.

Note: I tried the install on my hardware with
FreeBSD-10.2-RELEASE-amd64-uefi-memstick.img and VBox with
FreeBSD-10.2-RELEASE-amd64-uefi-disc1.iso.

My hardware:
- CPU: AMD FX-8350
- Motherboard: Gigabyte GA-990XA-UD3 with UEFI 2.31 (UEFI updated with the
2014/10/29 UEFI on gigabyte website)
- RAM: Kingston HyperX Fury 8GB 1866Mhz CL10
- GPU: Sapphire R9 270X Dual-X OC

I should mention that using "set boot_verbose" just before the boot doesn't
print any other message that the one showed in the photo, so I couldn't obtain
much information. I don't own a serial cable nor another computer so I can't
get log from serial console.
I had written the image on a usb stick using dd like that: " dd if=/path/to/img
of=/dev/sdc bs=4M"

Maybe someone have some idea on where does this bug come from or hwo to solve
it ? (maybe disabling some UEFI option or adding some flag to the kernel ?)

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202811-8>