From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: e1000 not detected in 2.5.53
Date: Thu, 02 Jan 2003 17:17:16 +0000 [thread overview]
Message-ID: <3E14741C.2040104@walrond.org> (raw)
In-Reply-To: 3E145A31.9000305@walrond.org
Same results for 2.54
Andrew Walrond wrote:
> Asus PR-DLS dual Xeon m/b with Intel 82544GC Gigabit controller onboard
> (And Intel 82551QM Fast Ethernet controller incidentally)
>
> Detected fine in 2.4.20; lspci gives
>
> 00:00.0 Host bridge: ServerWorks CMIC-LE (rev 13)
> 00:00.1 Host bridge: ServerWorks CMIC-LE
> 00:00.2 Host bridge: ServerWorks: Unknown device 0000
> 00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
> (rev 10)
> 00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
> 00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
> 00:0f.3 Host bridge: ServerWorks GCLE Host Bridge
> 00:10.0 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 00:10.2 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 00:11.0 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 00:11.2 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 0e:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev 07)
> 0e:04.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 (rev 07)
> 12:02.0 Ethernet controller: Intel Corp. 82544GC Gigabit Ethernet
> Controller (LOM) (rev 02)
>
> BUT in 2.5.53, it's not detected. lspci gives
>
> 00:00.0 Host bridge: ServerWorks CMIC-LE (rev 13)
> 00:00.1 Host bridge: ServerWorks CMIC-LE
> 00:00.2 Host bridge: ServerWorks: Unknown device 0000
> 00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
> (rev 10)
> 00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
> 00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
> 00:0f.3 Host bridge: ServerWorks GCLE Host Bridge
> 00:10.0 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 00:10.2 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 00:11.0 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
> 00:11.2 Host bridge: ServerWorks: Unknown device 0101 (rev 03)
>
> Looks like scsi controller is missed as well? (I don't use it anyway)
> The e1000 driver is compiled into the kernel. ACPI is enabled
>
> From dmesg
>
> Intel(R) PRO/1000 Network Driver - version 4.4.12-k1
> Copyright (c) 1999-2002 Intel Corporation.
>
> Any suggestions?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-01-02 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 15:26 e1000 not detected in 2.5.53 Andrew Walrond
2003-01-02 17:17 ` Andrew Walrond [this message]
2003-01-02 20:57 ` Andrew Walrond
2003-01-03 0:38 ` Christian Leber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E14741C.2040104@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox