[coreboot] Kernel couldn't find proper MAC address with coreboot (gigabyte ma785gmt-ud2h)

YongGon Kim ilios86 at gmail.com
Wed Jul 8 13:47:19 CEST 2015


I have used coreboot and successfully boot ubuntu 14.04 (only console
mode).
But kernel couldn't find proper MAC address and only ff:ff:ff:ff:ff:ff is
printed.

When kernel is booted, r8169 module is successfully loaded but
it failed to find proper MAC address with following messages.

[    1.165748] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.165850] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM
control
[    1.166010] r8169 0000:04:00.0 (unregistered net_device): unknown MAC,
using family default
[    1.176236] r8169 0000:04:00.0 (unregistered net_device):
rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
[    1.176448] r8169 0000:04:00.0: irq 43 for MSI/MSI-X
[    1.176609] r8169 0000:04:00.0 eth0: RTL8168b/8111b at
0xffffc900003ac000, ff:ff:ff:ff:ff:ff, XID 9cf0f8ff IRQ 43
[    1.176732] r8169 0000:04:00.0 eth0: jumbo features [frames: 4080 bytes,
tx checksumming: ko]


I found that, with normal BIOS, MAC address are located within PCI I/O
memory space pointed by 2nd base address register of ethernet PCI device.
But with coreboot, memory space pointed by 2nd BAR of ethernet device
only contains 0xff.

I tried to figure out how PCI I/O memory space is initialized and
allocated,
but i'm stuck now and need some helps.
I only found some hints in kernel log that following messages are only
shown with coreboot booting for ethernet pci device.
...
[    0.120164] pci 0000:04:00.0: no compatible bridge window for [mem
0xc8010000-0xc8010fff 64bit pref]
[    0.120164] pci 0000:04:00.0: no compatible bridge window for [mem
0xc8000000-0xc800ffff 64bit pref]
...
[    0.271531] pci 0000:04:00.0: BAR 4: can't assign mem pref (size 0x10000)
[    0.271620] pci 0000:04:00.0: BAR 4: trying firmware assignment [mem
0xc8000000-0xc800ffff 64bit pref]
[    0.271724] pci 0000:04:00.0: BAR 4: assigned [mem 0xc8000000-0xc800ffff
64bit pref]
...

Is there anyone who knows how to handle this situation?
It's okay for me to update kernel source (e.g. r8169 module) instead of
coreboot source code.
I just want to know what the problem is and any possible way to resolve it.


I'm using GIGABYTE GA-MA785GMT-UD2H (rev 1.1) with external graphic card
(nvida GTS 250).
I have uploaded detailed information using board_status.sh
Following is link for the information.
http://review.coreboot.org/gitweb?p=board-status.git;a=commit;h=dedf456d25748368da19d556828c7ef95e3f3073


Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20150708/de89c231/attachment.html>


More information about the coreboot mailing list