[MinnowBoard] Problems with firmware image building and with multiple BootXXXX
Дмитрий Оботуров
oboturoff at gmail.com
Sun May 31 22:09:34 UTC 2015
Hello.
I have one more question what we can't answer.
In the attachment you will find two files of firmware image that we get
from the same source code uefi. One of the firmware images was built on the
notebook but the other on the desktop.
image №1
https://drive.google.com/file/d/0B6BUWzw-c4Q7VVNvN0lValc2MHhyM3Z1QVgycUY5TlVsWEJZ/view?usp=sharing
image №2
https://drive.google.com/file/d/0B6BUWzw-c4Q7b2JfWnBxTWZ2ODNjNHpEX3VTcFI2a0FhSzNZ/view?usp=sharing
Could you please explain what is the reason that these two files differ
from each other? Why does one of them run on the board minnowboardMax as
for the other it runs also but we can't bring the network interface up. We
have the following log after trying of network device initialisation:
*ifconfig eth0 192.168.1.100 up[ 16.520206] r8169 0000:02:00.0 eth0:
rtl_phyar_cond == 1 (loop: 20, delay: 25).[ 16.537449] r8169 0000:02:00.0
eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).[ 16.554498] r8169
0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).[ 16.571401]
r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).[
16.588277] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay:
25).[ 16.804962] r8169 0000:02:00.0 eth0: rtl_phy_reset_cond == 1 (loop:
100, delay: 1).[ 16.820375] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1
(loop: 20, delay: 25).[ 16.834873] r8169 0000:02:00.0 eth0:
rtl_phyar_cond == 1 (loop: 20, delay: 25).[ 16.848134] r8169 0000:02:00.0
eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).[ 16.860811] r8169
0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).[ 16.873019]
r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).[
16.884830] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20, delay:
25).[ 16.896527] r8169 0000:02:00.0 eth0: rtl_phyar_cond == 1 (loop: 20,
delay: 25).[ 16.908048] r8169 0000:02:00.0 eth0: link up*
I can also send the source code of uefi that we used by getting of these
firmware images.
I would like to ask you one more question and I think it is more important
for us that the first one.
There is firmware image - MinnowBoard.MAX.FirmwareUpdateX64.efi that is
flashed in our minnowboardMax. This file we got from the intel site from
the archive named MinnowBoard.MAX_.X64.078.R02.bin.zip.
We are booting the linux kernel on the board and using the basic utility
efibootmgr for changing of BootOrder. Below you can find the log of what we
are doing.
*# ls -l /sys/firmware/efi/vars/total 0drwxr-xr-x 2 root
root 0 Mar 10 00:02
AuthVarKeyDatabase-aaf32c78-947b-439a-a180-2e144ec37792drwxr-xr-x 2
root root 0 Mar 10 00:02
BmmData-642237c7-35d4-472d-8365-12e0ccf27a22drwxr-xr-x 2 root
root 0 Mar 10 00:02
Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:02
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
BootState-60b5e939-0fcf-4227-ba83-6bbed45bc0e3drwxr-xr-x 2 root
root 0 Mar 10 00:02
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
EfiNicIp4ConfigVariable-09d5b53f-f4b0-4f59-a0b1-7b57d35c0e05drwxr-xr-x 2
root root 0 Mar 10 00:02
ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
FeData-1f2d63e1-febd-4dc7-9cc5-ba2b1cef9c5bdrwxr-xr-x 2 root
root 0 Mar 10 00:02
HwErrRecSupport-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:02
IP6_CONFIG_IFR_NVDATA-02eea107-98db-400e-9830-460a1542d799drwxr-xr-x 2
root root 0 Mar 10 00:02
ItkBiosModVar-3812723d-7e48-4e29-bc27-f5a39ac94ef1drwxr-xr-x 2 root
root 0 Mar 10 00:02
Lang-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
MTC-eb704011-1402-11d3-8e77-00a0c969723bdrwxr-xr-x 2 root
root 0 Mar 10 00:02
OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:02
OsSelection-86843f56-675d-40a5-9530-bc858372f103drwxr-xr-x 2 root
root 0 Mar 10 00:02
PciLanInfo-0d9a1427-e02a-437d-926b-aa521fd722badrwxr-xr-x 2 root
root 0 Mar 10 00:02
PlatformCpuInfo-10ba6bbe-a97e-41c3-9a07-607ad9bd60e5drwxr-xr-x 2
root root 0 Mar 10 00:02
PlatformInfo-10ba6bbe-a97e-41c3-9a07-607ad9bd60e5drwxr-xr-x 2 root
root 0 Mar 10 00:02
PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:02
RTC-378d7b65-8da9-4773-b6e4-a47826a833e1drwxr-xr-x 2 root
root 0 Mar 10 00:02
SECUREBOOT_CONFIGURATION-5daf50a5-ea81-4de2-8f9b-cabda9cf5c14drwxr-xr-x
2 root root 0 Mar 10 00:02
SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
Setup-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9drwxr-xr-x 2 root
root 0 Mar 10 00:02
SetupDefault-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9drwxr-xr-x 2 root
root 0 Mar 10 00:02
SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
SignatureSupport-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:02
Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:02
certdb-d9bee56e-75dc-49d9-b4d7-b534210f637a--w------- 1 root
root 0 Mar 10 00:02 del_var--w------- 1 root
root 0 Mar 10 00:02 new_var# efibootmgr BootCurrent:
0003Timeout: 5 secondsBootOrder: 0000,0001,0002,0003Boot0000* EFI Internal
ShellBoot0001* EFI Network 001320FE35AC IPv4Boot0002* EFI Network
001320FE35AC IPv6Boot0003* EFI USB Device# efibootmgr -o 0000BootCurrent:
0003Timeout: 5 secondsBootOrder: 0000Boot0000* EFI Internal ShellBoot0001*
EFI Network 001320FE35AC IPv4Boot0002* EFI Network 001320FE35AC
IPv6Boot0003* EFI USB Device# efibootmgrBootCurrent: 0003Timeout: 5
secondsBootOrder: 0000Boot0000* EFI Internal ShellBoot0001* EFI Network
001320FE35AC IPv4Boot0002* EFI Network 001320FE35AC IPv6Boot0003* EFI USB
Device*
Further we are rebooting the device and booting linux again. Below you can
find the log of efibootmgr utility running.
*# ls -l /sys/firmware/efi/vars/total 0drwxr-xr-x 2 root
root 0 Mar 10 00:05
AuthVarKeyDatabase-aaf32c78-947b-439a-a180-2e144ec37792drwxr-xr-x 2
root root 0 Mar 10 00:05
BmmData-642237c7-35d4-472d-8365-12e0ccf27a22drwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0000-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0001-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0002-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0003-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0005-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Boot0006-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
BootCurrent-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
BootOptionSupport-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:05
BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
BootState-60b5e939-0fcf-4227-ba83-6bbed45bc0e3drwxr-xr-x 2 root
root 0 Mar 10 00:05
ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
ConInDev-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
ConOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
EfiNicIp4ConfigVariable-09d5b53f-f4b0-4f59-a0b1-7b57d35c0e05drwxr-xr-x 2
root root 0 Mar 10 00:05
ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
ErrOutDev-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
FeData-1f2d63e1-febd-4dc7-9cc5-ba2b1cef9c5bdrwxr-xr-x 2 root
root 0 Mar 10 00:05
HwErrRecSupport-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:05
IP6_CONFIG_IFR_NVDATA-02eea107-98db-400e-9830-460a1542d799drwxr-xr-x 2
root root 0 Mar 10 00:05
ItkBiosModVar-3812723d-7e48-4e29-bc27-f5a39ac94ef1drwxr-xr-x 2 root
root 0 Mar 10 00:05
Lang-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
LangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
MTC-eb704011-1402-11d3-8e77-00a0c969723bdrwxr-xr-x 2 root
root 0 Mar 10 00:05
OsIndicationsSupported-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:05
OsSelection-86843f56-675d-40a5-9530-bc858372f103drwxr-xr-x 2 root
root 0 Mar 10 00:05
PciLanInfo-0d9a1427-e02a-437d-926b-aa521fd722badrwxr-xr-x 2 root
root 0 Mar 10 00:05
PlatformCpuInfo-10ba6bbe-a97e-41c3-9a07-607ad9bd60e5drwxr-xr-x 2
root root 0 Mar 10 00:05
PlatformInfo-10ba6bbe-a97e-41c3-9a07-607ad9bd60e5drwxr-xr-x 2 root
root 0 Mar 10 00:05
PlatformLang-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
PlatformLangCodes-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:05
RTC-378d7b65-8da9-4773-b6e4-a47826a833e1drwxr-xr-x 2 root
root 0 Mar 10 00:05
SECUREBOOT_CONFIGURATION-5daf50a5-ea81-4de2-8f9b-cabda9cf5c14drwxr-xr-x
2 root root 0 Mar 10 00:05
SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
Setup-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9drwxr-xr-x 2 root
root 0 Mar 10 00:05
SetupDefault-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9drwxr-xr-x 2 root
root 0 Mar 10 00:05
SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
SignatureSupport-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2
root root 0 Mar 10 00:05
Timeout-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
VendorKeys-8be4df61-93ca-11d2-aa0d-00e098032b8cdrwxr-xr-x 2 root
root 0 Mar 10 00:05
certdb-d9bee56e-75dc-49d9-b4d7-b534210f637a--w------- 1 root
root 0 Mar 10 00:05 del_var--w------- 1 root
root 0 Mar 10 00:05 new_var# efibootmgr BootCurrent:
0006Timeout: 5 secondsBootOrder: 0000,0004,0005,0006Boot0000* EFI Internal
ShellBoot0001* EFI Network 001320FE35AC IPv4Boot0002* EFI Network
001320FE35AC IPv6Boot0003* EFI USB DeviceBoot0004* EFI Network 001320FE35AC
IPv4Boot0005* EFI Network 001320FE35AC IPv6Boot0006* EFI USB Device*
The main question for us is the following: why had the number of BootXXXX
variables increased?
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.elinux.org/pipermail/elinux-minnowboard/attachments/20150601/c88be3c2/attachment-0001.html>
More information about the elinux-MinnowBoard
mailing list