Is there a SoftIron Overdrive 1000 expert in the house?
Jon Brawn
jon at brawn.org
Sun Dec 24 03:53:57 UTC 2017
> On Dec 21, 2017, at 11:57 AM, Warner Losh <imp at bsdimp.com> wrote:
>
>
>
> On Thu, Dec 21, 2017 at 7:54 AM, Emmanuel Vadot <manu at bidouilliste.com <mailto:manu at bidouilliste.com>> wrote:
> On Thu, 21 Dec 2017 01:12:16 -0600
> Jon Brawn <jon at brawn.org <mailto:jon at brawn.org>> wrote:
>
> > Wotcha!
> >
> > I?ve managed to upset my Overdrive 1000 by trying to upgrade it to 12.0-CURRENT, r326820.
> >
> > It used to boot from the internal hard drive with an older version of 12.0. Now it is unhappy; it now starts up,
> >
> > prints the early info,
> >
> > prints the bit about pressing ESCAPE for boot options, then drops into the UEFI Interactive shell stuff:
> >
> > UEFI Interactive Shell v2.1
> > EDK II
> > UEFI v2.60 (SoftIron Overdrive 1000, 0x00010000)
> > Mapping table
> > FS0: Alias(s):HD0b65535a1:;BLK1:
> > PciRoot(0x1)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(1,GPT,07AA3FF3-E61A-11E7-A2B0-E0FFF70020A6,0x28,0x64000)
> > BLK0: Alias(s):
> > PciRoot(0x1)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)
> > BLK2: Alias(s):
> > PciRoot(0x1)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(2,GPT,07AAD8D0-E61A-11E7-A2B0-E0FFF70020A6,0x64028,0x73F9BFF8)
> > BLK3: Alias(s):
> > PciRoot(0x1)/Pci(0x0,0x0)/Sata(0x1,0xFFFF,0x0)/HD(3,GPT,07AC2C1B-E61A-11E7-A2B0-E0FFF70020A6,0x74000020,0x706D67)
> > Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
> > Shell>
> >
> > Any ideas about what I do to get it to look for the kernel in /dev/ada0p2, in /boot/? ?
> >
> > I?m new to UEFI, having never used it before.
> >
> > Thanks for any help y?all can offer.
> >
> > Jon.
>
> What happens when you directly select the drive in the firmware ?
>
> r326820 is broken for many key scenarios, including zfs boot. Please try r326888 or newer.
>
> Warner
Wotcha!
The latest 12.0-CURRENT was no better when I tried installing it, but I was hit by inspiration, and poked around a bit. It turns out that the efi partition on the SATA boot drive was there, had an msdosfs file system on it, but was missing the efi hierarchy files. I copied the USB memory stick’s efi files over to the SATA drive’s partition, and as if by magic, it now boots. So, it would appear that the thing that is supposed to install the efi files isn’t installing them.
I suppose I now have to learn how to submit a bug ticket - who wants to send me a pointer to the appropriate docs or walk me through it?
Jon.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3848 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20171223/e65840c6/attachment.bin>
More information about the freebsd-arm
mailing list