Intel 82566DC-2 problem

[Michael Semcheski]

Hi everyone!  I've got a computer I'm trying to install Fedora 7 on.
It has an Intel 82566DC-2 Gigabit NIC.

It is the only NIC on the computer.  But, its not showing up as eth0
(or anything else, for that matter.)

I did an lscpci, and I see the NIC (that's how I know its an 82566DC-2).

# lspci | grep Gigabit
  Intel 82566DC-2 Gigabit... (typing from memory)
 # modprobe e1000
 # lsmod | grep e1000
   e1000 1117633 0  (typing from memory, the second number is 0)
 # dmesg | grep e1000
 # dmesg | grep eth0

Nothing in dmesg about it.  I understand the situation, it see the PCI
device but e1000 doesn't think it should deal with it.

What should I do?  I'm kind of stumped here.

[Jim Cornette]

Michael Semcheski wrote:
> Hi everyone!  I've got a computer I'm trying to install Fedora 7 on.
> It has an Intel 82566DC-2 Gigabit NIC.
>
> It is the only NIC on the computer.  But, its not showing up as eth0
> (or anything else, for that matter.)
>
> I did an lscpci, and I see the NIC (that's how I know its an 82566DC-2).
>
> # lspci | grep Gigabit
>   Intel 82566DC-2 Gigabit... (typing from memory)
>  # modprobe e1000
>  # lsmod | grep e1000
>    e1000 1117633 0  (typing from memory, the second number is 0)
>  # dmesg | grep e1000
>  # dmesg | grep eth0
>
> Nothing in dmesg about it.  I understand the situation, it see the PCI
> device but e1000 doesn't think it should deal with it.
>
> What should I do?  I'm kind of stumped here.

What is in /etc/modprobe.conf?

I have the below in mine for example. You would of course need 
parameters specific to your machine.

Bad answer on my part. More curious than knowledgable with this type of 
problem.

Jim

[Michael Semcheski]

> What is in /etc/modprobe.conf?

The modprobe.conf on the computer in question hasn't been altered
manually, and looks like modprobe.conf on other Fedora 7 computers I
have.
> I have the below in mine for example. You would of course need
> parameters specific to your machine.
>
> Bad answer on my part. More curious than knowledgable with this type of
> problem.

At this point, everything is helpful.

I have 5 workstations, all purchased within three months of each
other.  All are the same model and the same specs were used to
purchase them.  The 3 older ones have 82566DM as their network
(according to lspci).  The 2 newest ones have 82566DC-2 according to
lspci.  DM works great, DC-2 not at  all.  And I just can't figure out
what to try next.

Mike

[Michael Semcheski]

So here's the latest...

I downloaded a tarball from Intel with the latest e1000 source.

I attempted to build the driver from source, and it works, but it
doesn't... Details follow.

It might not sound all that hard to build the e1000 driver from source
(cd e1000/src; make install) but it was actually quite an exercise.

First, you have to get the kernel source rpm and install it.  Then you
have to get rpmbuild and sparse.  sparse wasn't on the Fedora 7 DVD,
so I had to burn that to a CD and sneakernet it over.

Lots of dependencies that you have to figure out to get the kernel
sources.  A lot more complicated if you don't have networking, because
yum is utterly helpless.

So I finally got rpmbuild installed, and I built the kernel source.
(Of course, I didn't actually build the kernel, maybe I should have.)
I learned that you have to begin the make to get version.h, which is
required for the e1000.ko to build.

Eventually, I did get e1000.ko built.  If I do an 'insmod e1000.ko', I
get an error about a struct being wrong.  Can't remember it, can
reproduce it if necessary.  I guess it is related to a slight
difference between versions of the kernel and the kernel object.
Something like that.  But, the device shows up!  Yeah for eth0!  One
problem, I have to insmod the kernel object by hand when the computer
reboots.  This is annoying, because things like dhcpd don't run.

So, the question is, how do I get this latest e1000.ko built and
installed CORRECTLY?  Do I have to build my own kernel?  Is there an
easier way?

Let me also say that building a kernel, especially without the use of
yum, is a difficult process.  I guess I have to build it to an rpm,
and then install the rpm.  After I do it 6 or 7 times, I'm sure I
won't think its so hard, but for now, I must admit, the docs at
fedoraproject.org/wiki/Docs/CustomKernel got me only 50% of the way
there.

On 8/30/07, Michael Semcheski  wrote:
> > What is in /etc/modprobe.conf?
>
> The modprobe.conf on the computer in question hasn't been altered
> manually, and looks like modprobe.conf on other Fedora 7 computers I
> have.
> > I have the below in mine for example. You would of course need
> > parameters specific to your machine.
> >
> > Bad answer on my part. More curious than knowledgable with this type of
> > problem.
>
> At this point, everything is helpful.
>
> I have 5 workstations, all purchased within three months of each
> other.  All are the same model and the same specs were used to
> purchase them.  The 3 older ones have 82566DM as their network
> (according to lspci).  The 2 newest ones have 82566DC-2 according to
> lspci.  DM works great, DC-2 not at  all.  And I just can't figure out
> what to try next.
>
> Mike

[Jim Cornette]

Michael Semcheski wrote:
> > What is in /etc/modprobe.conf?
>
> The modprobe.conf on the computer in question hasn't been altered
> manually, and looks like modprobe.conf on other Fedora 7 computers I
> have.

The reason I asked is it seems to contain sound and Ethernet information 
for my computer. Since no Ethernet, something might be missing from the 
file.

Truthfully, I always use neat (System-config-network) to configure the 
devices and do not manually add info to modprobe.conf - Most of the time 
the program finds the device without error.

If I recall discussions from the experts regarding modprobe.conf, it is 
for kernel modules which are contained in the initrd image. You can also 
regenerate the modprobe.conf by deleting some file and getting hardware 
detection to regenerate the modprobe.conf. I did not try this so I only 
know this exists.
> > I have the below in mine for example. You would of course need
> > parameters specific to your machine.

Added from previous omission: (forgot to paste it in the message.

cat /etc/modprobe.conf
alias eth0 natsemi
alias scsi_hostadapter pata_ali
alias eth1 airo_cs
alias snd-card-0 snd-ali5451
options snd-card-0 index=0
options snd-ali5451 index=0
> > Bad answer on my part. More curious than knowledgeable with this type of
> > problem.
>
> At this point, everything is helpful.
>
> I have 5 workstations, all purchased within three months of each
> other.  All are the same model and the same specs were used to
> purchase them.  The 3 older ones have 82566DM as their network
> (according to lspci).  The 2 newest ones have 82566DC-2 according to
> lspci.  DM works great, DC-2 not at  all.  And I just can't figure out
> what to try next.
>
> Mike

From a google search might be helpful.

https://www.redhat.com/archives/fedora-kernel-list/2007-August/msg00094.html

Regarding your module building efforts, I have no idea unless the source 
from the Intel site is older than Fedora uses.

Jim

[Michael Semcheski]

So, the solution to the whole problem ended up being a lot simpler
than I had feared.

Install kernel-devel rpm's from the Fedora DVD.
Sneakernet the e1000 tarball from Intel's website to the destination machine.

# tar zxvf e1000-abc.tar.gz
# cd e1000-abc/src
# make install
# chmod 744 /lib/modules/kernel-xyz/drivers/net/e1000/e1000.ko

The key step, which I didn't know to do the first time, was install
kernel-devel.  I thought I needed to install the kernel-source, and
build the kernel to generate version.h.

So, easily solved once you know the solution.

On 8/30/07, Jim Cornette  wrote:
> Michael Semcheski wrote:
> > > What is in /etc/modprobe.conf?
> >
> > The modprobe.conf on the computer in question hasn't been altered
> > manually, and looks like modprobe.conf on other Fedora 7 computers I
> > have.
>
> The reason I asked is it seems to contain sound and Ethernet information
> for my computer. Since no Ethernet, something might be missing from the
> file.
>
> Truthfully, I always use neat (System-config-network) to configure the
> devices and do not manually add info to modprobe.conf - Most of the time
> the program finds the device without error.
>
> If I recall discussions from the experts regarding modprobe.conf, it is
> for kernel modules which are contained in the initrd image. You can also
> regenerate the modprobe.conf by deleting some file and getting hardware
> detection to regenerate the modprobe.conf. I did not try this so I only
> know this exists.
> > > I have the below in mine for example. You would of course need
> > > parameters specific to your machine.
>
> Added from previous omission: (forgot to paste it in the message.
>
> cat /etc/modprobe.conf
> alias eth0 natsemi
> alias scsi_hostadapter pata_ali
> alias eth1 airo_cs
> alias snd-card-0 snd-ali5451
> options snd-card-0 index=0
> options snd-ali5451 index=0
> > > Bad answer on my part. More curious than knowledgeable with this type of
> > > problem.
> >
> > At this point, everything is helpful.
> >
> > I have 5 workstations, all purchased within three months of each
> > other.  All are the same model and the same specs were used to
> > purchase them.  The 3 older ones have 82566DM as their network
> > (according to lspci).  The 2 newest ones have 82566DC-2 according to
> > lspci.  DM works great, DC-2 not at  all.  And I just can't figure out
> > what to try next.
> >
> > Mike
>
> From a google search might be helpful.
>
> https://www.redhat.com/archives/fedora-kernel-list/2007-August/msg00094.html
>
> Regarding your module building efforts, I have no idea unless the source
> from the Intel site is older than Fedora uses.
>
> Jim
>
> --
> When you're dining out and you suspect something's wrong, you're
> probably right.
>
> --
> fedora-list mailing list
> [e-mail]
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

[Jim Cornette]

Michael Semcheski wrote:
> So, the solution to the whole problem ended up being a lot simpler
> than I had feared.
>
> Install kernel-devel rpm's from the Fedora DVD.
> Sneakernet the e1000 tarball from Intel's website to the destination machine.
>
> # tar zxvf e1000-abc.tar.gz
> # cd e1000-abc/src
> # make install
> # chmod 744 /lib/modules/kernel-xyz/drivers/net/e1000/e1000.ko
>
> The key step, which I didn't know to do the first time, was install
> kernel-devel.  I thought I needed to install the kernel-source, and
> build the kernel to generate version.h.
>
> So, easily solved once you know the solution.

I'm glad that you now have it working. The devel package for the kernel 
is used for applications like vmware and nvidia. It did not dawn on me 
that your Ethernet driver would only need the driver source and 
kernel-devel package.

Your solution should help others from getting the whole source for 
module compilation.

Jim
>