Hi Jay,
I'm CC'ing the list.
On Mon, Feb 21, 2011 at 05:22:19PM -0500, jarray52 jarray52 wrote:
Hi Kevin,
Here is the output of lspci -vvv.
http://coreboot.pastebin.com/PxF6JdKT
Currently, there is one SATA hard disk attached to an on board SATA connector. The machine does not have any other hard drives attached. The LSI SAS controller has been removed from the HP Proliant dl 145 g3 server.
Thanks. The lspci shows:
01:0e.0 RAID bus controller: Broadcom BCM5785 [HT1000] SATA (Native SATA Mode) (prog-if 05)
So, the device doesn't use a standard class code. Does anyone know if it accepts standard ATA or AHCI commands? If so, SeaBIOS could be hardcoded to try and use the device.
I sent two E-mails to the mailing list. The other E-mail I sent to the mailing list contains the errors when the LSI SAS controller is attached.
The second email - the one with the SAS controller - did not have debug level set to 8.
-Kevin
Thanks, Jay
On Mon, Feb 21, 2011 at 8:53 AM, Kevin O'Connor kevin@koconnor.net wrote:
On Sat, Feb 19, 2011 at 06:26:30PM -0500, jarray52 jarray52 wrote:
Hi,
My HP Proliant dl145 g3 with Coreboot Bios and SeaBIOS payload cannot
read
my hard disk. Here is the serial console output.
http://coreboot.pastebin.com/HYee3u0t
For easy reference, here is the coreboot page on the HP Proliant dl145
g3.
http://www.coreboot.org/HP_DL145_G3
To ensure the problem was not caused by an HP BIOS or the LSI SAS
controller
raid initialization of hard drives, I used a hard drive with OS created
on a
non HP(Asus) without either hardware or software raid. No hard drive with boot sector was readable by coreboot/seabios.
The log shows SeaBIOS found an ATA controller, but did not find any drives attached to the controller. It did not find an option rom on any cards - so no scsi option rom was run.
Can you post the output of lspci and identify which device you expected to boot from?
-Kevin