On Sun, Jul 22, 2018 at 11:50 PM, zahra rahimkhani
> Thank you very much.
> I compiled coreboot and seabios and got Microcode and Fsp on it.
> But I did not have output on serial port.
> Could you tell me How set menuconfig that see outpot on serial port.
It would be helpful if you can upload your .config somewhere such as
My guess is that you don't have CONFIG_ENABLE_BUILTIN_COM1 selected
(under "Chipset"), which is an option you have to set in addition to
the stuff under "Console."
> On Mon, Jul 23, 2018 at 10:58 AM David Hendricks <david.hendricks(a)gmail.com>
>> Hi Zahra,
>> On Mon, Jul 23, 2018 at 4:49 AM, zahra rahimkhani
>> <zrahimkhani2014(a)gmail.com> wrote:
>> > Dear friends
>> > I compile seaBios and coreboot for Minnowboard max .
>> > but I do not see output on Serial port .
>> > Does coreboot support USB to Serial Converters ?
>> > or how do I add this feature ?
>> The Minnowboard Max serial port does not go thru a USB to serial
>> converter. However, you may need to enable some config options.
>> Compare a sample config.txt from the supported mainboards page
>> (https://coreboot.org/status/board-status.html) to your .config file
>> to see if there is anything obviously missing.
>> Also, do you have the microcode files from Intel? If not, you can
>> download them from
>> > Thanks ,
>> > --
>> > coreboot mailing list: coreboot(a)coreboot.org
>> > https://mail.coreboot.org/mailman/listinfo/coreboot
I found new ACPI errors on my Lenovo X201i:
commit "60eca531df ec/lenovo/h8/acpi: Add WWAN ACPI methods" introduces
the following error just before shutdown:
thinkpad_acpi_ acpi_evalf(\WGSV, vd, ...) failed: AE_NOT_FOUND
and commit "31fb846c59 ec/lenovo/h8/acpi: Apply state on wake"
introduces the following errors on boot:
ACPI Error: No handler for Region [ERAM] ( (ptrval))
ACPI Error: Region EmbeddedControl (ID=3) has no handler
ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC.HKEY._INI,
ACPI Error: AE_NOT_EXIST, during \_SB.PCI0.LPCB.EC.HKEY._INI execution
Dear coreboot developers:
I am trying to create CB firmware for Broadwell-D 1559 system using CamelBack Mountain CRB as mainboard selection, and the system boots Windows and Linux operating systems but USB keyboard and mouse doesn't work.
I already enable/disabled EHCI/xHCI devices in devicetree without success.
I tried Seabios and Tianocore without success.
Anyone had experience this issue?
Any advise will be appreciated.
Thank you very much.
I compiled coreboot and seabios and got Microcode and Fsp on it.
But I did not have output on serial port.
Could you tell me How set menuconfig that see outpot on serial port.
On Mon, Jul 23, 2018 at 10:58 AM David Hendricks <david.hendricks(a)gmail.com>
> Hi Zahra,
> On Mon, Jul 23, 2018 at 4:49 AM, zahra rahimkhani
> <zrahimkhani2014(a)gmail.com> wrote:
> > Dear friends
> > I compile seaBios and coreboot for Minnowboard max .
> > but I do not see output on Serial port .
> > Does coreboot support USB to Serial Converters ?
> > or how do I add this feature ?
> The Minnowboard Max serial port does not go thru a USB to serial
> converter. However, you may need to enable some config options.
> Compare a sample config.txt from the supported mainboards page
> (https://coreboot.org/status/board-status.html) to your .config file
> to see if there is anything obviously missing.
> Also, do you have the microcode files from Intel? If not, you can
> download them from
> > Thanks ,
> > --
> > coreboot mailing list: coreboot(a)coreboot.org
> > https://mail.coreboot.org/mailman/listinfo/coreboot
On Mon, Jul 23, 2018 at 4:49 AM, zahra rahimkhani
> Dear friends
> I compile seaBios and coreboot for Minnowboard max .
> but I do not see output on Serial port .
> Does coreboot support USB to Serial Converters ?
> or how do I add this feature ?
The Minnowboard Max serial port does not go thru a USB to serial
converter. However, you may need to enable some config options.
Compare a sample config.txt from the supported mainboards page
(https://coreboot.org/status/board-status.html) to your .config file
to see if there is anything obviously missing.
Also, do you have the microcode files from Intel? If not, you can
download them from
> Thanks ,
> coreboot mailing list: coreboot(a)coreboot.org
(not affiliated with shady chinese seller, no idea how legit but if they
don't deliver a working board just complain to ebay)
Great chance to get the last and best owner controlled x86 board for
your legacy applications - they appear to be selling them for cheap as
they don't know how easy it is to flash a BIOS that can run the
"...and am curious...what is compelling for you and this ?"
The short answer - >nostalgia< and >spirit< .
A little bit longer answer (for those with patience);
You may take the following lines with a grain of salt, or . you can choose
to give it a though, a moment of reflection, if you want. I'm talking about
something, that I can only describe as a >human spirit< . that intangible
something, which rubbed off the minds of highly motivated engineers, and
transfered onto cold work of art in the process. I'm referring to people
from computer industry, who considered themselves to be lucky, for being
allowed (every now and then) to come up with a marvell of engineering, as
they were not forced to cut corners like nowadays (design, materials,
rigorous testing). Think IBM Model M keyboard for one, though there may be
far better examples.
Rest assure though . I can hear you all, loud and clear. I am actually aware
of the Sun's U40 M2 workstation age, but I can't help it . having a weakness
for stuff that was build to last, and - on top of that - has been known to
function reliably and pretty much flawlessly, for what seems like ages by
today's >standards<. Sure, I could have picked something younger, as in - a
newer board, to widen the pool of those who prefer >today & yesterday<
hardware, and thus contribute more relevant test results to the project's
efforts. The real question is - how do we qualify, with all the wisdom we
can muster, what to include and what to exclude (and when), and how do we
draw a sharp line, between the board being too old, and the one being still
young enough ? These things don't have easy answers, and Sun Ultra 40 M2 is
one of the best examples for this, IMHO.
It's so easy to jump the conclusions, by scanning fleetingly the second-hand
market every once in a while (been there), when trying to determine just how
many of certain >exotic< machines or boards are still out there - be it
actively used, or collecting the dust in some IT surplus warehouses. Just
take a look at eBay (US) offerings, which I've been following for years, if
not a decade; you can still find a dozen of U40 M2 machines, pretty much at
any given time. They don't sell, as more often than not the prices are
ridiculous. It would be also prudent to consider all those people, who might
have never felt the need to upgrade or change anything on their Sun
machines. This doesn't mean they never will, but it sure means you probably
never heard of them. Bear in mind that only a fraction of computer users are
actually active, to one degree or another, on any given computer forum, or .
on a project mailing list, for that matter.
Those crazy prices of U40 M2 machines, be it on eBayUS, or those being
offered by several Sun resellers in US, will have to come down eventually
(they crowd the warehouse space.). Likewise - a considearble number, of all
those >Happy Camper< U40 M2 users, will eventually hit the wall . wishing to
update their Sun's proprietary BIOS (to overcome limitations of old version,
or to repair their machine), only to realize they can't . at least not for
free, or not even against payment, if they are not customers with cotracts.
Chances are that many of these - the >invisible users< - will eventually
come out of the bushes and try the coreboot flavour, because .
a.) Their machines are still purring like healthy teenage cats,
b.) They just discovered, in all their excitement, how their >oldies< just
may work with Quad and Six-Core Opterons;
But all of that won't matter much, unless the coreboot port for U40 M2 is
kept alive. If it ends up in a dust bin too soon (burried in the pile of
older releases), those >regular Joes< like myself will have a hard time to
find it, or even be aware that something like that ever existed (as the
Google hits start to dwindle) . they will just dump the machine in the
junkyard, and that would be a shame. I'll say it again - I could have
cherry-picked one of the C32 boards I have at home (Tyan S8010, Supermicro
H8DCL-i), and I most probably will in the future . but I picked the Sun's
machine, to be my apprenticeship piece in the coreboot forge. Only time will
tell, if I'm worthy to continue my involvement in coreboot, to aid the
master blacksmiths with keeping the project alive. Like I already explained
before, admittedly in a bit long and winding fashion - I'm not a programmer
type of guy (well . I just ain't), but I'm also not a laid-back type of
person, to just sit and wait till someone else makes all the work, then
whine about it if they don't, or nod approvingly if they do, have a beer or
two, then download their work and off we go. Nope, that's just not me; I did
my share of nerve-wrecking computer diagnostics, for months on end and with
>graveyard shits< and all, so I know what I'm made of and I know that I'm up
to the challenge.
Perhaps it's just me, but . I sensed that I was somewhat gently nudged, for
being one of those in the coreboot flock who inevitably, albeit
inadvertedly, fragment the available >brain resources<, for the sake of
keeping our computer relics alive. It may as well be so, that we're nibbling
off the bits of finite spare time, of all those able and hard working genius
bees at the coreboot project, who contribute the bulk of ports and maintain
them with admirable tenacity . for all of us, the >eager beavers< (keen to
learn and advance ourselves), who would love to give back more if we knew
how to. It's pretty much the same in all communities of this type . there's
never enough time, and there's never enough brainy people, willing to work
pro-bono and sacrifice their spare time, to maintain the healthy heartbeat
of the good-cause projects.
I'm a strong believer in one's personal mind and determination . you do
listen to others, but you don't have to ditch something >old< and embrace
something >new & better<, just because you were told that >it's normal<, or
>that's how it is<, or >you can't change it<. Perhaps I really am one of the
dying breed, for even considering a purchase of such a dated machine, but
that's who I am . I decided to jump on the train, even if it might be THE
last train for the Sun Ultra 40 M2 board. All that with a purpose to learn
something new, to build the confidence by grabbing this bull by the horns,
to give back to community as my skills improve, but also to use the
knowledge acquired for my bread & butter job.
Looking forward .
I'm "bumping" my own thread already, as I realized that .txt may just as
well be the only supported (or allowed) format for attachments. Apologies to
all, it was a clumsy beginner's error in judgement. I promise to do
something about those excessive spacings between the paragraphs as well, by
using a Plain Text format from now on.
I copy/pasted the summary of my findings into .txt file ("Sun Ultra 40 M2 &
coreboot - Brief Summary"), but I'm not sure if the attachment will get
through (a brief HOW-TO would be nice ... I couldn't find anything on the
subject). The latest status table for Ultra 40 M2 board, that I was able to
find, is at the link below (to serve as a reference to my initial post