Tyan S2891 - Revision history

Stepan: /* VGA BIOS */

2010-04-29T17:40:40Z

‎VGA BIOS

Show changes

Uwe: Tyan S2891 Build Tutorial moved to Tyan S2891

2008-11-16T15:01:40Z

Tyan S2891 Build Tutorial moved to Tyan S2891

Leio: Add tutorials category, so it would show up in the tutorials list, as seen by Bari

2008-06-02T13:45:08Z

Add tutorials category, so it would show up in the tutorials list, as seen by Bari

Stepan at 16:36, 16 January 2008

2008-01-16T16:36:57Z

Uwe: Cosmetics.

2007-09-27T13:39:46Z

Cosmetics.

Ward: /* Status */

2007-09-25T15:49:57Z

‎Status

Ward: /* Status */

2007-09-25T15:38:00Z

‎Status

Ward at 15:37, 25 September 2007

2007-09-25T15:37:27Z

Ward at 15:30, 25 September 2007

2007-09-25T15:30:03Z

Ward: /* Payload */

2007-06-20T22:12:34Z

‎Payload

← Older revision		Revision as of 13:45, 2 June 2008
Line 345:		Line 345:

	{{GPL}}		{{GPL}}
		+	[[Category:Tutorials]]

@@ Line 50: / Line 50: @@
 | Serial port (COM1)
 | style="background:lime" | Works
-| Serial console for LinuxBIOS and Linux is fully operational.
+| Serial console for coreboot and Linux is fully operational.
 |- bgcolor="#eeeeee" valign="top"
 | PS/2 keyboard
@@ Line 79: / Line 79: @@
    http://www.ioss.com.tw/web/English/WheretoBuy.html
-Unfortunately the largest BiosSavior of the PMC type is only 512Kbyte; the proprietary BIOS is 1024Kbyte large. You can build a LinuxBIOS image in 512Kbyte, so this should not be a problem; you may want to buy a couple of extra 1Mbyte PLCC chips to save a copy of the original BIOS, and put it somewhere safe.
+Unfortunately the largest BiosSavior of the PMC type is only 512Kbyte; the proprietary BIOS is 1024Kbyte large. You can build a coreboot image in 512Kbyte, so this should not be a problem; you may want to buy a couple of extra 1Mbyte PLCC chips to save a copy of the original BIOS, and put it somewhere safe.
-While LinuxBIOS replaces the functions of the proprietary BIOS, it does ''not'' replace the VGA BIOS. If you want VGA on your LinuxBIOS'd machine (not strictly necessary for servers), you will need to extract the VGA BIOS and concatenate it with the LinuxBIOS image, before burning it to your ROM. See below for details.
+While coreboot replaces the functions of the proprietary BIOS, it does ''not'' replace the VGA BIOS. If you want VGA on your corebooted machine (not strictly necessary for servers), you will need to extract the VGA BIOS and concatenate it with the coreboot image, before burning it to your ROM. See below for details.
 This wiki page is maintained by Ward Vandewege (ward at gnu dot org).
@@ Line 87: / Line 87: @@
 ===Hardware===
-The S2891 comes with a 8Mbit BIOS chip (SST 49LF080A). This is sufficient to have a fully functional LinuxBIOS with FILO or LAB payload, as described below.
+The S2891 comes with a 8Mbit BIOS chip (SST 49LF080A). This is sufficient to have a fully functional coreboot with FILO or LAB payload, as described below.
 ===Payload===
-LinuxBIOS requires a [[Payloads|payload]] to boot an operating system.
+coreboot requires a [[Payloads|payload]] to boot an operating system.
 If you want to boot from the network, you will need to use [http://www.etherboot.org Etherboot].
@@ Line 103: / Line 103: @@
 === Building the payload ===
-You can build a LinuxBIOS image with a kconfig-style configuration tool (buildrom) if you want to use FILO or LAB. This is by far the easiest way to build a ROM image.
+You can build a coreboot image with a kconfig-style configuration tool (buildrom) if you want to use FILO or LAB. This is by far the easiest way to build a ROM image.
 ===Buildrom===
@@ Line 109: / Line 109: @@
 Check out buildrom:
-   svn co svn://linuxbios.org/buildrom
+   svn co svn://coreboot.org/buildrom
 Now configure buildrom:
@@ Line 196: / Line 196: @@
 ===VGA BIOS===
-Skip this section if you don't need VGA support in your LinuxBIOS.
+Skip this section if you don't need VGA support in your coreboot.
 The S2891 VGA BIOS is 36K long. The last 4KB are not available in RAM after boot (with the proprietary BIOS), however, so we can ''not'' use this method to extract the VGA BIOS:
@@ Line 319: / Line 319: @@
 After a bit of fun with 'strings', we can deduce that the OPROM1.rom file contains our VGA BIOS.
-So, now that we have the proper VGA BIOS image (36K long), we need to concatenate the VGA BIOS with the LinuxBIOS image
+So, now that we have the proper VGA BIOS image (36K long), we need to concatenate the VGA BIOS with the coreboot image
-   cat OPROM1.rom tyan-s2891.rom > final_linuxbios.rom
+   cat OPROM1.rom tyan-s2891.rom > final_coreboot.rom
 ===Burning the BIOS===
@@ Line 329: / Line 329: @@
 On the target machine:
-    cd LinuxBIOSv2/util/flashrom
+    cd coreboot-v2/util/flashrom
-    ./flashrom -v -w path/to/your/final_linuxbios.rom
+    ./flashrom -v -w path/to/your/final_coreboot.rom
-If you want VGA support, make sure you burn the final_linuxbios.rom image!
+If you want VGA support, make sure you burn the final_coreboot.rom image!
-===Booting LinuxBIOS===
+===Booting coreboot===
-You now need to 'halt' the machine. A soft reset won't work the first time you boot from the proprietary BIOS into LinuxBIOS.
+You now need to 'halt' the machine. A soft reset won't work the first time you boot from the proprietary BIOS into coreboot.
-Since we set up serial output in the LinuxBIOS configuration files above, you will want to hook up a serial console (or a copy of minicom or the like) to see what the box is doing while starting up. Keep your eyes on the screen after hitting the power button - LinuxBIOS will be up and running way before you expect it!
+Since we set up serial output in the coreboot configuration files above, you will want to hook up a serial console (or a copy of minicom or the like) to see what the box is doing while starting up. Keep your eyes on the screen after hitting the power button - coreboot will be up and running way before you expect it!
 If you have problems, don't despair. Power down the box, switch the BiosSavior to 'ORG' and boot in the proprietary BIOS. Just don't forget to switch the BiosSavior back to the 'RD1' position before flashing the BIOS!

@@ Line 1: / Line 1: @@
 ===Status===
@@ Line 28: / Line 26: @@
 | SATA
 | style="background:yellow" | WIP
-| There are issues with disk detection on the C804 chipset. This is [http://linuxbios.org/pipermail/linuxbios/2007-September/024937.html being investigated]
+| There are issues with disk detection on the CK804 chipset. This is [http://linuxbios.org/pipermail/linuxbios/2007-September/024937.html being investigated].
 |- bgcolor="#eeeeee" valign="top"
 | USB
@@ Line 81: / Line 79: @@
    http://www.ioss.com.tw/web/English/WheretoBuy.html
-Unfortunately the largest BiosSavior of the PMC type is only 512Kbyte; the proprietary bios is 1024Kbyte large. You can build a LinuxBIOS image in 512Kbyte, so this should not be a problem; you may want to buy a couple of extra 1Mbyte PLCC chips to save a copy of the original BIOS, and put it somewhere safe.
+Unfortunately the largest BiosSavior of the PMC type is only 512Kbyte; the proprietary BIOS is 1024Kbyte large. You can build a LinuxBIOS image in 512Kbyte, so this should not be a problem; you may want to buy a couple of extra 1Mbyte PLCC chips to save a copy of the original BIOS, and put it somewhere safe.
-While LinuxBIOS replaces the functions of the proprietary bios, it does NOT replace the VGA bios. If you want VGA on your linuxBIOS'd machine (not strictly necessary for servers), you will need to extract the VGA bios and concatenate it with the LinuxBIOS image, before burning it to your ROM. See below for details.
+While LinuxBIOS replaces the functions of the proprietary BIOS, it does ''not'' replace the VGA BIOS. If you want VGA on your LinuxBIOS'd machine (not strictly necessary for servers), you will need to extract the VGA BIOS and concatenate it with the LinuxBIOS image, before burning it to your ROM. See below for details.
 This wiki page is maintained by Ward Vandewege (ward at gnu dot org).
@@ Line 93: / Line 91: @@
 ===Payload===
-LinuxBIOS requires a [http://linuxbios.org/index.php/Payloads Payload] to boot an operating system.
+LinuxBIOS requires a [[Payloads|payload]] to boot an operating system.
 If you want to boot from the network, you will need to use [http://www.etherboot.org Etherboot].
-If you want to boot from an IDE drive, USB stick or CDROM, you can use [http://linuxbios.org/index.php/FILO FILO].
+If you want to boot from an IDE drive, USB stick or CDROM, you can use [[FILO]].
-Booting from SATA is a bit harder; the CK804 chipset on this board does not support a legacy IDE mode, so FILO and Etherboot can not boot directly from SATA (see [http://linuxbios.org/pipermail/linuxbios/2006-May/014654.html]).
+Booting from SATA is a bit harder; the CK804 chipset on this board does not support a legacy IDE mode, so FILO and Etherboot [http://linuxbios.org/pipermail/linuxbios/2006-May/014654.html can not boot directly from SATA].
-In order to boot from SATA, we need to use 'linux-as-a-bootloader' (LAB) as a payload. You will need a 1MB ROM chip (thankfully the s2891 comes with a 1MB ROM chip) for this payload. It consists of a (stripped down) kernel + busybox, which can then be used to kexec a kernel from disk. If your disks are playing up, you will still have a busybox environment on boot, which could be useful for debugging.
+In order to boot from SATA, we need to use 'linux-as-a-bootloader' (LAB) as a payload. You will need a 1MB ROM chip (thankfully the S2891 comes with a 1MB ROM chip) for this payload. It consists of a (stripped down) kernel + busybox, which can then be used to kexec a kernel from disk. If your disks are playing up, you will still have a busybox environment on boot, which could be useful for debugging.
 === Building the payload ===
@@ Line 126: / Line 124: @@
    deploy/tyan-s2891.rom
-This image will be exactly 988KB large, leaving 36KB for the VGA bios.
+This image will be exactly 988KB large, leaving 36KB for the VGA BIOS.
 ====FILO payload====
@@ Line 134: / Line 132: @@
 When using FILO in GRUB emulation mode, it's important to get a few details right in your GRUB boot stanza. This is what mine looks like:
-<pre>
+  title   Ubuntu LB, kernel 2.6.21-rc3
-title   Ubuntu LB, kernel 2.6.21-rc3
+  root    (hd4,0)
-root    (hd4,0)
+  kernel    /boot/vmlinuz-2.6.21-rc3 root=/dev/sda1 ro console=tty0 console=ttyS0,115200
-kernel    /boot/vmlinuz-2.6.21-rc3 root=/dev/sda1 ro console=tty0 console=ttyS0,115200
+  savedefault
-savedefault
+  boot
 boot
-</pre>
-Note the root device - FILO sees the first sata device as hd4.
+Note the root device &mdash; FILO sees the first SATA device as hd4.
 In order to get serial output from GRUB, you will also need to add something like this to your menu.lst:
@@ Line 194: / Line 190: @@
 The binary will also be considerably larger than its dynamically linked cousin.
-Note that you <b>must</b> build a 32-bit version of kexec, because buildrom puts a 32 bit kernel into the ROM image. A 32-bit kexec can kexec into a 64 bit kernel, so if your system is 64 bit this will work just fine.
+Note that you '''must''' build a 32-bit version of kexec, because buildrom puts a 32 bit kernel into the ROM image. A 32-bit kexec can kexec into a 64 bit kernel, so if your system is 64 bit this will work just fine.
 The LAB code currently expects lab.conf and kexec to live in / on /dev/sda1.
-===VGA bios===
+===VGA BIOS===
 Skip this section if you don't need VGA support in your LinuxBIOS.
-The s2891 VGA bios is 36K long. The last 4KB are not available in RAM after boot (with the proprietary BIOS), however, so we can NOT use this method to extract the VGA BIOS:
+The S2891 VGA BIOS is 36K long. The last 4KB are not available in RAM after boot (with the proprietary BIOS), however, so we can ''not'' use this method to extract the VGA BIOS:
    While booted with your proprietary BIOS, you can see where your vga bios starts
@@ Line 213: / Line 209: @@
    make out 'ATI RAGE' etc.
-So this does not work - the last 4K is missing. Thankfully, Anton Borisov has some tools that can extract the VGA BIOS - and other option ROMs, in fact - from the BIOS images that Tyan offers on its website.
+So this does not work - the last 4K is missing. Thankfully, Anton Borisov has some tools that can extract the VGA BIOS &mdash; and other option ROMs, in fact &mdash; from the BIOS images that Tyan offers on its website.
 You can download the tool for Phoenix here:
@@ Line 219: / Line 215: @@
    http://www.kaos.ru/biosgfx/download/PhoenixDeco_0.33.src.tar.gz
-Then download the latest proprietary BIOS for the s2891 from the TYAN website:
+Then download the latest proprietary BIOS for the S2891 from the Tyan website:
    http://www.tyan.com/support_download_bios.aspx?model=S.S2891
@@ Line 321: / Line 317: @@
    -rw-r--r-- 1 ward ward   8208 2007-06-20 15:16 UPDATE0.rom
-After a bit of fun with 'strings', we can deduce that the OPROM1.rom file contains our VGA bios.
+After a bit of fun with 'strings', we can deduce that the OPROM1.rom file contains our VGA BIOS.
-So, now that we have the proper VGA bios image (36K long), we need to concatenate the VGA bios with the linuxbios image
+So, now that we have the proper VGA BIOS image (36K long), we need to concatenate the VGA BIOS with the LinuxBIOS image
-   <code>cat OPROM1.rom tyan-s2891.rom > final_linuxbios.rom</code>
+   cat OPROM1.rom tyan-s2891.rom > final_linuxbios.rom
-===Burning the bios===
+===Burning the BIOS===
-Make sure your Biossavior is set to the 'RD1' position (not to 'ORG'!), so that you can always revert to the original bios.
+Make sure your BiosSavior is set to the 'RD1' position (not to 'ORG'!), so that you can always revert to the original BIOS.
 On the target machine:
@@ Line 344: / Line 340: @@
 Since we set up serial output in the LinuxBIOS configuration files above, you will want to hook up a serial console (or a copy of minicom or the like) to see what the box is doing while starting up. Keep your eyes on the screen after hitting the power button - LinuxBIOS will be up and running way before you expect it!
-If you have problems, don't despair. Power down the box, switch the biossavior to 'ORG' and boot in the proprietary BIOS. Just don't forget to switch the biossavior back to the 'RD1' position before flashing the BIOS!
+If you have problems, don't despair. Power down the box, switch the BiosSavior to 'ORG' and boot in the proprietary BIOS. Just don't forget to switch the BiosSavior back to the 'RD1' position before flashing the BIOS!
-See what went wrong, and subscribe and post to the friendly and helpful [http://wiki.linuxbios.org/index.php/Mailinglist mailing list] if you can't figure it out by yourself.
+See what went wrong, and subscribe and post to the friendly and helpful [[Mailinglist|mailing list]] if you can't figure it out by yourself.

@@ Line 59: / Line 59: @@
 |- bgcolor="#eeeeee" valign="top"
 | PS/2 mouse
-| style="background:lime" | Works
+| style="background:yellow" | ?
 | &mdash;
 |- bgcolor="#eeeeee" valign="top"

@@ Line 32: / Line 32: @@
 | USB
 | style="background:yellow" | ?
+| &mdash;
 |- bgcolor="#eeeeee" valign="top"
 | On-board ethernet
@@ Line 74: / Line 74: @@
 | &mdash;
 |}
 ===Before you begin===

@@ Line 24: / Line 24: @@
 If you want to boot from an IDE drive, USB stick or CDROM, you can use [http://linuxbios.org/index.php/FILO FILO].
-Booting from SATA is problematic; the CK804 chipset on this board does not support a legacy IDE mode, so FILO and Etherboot can not boot directly from SATA (see [http://linuxbios.org/pipermail/linuxbios/2006-May/014654.html]). Putting a tiny Linux kernel in the rom image solves this problem though.
+Booting from SATA is a bit harder; the CK804 chipset on this board does not support a legacy IDE mode, so FILO and Etherboot can not boot directly from SATA (see [http://linuxbios.org/pipermail/linuxbios/2006-May/014654.html]).
-===Building the payload===
+In order to boot from SATA, we need to use 'linux-as-a-bootloader' (LAB) as a payload. You will need a 1MB ROM chip (thankfully the s2891 comes with a 1MB ROM chip) for this payload. It consists of a (stripped down) kernel + busybox, which can then be used to kexec a kernel from disk. If your disks are playing up, you will still have a busybox environment on boot, which could be useful for debugging.
-TODO: this is work-in-progress. Come back in a bit...
+=== Building the payload ===
-In order to boot from a SATA disk, we use ... a kernel in the rom image.
+You can build a LinuxBIOS image with a kconfig-style configuration tool (buildrom) if you want to use FILO or LAB. This is by far the easiest way to build a ROM image.
-In order to get serial output from Grub, you will also need to add something like this to your menu.list:
+Check out buildrom:
    # serial port 0
@@ Line 39: / Line 75: @@
    terminal --timeout=15 serial console
-===Building LinuxBIOS===
+====LAB payload====
-Download LinuxBIOS (http://linuxbios.org/index.php/Download_LinuxBIOS).
+Skip this section if you use the FILO payload.
-If you want VGA support, a few changes are required in the linuxbios source tree. Edit this file:
+The LAB payload expects a file /lab.conf on /dev/sda1 with contents like this:
-   src/mainboard/tyan/s2891/Options.lb
+   CMDLINE="root=/dev/sda1 ro console=tty0 console=ttyS0,115200"
-You'll need to enable the following two lines:
+This is the kernel that you will be running after boot. It will be kexec'ed by the kernel that is burned into your ROM chip.
-  #VGA Console
+You will also need a statically linked copy of kexec, which the LAB payload expects to reside at
-  default CONFIG_CONSOLE_VGA=1
-  default CONFIG_PCI_ROM_RUN=1
-Whether you want VGA or not, build a tyan/s2891 tree.
+  /sbin/kexec
-  cd targets
+If you are on a Debian-based system, you can easily recompile your kexec package to be statically linked by following these instructions:
-  ./buildtarget tyan/s2891
-Modify tyan/s2891/Config.lb; change payload setting to point to your payload elf file<br>
+  cd /usr/src
-If you don't need VGA, you will need to modify tyan/s2891/Config.lb. Comment out the line:
+Now edit kexec-tools-1.101-kdump10/kexec-tools-1.101/kexec/Makefile, change line 53 to
-  option ROM_SIZE = 1024*1024-48*1024
+(you're adding the LDFLAGS variable)
-If you do need VGA, modify the ROM_SIZE line to the following, because our VGA bios is only 36KB, not 48K:
+  cd kexec-tools-1.101-kdump10
-  option ROM_SIZE = 1024*1024-36*1024
+Adjust the package name as necessary for your distribution. You can tell if your copy of kexec is statically linked by running 'file' on it:
-NOTE: if you are planning to put the image in the built-in BiosSavior chip (which is only 512Kbyte), use this ROM_SIZE:
+  file /sbin/kexec
-  option ROM_SIZE = 512*1024-36*1024
+If all is well, you will see something like this:
-Build the image:
+  /sbin/kexec: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, statically linked, for GNU/Linux 2.2.0, stripped
-  cd tyan/s2891/s2891
+The binary will also be considerably larger than its dynamically linked cousin.
-  make
-If you see compilation errors, make sure you have GCC's stack protector disabled. See the [[stack protector]] page to deal with that.
+The LAB code currently expects lab.conf and kexec to live in / on /dev/sda1.
 ===VGA bios===
@@ Line 206: / Line 250: @@
 So, now that we have the proper VGA bios image (36K long), we need to concatenate the VGA bios with the linuxbios image
-   <code>cat OPROM1.rom linuxbios.rom > final_linuxbios.rom</code>
+   <code>cat OPROM1.rom tyan-s2891.rom > final_linuxbios.rom</code>
 ===Burning the bios===
@@ Line 215: / Line 259: @@
     cd LinuxBIOSv2/util/flashrom
-    ./flashrom -v -w path/to/your/linuxbios.rom
+    ./flashrom -v -w path/to/your/final_linuxbios.rom
 If you want VGA support, make sure you burn the final_linuxbios.rom image!