From owner-freebsd-current@freebsd.org Thu Jan 19 13:56:25 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41C4CCB7ED9 for ; Thu, 19 Jan 2017 13:56:25 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 92A4D16E3 for ; Thu, 19 Jan 2017 13:56:21 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M2tKM-1cE3QS23S2-00seYd; Thu, 19 Jan 2017 14:56:18 +0100 Date: Thu, 19 Jan 2017 14:56:17 +0100 From: "O. Hartmann" To: freebsd-current , freebsd-efi@freebsd.org Subject: CURRENT: UEFI boot does not work on ASrock Z77 M4 Message-ID: <20170119145617.3a321761@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:g+zCFg7K3Tg4VqNyAYOjjX8ffYUygt4pX37S99/MBCcygzc9Jis l/B5oePp1pBFW7Ux2bAfqDOz5SSqGAxS7jvjGpTqZJX5KTvraDhrzsMJfN2xTSZMsWK06Si HpLiQjVFP4LYiZb8kwLGlG5Gc4ai3uXRMkKRtsUYgvKxuoRbXHR6eGbf+ZemQ020vmWAuPT 9ZYwsvaDov98N0AEr9/lQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:vCSk4NcSFLQ=:KQBphWScnMJrfryHB60YwI vKCn3eSjVelm7jrxIUcZCU817Ay4XW3ClNEVOYSO3RYgDUzgU+wG7L1KhYIy1CCt+DmSZFwHu nFof1n0RTk7pHQJmwXNAITxHfzdIoIzZuN2+56x1cAFjkU1VJlWNqTAKg9pNLhWMznkFnRgUN 8b1HPYTJoEzkYL7qJGARTs69Ln3XifJFU1p21ZegnOD+MJapc4n/qUabk683UlSx2VWyWuZ8a ara+dO/y4yqm6312fDzDGdlDQxBbj/yiT3ZvewaePnYXKW1orCwtVaYjAIrFYm4Q8dIjWIqQR fAtYgX/cbAl29OR0InN1DPolSjbrIJceKR6WFqww92ncnAnKg+Cg2bdYTSlz1H89WO/mggIl0 YCyxcN9m5DrE/13ugRFzZzLKwlnBxxSFqIC/VxgoWdUFkZxJf0JOY97k9Fn9eUaY5o5BSe5Q7 zqtDEWbvBbcwyEXli2Pq+L2qzKHQJWfYWuoNfE8Kbgd2KSweNqrYuR9O5ih9fPsBM4P3QgjQO qnbk3jIem5d0GGRc++GLssGHTMi2jrZ68yAQbe9DRFiwM3ver25dqTxecYbS80kmKOIwKnhYT qBAModkQ2FqrNcT9N01bD8Veeq6oOirYGgpx09JxmEokajDeAaQrVGS1g+FPv1+8n4jS3B/wh 8jOKOsWDH33Ur7ovMVTFOmxa1WmQUeV4NAkPR9QpwNRnYSlHO+Gzxf32zbcfZ7hJo3J76ymGy 8wvSOWNC3GQWgcu1qP6BdjyS9W1lgQhDMARgYGkBBS4ZZs74L7yi2mnvmpqVZiYm60t27CiwD 8EQYcGPk/bFRJHCSVlDnSvmf3pFQQ== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2017 13:56:25 -0000 I'm utilizing two systems running FreeBSD Current (most recent) on top of Asrock Z77 M4pro main PCBs (one is the uATX version, the other regular ATX). The firmware is the last one a customer can pick up from Asrock's website and it is dated from 2013. Apart from the fact that the hardware is not useful for any reliable system, I'm out of resources to exchange these systems with more modern hardware. The problem I face is with UEFI. Both boxes do have their OS on SSD (Samsung 850Pro and Samsung 830). I've created a EFI partition of 800k in size with gpart and it is the first one on the SSD. Both SSDs are UFS and GPT. The partiton starts at block 40. Such a configuration works with the very same SSD fine with more modern hardware (checked with a Fujitsu Celsius M740/UEFI). But the crap Asrock rejects to boot UEFI. I tried to prepare a hdd the same way - no success. The funny part is that any USB thumbdrive with UEFI boot only is booting UEFI as expected and several Windows 8 or Windows 10 DVDs seem to have no problem. Maybe the location of the EFI partition (starting block) keeps the secret to success, but I failed to put the partition at a proper starting point. On the other hand, all SSDs I have prepared so far for UEFI booting, start their efi partition with block 40 and they boot. The big question is: what is the efford to fix this issue - if their will be a fixing ever? The firmware of those boxes is really as minimal as possible regarding to options for UEFI booting - but it is fancy coloured ;-) Many thanks in advance, Oliver