Bug 546047

Summary: FATAL module ahci not found shown during boot but not in boot.msg
Product: [openSUSE] openSUSE 11.2 Reporter: Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: linux
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User --EoyBps8f 2009-10-11 19:28:12 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-2.1 Firefox/3.5.3

When I boot I see:

doing fast boot
FATAL module ahci not found

Yet if I check the boot.msg I do not see such an entry.

lsmod | grep ahci does not find anything, not even after modprobe ahci.

Where can I look to find out what's wrong?

Reproducible: Always
Comment 1 Daniel Bauer 2009-11-15 11:52:17 UTC
Same here on two new machines:

1) HP Pavilion dv3-2100 Notebook: 

(specifications here: http://h10010.www1.hp.com/wwpc/ch/de/ho/WF06a/321957-321957-3329744-64354-64354-3945119.html )

First Boot Messages:
[    0.000000] failed to get NUMA memory information from SRAT table
[    0.900160] pci 0000:01:00.: BAR 6: no parent found for device [0xfffe000 
0-0xffffffff]
[    0.900178] pci 0000:04:00.: BAR 6: no parent found for device [0xfffe000 
0-0xffffffff]
doing fast boot
FATAL: Module ahci not found


2) Desktop PC
Gigabyte  EG31M-ES2L with Intel G31 Chipset, FSB 1333, DDR2, SATAII,GLAN
Intel DUAL-Core E5300, 775P,800MHz,2MB,45nm,Fan,BOX Wolfdale, 2.6GHz.
Intel GMA 3100 Integrated Graphics (on Board), bis zu 256MB Shared

First Boot Messages:
[    0.000000] failed to get NUMA memory information from SRAT table
doing fast boot
FATAL: Module ahci not found
FATAL: Error running install command for ata_piix

If you need more info, please let me know.

Daniel
Comment 2 Jeff Mahoney 2009-11-25 00:03:39 UTC
This is a duplicate of bug #541519

*** This bug has been marked as a duplicate of bug 541519 ***