Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
coreboot-2.0.0.0-Fallback Mo 18. Feb 16:59:57 CET 2008 starting..."
I tried with a PCI-VGA-card, "option CONFIG_CONSOLE_VGA = 1" and "option CONFIG_PCI_ROM_RUN=1". This breaks up with this error:
"INSTALL REAL-MODE IDT DO THE VGA BIOS found VGA: vid=102b, did=519 rom base, size: fffc0000 write_protect_vgabios bus/devfn = 0xa0 Unexpected Exception: 13 @ 10:00013808 - Halting Code: 0 eflags: 00010002 eax: 00000011 ebx: 000247d4 ecx: 00023f8c edx: 00024a70 edi: 0001a4b0 esi: 00024a70 ebp: 00023f54 esp: 00023f54"
And using VGA-support with onboard device I get this message: "DO THE VGA BIOS found VGA: vid=1106, did=3122 rom base, size: fffc0000 BAD SIGNATURE 0x7f 0x45 Unexpected Exception: 13 @ 10:000130fe - Halting Code: 0 eflags: 00010006 eax: 00000000 ebx: 000247d4 ecx: 80010030 edx: 00000cfc edi: 0001a4b0 esi: 000247d4 ebp: 00023f8c esp: 00023f6c"
What do I have to do to boot with a VGA-card? Are there any options which have to be set?
Else, using onboard vga device I got the vga-bios by PERL-script (www.coreboot.org/VGA_support). Is it right this vga bios has to be insert in front of coreboot image? Should it be 64k big or just as big as it is in original? And on which adresses the parts of vga-bios, normal and fallback (with there payload) have to be set?
Does anyone use this board with coreboot too? Could some show a Config-file for this so I may see my mistakes?
* Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was console=ttyS0,... specified as a command line option to the kernel?
And using VGA-support with onboard device I get this message: "DO THE VGA BIOS found VGA: vid=1106, did=3122 rom base, size: fffc0000 BAD SIGNATURE 0x7f 0x45 Unexpected Exception: 13 @ 10:000130fe - Halting Code: 0 eflags: 00010006 eax: 00000000 ebx: 000247d4 ecx: 80010030 edx: 00000cfc edi: 0001a4b0 esi: 000247d4 ebp: 00023f8c esp: 00023f6c"
What do I have to do to boot with a VGA-card? Are there any options which have to be set?
I think you need a special version of the vga option rom. Have you used the one from the optionroms repo? http://www.coreboot.org/viewvc/trunk/optionroms/?root=optionroms
Stefan
Am Montag, 3. März 2008 21:33 schrieben Sie:
- Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was console=ttyS0,... specified as a command line option to the kernel?
Yes, I use following startup parameters: "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200"
And using VGA-support with onboard device I get this message: "DO THE VGA BIOS found VGA: vid=1106, did=3122 rom base, size: fffc0000 BAD SIGNATURE 0x7f 0x45 Unexpected Exception: 13 @ 10:000130fe - Halting Code: 0 eflags: 00010006 eax: 00000000 ebx: 000247d4 ecx: 80010030 edx: 00000cfc edi: 0001a4b0 esi: 000247d4 ebp: 00023f8c esp: 00023f6c"
What do I have to do to boot with a VGA-card? Are there any options which have to be set?
I think you need a special version of the vga option rom. Have you used the one from the optionroms repo? http://www.coreboot.org/viewvc/trunk/optionroms/?root=optionroms
Stefan
I did not use that optionroms. But how can I use this optionrom? Where do I have to put it in my image?
Klaus
On Tue, Mar 04, 2008 at 08:31:23AM +0100, Klaus Stammermann wrote:
Am Montag, 3. März 2008 21:33 schrieben Sie:
- Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was console=ttyS0,... specified as a command line option to the kernel?
Yes, I use following startup parameters: "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200"
And you also use 'USE_GRUB = 0'? Otherwise FILO will try to read your menu.lst file from GRUB and ignore the above line.
I did not use that optionroms. But how can I use this optionrom? Where do I have to put it in my image?
I think at the beginning (but someone please correct me if I'm wrong), i.e.
cat vga.rom coreboot.com > coreboot_full.rom
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
Uwe.
Am Dienstag, 4. März 2008 12:50 schrieben Sie:
On Tue, Mar 04, 2008 at 08:31:23AM +0100, Klaus Stammermann wrote:
Am Montag, 3. März 2008 21:33 schrieben Sie:
- Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was console=ttyS0,... specified as a command line option to the kernel?
Yes, I use following startup parameters: "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200"
And you also use 'USE_GRUB = 0'? Otherwise FILO will try to read your menu.lst file from GRUB and ignore the above line.
In file Config on filo 0.4.2 I can't find such an option. But I use LINUX_LOADER = 1 which should activate filo as loader for standard Linux kernel image.
I did not use that optionroms. But how can I use this optionrom? Where do I have to put it in my image?
I think at the beginning (but someone please correct me if I'm wrong), i.e.
cat vga.rom coreboot.com > coreboot_full.rom
I think so too but I don't know exactly. So I will try this.
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
Uwe.
Klaus
Am Dienstag, 4. März 2008 12:50 schrieb Uwe Hermann:
On Tue, Mar 04, 2008 at 08:31:23AM +0100, Klaus Stammermann wrote:
Am Montag, 3. März 2008 21:33 schrieben Sie:
- Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was console=ttyS0,... specified as a command line option to the kernel?
Yes, I use following startup parameters: "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200"
And you also use 'USE_GRUB = 0'? Otherwise FILO will try to read your menu.lst file from GRUB and ignore the above line.
I did not use that optionroms. But how can I use this optionrom? Where do I have to put it in my image?
I think at the beginning (but someone please correct me if I'm wrong), i.e.
cat vga.rom coreboot.com > coreboot_full.rom
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
I get some problem at making coreboot.rom smaller. Normal and fallback get 128kb before. I tried two different possibilities to get space for it, but both failed.
I need 57344b. But taking 57344/2 out of both raises error "XIP_ROM_BASE is not multiple of XIP_ROM_SIZE". And reducing one of them about 57344b make breaks because of overleaping sections.
Is there any overview how to use all these option in Config.lb? I think I don't understand the structur of all these options and their results.
Klaus
On Tue, Mar 04, 2008 at 02:42:19PM +0100, Klaus Stammermann wrote:
I think at the beginning (but someone please correct me if I'm wrong), i.e.
cat vga.rom coreboot.com > coreboot_full.rom
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
I get some problem at making coreboot.rom smaller. Normal and fallback get 128kb before. I tried two different possibilities to get space for it, but both failed.
This stuff is highly confusing in coreboot, sorry. Please post your current patch against svn (all changes you made to any files).
Also, where did you get your VGA ROM from? Using which tools (awardeco, amideco, phnxdeco, other)? How big is it exactly?
I hope we can post a patch for you which should build a working coreboot.rom where you can prepend the VGA BIOS with enough information.
I need 57344b. But taking 57344/2 out of both raises error "XIP_ROM_BASE is not multiple of XIP_ROM_SIZE". And reducing one of them about 57344b make
Don't mess with XIP_ROM_SIZE, that's not what you want.
Uwe.
On Tue, Mar 4, 2008 at 7:23 AM, Uwe Hermann uwe@hermann-uwe.de wrote:
Don't mess with XIP_ROM_SIZE, that's not what you want.
yes.
Marc has I believe posted a nice map of the various ROM control parameters and how they work.
I'm sorry it is so messy, we only learned a good way to do this in v3 :-(
Also, don't forget, for changing ROM sizes you should only ever adjust config files in the target directory.
ron
Am Dienstag, 4. März 2008 16:23 schrieben Sie:
On Tue, Mar 04, 2008 at 02:42:19PM +0100, Klaus Stammermann wrote:
I think at the beginning (but someone please correct me if I'm wrong), i.e.
cat vga.rom coreboot.com > coreboot_full.rom
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
I get some problem at making coreboot.rom smaller. Normal and fallback get 128kb before. I tried two different possibilities to get space for it, but both failed.
This stuff is highly confusing in coreboot, sorry. Please post your current patch against svn (all changes you made to any files).
Here the diff: ----------------------------------------------------------------------------------------------------------------------------------- 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) @@ -51,8 +51,8 @@ ### ### Build options ### -default CONFIG_PCI_ROM_RUN=0 -default CONFIG_CONSOLE_VGA=0 +default CONFIG_PCI_ROM_RUN=1 +default CONFIG_CONSOLE_VGA=1
## ## Build code for the fallback boot 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=(96*1024)
## Coreboot C code runs at this location in RAM option _RAMBASE=0x00004000 @@ -31,18 +31,22 @@ # romimage "normal" option USE_FALLBACK_IMAGE=0 -#option ROM_IMAGE_SIZE=128*1024 - option ROM_IMAGE_SIZE=64*1024 +# 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)/svn/payload.elf + 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=(128*1024)-27312 + 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.elf end
buildrom ./coreboot.rom ROM_SIZE "normal" "fallback" ----------------------------------------------------------------------------------------------------------------------------------- In an earlier version I changed Config.lb in src dir to get VGA BIOS. But now it isn't included. If it is important, I could post it later.
Also, where did you get your VGA ROM from? Using which tools (awardeco, amideco, phnxdeco, other)? How big is it exactly?
On http://www.coreboot.org/VGA_support at bottom there is a perl script. Using this I got my VGABIOS. This is 60416 bytes big (optionsrom is 57344 bytes which I used at last).
filo.small.elf is 27312 bytes big. So don't wonder what number this is.
I hope we can post a patch for you which should build a working coreboot.rom where you can prepend the VGA BIOS with enough information.
That would be very nice and I hope we could solve this problems. Sorry but till next monday I can't get more information from my development system. I will look at this mailinglist and maybe some easy information I could give out of my mind.
I need 57344b. But taking 57344/2 out of both raises error "XIP_ROM_BASE is not multiple of XIP_ROM_SIZE". And reducing one of them about 57344b make
Don't mess with XIP_ROM_SIZE, that's not what you want.
OK, that sounds very good :-)
Thank you for your help.
Klaus
On Tue, Mar 04, 2008 at 05:10:40PM +0100, Klaus Stammermann wrote:
Here the diff:
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) @@ -51,8 +51,8 @@ ### ### Build options ### -default CONFIG_PCI_ROM_RUN=0 -default CONFIG_CONSOLE_VGA=0 +default CONFIG_PCI_ROM_RUN=1 +default CONFIG_CONSOLE_VGA=1
Looks ok.
## ## Build code for the fallback boot 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)
OK, assuming you have a 256KB ROM chip and your VGA BIOS is 64KB.
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
Why?
### 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=(96*1024)
Not sure about this. I'd rather not change it unless really necessary (it isn't in this case, I think).
## Coreboot C code runs at this location in RAM option _RAMBASE=0x00004000 @@ -31,18 +31,22 @@ # romimage "normal" option USE_FALLBACK_IMAGE=0 -#option ROM_IMAGE_SIZE=128*1024
- option ROM_IMAGE_SIZE=64*1024
+# option ROM_IMAGE_SIZE=(128*1024)-27312
- option ROM_IMAGE_SIZE=(96*1024)-27312
This is wrong.
ROM_IMAGE_SIZE is the maximum size the coreboot code can use (without payload, without VGA ROM, etc).
Something like 64*1024 is usually ok.
+# option ROM_IMAGE_SIZE=0xc000 +# option ROM_SECTION_OFFSET=0x10000 +# option ROM_SECTION_SIZE=0x18000 option COREBOOT_EXTRA_VERSION=".0-Normal"
- payload $(HOME)/svn/payload.elf
- payload $(HOME)/Entwicklung/LinuxBIOS/VIA-BIOS/filo.small.elf
Never used $(HOME) here, but I assume it works? If not, try /tmp/filo.elf and copy your payload there.
end
romimage "fallback" option USE_FALLBACK_IMAGE=1
- #option ROM_IMAGE_SIZE=128*1024
- option ROM_IMAGE_SIZE=60*1024
+# option ROM_IMAGE_SIZE=(128*1024)-27312
- option ROM_IMAGE_SIZE=(96*1024)-27312
Also wrong, see above.
+# option ROM_IMAGE_SIZE=0xc000 option COREBOOT_EXTRA_VERSION=".0-Fallback"
- payload $(HOME)/svn/payload.elf
- payload $(HOME)/Entwicklung/LinuxBIOS/VIA-BIOS/filo.small.elf
end
buildrom ./coreboot.rom ROM_SIZE "normal" "fallback"
In an earlier version I changed Config.lb in src dir to get VGA BIOS. But now it isn't included. If it is important, I could post it later.
Plese post it.
But the above patch comes from an 'svn diff' at the top-level directory, correct? I.e. all your current changes are in there?
Also, where did you get your VGA ROM from? Using which tools (awardeco, amideco, phnxdeco, other)? How big is it exactly?
On http://www.coreboot.org/VGA_support at bottom there is a perl script. Using this I got my VGABIOS. This is 60416 bytes big
OK. Which vendor BIOS does the board have? Can you use awardeco/amideco/phnxdeco to get the VGA BIOS and compare it with the one from the script? Just to be sure that worked fine...
(optionsrom is 57344 bytes which I used at last).
Huh, what's that? Where from?
filo.small.elf is 27312 bytes big. So don't wonder what number this is.
Are you sure this is ok? The smallest usable FILO I've used so far is ca. 57 KB. Your 27 KB FILO looks _very_ small.
Also, please use the latest version from
% svn co svn://coreboot.org/filo/trunk/filo-0.5
Type 'make' (that will generate a Config file), then edit Config, then type make again.
Uwe.
On Tue, Mar 04, 2008 at 05:10:40PM +0100, Klaus Stammermann wrote:
Here the diff:
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) @@ -51,8 +51,8 @@ ### ### Build options ### -default CONFIG_PCI_ROM_RUN=0 -default CONFIG_CONSOLE_VGA=0 +default CONFIG_PCI_ROM_RUN=1 +default CONFIG_CONSOLE_VGA=1
Looks ok.
## ## Build code for the fallback boot 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)
OK, assuming you have a 256KB ROM chip and your VGA BIOS is 64KB.
I have 256KB ROM and I got some VGA BIOS. One of them is exactly 64KB but that one out of script is smaller (see below).
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
Why?
### 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=(96*1024)
Not sure about this. I'd rather not change it unless really necessary (it isn't in this case, I think).
## Coreboot C code runs at this location in RAM option _RAMBASE=0x00004000 @@ -31,18 +31,22 @@ # romimage "normal" option USE_FALLBACK_IMAGE=0 -#option ROM_IMAGE_SIZE=128*1024
- option ROM_IMAGE_SIZE=64*1024
+# option ROM_IMAGE_SIZE=(128*1024)-27312
- option ROM_IMAGE_SIZE=(96*1024)-27312
This is wrong.
ROM_IMAGE_SIZE is the maximum size the coreboot code can use (without payload, without VGA ROM, etc).
Something like 64*1024 is usually ok.
OK, I will look at that. I got these options out of Config.vga.filo.
+# option ROM_IMAGE_SIZE=0xc000 +# option ROM_SECTION_OFFSET=0x10000 +# option ROM_SECTION_SIZE=0x18000 option COREBOOT_EXTRA_VERSION=".0-Normal"
- payload $(HOME)/svn/payload.elf
- payload $(HOME)/Entwicklung/LinuxBIOS/VIA-BIOS/filo.small.elf
Never used $(HOME) here, but I assume it works? If not, try /tmp/filo.elf and copy your payload there.
I don't think I got problems with this but I can try an absolute path.
end
romimage "fallback" option USE_FALLBACK_IMAGE=1
- #option ROM_IMAGE_SIZE=128*1024
- option ROM_IMAGE_SIZE=60*1024
+# option ROM_IMAGE_SIZE=(128*1024)-27312
- option ROM_IMAGE_SIZE=(96*1024)-27312
Also wrong, see above.
+# option ROM_IMAGE_SIZE=0xc000 option COREBOOT_EXTRA_VERSION=".0-Fallback"
- payload $(HOME)/svn/payload.elf
- payload $(HOME)/Entwicklung/LinuxBIOS/VIA-BIOS/filo.small.elf
end
buildrom ./coreboot.rom ROM_SIZE "normal" "fallback"
In an earlier version I changed Config.lb in src dir to get VGA BIOS. But now it isn't included. If it is important, I could post it later.
Plese post it.
On monday I'll send it to mailinglist.
But the above patch comes from an 'svn diff' at the top-level directory, correct? I.e. all your current changes are in there?
Yes, these are actual all changes on top-level dir of corebott sandbox.
Also, where did you get your VGA ROM from? Using which tools
(awardeco,
amideco, phnxdeco, other)? How big is it exactly?
On http://www.coreboot.org/VGA_support at bottom there is a perl script. Using this I got my VGABIOS. This is 60416 bytes big
OK. Which vendor BIOS does the board have? Can you use awardeco/amideco/phnxdeco to get the VGA BIOS and compare it with the one from the script? Just to be sure that worked fine...
I'll try this on monday. I don't know, what vendor BIOS was in ROM. I used the original BIOS got from VIA.
(optionsrom is 57344 bytes which I used at last).
Huh, what's that? Where from?
Look at post of Stefan Reinauer (http://www.coreboot.org/pipermail/coreboot/2008-March/031664.html)
filo.small.elf is 27312 bytes big. So don't wonder what number this is.
Are you sure this is ok? The smallest usable FILO I've used so far is ca. 57 KB. Your 27 KB FILO looks _very_ small.
Also, please use the latest version from
% svn co svn://coreboot.org/filo/trunk/filo-0.5
Type 'make' (that will generate a Config file), then edit Config, then type make again.
Uwe.
http://www.hermann-uwe.de | http://www.holsham-traders.de http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
I'm not sure if payload is ok. But at first I used a bigger one and the errors where same. So I removed all I think I'll not need. How can I test payload?
But if your smallest payload is 57KB and I will use normal and fallback and a VGA BIOS I get space problems. About 64KB for VGA and 2 payloads about 57KB are 178KB. Is 78KB for normal and fallback not too small?
I will update my filo and look at that config. Maybe there is some special on my config (e.g. I only need ext2, so all other are deactivated).
Klaus
Klaus Stammermann wrote:
Here the diff:
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) @@ -51,8 +51,8 @@ ### ### Build options ### -default CONFIG_PCI_ROM_RUN=0 -default CONFIG_CONSOLE_VGA=0 +default CONFIG_PCI_ROM_RUN=1 +default CONFIG_CONSOLE_VGA=1
This won't work. Epia-M brings its own vm86 based pci option rom execution. The above additionally enables x86emu. Unfortunately x86emu is not capable of executing the Epia-M option rom. Sorry for the confusion.
Stefan
Klaus Stammermann wrote:
Here the diff:
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) @@ -51,8 +51,8 @@ ### ### Build options ### -default CONFIG_PCI_ROM_RUN=0 -default CONFIG_CONSOLE_VGA=0 +default CONFIG_PCI_ROM_RUN=1 +default CONFIG_CONSOLE_VGA=1
This won't work. Epia-M brings its own vm86 based pci option rom execution. The above additionally enables x86emu. Unfortunately x86emu is not capable of executing the Epia-M option rom. Sorry for the confusion.
Stefan
-- coresystems GmbH ⢠Brahmsstr. 16 ⢠D-79104 Freiburg i. Br. Tel.: +49 761 7668825 ⢠Fax: +49 761 7664613 Email: info@coresystems.de ⢠http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg ⢠HRB 7656 Geschäftsführer: Stefan Reinauer ⢠Ust-IdNr.: DE245674866
OK, I will try without these options. But if we get coreboot running on this system we should update the examples for config files. So for others it would be easier to use coreboot.
Klaus
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
On Mon, Mar 10, 2008 at 04:00:32PM +0100, Klaus Stammermann wrote:
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.
What kind of CF-IDE adapter? I have come across some nameless products that cause a CF to just not work. PC Engines' adapters on the other hand have always worked perfectly for me.
Does anyone get an idea how to solve this problem?
Try booting from a normal disk.
//Peter
Hi,
IDE-CF should work just fine, but you have to disable DMA for IDE port where you have it connected (boot parameter: ide1=nodma - does not work with some kernels). I've been using straight IDE to CF adapter with no electronics on it, and never had any problems. Use branded CF cards though, Transcend proved to be good on it, but A-data works with hick-ups.
On Mon, 2008-03-10 at 19:05 +0100, Peter Stuge wrote:
On Mon, Mar 10, 2008 at 04:00:32PM +0100, Klaus Stammermann wrote:
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.
What kind of CF-IDE adapter? I have come across some nameless products that cause a CF to just not work. PC Engines' adapters on the other hand have always worked perfectly for me.
Does anyone get an idea how to solve this problem?
Try booting from a normal disk.
//Peter
On Tue, Mar 11, 2008 at 08:53:40PM -0500, Jacek Chruscik wrote:
IDE-CF should work just fine,
Yet it does not always.
but you have to disable DMA for IDE port where you have it connected (boot parameter: ide1=nodma - does not work with some kernels).
Not neccessary with SanDisk Extreme III in PC Engines straight adapter. DMA or not depends on both card and adapter.
I've been using straight IDE to CF adapter with no electronics on it, and never had any problems.
Right, that is my experience as well.
Use branded CF cards though, Transcend proved to be good on it, but A-data works with hick-ups.
My point was that with the same SanDisk card one adapter worked and another didn't.
On Mon, 2008-03-10 at 19:05 +0100, Peter Stuge wrote:
On Mon, Mar 10, 2008 at 04:00:32PM +0100, Klaus Stammermann wrote:
Does anyone get an idea how to solve this problem?
Try booting from a normal disk.
I stand by this. It is a simple way to exclude all problems related to CF.
//Peter
On Tue, 2008-03-04 at 14:42 +0100, Klaus Stammermann wrote:
Am Dienstag, 4. März 2008 12:50 schrieb Uwe Hermann:
On Tue, Mar 04, 2008 at 08:31:23AM +0100, Klaus Stammermann wrote:
Am Montag, 3. März 2008 21:33 schrieben Sie:
- Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I hope someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs till jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was console=ttyS0,... specified as a command line option to the kernel?
Yes, I use following startup parameters: "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0 console=ttyS0,115200"
And you also use 'USE_GRUB = 0'? Otherwise FILO will try to read your menu.lst file from GRUB and ignore the above line.
I did not use that optionroms. But how can I use this optionrom? Where do I have to put it in my image?
I think at the beginning (but someone please correct me if I'm wrong), i.e.
cat vga.rom coreboot.com > coreboot_full.rom
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
I get some problem at making coreboot.rom smaller. Normal and fallback get 128kb before. I tried two different possibilities to get space for it, but both failed.
I need 57344b. But taking 57344/2 out of both raises error "XIP_ROM_BASE is not multiple of XIP_ROM_SIZE". And reducing one of them about 57344b make breaks because of overleaping sections.
Is there any overview how to use all these option in Config.lb? I think I don't understand the structur of all these options and their results.
I think you don't really need "normal" image at all. I was able to compile just "fallback" image (ROM_IMAGE_SIZE 64kB) with filo payload (~48kB), and tried to save 57344 bytes for vga bios. This makes ROM_SIZE=204800 , probably hou have to set up FALLBACK_SIZE to same value, otherwise the build will end up being 131072 (I can't understand why) Unfortunately, this does not work, I mean, I compiled rom image of given size, prepended vga bios, and it gave me exactly 256kB of the image. The problem is that coreboot boots, then runs vgabios (my screen initializes), but then fails on filo (cannot load ELF image). It works fine without vgabios though. I think there might be some bug in scripts, because buildtarget shows correct ROM_SIZE, but the build is 128kB if I don't set-up FALLBACK_SIZE.
good luck
Klaus
On Thu, Mar 6, 2008 at 1:12 AM, Jacek Chruscik mercury@wirebros.com wrote:
On Tue, 2008-03-04 at 14:42 +0100, Klaus Stammermann wrote:
Am Dienstag, 4. März 2008 12:50 schrieb Uwe Hermann:
On Tue, Mar 04, 2008 at 08:31:23AM +0100, Klaus Stammermann wrote:
Am Montag, 3. März 2008 21:33 schrieben Sie:
- Klaus Stammermann klaus123@ibnoetzold.de [080303 15:20]:
Hi there
I have some trouble to use coreboot on my VIA EPIA-ME6000 so I
hope
someone could give me some hints.
With epia-m and filo I can build a bios without vga. This runs
till
jumping to kernel. This breaks up with an error: Loading kernel... ok "Jumping to entry point... 0
Was the kernel built with serial console support? Was
console=ttyS0,...
specified as a command line option to the kernel?
Yes, I use following startup parameters: "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0
console=ttyS0,115200"
And you also use 'USE_GRUB = 0'? Otherwise FILO will try to read your menu.lst file from GRUB and ignore the above line.
I did not use that optionroms. But how can I use this optionrom?
Where do
I have to put it in my image?
I think at the beginning (but someone please correct me if I'm wrong),
i.e.
cat vga.rom coreboot.com > coreboot_full.rom
But you need to tweak the config files too in order to make the coreboot.rom smaller (so there's place for vga.rom).
I get some problem at making coreboot.rom smaller. Normal and fallback
get
128kb before. I tried two different possibilities to get space for it,
but
both failed.
I need 57344b. But taking 57344/2 out of both raises error "XIP_ROM_BASE
is
not multiple of XIP_ROM_SIZE". And reducing one of them about 57344b
make
breaks because of overleaping sections.
Is there any overview how to use all these option in Config.lb? I think
I
don't understand the structur of all these options and their results.
I think you don't really need "normal" image at all. I was able to compile just "fallback" image (ROM_IMAGE_SIZE 64kB) with filo payload (~48kB), and tried to save 57344 bytes for vga bios.
You can pad the end of the vga bios with zeros to make it exactly 64k. This should do it: $ dd if=/dev/zero of=goop bs=1 count=8192 $ cat vgabios.rom good > vgabios_64k.rom
That gets rid of, or at least eases, the confusion of trying to figure out fallback and XIP sizes that compile.
This makes ROM_SIZE=204800 , probably hou have to set up FALLBACK_SIZE
to same value, otherwise the build will end up being 131072 (I can't understand why)
Without the normal image, the build system gets confused and doesn't know that it is supposed to fill another 128k. Pesky bug.
Unfortunately, this does not work, I mean, I compiled rom image of given size, prepended vga bios, and it gave me exactly 256kB of the image. The problem is that coreboot boots, then runs vgabios (my screen initializes), but then fails on filo (cannot load ELF image). It works fine without vgabios though.
This sounds like an issue with the memory setup, VGA is probably claiming memory that coreboot doesn't know about, so FILO tries to use it, and you can see how well that would goes. Any chance you have the CLE266 datasheet?
I think there might be some bug in scripts, because buildtarget shows correct ROM_SIZE, but the build is 128kB if I don't set-up FALLBACK_SIZE.
good luck
-Corey
don't forget earlyprintk
console=ttyS0,115200 earlyprintk=ttyS0,115200[,keep]
ron
-
Corey Osgood -
Jacek Chruscik -
Klaus Stammermann -
Peter Stuge -
ron minnich -
Stefan Reinauer -
Uwe Hermann