ok - i have just tried to be friendly and let you ask information needed
must apologize if tones of my messages are wrong as i'm not native
english and it may affect nuances of my writing or how it sounds to
- the basic issue is that after following your pages, coreboot won't boot
- i have not yet tried to get output w serial console but try to
follow previous hint to do 'make crossgcc'
- as i try to do 'make crossgcc' the system appears to go to loop =
now it has been trying for an hour with only output on attached
make_crossgcc_out / make_crossgcc_err
- there is nothing in syslog
- distribution is CRUX 2.8 (
ftp://ftp.spline.inf.fu-berlin.de/pub/crux/crux-2.8/iso/ ) but only
bare minimum of stuff installed ( installed_stuff ) and after coreboot
running i get rid of even some of them to begin building my kind of things
- attached linux_config_mc for kernel 3.5.4 - and note that udev is not running
Thanks to all of you
On 6/8/13, Paul Menzel <paulepanter(a)users.sourceforge.net> wrote:
> Dear Matti,
> Am Samstag, den 08.06.2013, 13:38 +0300 schrieb matti christensen:
>> trying 'make crossgcc' - it says 'Welcome to the coreboot cross
>> toolchain...etc.' after several tens of minutes and one bash is taking
>> ~100% and hd is in standby ....
> Please paste what is written on the console. (Including log files is
> always recommended.) As all the tools get compiled from source it is to
> be expected that the CPU is used a lot.
> Furthermore, what distribution do you use?
> PS: Please adhere to the netiquette  and use interleaved quoting
>  http://en.opensuse.org/openSUSE:Mailing_list_netiquette
Am Samstag, den 08.06.2013, 13:38 +0300 schrieb matti christensen:
> trying 'make crossgcc' - it says 'Welcome to the coreboot cross
> toolchain...etc.' after several tens of minutes and one bash is taking
> ~100% and hd is in standby ....
Please paste what is written on the console. (Including log files is
always recommended.) As all the tools get compiled from source it is to
be expected that the CPU is used a lot.
Furthermore, what distribution do you use?
PS: Please adhere to the netiquette  and use interleaved quoting
matti christensen wrote:
> after reading coreboot pages, getting coreboot, filo and flashrom
> sources from git, configuring and building them to best of my
> understanding, system does not boot.
> would someone like to help me - i can of course deliver config, dmesg,
> what-ever ?
Make sure to build everything using the reference toolchain. Run
in the coreboot directory.
Then post the debug log (serial output) from coreboot.
i bought brand new pc500e from ebay as i really like via - and have
been interested in coreboot for a long time. board is exactly the same
as in Uve Hermanns image - http://www.coreboot.org/VIA_pc2500e .
i have been using Linux for ages ( from kernel 1.2.13 or so ) and
built my stuff mostly myself using some aschetic distribution, like
early slackware and now CRUX to get started.
after reading coreboot pages, getting coreboot, filo and flashrom
sources from git, configuring and building them to best of my
understanding, system does not boot.
i have spare w39v040bfz, which works with original bios burned into
it, but not w coreboot.
would someone like to help me - i can of course deliver config, dmesg,
On 06/07/13 03:11, Svetoslav Trochev wrote:
> Hi Everyone,
> I was looking at the wiki's Getting Started | QEMU section  and I
> noticed that all examples are outdated: coreboot V2 or V3. I
> understand that for most coreboot developers QEMU will provide no
> benefits, but for me it seem a good idea to practice building coreboot
> for QEMU in order to gain better understanding about coreboot before I
> start working with hardware. So my question is: Why listed examples
> are out of date? Is it because there is no much of benefit to play
> with QEMU/coreboot, or just because there is no human resources to
> maintain up to date version of the tutorial and ready-build images?
It's pretty simple with v4 + recent qemu:
(1) "make config"
- pick CONFIG_BOARD_EMULATION_QEMU_X86
- pick the payload you want play with
- tweak any config options as you like,
if in doubt simply stick to the defaults.
(3) "qemu -bios /path/to/coreboot/build/coreboot.rom $other $args".
 As in "newer than 0.12" which is several years old by now.
No special care for vgabios needed any more.
Is it possible to build a single rom which is able to run on two
Background: qemu recently got an emulation for a more recent chipset.
Current seabios roms detect at runtime whenever runs on the old (i440fx
+ piix4) or the new (q35 + ich9) and initializes the hardware
accordingly. I'd like to do the same with coreboot if possible.
Drivers seem to be kicked by hardware detection (struct pci_driver), so
it looks like simply compiling in two southbridges could work. Tried,
got duplicate symbols. Hmm.
There also is no obvious way to have two devicetrees and pick one of
them at runtime. Same with acpi tables.
I was looking at the wiki's Getting Started | QEMU section  and I
noticed that all examples are outdated: coreboot V2 or V3. I
understand that for most coreboot developers QEMU will provide no
benefits, but for me it seem a good idea to practice building coreboot
for QEMU in order to gain better understanding about coreboot before I
start working with hardware. So my question is: Why listed examples
are out of date? Is it because there is no much of benefit to play
with QEMU/coreboot, or just because there is no human resources to
maintain up to date version of the tutorial and ready-build images?
On 06/04/2013 12:36 AM, David Hendricks wrote:
> On Mon, Jun 3, 2013 at 1:57 PM, Alex G. <mr.nuke.me(a)gmail.com> wrote:
>> On 06/03/2013 03:10 PM, Oliver Schinagl wrote:
>>> On 06/03/13 16:03, Denis 'GNUtoo' Carikli wrote:
>>>> On Sun, 2 Jun 2013 20:54:04 -0500
>>>> slhac tivist<slhactivist(a)gmail.com> wrote:
>>>>>> Which supported laptop is the most free?
>>>> The Lenovo X60.
>>> Strange that an Intel Part has the best support.
>> I find the same thing depressing.
>>> When A) AMD officially supports coreboot
>> There really aren't that many laptops with AMD CPUs. I think that's the
>> root of the problem here.
> AMD CPUs are generally very well supported by coreboot.
> But as you point out, the number of laptops with AMD CPUs is somewhat
> low. And to make matters more complicated, the number of laptops with
> an AMD CPU *and* a well-understood embedded controller* are even
> lower. Maybe someone knows of a good AMD target laptop with a workable EC?
Add an A10 processor, backlit keyboard, and IPS display. I'd love to get
one of those.
On Sun, 2 Jun 2013 20:54:04 -0500
slhac tivist <slhactivist(a)gmail.com> wrote:
> Which supported laptop is the most free?
The Lenovo X60.
> According to the laptop section of:
That should probably be updated...
> The the status of the Roda and Getac board (both "OK") doesn't link to
> anything. Is the implication that coreboot works flawlessly on these
> boards? And how bad is the proprietary code? Can Getac and Roda still
> spy on me with it?
I don't know about theses, I haven't looked yet and don't own them.
> I'd like to get a chromebook. The status is "OK" but links to a page
> that says there are proprietary components.
> What is microcode?
The microcode is like a "firmware" sent to the CPU.
we don't think it's code but we don't really know.
It seem signed according to what people say on the internet, and its
purpose is to workarround hardware bugs in the CPU, by disabling paths
of executions etc...
> What is MRC.bin
It's the memory intialization blob. it runs on the main CPU during
coreboot initalization and is proprietary.
Its size is big and we don't know what it does exactly.
> and ME.bin?
it's the Management engine, see AMT on wikipedia:
That is really really problematic.
On the X201 there are full versions of that,
on the chromebooks there are light versions, but we don't know what
theses light version do.
> Again, can google control my laptop with this code?
ME.bin and MRC.bin and the microcode are from Intel, I don't know if
google modified them or not.
> Finally, if the above options don't pan out, I could get a Lenovo. The
> X60[s] and T60[p] made no mention of proprietary code. :) Can anyone
> confirm this? That would be pretty sweet!
Theses have microcode.
Prefer the X60[s] for now because it has native graphic initialization
that will be submited for review really soon.
The T60 is very similar though, so once the code will be submited, and
if you're skilled enough you could port that code to the T60.
Note that some T60 have an ATI graphic card, that won't work with the
native graphics initialization becasue it's made for intel GPUs.
Currently native graphics initialization gives graphics in grub as a
payload. Peter Stuge has code on top of my code and I'm waiting for him
to submit it. Then I'll test it even more but I was able to load
parabola and trisquel distributions trough this method...
Without native graphics init or the non-free option rom(which the
native graphics init tries to replace) you will have no graphics during
boot and probably some memory corruption issues with lastest parabola
kernels. also nvramtool will need an extra parameter to work and cbmem
-c will not work.
Parabola is based on arch, Trisquel is based on ubuntu, both are 100%
> The Lenovo X201 supports a faster cpu, but the status links to a page
> that says it has proprietary components too...anyone know anything
> about these proprietary components? I don't want Lenovo sending my
> laptop secret messages!
It has only the ME, however you probably don't want that, especially
because it's a full one...
> Any advice would be greatly appreciated. My goal is to build a laptop
> that is 100% free of proprietary code...
Right now there are some options:
*) The Lemote netbook(not the notebook which has an ATI option rom).
*) The Lenovo X60
*) The Lenovo T60
If you also plan to run a 100% free distribution on the Lenovo X60 or
T60, you will probably need an internal or external wifi card that is
not intel(because it requires a non-free firmware).
Thinkpenguin sells some ( https://www.thinkpenguin.com/ ) that are
supported by 100% free software.
Also you probably want the dock for having serial(that's where coreboot
logs are sent). it's the best way to get logs.
The other way that would work is spkmodem, which only require an audio
cable, however it's way slower, is receive only and only works in
coreboot and grub2.
cbmem is not a really good way to obtain reliable logs because:
* it require a booted computer(up to grub or GNU/Linux).
* it truncate logs when writing is slower than the flow of execution...