[coreboot] Problems with VIA EPIA-ME6000
corey.osgood at gmail.com
Thu Mar 6 08:03:45 CET 2008
On Thu, Mar 6, 2008 at 1:12 AM, Jacek Chruscik <mercury at 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 at ibnoetzold.de> [080303 15:20]:
> > > > > > Hi there
> > > > > >
> > > > > > I have some trouble to use coreboot on my VIA EPIA-ME6000 so I
> > > > > > someone could give me some hints.
> > > > > >
> > > > > > With epia-m and filo I can build a bios without vga. This runs
> > > > > > 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
> > > > > specified as a command line option to the kernel?
> > > >
> > > > Yes, I use following startup parameters:
> > > > "hda1:/boot/vmlinuz root=/dev/hda1 console=tty0
> > >
> > > 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),
> > >
> > > 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
> > 128kb before. I tried two different possibilities to get space for it,
> > both failed.
> > I need 57344b. But taking 57344/2 out of both raises error "XIP_ROM_BASE
> > not multiple of XIP_ROM_SIZE". And reducing one of them about 57344b
> > breaks because of overleaping sections.
> > Is there any overview how to use all these option in Config.lb? I think
> > 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
> good luck
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the coreboot