Re: Problem: 2.6.x and network (e1000 Intel 82546EB)

From: Stephen P Williams (stephen_p_williams_at_pacbell.net)
Date: 04/27/04

  • Next message: Miquel van Smoorenburg: "Re: mountkernfs, mountvirtfs, and devpts.sh" 
    Date: Mon, 26 Apr 2004 17:26:05 -0700
To: debian-user@lists.debian.org

    On Wed, 7 Apr 2004, "W. Borgert" <debacle@debian.org> wrote:

    > Hi,
    >
    > after installing a fresh sarge on a Sun (dual XEON) with two
    > e1000 Intel 82546EB Gigabit Ethernet Controller everything
    > worked fine so far with the default 2.4.x kernel. But after
    > changing to 2.6.x the network just does not work anymore. I
    > use e1000 as the driver and the official kernel images
    > (kernel-image-2.6.[34]-1-686-smp. Of course, I looked in
    > /var/log/* for interesting messages, but got nothing out of
    > it. rmmod e1000; modprobe e1000; /etc/init.d/networking
    > restart gave "Ignoring unknown interface eth0=hotplug" and
    > "Ignoring unknown interface eth1=hotplug". Hotplug?
    >
    > Any ideas? Thanks in advance!

    This is something I ran into on one of my Intel SE7501WV2 systems. The
    problem is that the 82546EB is a dual Ethernet controller, and
    evidently, something has changed in the e1000 driver between 2.4.x and
    2.6.x that affects the ordering of which port gets assigend as eth0 and
    which as eth1. The simple solution is to switch network ports, but that
    is inconvenient if you need to switch kernel versions.

    Looking at the driver source code, I don't see any module parameters
    that will tell the 2.6.x driver to revert to port ordering behavior of
    the 2.4.x driver.

    If it is any consolation, the 2.6.x way seems "right" to me -- the ports
    on my server's chassis are labeled "1" and "2". Under 2.4.x, the port
    labeled "2" was eth0, which always bugged me. Under 2.6.x, eth0 is now
    the port labeled "1" and eth1 is the port labeled "2".

    As for the "eth0=hotplug", this has been well discussed in regards to
    the ifupdown and hotplug tools. The solution here is to add stanzas
    into /etc/network/interfaces as you will find documented in
    /usr/share/doc/hotplug/README.Debian.

    Hope that helps,
    Steve Williams 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Miquel van Smoorenburg: "Re: mountkernfs, mountvirtfs, and devpts.sh"

    Relevant Pages

    • Re: problems with wvdial
      ... hci-hcd (the USB port driver)? ... down the port. ... One of the USB gurus tho whom I have spoken (Alan Stern ... I think it's a kernel config option though. ...
      (comp.os.linux.networking)
    • qla2xx: NULL pointer dereference (2.6.33.1)
      ... The device is an older infortrend FC Raid system connected to a dual port ... The same hardware works fine with an older 2.6.27 kernel. ... Performance Events: AMD PMU driver. ... Testing event lock_kernel: OK ...
      (Linux-Kernel)
    • Re: How to send a simple MIDI-note on a soundcard?
      ... to find the port you want, you can do something similar to: ... I thought it would be easy to access sound card via kernel streaming. ... May I create a Miniport driver like in src\wdm\audio\mpu401 sample with my ...
      (microsoft.public.development.device.drivers)
    • Re: Serial Driver --> Unable to open COM1 Port ( transport and download port)
      ... If this is the case you won't have a driver loaded on COM1 instead it is the ... kernel talking to the HW directly, you need to make sure that the kernel ... transport and download port. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: problems with wvdial
      ... Neither was I. I've found over may years of troubleshooting problems ... hci-hcd (the USB port driver)? ... the driver and then issue the command to shut down power on the port. ... I think it's a kernel config option though. ...
      (comp.os.linux.networking)