Coreboot doesn't boot on Arima HDAMA rev.G mainboard

[Joop Boonen]

All,'

I cant create a bug ticket in:
http://tracker.coreboot.org/trac/coreboot/newticket

I've build Coreboot for this main board with LIFO with and without VGA
ROM. But it doesn't get trough the boot process.

I've attached some logging files and hwinfo as openSuSE shows it.

Can someone help me?

How can I create a bugzilla ticket, do I need a username/password?

Regards,

Joop.

[Myles Watson]

> I've build Coreboot for this main board with LIFO with and without VGA
> ROM. But it doesn't get trough the boot process.

It quits really early in device enumeration.  You could put some debugging
statements (printk) in amdk8_scan_chains and friends to see why it quits.
> Can someone help me?

It worked around rev 4920.  Have you tried multiple revisions?  It's not
getting close to starting FILO or initializing the VGA.

Thanks,
Myles

[Joop Boonen]

On Tue, May 4, 2010 1:02 am, Myles Watson wrote:
> > I've build Coreboot for this main board with FILO with and without VGA
> > ROM. But it doesn't get trough the boot process.
>
> It quits really early in device enumeration.  You could put some debugging
> statements (printk) in amdk8_scan_chains and friends to see why it quits.

I will, try this after I try rev 4920.
> > Can someone help me?
>
> It worked around rev 4920.  Have you tried multiple revisions?  It's not
> getting close to starting FILO or initializing the VGA.

I will try this first (rev 4920). I'll let you know the outcome as soon as
I've tested it.
> Thanks,
> Myles

[Joop Boonen]

On 05/04/2010 11:14 AM, Joop Boonen wrote:
> On Tue, May 4, 2010 1:02 am, Myles Watson wrote:
> > > I've build Coreboot for this main board with FILO with and without VGA
> > > ROM. But it doesn't get trough the boot process.
> >
> > It quits really early in device enumeration.  You could put some debugging
> > statements (printk) in amdk8_scan_chains and friends to see why it quits.
>
> I will, try this after I try rev 4920.

rev 4920 works without a problem, also with the extracted VGA. I get the
FILO screen.
> > > Can someone help me?
> >
> > It worked around rev 4920.  Have you tried multiple revisions?  It's not
> > getting close to starting FILO or initializing the VGA.
>
> I will try this first (rev 4920). I'll let you know the outcome as soon as
> I've tested it.
> > Thanks,
> > Myles

[Myles Watson]

> rev 4920 works without a problem, also with the extracted VGA. I get the
> FILO screen.

Great.  You could check the values from Kconfig (build/config.h) and compare
them to the values from 4920.  That would be the easiest thing to fix.

Thanks,
Myles

[Myles Watson]

On Tue, May 4, 2010 at 11:54 AM, Myles Watson  wrote:
> > rev 4920 works without a problem, also with the extracted VGA. I get the
> > FILO screen.
>
> Great.  You could check the values from Kconfig (build/config.h) and compare
> them to the values from 4920.  That would be the easiest thing to fix.

I think the most likely culprit is SB_HT_CHAIN_ON_BUS0.  Could you
change it to 1 in src/mainboard/arima/hdama/Kconfig, make oldconfig,
and test?

Thanks,
Myles

[Joop Boonen]

On Tue, May 4, 2010 8:16 pm, Myles Watson wrote:
> On Tue, May 4, 2010 at 11:54 AM, Myles Watson  wrote:
> > > rev 4920 works without a problem, also with the extracted VGA. I get
> > > the
> > > FILO screen.
> >
> > Great.  You could check the values from Kconfig (build/config.h) and
> > compare
> > them to the values from 4920.  That would be the easiest thing to fix.
>
> I think the most likely culprit is SB_HT_CHAIN_ON_BUS0.  Could you
> change it to 1 in src/mainboard/arima/hdama/Kconfig, make oldconfig,
> and test?

I've tested it. I get the filo screen now.

When I do a probe I don't see any IDE device yet. Neither IDE nor SATA
SIL3114 drive. This also didn't work for version 4920.
> Thanks,
> Myles

[Myles Watson]

> > I think the most likely culprit is SB_HT_CHAIN_ON_BUS0.  Could you
> > change it to 1 in src/mainboard/arima/hdama/Kconfig, make oldconfig,
> > and test?
>
> I've tested it. I get the filo screen now.

Great.  I checked that in Rev 5522.
> When I do a probe I don't see any IDE device yet. Neither IDE nor SATA
> SIL3114 drive. This also didn't work for version 4920.

Have you tried SeaBIOS?  I haven't used FILO much.  In your log it
looks like FILO is expecting to find something in your CMOS that it
doesn't find.

ERROR: No such CMOS option (boot_devices)
menu: hda3:/boot/filo/menu.lst

You could look into that.

Thanks,
Myles

[Joop Boonen]

On Wed, May 5, 2010 12:35 am, Myles Watson wrote:
> > > I think the most likely culprit is SB_HT_CHAIN_ON_BUS0.  Could you
> > > change it to 1 in src/mainboard/arima/hdama/Kconfig, make oldconfig,
> > > and test?
> >
> > I've tested it. I get the filo screen now.
>
> Great.  I checked that in Rev 5522.
> > When I do a probe I don't see any IDE device yet. Neither IDE nor SATA
> > SIL3114 drive. This also didn't work for version 4920.
>
> Have you tried SeaBIOS?  I haven't used FILO much.  In your log it
> looks like FILO is expecting to find something in your CMOS that it
> doesn't find.
>
> ERROR: No such CMOS option (boot_devices)
> menu: hda3:/boot/filo/menu.lst

I've just used SeaBIOS. With SeaBIOS LInux boots without a problem (except
for ACPI, I understood this is not (fully) supported yet.

I have a feeling that FILO has an issue?
> You could look into that.
>
> Thanks,
> Myles

[Joop Boonen]

On Wed, May 5, 2010 12:35 am, Myles Watson wrote:
> > > I think the most likely culprit is SB_HT_CHAIN_ON_BUS0.  Could you
> > > change it to 1 in src/mainboard/arima/hdama/Kconfig, make oldconfig,
> > > and test?
> >
> > I've tested it. I get the filo screen now.
>
> Great.  I checked that in Rev 5522.
> > When I do a probe I don't see any IDE device yet. Neither IDE nor SATA
> > SIL3114 drive. This also didn't work for version 4920.
>
> Have you tried SeaBIOS?  I haven't used FILO much.  In your log it
> looks like FILO is expecting to find something in your CMOS that it
> doesn't find.
>
> ERROR: No such CMOS option (boot_devices)
> menu: hda3:/boot/filo/menu.lst

I've just used SeaBIOS. With SeaBIOS LInux boots without a problem (except
for ACPI, I understood this is not (fully) supported yet.

I have a feeling that FILO has an issue?

I booted off an ATA disk.
> You could look into that.
>
> Thanks,
> Myles

[Rudolf Marek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think we miss ACPI support for this board and PowerNow. The documentation is
available and I think it could be added easily.

I'm willing to help give/hints if somebody takes that.

Rudolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvh6LQACgkQ3J9wPJqZRNWCmQCdGESsx0CQN5ynhzSMyKcGsuwQ
tPkAn0xt4wTbmcKDka03rciPSSAv4vzf
=+yhi
-----END PGP SIGNATURE-----

[Ward Vandewege]

On Tue, May 04, 2010 at 11:59:26PM +0200, Joop Boonen wrote:
> On Tue, May 4, 2010 8:16 pm, Myles Watson wrote:
> > On Tue, May 4, 2010 at 11:54 AM, Myles Watson  wrote:
> > > > rev 4920 works without a problem, also with the extracted VGA. I get
> > > > the
> > > > FILO screen.
> > >
> > > Great.  You could check the values from Kconfig (build/config.h) and
> > > compare
> > > them to the values from 4920.  That would be the easiest thing to fix.
> >
> > I think the most likely culprit is SB_HT_CHAIN_ON_BUS0.  Could you
> > change it to 1 in src/mainboard/arima/hdama/Kconfig, make oldconfig,
> > and test?
>
> I've tested it. I get the filo screen now.
>
> When I do a probe I don't see any IDE device yet. Neither IDE nor SATA
> SIL3114 drive. This also didn't work for version 4920.

Yeah, the Sil3114 needs special handling for its SATA ports. The Tyan S2881
board has the same problem. I'm not sure about the IDE ports.

In the past I've used a linux kernel payload to get around that. Rudolf has
had success with SeaBIOS (and the SiL3114 option rom, I believe)

http://www.coreboot.org/pipermail/coreboot/2009-February/044781.htm

but I have not been able to replicate that yet on my Tyan s2881.

I wonder if we could make Coreboot do the necessary to initialize that
controller, so that we don't need that binary blob or a full blown linux
kernel anymore.

There appear to be public datasheets for Sil3114, referenced here

https://ata.wiki.kernel.org/index.php/Sata_sil

And the kernel driver also knows how to bring it up, since using a linux
kernel as a payload has worked for me in the past.

Thanks,
Ward.

[Rudolf Marek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I used the Sillicon Image PCI card with onboard BIOS. It works well in SeaBIOS.
I would say here would be enough to extract the optionrom from orig BIOS. And
SeaBIOS will assign/use it.

By the bizarre coincidence I had this board @home and booting from IDE worked
well (under SeaBIOS).

Attached patch enables bios_extract to extract the BIOS ;)

oprom_4.rom is for SATA
oprom_3.rom is FastTRAK

I think you can http://www.coreboot.org/SeaBIOS go same as for Adding the VGA
rom here.

As a side note one could program an GPL rombios for this controller - any takers?

Thanks,
Rudolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvh0FgACgkQ3J9wPJqZRNWS9ACfX/zKWvtO+WV/wwHkDxPdq6P9
qZgAoIrO8y4BaYJBV2e/Lx//gsbpy6I/
=vBZM
-----END PGP SIGNATURE-----

[Joop Boonen]

On 05/04/2010 12:42 AM, Joop Boonen wrote:
> All,
>
> I cant create a bug ticket in:
> http://tracker.coreboot.org/trac/coreboot/newticket
>
> I've build Coreboot for this main board with LIFO with and without VGA
> ROM. But it doesn't get trough the boot process.
>
> I've attached some logging files and hwinfo as openSuSE shows it.

I've attached the .config to this email.
> Can someone help me?
>
> How can I create a bugzilla ticket, do I need a username/password?
>
> Regards,
>
> Joop.