Bootable image for Macchatobin Double Shot?
Mark Murray
markm at FreeBSD.org
Sat Apr 25 16:32:07 UTC 2020
Hi Greg
> On 25 Apr 2020, at 17:12, greg at unrelenting.technology wrote:
>
> Woah, "/home/mw/git/uefi-27" doesn't look like something that should appear in one of my builds..!
>
> I guess flash-image2 is a reupload of an old build from the github wiki, and flash-image was my build,
> but I might have overwritten it with a bad one. *facepalm*
Hehehe! It happens!
> Uploaded a new untested build that should work as
> https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image.bin <https://unrelentingtech.s3.dualstack.eu-west-1.amazonaws.com/flash-image.bin>
> (sha256:8ae81d0cb07b36bd145ae56621e63c48c303641e1cf1a574714ca60211d66c66)
It's different:
UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
map: No mapping found.
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell> pci
pci: Protocol - PciRootBridgeIo not found.
Shell>
I get straight to the UEFI shell, and it won't boot. In the UEFI options pages, the usual list of devices etc is missing:
/------------------------------------------------------------------------------\
| Boot Manager |
\------------------------------------------------------------------------------/
Device Path :
Boot Manager Menu HD(1,GPT,58E6C0D3-86DB
-11EA-ADE5-F5837826388
FreeBSD B,0x28,0x64000)/\EFI\f
UEFI Shell reebsd\loader.efi
Use the <^> and <v> keys to choose a boot option,
the <Enter> key to select a boot option, and the
<Esc> key to exit the Boot Manager Menu.
/------------------------------------------------------------------------------\
| |
| ^v=Move Highlight <Enter>=Select Entry Esc=Exit |
\------------------------------------------------------------------------------/
... but trying to boot just lands me back at the UEFI Shell.
> I really should finally get around to making this a proper "release", with a setting in the Setup screen
> that would allow toggling the ECAM workaround on and off, and toggling the SPCR Linux workaround.
> But first I'd like to switch to upstream TrustedFirmware, but my builds of it (using clang) don't work..
> (This is currently using older Marvell-forked TF-A.)
Can I help in any way? I'm used to big build (but no good at building on Windows).
>>> Also, have you tried any other PCIe cards?
>>
>> Nope - 'fraid not :-(.
>>
>> My intention is to use this dual-port NIC until (if?) the on-board NICs are made to work, then I'll
>> use them and then buy a cheapo PCIe video card to make a proper console I can use with a KVM
>> switch. But I need to get the PCI going first :-)
>
> I've started an attempt at porting the onboard NIC driver last summer:
> https://github.com/myfreeweb/pepevtwo-kmod <https://github.com/myfreeweb/pepevtwo-kmod>
Oooh! Are you amenable to bribery? ;-)
> Got as far as initializing stuff (except DMA) that's initialized before the ports.
Progress is progress!
M
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 556 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20200425/c4b37b7b/attachment.sig>
More information about the freebsd-arm
mailing list