<div dir="ltr"><div><div><div><div><div><div><div>Hello Serdar,<br><br></div>I have looked in your dmesg log: <a href="http://paste.debian.net/924457" rel="noreferrer" target="_blank">paste.debian.net/924457</a> dmesg. Did not look into <a href="http://paste.debian.net/924458" rel="noreferrer" target="_blank">paste.debian.net/924458</a> journalctl -k .<br><br>I had some comparison to do, trying to understand what is going on with your Coreboot FW versus, for example, BIOS one. Few interesting things cot my eye, but I'll keep it for later... ;-)<br><br></div>I can see that you are actually using (my best guess) 4GB of memory (probably 2 banks of DDR2 x 2GB), since we have here Code Name Penryn: <a href="http://ark.intel.com/products/35569/Intel-Core2-Duo-Processor-P8400-3M-Cache-2_26-GHz-1066-MHz-FSB" target="_blank">http://ark.intel.com/products/<wbr>35569/Intel-Core2-Duo-<wbr>Processor-P8400-3M-Cache-2_26-<wbr>GHz-1066-MHz-FSB</a><br><br></div>CPUID: 0x10676, paired with ICH9 PCH, if I am not mistaken. Also, you are probably (almost for sure) using SeaBIOS as payload.<br><br></div>The thing which really confuses me is Debian Kernel command line: I am used 99% to RHEL/Fedora logs, so this command like is really confusing, since I could not determine too much about your GRUB2.<br><br></div><div>Here it is (too simplictic for me, should have much more in it): <i><u>Command line: BOOT_IMAGE=(ahci0,msdos1)/vmlinuz root=/dev/sda1</u></i><br></div><div><br></div>And, after carefully examining PCIe bus, I found the ETH controller: 00:19.0 [VID=0x8086, DID=0x294C]:<br><a href="https://pci-ids.ucw.cz/read/PC/8086/294c" target="_blank">https://pci-ids.ucw.cz/read/<wbr>PC/8086/294c</a><br><br>[user@localhost projects]$ cat dmesg.txt | grep 00:19.0<br>[ 0.151652] pci 0000:00:19.0: <u><i><b>[8086:294c</b></i></u>] type 00 class 0x020000<br>[ 0.151694] pci 0000:00:19.0: reg 0x10: [mem 0xe1600000-0xe161ffff]<br>[ 0.151707] pci 0000:00:19.0: reg 0x14: [mem 0xe1624000-0xe1624fff]<br>[ 0.151721] pci 0000:00:19.0: reg 0x18: [io 0x3000-0x301f]<br>[ 0.151802] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold<br>[ 1.489719] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode<br>[ 1.611526] e1000e 0000:00:19.0: The NVM Checksum Is Not Valid<br><span style="color:rgb(255,0,0)"><u><i><b>[ 1.635873] e1000e: probe of 0000:00:19.0 failed with error -5</b></i></u></span><br>[user@localhost projects]$ <br><br></div>Now, I need from you the following: ifconfig -a (to see if your wired ETH controller is present there).<br><br></div>You can try to do the following (as root): service network restart . If it does not help, you need to read the following page, and try to navigate through it: <br><a href="http://unix.stackexchange.com/questions/182600/how-do-i-troubleshoot-networking-on-debian" target="_blank">http://unix.stackexchange.com/<wbr>questions/182600/how-do-i-<wbr>troubleshoot-networking-on-<wbr>debian</a><br><br><div class="gmail_extra">Since you are using the very recent Coreboot: 4.5-1094-ga154a91 03/01/2017, I'll ask Coreboot people to tell you what INTEL board and what ETH controller you should set up for your (Lenovo) x200, since I could not find right mapping?!</div><div class="gmail_extra"><br></div><div class="gmail_extra">Martin, Patrick,</div><div class="gmail_extra"><br></div><div class="gmail_extra">What INTEL board (name) in Coreboot terminology maps to Lenovo x200 notebook, and which generic ETH driver should be enabled there (maybe Serdar did not enable the right ETH one, most likely seems from the dmesg logs)?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thank you,</div><div class="gmail_extra">Zoran</div><div class="gmail_extra">_______</div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 26, 2017 at 7:58 PM, serdar tunc <span dir="ltr"><<a href="mailto:serdarot5@gmail.com" target="_blank">serdarot5@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><a href="http://paste.debian.net/924457" rel="noreferrer" target="_blank">paste.debian.net/924457</a> dmesg<br>
<a href="http://paste.debian.net/924458" rel="noreferrer" target="_blank">paste.debian.net/924458</a> journalctl -k<br>
Thank you<br>
<div class="gmail-m_66589184306542510HOEnZb"><div class="gmail-m_66589184306542510h5"><br>
On Sat, Mar 25, 2017 at 11:57 AM, Zoran Stojsavljevic<br>
<<a href="mailto:zoran.stojsavljevic@gmail.com" target="_blank">zoran.stojsavljevic@gmail.com</a><wbr>> wrote:<br>
> I need these journalctl -k and dmesg logs (to trace the problem).<br>
><br>
> Thank you,<br>
> Zoran<br>
><br>
> On Fri, Mar 24, 2017 at 10:11 AM, serdar tunc <<a href="mailto:serdarot5@gmail.com" target="_blank">serdarot5@gmail.com</a>> wrote:<br>
>><br>
>> ---------- Yönlendirilen ileti ----------<br>
>> Gönderen: "serdar tunc" <<a href="mailto:serdarot5@gmail.com" target="_blank">serdarot5@gmail.com</a>><br>
>> Tarih: 22 Mar 2017 19:14<br>
>> Konu: Ethernet problem in x200<br>
>> Alıcı: <<a href="mailto:coreboot-request@coreboot.org" target="_blank">coreboot-request@coreboot.org</a><wbr>><br>
>> Cc:<br>
>><br>
>> I have x200 installed coreboot inside<br>
>> But my ethernet doesnt work. How can i fix it?<br>
>> <a href="http://paste.debian.net/923338" rel="noreferrer" target="_blank">paste.debian.net/923338</a> journalctl -k message<br>
>> <a href="http://paste.debian.net/9233342" rel="noreferrer" target="_blank">paste.debian.net/9233342</a> dmesg message<br>
>><br>
>> --<br>
>> coreboot mailing list: <a href="mailto:coreboot@coreboot.org" target="_blank">coreboot@coreboot.org</a><br>
>> <a href="https://www.coreboot.org/mailman/listinfo/coreboot" rel="noreferrer" target="_blank">https://www.coreboot.org/mailm<wbr>an/listinfo/coreboot</a><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>