SeaBIOS

seabios@seabios.org

4 participants
3801 discussions

Re: [SeaBIOS] DC Mapping
by Fred . 31 Aug '12

31 Aug '12

Can SeaBIOS output colored text? It would be good to highlight keys. such as "Press F12 for menu" then highlight "F12". Other BIOS such as Award and AMI can use colors in text. Example "Press F12 for boot menu", then "F12" is in highlighted color. On Fri, Aug 31, 2012 at 4:21 PM, Christian Gmeiner <christian.gmeiner(a)gmail.com> wrote: > Hi all, > > I posted some patches to the ML and want to discuss a part of if - DC mapping. > > After looking at the patches again, I think I miss understood something :) DC > mapping is used to be able to configure the display controller via the defined > memory region. > > A0000 Graphics Mode > B0000 Monochrome Text Mode > B8000 Color Text Mode > > That would mean that if I map the DC to A0000 I can access its registers via > A0000 + register offset or? If this is the case then drop my last two patches. > > The "bad" thing is that I don't have a "normal" lx800 platform to test all my > patches. > > --- > Christian Gmeiner, MSc > > _______________________________________________ > SeaBIOS mailing list > SeaBIOS(a)seabios.org > http://www.seabios.org/mailman/listinfo/seabios

1 0

iasl-option not working
by Kevin O'Connor 31 Aug '12

31 Aug '12

Hi Michael, I was running through the SeaBIOS release checks when I found that the new iasl-option code in the Makefile seems to choke on older versions of iasl (for example, version 20120123 as shipped with fc13). Can you verify if the iasl detection still works properly for you with the patch below? -Kevin >From 51755c3b5ed9dcdfdef8cee56631d68642bde416 Mon Sep 17 00:00:00 2001 From: Kevin O'Connor <kevin(a)koconnor.net> Date: Wed, 29 Aug 2012 21:27:37 -0400 Subject: [PATCH] Make iasl option check work with older versions of iasl. To: seabios(a)seabios.org Signed-off-by: Kevin O'Connor <kevin(a)koconnor.net> --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 72ee152..45ea48a 100644 --- a/Makefile +++ b/Makefile @@ -221,7 +221,7 @@ $(OUT)vgabios.bin: $(OUT)vgabios.bin.raw tools/buildrom.py ################ DSDT build rules -iasl-option=$(shell if "$(1)" "$(2)" -h > /dev/null 2>&1 \ +iasl-option=$(shell if test -z "`$(1) $(2) 2>&1 > /dev/null`" \ ; then echo "$(2)"; else echo "$(3)"; fi ;) $(OUT)%.hex: src/%.dsl ./tools/acpi_extract_preprocess.py ./tools/acpi_extract.py -- 1.7.11.4

2 4

DC Mapping
by Christian Gmeiner 31 Aug '12

31 Aug '12

Hi all, I posted some patches to the ML and want to discuss a part of if - DC mapping. After looking at the patches again, I think I miss understood something :) DC mapping is used to be able to configure the display controller via the defined memory region. A0000 Graphics Mode B0000 Monochrome Text Mode B8000 Color Text Mode That would mean that if I map the DC to A0000 I can access its registers via A0000 + register offset or? If this is the case then drop my last two patches. The "bad" thing is that I don't have a "normal" lx800 platform to test all my patches. --- Christian Gmeiner, MSc

1 0

What do I pass to cbfs_run_payload() after finding the payload with romfile_find() ?
by Dave Frodin 30 Aug '12

30 Aug '12

I'm having a problem finding/loading/executing a payload from seabios which is now using the romfile functions for cbfs (commit 59d6ca52a7eba5). I do have the cpu_to_be32() patch to get the correct payload destination address. Here's what I had previously that worked before the change... // Output the LCD splash image to the Explorer board struct cbfs_file *file; dprintf(1,"Looking for Explorer LCD splash payload ... "); file = cbfs_finddatafile("img/explorer-splash"); if(file) { dprintf(1," found file [%s]. Loading it...\n ",file->filename); cbfs_run_payload(file); } else dprintf(1,"could NOT find it!\n"); This is where I'm at after the change ... // Output the LCD splash image to the Explorer board struct romfile_s *file; dprintf(1,"Looking for Explorer LCD splash payload ... "); file = romfile_find("img/explorer-splash"); if(file) { dprintf(1," found file [%s]. Loading it...\n ",file->name); <=== everything works up to here // cbfs_run_payload(); } else dprintf(1,"could NOT find it!\n"); The cbfs_run_payload is expecting (cbfs_file *). How do I extract what cbfs_run_payload() wants from what I got back from romfile_find() ? Thanks in advance, Dave

2 2

Re: [SeaBIOS] int10 handling
by Kevin O'Connor 29 Aug '12

29 Aug '12

On Wed, Aug 29, 2012 at 09:36:44AM +0200, Christian Gmeiner wrote: > 2012/8/29 Kevin O'Connor <kevin(a)koconnor.net>: > > On Tue, Aug 28, 2012 at 05:11:22PM +0200, Christian Gmeiner wrote: > >> Hi all, > >> > >> I have made some progress in my flat panel work, but I run into a very > >> interesting problem. > >> It looks like that int10 is not handled by VBios but by SeaBios itself. > > > > The SeaBIOS int10 handler is overwritten by the vgabios. So, for some > > reason the vgabios didn't install a handler. The log excerpt you > > included doesn't go far enough back to see what happenend during the > > vgabios execution. Make sure you are running the vgabios from SeaBIOS > > (not coreboot) and add debugging to it to verify where it is failing. > > > > thanks for the hint... I let coreboot load the option rom to 0xc0000 > but let it not > start and in SeaBios I am using CONFIG_OPTIONROMS_DEPLOYED to start > the loaded VBios. But there is lot to do before the bootsplash gets shown :( SeaBIOS needs to be the sole executor of option roms. Things tend to mysteriously break in any other configuration. -Kevin

2 1

Failed flash recovery & dual BIOS support
by Fred . 29 Aug '12

29 Aug '12

Add support for "dual BIOS" and failed flash recovery. Many motherboards have 2 firmware ICs. Motherboard manufacturers tend to market this as "dual BIOS". It checks the integrity of the BIOS and if it fails the test, then it boots using the other firmware image on the other circuit.

1 0

Re: [SeaBIOS] int10 handling
by Kevin O'Connor 29 Aug '12

29 Aug '12

On Tue, Aug 28, 2012 at 05:11:22PM +0200, Christian Gmeiner wrote: > Hi all, > > I have made some progress in my flat panel work, but I run into a very > interesting problem. > It looks like that int10 is not handled by VBios but by SeaBios itself. The SeaBIOS int10 handler is overwritten by the vgabios. So, for some reason the vgabios didn't install a handler. The log excerpt you included doesn't go far enough back to see what happenend during the vgabios execution. Make sure you are running the vgabios from SeaBIOS (not coreboot) and add debugging to it to verify where it is failing. -Kevin

2 1

int10 handling
by Christian Gmeiner 28 Aug '12

28 Aug '12

Hi all, I have made some progress in my flat panel work, but I run into a very interesting problem. It looks like that int10 is not handled by VBios but by SeaBios itself. ... |0f7a0000| send_cmd : read error (status=51 err=04) |0f7a5000| pmm_free 0x0f7bf000 (detail=0x0f7a6690) |0f7a5000| pmm_free 0x0f7bef80 (detail=0x0f7a6660) |0f7a5000| pmm_free 0x0f7bef00 (detail=0x0f7a6630) |0f7a5000| pmm_free 0x0f7a66f0 (detail=0x0f7a6740) |0f7a0000| pmm_free 0x0f7a5000 (detail=0x0f7a66c0) \0f7a5000/ End thread |0f7a0000| ata_pio_transfer id=0x0f7a0f94 write=0 count=1 bs=512 buf=0x0f7a0d94 |0f7a0000| Read sector id=0x0f7a0f94 dest=0x0f7a0d94 |0f7a0000| pmm_malloc zone=0x0f7afe9b handle=ffffffff size=44 align=10 ret=0x000fdb10 (detail=0x0f7a6740) |0f7a0000| pmm_malloc zone=0x0f7afe93 handle=ffffffff size=80 align=10 ret=0x0f7a66c0 (detail=0x0f7a6710) |0f7a0000| ata0-0: SFCF4096H2BI2SA I Q1 311 STD ATA-0 Hard-Disk (3919 MiBytes) |0f7a0000| pmm_malloc zone=0x0f7afe93 handle=ffffffff size=20 align=10 ret=0x0f7a6670 (detail=0x0f7a6690) |0f7a0000| Registering bootable: ata0-0: SFCF4096H2BI2SA I Q1 311 STD ATA-0 Hard-Disk (3919 MiBytes) (type:2 prio:103 data:fdb10) |0f7a0000| ata_detect resetresult=400f |0f7a0000| powerup iobase=1f0 st=50 |0f7a0000| powerup iobase=1f0 st=0 |0f7a0000| ata_detect ata0-1: sc=55 sn=aa dh=b0 |0f7a0000| send_cmd : DRQ not set (status 00) pmm_free 0x0f7a0000 (detail=0x0f7a63d0) \0f7a0000/ End thread All threads complete. handle_08 handle_76 enter handle_16: a=00000100 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d58 cs=f000 ip=e985 f=0202 handle_08 enter handle_10: a=00000e50 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e72 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e65 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e73 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e73 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e20 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e46 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e31 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e32 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e20 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e66 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e6f b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e72 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e20 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e62 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e6f b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e6f b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e74 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e20 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e6d b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e65 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e6e b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e75 b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e2e b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e0d b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d64 cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e0a b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am enter handle_10: a=00000e0d b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d64 cs=f000 ip=c2de f=0202 Here I am handle_08 enter handle_10: a=00000e0a b=00000000 c=00000000 d=00000000 ds=0000 es=0000 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006d6c cs=f000 ip=c2de f=0202 Here I am Checking for bootsplash pmm_malloc zone=0x0f7afe93 handle=ffffffff size=921655 align=10 ret=0x0f6c5360 (detail=0x0f7a6640) Copying romfile 'bootsplash.bmp' (len 921654) Copying data 921654@0xffe2f3a8 to 921654@0x0f6c5360 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 handle_08 start showing bootsplash pmm_malloc zone=0x0f7afe97 handle=ffffffff size=256 align=10 ret=0x0008ff00 (detail=0x0f7a6610) pmm_malloc zone=0x0f7afe97 handle=ffffffff size=256 align=10 ret=0x0008fe00 (detail=0x0f7a65e0) handle_08 enter handle_10: a=00004f00 b=00000000 c=00000000 d=00000000 ds=0000 es=8ff0 ss=0000 si=00000000 di=00000000 bp=00000000 sp=00006dbc cs=f000 ip=c2de f=0202 Here I am No VBE2 found. was 32454256 pmm_free 0x0f6c5360 (detail=0x0f7a6640) pmm_free 0x0008ff00 (detail=0x0f7a6610) pmm_free 0x0008fe00 (detail=0x0f7a65e0) ... the int10 4f00 should be handled by vbe.c in the VBIOS but it is handled by src/misc.c - "Here I am" output. I am running latest git version of SeaBios with some changes - patch attached. I see nothing that is wrong as the patch only extends the geode stuff. I am quite happy for every hint. --- Christian Gmeiner, MSc

1 0

Next release
by Kevin O'Connor 28 Aug '12

28 Aug '12

Hi, I'm planning on making a SeaBIOS release - version 1.7.1. The goal is to make a release for the upcoming QEMU 1.2.0 release. The QEMU team recently pulled in SeaBIOS revision 5a023065. That revision is just one prior to the head of the current SeaBIOS tree. I'm thinking of just retroactively marking the 5a023065 revision as version 1.7.1. Does anyone know of any bugs that should be fixed prior to marking a release? I know of a bugfix for coreboot payload booting (the be64_to_cpu fix), but that seems to be an infrequent code path. I'm also aware of several feature patches pending (alt-numpad patch, geode vga improvements, ipmi patches, ACPI LNKS patch, dynamic SSDT patches, PCI v3 support patch, and PMTIMER patches). Apologies for falling behind on these pending patches. However, I think all of these can wait until after tagging the next version. Unless something comes up, I'll likely tag the next release on Wednesday. Thanks, -Kevin

2 2

Re: [SeaBIOS] [Qemu-devel] [Bug 1042084] [NEW] Windows 7 guest cannot boot after seabios updated
by Gerd Hoffmann 28 Aug '12

28 Aug '12

On 08/28/12 10:07, Stefan Hajnoczi wrote: > On Mon, Aug 27, 2012 at 7:54 AM, Vic <llyzs(a)163.com> wrote: >> Public bug reported: >> >> Hi, >> >> I can no longer boot my Windows 7 guest after this commit (update >> seabios to latest master) >> >> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=01afdadc92e71e29700e64f3a5f4… >> >> When I tried to boot Windows, it BSOD and said "The BIOS in this system >> is not fully ACPI compliant. Please contact your system vendor for an >> updated BIOS". Reverting this commit will fix the issue. > > Gerd, Kevin: Any ideas? Not yet. My win7 32bit guests boots fine. Installing 64bit version right now to see how that behaves, at least the windows setup booted just fine too. cheers, Gerd

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS