#95: Run coreboot in VirtualBox
Reporter: uwe | Owner: somebody
Type: defect | Status: new
Priority: minor | Milestone:
Component: misc | Version:
Keywords: | Dependencies:
Patchstatus: there is no patch |
It would be nice if we could test coreboot images in VirtualBox, see
VirtualBox does not (yet) provide a simple mechanism to use a different
BIOS in their emulated machines (something like "-L" in qemu). Instead the
BIOS image (a custom bochs BIOS + LGPL'g VGABIOS) is converted to C code
(an array of bytes, or the like) and merged into the VirtualBox
The relevant files are
if someone want to hack VirtualBox to easily support using coreboot images
instead of their usual BIOS.
Ticket URL: <http://tracker.coreboot.org/trac/coreboot/ticket/95>
On 10.02.2014 23:47, David Hendricks wrote:
> On Sun, Feb 9, 2014 at 4:50 AM, Paul Menzel
> <mailto:firstname.lastname@example.org>> wrote:
> Dear coreboot folks,
> currently no coreboot messages are stored for boards not supporting
> CBMEM console (or where this option is disabled (currently by default))
> or no coreboot *romstage* messages are stored for boards, where the data
> cannot be preserved (passed to ramstage).
> Using the serial (or USB) console all these messages can be captured
> with no problem, so I propose to just add these captured messages into
> the file `serial_console.txt`. Of course this file probably contains
> also the payload and (Linux) kernel log, but I think that is fine.
> SeaBIOS’ `readserial.py` should be used for capturing the messages as it
> adds time stamps.
> Scripting this is going to be hard, as the log is captured on a
> different system. So for now I propose to add it manually.
> I don't think the script itself should be responsible for collecting
> serial output. Instead, how about adding an argument to override the
> default behavior of running "cbmem -c" on the target so that the user
> can pass in a filename? The user will simply capture the serial output
> using whatever tool they like, dump the output to a text file, and run
> the script with an argument to use the file instead of calling "cbmem
> -c". Here is a proof-of-concept: http://review.coreboot.org/#/c/5191 .
This requires user to do right manipulations. While keyboard and chair
are usually fine, the space between them exhibits strong bug-inducing
properties. The idea of the script is to reduce a possibility of user
error creating strange reports. In this case the common erro I expect is
using a stale file fom some other version. It's a particularly nasty one
as at first glance in may look fine but would be almost useless to track
how details changed from one submit to the next. If we let user supply
files at all, it should be added to report, not replace files, and it
should have some prefix to clearly indicate that user was involved in
creating them. E.g. user_serial_log.txt
> But in general I think I agree with Vladimir. CBMEM console should be
> supported and if not then that should be fixed.
> David Hendricks (dhendrix)
> Systems Software Engineer, Google Inc.
I wanted to know which physical port of my multiple USB controllers have
the debug capability. There was no way to find that easily, so I created
a tool which will do most of the work for the user.
The following PCI devices support a USB debug port (says lspci):
The following PCI devices support a USB debug port (says the kernel):
PCI device 0000:00:1d.7, USB bus 3, USB physical port 1
Currently connected high-speed devices:
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
|__ Port 2: Dev 20, If 0, Class=stor., Driver=usb-storage, 480M
The output can be improved, but it's a good start.
HP and other laptop vendors claim to use an AMD A76M chipset in some of
their machines. I have been unable to find any info about (or even
confirm the existence of) the A76M on the AMD website or any other
https://en.wikipedia.org/wiki/Comparison_of_AMD_chipsets is also silent,
but the numbers there suggest the A76M might be a Bolton chipset.
Does anyone know if there are public docs for the A76M (possibly under
another name), and how feasible it is to drive it with current public
(or to-be-released) AGESA?
#201: Error building coreboot for Samsung Exynos5 Google Snow
Reporter: Pete <bluestore.logmein@…> | Owner: stepan@…
Type: defect | Status: new
Priority: major | Milestone:
Component: coreboot | Keywords:
Dependencies: | Patch Status: there is no
I am trying to compile a coreboot rom for the Samsung chromebook Series 3
- Exynos5, i followed the instructions at http://www.coreboot.org/Exynos5
to compile the armv7a-eabi toolchain and evertyhing went ok. At the
menuconfig i selected Google MainBoard, model Snow, exit and save. It
starts to compile until it returns this error:
build/ec/google/chromeec/ec.romstage.o: In function
reference to `recovery_mode_enabled'
collect2: error: ld returned 1 exit status
make: *** [build/cbfs/fallback/romstage.debug] Error 1
Am i missing something?
Also tried make clean and make crossgcc, and even the built went fine,
when i run make always returns this error.
Thank you, Pete
Ticket URL: <https://tracker.coreboot.org/trac/coreboot/ticket/201>
I looked on a couple websites (Pricewatch & Newegg) for ASUS F2A85-M,
but I only found Pros. The wiki page said to contact the mailing list
for details. I'll appreciate any guidance or shopping suggestions. On
the sites I mentioned, I can order motherboards as a part of an
To manufacturers of Chromebooks,
Sorry guys, I have a chromebook myself, and its touchpad is appalling. I've
also tried the chromebooks in stores and they aren't much better.
But have no fear, Alex is here, and has the perfect recipe on how to squash
such hardware bugs early on. Following these steps, you are guaranteed to
never make this mistake again:
1. Go to your favorite bidding site
2. Enter the following search terms: "HP Pavilion M6 1035dx"
3. Find a matching listing
4. Purchase full laptop
5. When you get it, observe its touchpad
6. Notice the big, easy to hit buttons
7. Notice the surface area
8. Notice the smoothness of the surface
9. Notice the ease of moving the pointer
10. Notice the tactile feedback from the buttons
11. Notice the evenness of the force needed to engage the button
12. Notice the fatigue of repeatedly pressing the buttons (hint:there is none)
13. Play with its touchpad
14. Play some more with its touchpad
15. Now play with the Unreleased(TM) Chromebook's touchpad
16. If it seems inferior, it probably is
You'll be making perfect touchpads now, won't you?
-----BEGIN PGP SIGNED MESSAGE-----
After flashing my T60 (ATI X1400) to coreboot my laptop screen will
not come up, even after adjusting the brightness keys. I can output
video fine via DVI via a port replicator. I've heard that other ATI
users have had similar problems and I'm attaching my oprom, dmesg, and
xrandr output for anyone to have a look.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----