[coreboot] Problems with VIA EPIA-ME6000 Vol2
Klaus Stammermann
klaus123 at ibnoetzold.de
Mon Mar 10 16:22:31 CET 2008
Hi
My original email was not added to mailing list. Therefore I sent it
again. I hope it is not just a delay so it would be a double posting.
Here my original email:
------------------------ Ursprüngliche Nachricht -------------------------
Betreff: Re: [coreboot] Problems with VIA EPIA-ME6000
Von: "Klaus Stammermann" <klaus123 at ibnoetzold.de>
Datum: Mo, 10.03.2008, 16:00
An: coreboot at coreboot.org
--------------------------------------------------------------------------
Hi there
I made some changes on config and now I got vga output. Now I use filo 0.5
as payload and I removed "normal" boot option (just fallback). As vga bios
I got optionroms extend by some 0 to 64K.
Here svn diff on whole coreboot sandbox:
Index: src/mainboard/via/epia-m/Options.lb
=================================================================== ---
src/mainboard/via/epia-m/Options.lb (Revision 3086)
+++ src/mainboard/via/epia-m/Options.lb (Arbeitskopie)
@@ -52,7 +52,7 @@
### Build options
###
default CONFIG_PCI_ROM_RUN=0
-default CONFIG_CONSOLE_VGA=0
+default CONFIG_CONSOLE_VGA=1
##
## Build code for the fallback boot
Index: src/mainboard/via/epia-m/Config.lb
=================================================================== ---
src/mainboard/via/epia-m/Config.lb (Revision 3086)
+++ src/mainboard/via/epia-m/Config.lb (Arbeitskopie)
@@ -181,10 +181,18 @@
device pci 12.0 on end # Ethernet
end
# This is on the EPIA MII, not the M.
- chip southbridge/ricoh/rl5c476
- register "enable_cf" = "1"
- device pci 0a.0 on end
- device pci 0a.1 on end
- end
+# chip southbridge/ricoh/rl5c476
+# register "enable_cf" = "1"
+# device pci 0a.0 on end
+# device pci 0a.1 on end
+# end
end
+ device pci_domain 1 on
+ device pci 0.0 on # PCI
+ chip drivers/pci/onboard
+ device pci 0.0 on end
+ register "rom_address" = "0xfffc0000" #256k image
+ end
+ end
+ end
end
Index: targets/via/epia-m/Config.lb
=================================================================== ---
targets/via/epia-m/Config.lb (Revision 3086)
+++ targets/via/epia-m/Config.lb (Arbeitskopie)
@@ -7,21 +7,21 @@
option DEFAULT_CONSOLE_LOGLEVEL=8
option CONFIG_CONSOLE_SERIAL8250=1
-option ROM_SIZE=256*1024
+option ROM_SIZE=(256*1024)-(64*1024)
option HAVE_OPTION_TABLE=1
option CONFIG_ROM_PAYLOAD=1
option HAVE_FALLBACK_BOOT=1
#option CONFIG_COMPRESSED_PAYLOAD_NRV2B=1
-option CONFIG_COMPRESSED_PAYLOAD_NRV2B=0
+#option CONFIG_COMPRESSED_PAYLOAD_NRV2B=0
###
### Compute the location and size of where this firmware image
### (coreboot plus bootloader) will live in the boot rom chip.
###
-option FALLBACK_SIZE=131072
+option FALLBACK_SIZE=(192*1024)
## Coreboot C code runs at this location in RAM
option _RAMBASE=0x00004000
@@ -29,20 +29,24 @@
#
# Via EPIA M
#
-romimage "normal"
- option USE_FALLBACK_IMAGE=0
-#option ROM_IMAGE_SIZE=128*1024
- option ROM_IMAGE_SIZE=64*1024
- option COREBOOT_EXTRA_VERSION=".0-Normal"
- payload $(HOME)/svn/payload.elf
-end
+#romimage "normal"
+# option USE_FALLBACK_IMAGE=0
+# option ROM_IMAGE_SIZE=(128*1024)-27312
+# option ROM_IMAGE_SIZE=(96*1024)-27312
+# option ROM_IMAGE_SIZE=0xc000
+# option ROM_SECTION_OFFSET=0x10000
+# option ROM_SECTION_SIZE=0x18000
+# option COREBOOT_EXTRA_VERSION=".0-Normal"
+# payload $(HOME)/Entwicklung/LinuxBIOS/VIA-BIOS/filo.small.elf
+#end
romimage "fallback"
option USE_FALLBACK_IMAGE=1
- #option ROM_IMAGE_SIZE=128*1024
- option ROM_IMAGE_SIZE=60*1024
+ option ROM_IMAGE_SIZE=(192*1024)-33104
+# option ROM_IMAGE_SIZE=(96*1024)-27312
+# option ROM_IMAGE_SIZE=0xc000
option COREBOOT_EXTRA_VERSION=".0-Fallback"
- payload $(HOME)/svn/payload.elf
+ payload $(HOME)/Entwicklung/LinuxBIOS/VIA-BIOS/filo.small.05.elf
end
-buildrom ./coreboot.rom ROM_SIZE "normal" "fallback"
+buildrom ./coreboot.rom ROM_SIZE "fallback"
But system does not booting at all. I think device mapping works not
correct. On booting system is checking sda. Some errors like:
exception Emask ... 0x2 frozen
soft resetting port...
configured for UDMA...
(... are inserted by me because I got this output only on display)
At end kernel panic is shown:
0800 2000880 sda driver: sd
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
But installed system starts with original bios. As device I use a CF-disk
on an CF-IDE adapter.
Does anyone get an idea how to solve this problem?
Klaus
Dipl.-Ing.(FH) Klaus Stammermann
Softwareentwickler
--------------------------------------------------
IBN - Ingenieurbüro Nötzold
Technische Informatik & Software-Projektmanagement
Lise-Meitner-Str. 2
24941 Flensburg
FON: +49 (0)461 505 188 10
FAX: +49 (0)461 505 188 18
NET: http://www.ibnoetzold.de
More information about the coreboot
mailing list