From owner-freebsd-stable@FreeBSD.ORG Sat Aug 4 05:58:54 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 573F81065675 for ; Sat, 4 Aug 2012 05:58:54 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id D6B438FC23 for ; Sat, 4 Aug 2012 05:58:53 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1139015wgb.31 for ; Fri, 03 Aug 2012 22:58:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cCV09dX6zsB5kYHB8MZVTYUwu0pVmjfjvGtCMnq08zI=; b=Gs8jQ7Tgat3n6c7mK0bvMpebgfIm5Uk+jmfWsycBEygmWmRWaoICL7zevWYSbsVY3i YumuRG+XUthjZh0KIg6qTsCEtJ9sbreBT53lDn6b2uzGeUQEcoZhARprhfRwBSzgpHnQ SfbwhzCIs+hE91C0KONTrYqJS/u1OT++hHV6wv5Ykap5kHOgyJulYhWrhAKvRjWWOXhh 1YWWv5vRq/vk2bep6aogVni99574tpwDOlPsy94oA9zW7q302NaAVLSKH/RTR9XyG5a0 FWY0TfVCH2uoMCjqQAaDVJUe4i1FKuUH9PoTzPyhZRZ8PYwWY6GGuf7dPIdY2IX7Kp1O 9f6Q== MIME-Version: 1.0 Received: by 10.180.106.97 with SMTP id gt1mr2173642wib.5.1344059932475; Fri, 03 Aug 2012 22:58:52 -0700 (PDT) Received: by 10.223.60.147 with HTTP; Fri, 3 Aug 2012 22:58:52 -0700 (PDT) In-Reply-To: <20120804000931.ad04735d9a9966ec1709a3a8@getmail.no> References: <20120324172603.ee066e06.torfinn.ingolfsen@getmail.no> <20120804000931.ad04735d9a9966ec1709a3a8@getmail.no> Date: Fri, 3 Aug 2012 22:58:52 -0700 Message-ID: From: Kevin Oberman To: Torfinn Ingolfsen Content-Type: text/plain; charset=UTF-8 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 9.0 - GPT boot problems? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Aug 2012 05:58:54 -0000 On Fri, Aug 3, 2012 at 3:09 PM, Torfinn Ingolfsen wrote: > Just a short update on this machine (Acer Aspire X1470) and the GPT / UEFI situation. > > Today I set up another partition, EFI system partition. The partyitions now looks like this: > root@kg-vm2# gpart show ada0 > => 34 250069613 ada0 GPT (119G) > 34 128 1 freebsd-boot (64k) > 162 119537664 2 freebsd-ufs (57G) > 119537826 8388608 3 freebsd-swap (4.0G) > 127926434 121634816 4 freebsd-ufs (58G) > 249561250 204800 5 efi (100M) > 249766050 303597 - free - (148M) > > I formatted the partition like this: > root@kg-vm2# newfs_msdos -F32 /dev/ada0p5 > newfs_msdos: trim 50 sectors to adjust to a multiple of 63 > /dev/ada0p5: 204512 sectors in 12782 FAT32 clusters (8192 bytes/cluster) > BytesPerSec=512 SecPerClust=16 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=204750 FATsecs=100 RootCluster=2 FSInfo=1 Backup=2 > > I have tried putting an EFI shell on it (I got the idea from this[1] page, I have tried both the 1.0 and 2.0 x64 shell), like this: > root@kg-vm2# mount -t msdosfs /dev/ada0p5 /mnt > root@kg-vm2# ls -l /mnt > total 848 > drwxr-xr-x 1 root wheel 8192 Aug 3 14:30 EFI > drwxr-xr-x 1 root wheel 8192 Aug 3 16:21 boot > -rwxr-xr-x 1 root wheel 847232 Aug 3 14:56 shellx64.efi > root@kg-vm2# ls -l /mnt/boot > total 760 > -rwxr-xr-x 1 root wheel 771072 Aug 3 16:23 bootx64.efi > root@kg-vm2# ls -l /mnt/EFI > total 16 > drwxr-xr-x 1 root wheel 8192 Aug 3 14:30 FreeBSD > drwxr-xr-x 1 root wheel 8192 Aug 3 15:06 boot > root@kg-vm2# ls -l /mnt/EFI/boot > total 760 > -rwxr-xr-x 1 root wheel 771072 Aug 3 15:29 bootx64.efi > > but no dice - it is not working, it still prints "ERROR: No boot disk has been detected or the disk has failed." > when I try to boot from this disk. > How do I figure out where this UEFI firmware that Acer has put in this machine is getting it's boot manager and or boot loader from? > I tried running 'strings -f' on the BIOS file (sorry, UEFI firmware), that got me all the EFI error messages, but nothing useful. > Googling didn't help either. > > References: > 1) https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface It's not clear from your message, but did you use the gpart bootcode command to write the protective MBR and the gptboot code as documented in the gpart(8) man page? -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com