FW: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped

FW: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped

Post by Sean Brun » Mon, 27 Jun 2005 05:10:06


n Sat, 2005-06-25 at 13:02 -0700, Sean Bruno wrote:
I got FC4 to install using the Silicon Image SATA controller and an IDE
CDROM. I also inserted a PCI 10/100 card to get network support. After
installing FC4(or any distro for that matter), edit your inittab before
you reboot and set it to boot into run level 3. Once you have rebooted,
you can run an update(via yum) to get the latest kernel and Xorg stuff.
This allowed me to boot the machine into level 5 and my video card did
function(NV 6200).

Indeed, ASUS is kind of "sucking" in the tech support realm on this
issue. I have been poking around with "dmidecode" and "lshw" and found
some really interesting stuff.

Handle 0x0023
DMI type 9, 13 bytes.
System Slot Information
Designation: PCIEX1_1
Type: <OUT OF SPEC><OUT OF SPEC>
Current Usage: In Use
Length: Other
Characteristics:
5.0 V is provided
PME signal is supported
Handle 0x0024
DMI type 9, 13 bytes.
System Slot Information
Designation: PCIEX16_1
Type: <OUT OF SPEC><OUT OF SPEC>
Current Usage: Available
Length: Other
Characteristics:
5.0 V is provided
PME signal is supported

I am assuming that this is causing some kind of weirdness that disables
the use of the NV SATA, USB, Sound and the Broadcom ethernet device.
Any ideas what the "OUT OF SPEC" warning actually means?

Sean

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 
 
 

1. Updating PCI/PCI Express configuration values for PCI/PCI Express bridge

2. [v1 PATCH 1/1] PCI: Add AMD8111 PCI Bridge PCI Device ID

Hi Greg,

Please see my answers below.


Greg KH :

This new id is to be used in the newly added edac driver amd8111_edac.c
that I have posted to the mailing list on March 9th, it is used to probe
the PCI Bridge Controller on AMD8111 chip.

Ok, I see for the time being I had better define this new id as a macro
in amd8111_edac.c.

And I am a little curious that do you mean that pci_ids.h maintainer
would have to track how many times a new id have been requested to
decide if to merge it into the file or not?

Thank you very much for your comments!

Best regards,

Harry


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/

3. Ok, lets kill the 'PCI hidden behind bridge' message (was: pci=assign-busses)

4. Ok, lets kill the 'PCI hidden behind bridge' message (was: pci=assign-busses)

5. PCI: Bus #0b (-#0e) is hidden behind transparent bridge #0a (-#0b) (try 'pci=assign-busses')

6. PCI: Bus #02 (-#05) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')

7. PCI: Bus #02 (-#05) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')

8. [patch 21/28] PCI: lets kill the PCI hidden behind bridge message

9. Ok, lets kill the 'PCI hidden behind bridge' message (was: pci=assign-busses)

10. Accessing PCI-to-PCI bridge in PCI Configuration Space

11. PCI Standard PCI-to-PCI Bridge

12. PCI Standard PCI-to-PCI bridge

13. [PATCH] PCI: handle subtractive decode pci-pci bridge better

14. [PATCH 1/2] PCI-PCI transparent bridge handling improvements (pci core)

15. PCI Standard PCI-PCI Bridge Duplicated