On Sun, Jun 12, 2011 at 10:25 PM, Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
On Sat, 28 May 2011 18:59:23 +0300 Tero Peippola xeropp@gmail.com wrote:
On Sat, May 28, 2011 at 4:28 PM, Stefan Tauner stefan.tauner@student.tuwien.ac.at wrote:
your report also shows that your board is matched by a board enable, but does not need it. i would like to investigate that a bit further and need your help to do so. can you please run lspci -nnvvvxxx and superiotool -deV as root and send us their output?
hello again,
i have added a DMI search pattern to said board enable which should prevent your board (and many others) from being detected incorrectly to be compatible with that board enable.
Thanks, I'll test that.
One word of warning when you take a look at logs. Coreboot (4.0 r6554) manages to boot fine with seabios payload, but I'm having similar problems as in http://www.mail-archive.com/coreboot@coreboot.org/msg29682.html (PS/2 keyboard not working, boot device not found. Compiled with crossgcc or Ubuntu 4.4.3-4ubuntu5-gcc).
Today I also noticed that link of onboard NIC did not go up after several coreboot boot attempts. (Also attached dmesg.txt)
the coreboot people would certainly be a better addressee for this than i am ;) sorry
Sure :) Just wanted to warn you there might be unreliable results in registerd dumps. In case the board is unstable. But looks like this was just a bad LAN cable.
Regards, Tero