I've installed Red Hat Ver 5 (kernel 2.6.18-8) on a Laptop with a PCI-PCI Bridge (Intel 21152 Bridge). I also have installed a fibre channel card into the laptop's available PCI slot. Upon boot up, after kernel is loaded, I get an error message as follows:
"PCI: device 0000:06:06.0 has unknown header type 7f, ignoring"

1) The card definitely works.
2) The slot definitely works (i installed a generic ethernet card and 'lspci' can pick it up)

Now the first thing you can possibly say is the PCI card probably doesn't comply with PCI specifications since the kernel only supports header types 00 through 03 (I think). But I installed this card onto another laptop using a different chipset and this other laptop has no problems recognizing this card (I can do an 'lspci' and see the device).

I'm guessing it may be the standard Red Hat kernel may not have the necessary module support for this chipset??? If so, can I simply enable a specific module under 'make menuconfig' and recompile/reinstall kernel? Is this a initrd issue instead of a kernel issue?

Stumped here and could use any help out there...

it would have helped if you listed what the card is, what lspci shows it as on the machine that works as well as the machine in question, are both machines running the same version of Linux ? etc..

don't know how to tell you what to look for if we don't even know what the device is..


I would also check to see if the card is listed in the PCI ID database on the rhel machine in question..
you may need to update the pciids file on your RHEL machine..
http://pciids.sourceforge.net/

Good point.

The results of lspci on the unit that doesn't work:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express (rev 02)
03:06.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 01)
03:07.0 ISA bridge: Winbond Electronics Corp Unknown device 0628
03:08.0 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01)
03:08.1 CardBus bridge: Texas Instruments PCI1520 PC card Cardbus Controller (rev 01)
03:0c.0 PCI bridge: Intel Corporation 21152 PCI-to-PCI Bridge


And the results from the unit that works:

00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
01:07.0 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
01:07.1 CardBus bridge: Texas Instruments PCI4451 PC card Cardbus Controller
01:07.2 FireWire (IEEE 1394): Texas Instruments PCI4451 IEEE-1394 Controller
01:08.0 Ethernet controller: Intel Corporation 82801DB PRO/100 VE (CNR) Ethernet Controller (rev 83)
01:0c.0 PCI bridge: Intel Corporation 21152 PCI-to-PCI Bridge
02:05.0 Communication controller: ILC Data Device Corp Unknown device 0e17

If I do a lspci -vvv on the working unit for the DDC device I get:

[SIZE="1"]02:05.0 Communication controller: ILC Data Device Corp Unknown device 0e17
Subsystem: ILC Data Device Corp Unknown device 0e17
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 8 (21250ns min, 9250ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at d0000000 (32-bit, non-prefetchable) [size=64K]
Region 1: Memory at d0010000 (32-bit, non-prefetchable)

And results of lspci -t for the non-working are:
-[0000:00]-+-00.0
+-02.0
+-02.1
+-1b.0
+-1c.0-[0000:02]----00.0
+-1d.0
+-1d.1
+-1d.2
+-1d.3
+-1d.7
+-1e.0-[0000:03-0e]--+-06.0
| +-07.0
| +-08.0
| +-08.1
| \-0c.0-[0000:06]--
+-1f.0
+-1f.1
+-1f.2
\-1f.3

And for the working unit:
-[0000:00]-+-00.0
+-00.1
+-00.3
+-02.0
+-02.1
+-1d.0
+-1d.1
+-1d.2
+-1d.7
+-1e.0-[0000:01-0a]--+-07.0
| +-07.1
| +-07.2
| +-08.0
| \-0c.0-[0000:02]----05.0
+-1f.0
+-1f.1
+-1f.3
+-1f.5
\-1f.6

Both units have the same kernel version (same RH version too).

Learning more as we go here...

If I do a 'lspci -H1', I can see the card:

06:06.0 Class ffff: ILC Data Device Corp Unknown device 0e17 (rev ff)

Of course if I try 'lspci -vvv -s 06:06.0 -H1', I get:

06:06.0 Class ffff: ILC Data Device Corp Unknown device 0e17 (rev ff) (prog-if ff)
!!! Unknown header type 7f

In /var/log/messages, I notice the following log messages:

...
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge (PCI0] (0000:00)
PCI: Ignoring BAR0-3 of IDE controller 000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
PCI: device 0000:06:06.0 has unknown header type 7f, ignoring.
PCI: Bus #7 (-#0a) is hidden behind transparent bridge #03 (-#06) (try 'pci=assign-busses' )
Please report the result to linux-kernel to fix this permanently
PCI: Bus #0b (-#0e) is hidden behind transparent bridge #03 (-#06) (try 'pci=assign-busses' )
Please report the result to linux-kernel to fix this permanently
...

So when I try and pass 'pci=assign-busses' to the kernel line at boot-up, I still get no lspci result. One thing different is that I get the result:

PCI: device 0000:0b:06.0 has unknown header type 7f, ignoring.

Instead of...

PCI: device 0000:06:06.0 has unknown header type 7f, ignoring.

Is it as simple as passing other kernel parameters in addition to just 'pci=assign-busses'?

For anyone experiencing similar issues, the problem had to do with the PCI Bridge not providing the correct voltages (3.3V) to the Fibre Channel card. Thanks for all the help.

Well I was going to suggest that the problem was someplace in the hardware that the card didn't work with, and a voltage problem certainly falls within that domain. I suppose you turned up the voltage in BIOS?

That would've been too easy! The BIOS, strangely enough, has absolutely no configuration control other than displaying UUID of the hard drive, enabling serial port IRQs & specifying boot sequence. Its pretty frustrating. I'm suspecting here that the problem may be related to how the manufacturer of the laptop chose to implement Intel's PCI-to-PCI Bridge (21152) and maybe they didn't bother complying with the App notes.