<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thank you for your kind reply Gergely.</p>
<p>I think the cable is not the problem, I have been using it for
years and it's intact.</p>
<p>I am using a usb dongle but not a cheap one. Tomorrow I will try
with another cable and a real COM port. Just to be 100% sure.</p>
<p>Console is fast at the very first time (just the "normal") but
after two seconds it becomes extremely slow.<br>
</p>
<p>Please, can you say me which is the git revision you are using?</p>
<p>The console log I attached is from a SPEW debug level, not
corresponding with the config.. I tried several configs today :-)
.</p>
<p>Is it possible to share your config with me?</p>
<p>Best regards,</p>
<p>Eli<br>
</p>
<br>
<div class="moz-cite-prefix">On 10/02/18 21:44, Gergely Kiss wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF-mK=UtAx8FzhfHO7-JW2SCni+Tfox_L1E8JU1emjvnb_8TUw@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Hi Eli,<br>
<br>
</div>
I've been using Coreboot on my board for several weeks,
it is serving as an HTPC running 24/7 and it's working
perfectly stable which suggests the firmware should be
free of bugs. It is likely that you are facing some
configuration or hardware issue here.<br>
<br>
</div>
<div>I didn't see any issues with the serial output while
working with the board once the SuperIO chip started to
work. Make sure the cable you use is intact and try to
attach it to another machine. At the time I was working
with my board, I used a Dell Port Replicator with a
native COM port so I could use a standard null-modem
cable and it was working flawlessly. In case you use a
USB serial adapter, try replacing it or attach the
serial cable directly to a COM port if you have one
available.<br>
</div>
<div><br>
</div>
Also, please enable debug_level=Spew as it seems the
console log you attached comes from a less verbose setting
and therefore it's not as useful as it should be.<br>
<br>
Note that the VBIOS image is executed by SeaBIOS which
means you won't see anything on your display until the
payload is executed.<br>
<br>
</div>
If all else fails, you can still attach a POST debug module
to the LPC header of the board [1] which can help a lot to
find out where the boot process hangs.<br>
<br>
</div>
<div>Feel free to contact me if you need some more help or
information, I'm happy to assist!<br>
</div>
<div><br>
</div>
Regards,<br>
</div>
Gergely<br>
<br>
[1] <a href="https://www.youtube.com/watch?v=aGGqsWx3-1c"
moz-do-not-send="true">https://www.youtube.com/watch?v=aGGqsWx3-1c</a><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 10 February 2018 at 18:17,
Elisenda Cuadros <span dir="ltr"><<a
href="mailto:lists@e4l.es" target="_blank"
moz-do-not-send="true">lists@e4l.es</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
I'm trying to use Coreboot in an Asus AM1I-A board
recently ported by Gergely Kiss (thank you!).<br>
<br>
I am using the default config settings and added vga rom
extracted with UEFITool from the vendor bios.<br>
<br>
After flashing and booting I get no output from vga.<br>
<br>
Serial console is extremely slow too (30 minutes to write
the log)<br>
<br>
I attach the coreboot console log, config and cbfs.txt.<br>
<br>
Any hints?<br>
<br>
Thanks in advance.<br>
<br>
Best regards,<br>
<br>
-- Eli<br>
<br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>