[nSLUG] Redhat 8, Dell Dimension L500r, RTL8139

bdavidso at supercity.ns.ca bdavidso at supercity.ns.ca
Tue Mar 11 20:59:13 AST 2003


On Tue, 11 Mar 2003, Dean Landry wrote:

> they both throw an error saying there is no such device.  This is the output
> from 'dmseg'.  Do the lines starting with 'PCI:' look suspicious?
[snip]
> PCI: PCI BIOS revision 2.10 entry at 0xfda95, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Unable to handle 64-bit address for device 01:08.0
> PCI: Unable to handle 64-bit address for device 01:09.0
> Unknown bridge resource 0: assuming transparent
> PCI: Using IRQ router PIIX [8086/2410] at 00:1f.0
> PCI: Cannot allocate resource region 2 of device 01:09.0
> PCI: Cannot allocate resource region 3 of device 01:09.0
> PCI: Cannot allocate resource region 2 of device 01:08.0
> PCI: Failed to allocate resource 0(10000000-0) for 01:08.0
> PCI: Error while updating region 01:08.0/2 (fc000000 != 02000000)
> PCI: Failed to allocate resource 0(10000000-0) for 01:09.0
> PCI: Error while updating region 01:09.0/2 (fa700000 != 02000010)
> PCI: Error while updating region 01:09.0/3 (fa700100 != 00000100)

Not so much suspicious as alarming.  That's a lot of errors and failures
configuring the PCI bus.

What about the output of lspci -v (or even lspci -vvv)?

For example, on my system:

00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
10)
        Subsystem: AOPEN Inc. ALN-325C
        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: 32 (8000ns min, 16000ns max)
        Interrupt: pin A routed to IRQ 9
        Region 0: I/O ports at ec00 [size=256]
        Region 1: Memory at d7000000 (32-bit, non-prefetchable) [size=256]

Of course, I have no idea what most of that actually means, but at least I
can see that my 8139 card is device 8.0 on bus 00, it uses IRQ 9, it uses
I/O ports at ec00, and it uses memory at d7000000.  I can also see details
about the Northbridge and Southbridge etc.

I think you need to look at that output, and as Donald suggested look at
your /etc/modules.conf as well.

In short, I don't know what is wrong, but it seems like quite a lot there
isn't quite right.

Bill Davidson





More information about the nSLUG mailing list