On Mon, Feb 21, 2011 at 06:16:55PM +0200, Alex G. wrote: > On 02/21/2011 03:53 PM, Kevin O'Connor wrote: > > 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. > > > He removed the SAS card from the system, as running its option ROM would > freeze the boot process.
A boot log with debug level set to 8 from that event would be helpful. [...] > The coreboot log does show the SATA controller to be initialized (if I > am reading it correctly). > > PCI: 01:0e.0 [1166/024a] ops > PCI: 01:0e.0 [1166/024a] enabled > malloc Enter, size 68, free_mem_ptr 00150224 > malloc 00150224 > PCI: 01:0e.1 [1166/024a] ops > PCI: 01:0e.1 [1166/024a] enabled > POST: 0x25 > > The 1166:024a is the SATA controller. It doesn't look like the class field of that pci device identified itself as ATA or AHCI. (SeaBIOS just skipped over the device.) > > Can you post the output of lspci and identify which device you > > expected to boot from? > > > Better lspci -nn ? Yeah - actually "lspci -vnn" would be better. -Kevin -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot