Vladimir 'φ-coder/phcoder' Serbinenko
phcoder at gmail.com
Tue Mar 11 22:13:55 CET 2014
@ron: please provide more information about your qemu: version, how
built, options, patches,... Try -M pc-q35-1.7 and -M pc-i440fx-1.7. Try
specifying --no-kvm and --enable-kvm. Speyifying -cpu may help as well.
From my experience with GRUB, qemu has following flaws:
- From version to version they sometimes do subtle changes which break
- On some CPUs kvm bugs or behaves unexpectedly.
On 10.03.2014 14:43, David Hubbard wrote:
> On Sunday, March 09, 2014 08:26:05 PM you wrote:
>> On Sunday, March 09, 2014 05:14:51 PM you wrote:
>> > Story so far:
>> > 1. pick q35 chipset
>> > 2. qemu -M q35 etc. etc.
>> $ qemu-system-i386 -M q35 --bios build/coreboot.rom
>> > 1. pick i440fx chipset.
>> > 2. qemu -M pc etc. etc.
>> qemu-system-i386 --bios build/coreboot.rom
>> > Endless repetitions of
>> > qemu: unsupported keyboard cmd cmd=0x00
>> > or 0x80
>> Same with qemu-kvm.
>> > This is with crossgcc.
>> > I'm disappointed it's this fragile. I'm worried that feature push has
>> > gotten ahead of reliability push.
>> Or your qemu installation is b0rk3d.
> Perhaps if it is that easy to break the installation -- remember, he did
> a clean checkout -- then there could be a broken dependency, or
> something similar which involves digging deeply into the build system.
> In other words, even if what you say is true, we still need to have this
> I feel like Coreboot is a bit fiddly to get set up right. To a degree,
> that helps communicate that working with coreboot is hard stuff. But
> still, we should implement some better quality controls, imho.
> Hopefully we can figure out what Ron ran into. That would be a good start.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 274 bytes
Desc: OpenPGP digital signature
More information about the coreboot