These are my notes about the Seeed Studio Odyssey X86J4105 board.
See firmware.
Be aware that (non)-composite USB keyboards can only be used to enter the BIOS (by pressing the DELETE key) when Fast Boot is disabled (which is the default after a BIOS Restore Defaults).
Make sure you enable the Wake-On-LAN feature in the Chipset page of the firmware:
Then you can send a Wake-On-LAN "Magic Packet" from a local network interface to one of the odyssey network interfaces mac addresses, e.g.:
sudo etherwake -i enp3s0 00:e0:4c:01:93:a8Since the board ships with Windows 10 pre-installed, the UEFI bootloader
retains the Windows Boot Manager entry as seen by:
efibootmgr --verboseThe command should return the current boot settings, something alike:
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001,0002,0000,0005
Boot0000* Windows Boot Manager HD(1,GPT,93faa71b-80e1-42f4-a7dd-0fb3a1c1a75e,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0001* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0002* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\UBUNTU\GRUBX64.EFI)..BO
Manually remove the Boot0000 entry with:
efibootmgr --verbose --bootnum 0000 --delete-bootnumThe command should return the current boot settings, something alike:
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0001,0002,0005
Boot0001* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0002* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
Boot0005* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\UBUNTU\GRUBX64.EFI)..BO
Or better yet, remove all entries, as in my case:
efibootmgr --verbose --bootnum 0001 --delete-bootnum
efibootmgr --verbose --bootnum 0002 --delete-bootnum
efibootmgr --verbose --bootnum 0005 --delete-bootnumDelete the boot order (grub-install will re-create it):
efibootmgr --verbose --delete-bootorderThen reinstall the ubuntu boot entry with:
grub-installThe end result should be:
BootCurrent: 0001
Timeout: 5 seconds
BootOrder: 0000
Boot0000* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Then reboot the machine:
rebootAfter reboot, the boot settings should be something alike:
BootCurrent: 0000
Timeout: 5 seconds
BootOrder: 0000,0001,0002
Boot0000* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0001* ubuntu HD(1,GPT,e2daca90-f32f-4d3e-b696-0244329c6551,0x800,0x100000)/File(\EFI\UBUNTU\GRUBX64.EFI)..BO
Boot0002* UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)..BO
NB The entries after Boot0000 are automatically populated by the UEFI.
The system can reboot to the firmware using:
systemctl reboot --firmware-setupFor more details see:
- https://www.freedesktop.org/software/systemd/man/systemctl.html#--firmware-setup
- efi_reboot_to_firmware_supported
- get_os_indications
SystemD will manipulate these UEFI variables:
efivar --name 8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndicationsSupported --print
efivar --name 8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndications --printGUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c
Name: "OsIndicationsSupported"
Attributes:
Boot Service Access
Runtime Service Access
Value:
00000000 03 00 00 00 00 00 00 00 |........ |
GUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c
Name: "OsIndications"
Attributes:
Non-Volatile
Boot Service Access
Runtime Service Access
Value:
00000000 00 00 00 00 00 00 00 00 |........ |
See Network Boot.
Ubuntu 20.10 works out of the box.
The Wifi/Bluetooth module has two IPEX MHF4 RF antenna connectors.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent