Re: [coreboot] coreboot Digest, Vol 113, Issue 17

[Wen Wang]

Paul,

Attached please find the console log for coreboot and seabios (not really
anything).

Since my board does not have a physical VGA adapter. I did not configure
anything for VGA in coreboot.  Do I need to configure anything to tell
coreboot to load the sgabios? As you can see in the log, there is nothing
indicating coreboot loading the sgabios.

Thanks!

Wen

PS: I set my outlook to send plain text. Hope the setting works. :-)

Date: Fri, 11 Jul 2014 23:10:25 +0200
From: Paul Menzel 
To: [e-mail]
Subject: Re: [coreboot] sgabios no console output from Seabios
Message-ID: 
Content-Type: text/plain; charset="utf-8"

Dear Wen,

Am Freitag, den 11.07.2014, 10:41 -0400 schrieb Wen Wang:
> I am experimenting Coreboot on an Intel Rangeley based system using 
> Seabios
> (master) as payload. The system does not have VGA adapter. So I added 
> sgabios.

welcome to coreboot! Please note that the official spelling of coreboot is
all lowercase. (Also SeaBIOS.)
> $ ./build/cbfstool build/coreboot.rom print
>
> coreboot.rom: 8192 kB, bootblocksize 720, romsize 8388608, offset 
> 0x400000
>
> Alignment: 64 bytes
>
> Name                           Offset     Type         Size
>
> cpu_microcode_blob.bin         0x0        microcode    166976
>
> cmos_layout.bin                0x28c80    cmos layout  1164
>
> fallback/coreboot_ram          0x29140    stage        41355
>
> config                         0x33340    raw          3307
>
> vgaroms/sgabios.bin            0x34080    raw          4096
>
> (empty)                        0x350c0    null         44696
>
> fallback/romstage              0x3ff80    stage        182967
>
> fallback/payload               0x6cac0    payload      58701
>
> (empty)                        0x7b080    null         3165976
>
> FvFsp.bin                      0x37ffc0   raw          372736
>
> (empty)                        0x3db000   null         150760
>
> However I don't see Seabios boot menu on console. The system pauses 
> after Seabios is loaded and then starts OS.  There is no problem with 
> Coreboot and Linux console output, but no output from Seabios is seen 
> at all on the console.
>
> ..
>
> Payload (probably SeaBIOS) loaded into a reserved area in the lower 
> 1MB
>
> Loading Segment: addr: 0x00000000000e4350 memsz: 0x000000000001bcb0

filesz:
> 0x000000000000e50c
>
> lb: [0x0000000000100000, 0x00000000001a4000)
>
> Post relocation: addr: 0x00000000000e4350 memsz: 0x000000000001bcb0

filesz:
> 0x000000000000e50c
>
> using LZMA
>
> [ 0x000e4350, 00100000, 0x00100000) <- ffc6cb30
>
> dest 000e4350, end 00100000, bouncebuffer 7fc98000
>
> Loaded segments
>
> Jumping to boot code at fd567
>
> entry    = 0x000fd567
>
> lb_start = 0x00100000
>
> lb_size  = 0x000a4000
>
> adjust   = 0x7fc3c000
>
> buffer   = 0x7fc98000
>  elf_boot_notes = 0x001185b4
>
> adjusted_boot_notes = 0x7fd545b4
>
> [    0.000000] Initializing cgroup subsys cpuset
> [    0.000000] Initializing cgroup subsys cpu..
>
> Seabios (master) is pulled and automatically built as part of the 
> coreboot build. During the build, it popped out a menu to for VGA hardware

type.
> VGA Hardware Type
> > None (NO_VGABIOS)
> GeodeGX2 (VGA_GEODEGX2)
> GeodeLX (VGA_GEODELX)
> coreboot linear framebuffer (VGA_COREBOOT) (NEW)
>
> choice[1-4]:
>
> I tried both 1 and 4. Neither of them seem to work. Did I miss something?

I did not spot anything. Could you please attach/paste the whole coreboot
and SeaBIOS log?

Thanks,

Paul

PS: Could you please just send plain text messages, that means no HTML, to
the list? Big thanks in advance.

sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

[Paul Menzel]

Dear Wen,

Am Sonntag, den 13.07.2014, 17:35 -0400 schrieb Wen Wang:
> Attached please find the console log for coreboot and seabios (not really
> anything).

very strange.

$ grep SERIAL payloads/external/SeaBIOS/Makefile.inc
        	echo "CONFIG_DEBUG_SERIAL=y" >> $(OUT)/seabios/.config
        	echo "CONFIG_DEBUG_SERIAL_PORT=0x3f8" >> $(OUT)/seabios/.config

Could you take a look at the file `.config` in the build directory of
SeaBIOS and check that everything is set correctly?

How did you capture the log? I guess the serial console, but want to
make sure. I have no idea why the SeaBIOS messages go missing.

You could try to configure build SeaBIOS yourself and add that to the image.

You could try to enable CBMEM console in coreboot and in SeaBIOS. No
coreboot messages will be captured to my knowledge on Intel devices with
FSP software, but maybe the SeaBIOS messages survive. You can read it
out with `cbmem -c` from `util/cbmem/`.
> Since my board does not have a physical VGA adapter. I did not configure
> anything for VGA in coreboot.  Do I need to configure anything to tell
> coreboot to load the sgabios? As you can see in the log, there is nothing
> indicating coreboot loading the sgabios.

SeaBIOS should load all the Option ROMs.

By the way, what is your use case for SGABIOS?

Thanks,

Paul
> PS: I set my outlook to send plain text. Hope the setting works. :-)

It worked! Thanks a lot! Two more nitpicks as you use digest mode.
Please update the summary of the message and also add the correct
In-Reply-To header field so that the messages are threaded correctly. I
guess the second thing is not easy to do in Microsoft Outlook. Maybe
just deactivate the digest mode and use the “normal” mode as long as you
are actively communicating with the list.

sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

[Wen Wang]

Paul,

Thanks for looking into to it!

I pulled the seabios tree and built seabios manually (.config shown below). I then loaded seabios/out/bios.bin.elf as coreboot payload and sgabios as option rom. Unfortunately the same result, no output from seabios at all.

The console log was captured by hyperterm. For sgabios use case, I need to be able to access the seabios boot menu.

Thanks!

Wen

$cat seabios/.config
#
# Automatically generated file; DO NOT EDIT.
# SeaBIOS Configuration
#

#
# General Features
#
CONFIG_COREBOOT=y
# CONFIG_QEMU is not set
# CONFIG_CSM is not set
# CONFIG_QEMU_HARDWARE is not set
CONFIG_THREADS=y
CONFIG_RELOCATE_INIT=y
CONFIG_BOOTMENU=y
CONFIG_BOOTSPLASH=y
CONFIG_BOOTORDER=y
CONFIG_COREBOOT_FLASH=y
CONFIG_LZMA=y
CONFIG_CBFS_LOCATION=0
CONFIG_FLASH_FLOPPY=y
CONFIG_ENTRY_EXTRASTACK=y
CONFIG_MALLOC_UPPERMEMORY=y
CONFIG_ROM_SIZE=0

#
# Hardware support
#
CONFIG_ATA=y
# CONFIG_ATA_DMA is not set
# CONFIG_ATA_PIO32 is not set
CONFIG_AHCI=y
CONFIG_MEGASAS=y
CONFIG_FLOPPY=y
CONFIG_PS2PORT=y
CONFIG_USB=y
CONFIG_USB_UHCI=y
CONFIG_USB_OHCI=y
CONFIG_USB_EHCI=y
CONFIG_USB_XHCI=y
CONFIG_USB_MSC=y
CONFIG_USB_UAS=y
CONFIG_USB_HUB=y
CONFIG_USB_KEYBOARD=y
CONFIG_USB_MOUSE=y
CONFIG_SERIAL=y
CONFIG_LPT=y
CONFIG_PMTIMER=y

#
# BIOS interfaces
#
CONFIG_DRIVES=y
CONFIG_CDROM_BOOT=y
CONFIG_CDROM_EMU=y
CONFIG_PCIBIOS=y
CONFIG_APMBIOS=y
CONFIG_PNPBIOS=y
CONFIG_OPTIONROMS=y
CONFIG_PMM=y
CONFIG_BOOT=y
CONFIG_KEYBOARD=y
CONFIG_KBD_CALL_INT15_4F=y
CONFIG_MOUSE=y
CONFIG_S3_RESUME=y
CONFIG_VGAHOOKS=y
# CONFIG_DISABLE_A20 is not set

#
# VGA ROM
#
CONFIG_NO_VGABIOS=y
# CONFIG_VGA_GEODEGX2 is not set
# CONFIG_VGA_GEODELX is not set
# CONFIG_VGA_COREBOOT is not set
# CONFIG_BUILD_VGABIOS is not set
CONFIG_VGA_EXTRA_STACK_SIZE=512

#
# Debugging
#
CONFIG_DEBUG_LEVEL=3
CONFIG_DEBUG_SERIAL=y
CONFIG_DEBUG_SERIAL_PORT=0x3f8
CONFIG_DEBUG_COREBOOT=y

-----Original Message-----
From: Paul Menzel [mailto:[e-mail]] 
Sent: Sunday, July 13, 2014 6:46 PM
To: Wen Wang
Cc: [e-mail]
Subject: Re: sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

Dear Wen,

Am Sonntag, den 13.07.2014, 17:35 -0400 schrieb Wen Wang:
> Attached please find the console log for coreboot and seabios (not 
> really anything).

very strange.

$ grep SERIAL payloads/external/SeaBIOS/Makefile.inc
        	echo "CONFIG_DEBUG_SERIAL=y" >> $(OUT)/seabios/.config
        	echo "CONFIG_DEBUG_SERIAL_PORT=0x3f8" >> $(OUT)/seabios/.config

Could you take a look at the file `.config` in the build directory of SeaBIOS and check that everything is set correctly?

How did you capture the log? I guess the serial console, but want to make sure. I have no idea why the SeaBIOS messages go missing.

You could try to configure build SeaBIOS yourself and add that to the image.

You could try to enable CBMEM console in coreboot and in SeaBIOS. No coreboot messages will be captured to my knowledge on Intel devices with FSP software, but maybe the SeaBIOS messages survive. You can read it out with `cbmem -c` from `util/cbmem/`.
> Since my board does not have a physical VGA adapter. I did not 
> configure anything for VGA in coreboot.  Do I need to configure 
> anything to tell coreboot to load the sgabios? As you can see in the 
> log, there is nothing indicating coreboot loading the sgabios.

SeaBIOS should load all the Option ROMs.

By the way, what is your use case for SGABIOS?

Thanks,

Paul
> PS: I set my outlook to send plain text. Hope the setting works. :-)

It worked! Thanks a lot! Two more nitpicks as you use digest mode.
Please update the summary of the message and also add the correct In-Reply-To header field so that the messages are threaded correctly. I guess the second thing is not easy to do in Microsoft Outlook. Maybe just deactivate the digest mode and use the “normal” mode as long as you are actively communicating with the list.

sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

[Paul Menzel]

Dear Wen,

Am Montag, den 14.07.2014, 11:32 -0400 schrieb Wen Wang:
> Thanks for looking into to it!
>
> I pulled the seabios tree and built seabios manually (.config shown
> below). I then loaded seabios/out/bios.bin.elf as coreboot payload and
> sgabios as option rom. Unfortunately the same result, no output from
> seabios at all.

If you build and run the utility `cbmem` as shown below, what is the
output of the last two commands?

$ cd util/cbmem
        $ make
        $ sudo cbmem -l
        $ sudo cbmem -c

Thanks,

Paul

sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

[WANG FEI]

Wang Wen,

I found following message in the coreboot-seabios log,

[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.3.4-5.fc17.x86_64
root=UUID=c4d4a429-d880-4caa-831e-9e95b5595f67 ro rd.md=0 rd.lvm=0 rd.dm=0
SYSFONT=True KEYTABLE=us rd.luks=0 LANG=en_US.UTF-8 console=ttyS1,115200n8

It shows "console=ttyS1,115200n8", it means the Linux kernel is using ttyS1
as the primary serial console, which is I/O port 0x2f8. But the seabios
configure file shows seabios is configured using I/O port 0x3f8. it might
be the problem.

Please run "make menuconfig" in seabios and reconfigure the serial port to
0x2f8, let us know any difference.

-Wang Fei

On Mon, Jul 14, 2014 at 9:53 PM, Paul Menzel <
[e-mail]> wrote:
> Dear Wen,
>
> Am Montag, den 14.07.2014, 11:32 -0400 schrieb Wen Wang:
> > Thanks for looking into to it!
> >
> > I pulled the seabios tree and built seabios manually (.config shown
> > below). I then loaded seabios/out/bios.bin.elf as coreboot payload and
> > sgabios as option rom. Unfortunately the same result, no output from
> > seabios at all.
>
> If you build and run the utility `cbmem` as shown below, what is the
> output of the last two commands?
>     $ cd util/cbmem
>     $ make
>     $ sudo cbmem -l
>     $ sudo cbmem -c
>
>
> Thanks,
>
> Paul

sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

[Wen Wang]

Paul,

I am on an old coreboot branch for this Rangeley/fsp experiment. This branch only has cbmem.py utility. I seem to have issue running the python script on target. I will need to spend some time figuring out the problem or switch to the newer cbmem.c to check cbmem.

Meanwhile, as Wang Fei pointed out, I changed seasbios I/O port base address and I am able to see seabios output using sgabios as option rom.

Thanks,

Wen

-----Original Message-----
From: Paul Menzel [mailto:[e-mail]] 
Sent: Monday, July 14, 2014 4:54 PM
To: [e-mail]
Cc: Wen Wang
Subject: Re: [coreboot] sgabios no console output from Seabios (was: coreboot Digest, Vol 113, Issue 17)

Dear Wen,

Am Montag, den 14.07.2014, 11:32 -0400 schrieb Wen Wang:
> Thanks for looking into to it!
>
> I pulled the seabios tree and built seabios manually (.config shown 
> below). I then loaded seabios/out/bios.bin.elf as coreboot payload and 
> sgabios as option rom. Unfortunately the same result, no output from 
> seabios at all.

If you build and run the utility `cbmem` as shown below, what is the output of the last two commands?

$ cd util/cbmem
        $ make
        $ sudo cbmem -l
        $ sudo cbmem -c

Thanks,

Paul