mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Clem Taylor" <clem.taylor@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: e1000 driver not loading in 2.6.24.3 on x86_64 (worked in 2.6.24-rc7)
Date: Sat, 1 Mar 2008 15:42:58 -0500	[thread overview]
Message-ID: <ecb4efd10803011242w3874d27eyb1afaea06766bdbf@mail.gmail.com> (raw)

I'm trying to move from 2.6.24-rc7 to 2.6.24.3 on a x86_64 desktop
machine. With 2.6.24.3, the e1000 driver (compiled in, not a module)
does not claim the device. In 2.6.24-rc7 it works just fine.

The ethernet device shows up in lspci in both kernels, but the driver
doesn't seem to probe the card in 2.6.24.3

2.6.24-rc7:
loop: module loaded
Intel(R) PRO/1000 Network Driver - version 7.3.20-k2
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:04:00.0 to 64
e1000: 0000:04:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) 00:16:76:c9:33>
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2

2.6.24.3:
loop: module loaded
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2

There were a few minor configuration changes between the two kernels
(added ACPI_SYSFS_POWER, removed ACPI_PROC_EVENT) but nothing I would
think that prevent the e1000 driver from loading.

                                          Any ideas?
                                          Clem

             reply	other threads:[~2008-03-01 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-01 20:42 Clem Taylor [this message]
2008-03-01 21:03 ` Phil Oester
2008-03-03 17:41   ` Kok, Auke

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=ecb4efd10803011242w3874d27eyb1afaea06766bdbf@mail.gmail.com \
    --to=clem.taylor@gmail.com \
    --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

all inboxes | Powered by JetHome®