Home Home > 2008 > 09 > 22 > Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1
Sign up | Login

Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1

September 22nd, 2008 by

We have an important announcement regarding openSUSE 11.1 beta 1 and SUSE Linux Enterprise 11 beta 1:

The Intel e1000e driver on openSUSE 11.1 Beta 1 and SUSE Linux Enterprise 11 Beta 1 might have a serious issue with the potential to damage the network card in a way that it cannot be used any longer.

Intel and Novell are currently working to analyze and solve the issue.

For the time being:

Please do NOT USE:

openSUSE 11.1 Beta 1
or
SUSE Linux Enterprise 11 Beta 1

on systems with Intel e1000e hardware.

Any other hardware, including systems with Intel e1000 (without -e) network cards, is not affected by this issue.

We will keep you posted. Please watch news.opensuse.org and the opensuse-announce mailing list for more information.

Update: Check this page for a list of devices that use the e1000e driver. It may not be an exhaustive list. If you have an Intel PCI Express PRO/1000 gigabit Ethernet card, it uses the e1000e driver and you should avoid booting or using beta 1. Intel has instructions on how to identify your card.

Both comments and pings are currently closed.

24 Responses to “Serious e1000e Driver Issue in SLE 11 Beta 1 and openSUSE 11.1 Beta 1”

  1. j_engelh

    1. Why does the hardware even ALLOW to be programmed in such a way? Monitor manufacturers realized that long ago…

    2. Will it fry my VMware virtual network card? (SCNR, though it has e1000 not e1000e.)

  2. Heinz

    Btw, this seems to be an upstream problem, so users of latest kernel snapshots should be carefull as well on their systems …

  3. Stephen

    Have you any idea how retarded this request is for anything with an SLE prefix? C’mon guys, get with the programme. Jeez, blow up HW with a SW upgrade, what is this, a TRS-80 retrospective?

    • Anonymous

      Have you any idea how poor your comment is?

      • Joban

        +1

      • Anonymous

        -1 for a valid Enterprise (SLE) gripe comment??

        I completely **agree** with this guy: “Have you any idea how retarded this request is for anything with an SLE prefix?”

        Let me explain the rationale here: A SuSE Linux Enterprise (SLE) software release has code that erases embedded firmware?!? That’s not Enterprise software, that’s barely hobbyist software. Not trying to throw stones, but Enterprise software should, well, be ready for the enterprise. It *IS* tagged beta, I agree — so it’s for testing and not for production use. And this is an upstream bug which just got passed along, an accident. And it DID get caught before it was truly released for production use.

        But if this is Novell’s (I’m a Novell CNE/CDE/CLP and RHCE and LPI something — no cisco or MS creds) true idea of Enterprise release quality testing — even in a beta — thank you, I’m done now.

        “Enterprise” — this just sounds like another cheapening of yet another English word. Remember the (decade-) old legal squabble with the E in CNE? If not, look up the legal definition of Engineer, and then wonder why they would be upset with people who were identifying themselves as one without going through the same qualifications?

        Two things labeled the same implies the same quality of support, quality-assurance, and polish. But if NOT, then don’t use the same labels. __Released Enterprise software__, even beta, shouldn’t destroy hardware or software. They might not _work_ fast enough / be shiny enough / have enough documentation / what-not, but they should almost be ready for production. Not smoke things.

        IMO — Your expectations, assumptions, English usage, support costs, and downsides on failure may vary. Please do not fold, spindle, or mutilate.

        • anon

          These problems exist in beta’s, and there have been plenty of problems like this in windows. When you download a beta,, you do so at your own risk knowing full well that it is a beta and it will have problems in it, and that it could affect your hardware.

        • Octopus

          Imho, a system administrator who uses the beta software in the Enterprise should quickly search for another job…

        • Anonymous

          “CNE/CDE/CLP and RHCE and LPI something” != engineer

  4. Hi,
    do someone know if it can create problem also cirtualized in a Virtual Box machine?

  5. NotCool

    Holy crap, now SuSe says this after it fried my hardware. Holy crap I am suing novell for this. You friggin pricksters.

    • Djhg2K

      Calling them names won’t help…

    • diced_apple

      I am pretty sure like all software (MS, Redhat, Apple) that in the License it will state they cannot be held responcilble for any damage caused by the use of their software.

      • superpppl

        Furthermore, GPL’ed software comes with NO warranty, and no one but you is responsible for your own hardware/problems. Novell will only help you if (a) you are a paying customer or (b) out of the grace of their heart.
        It’s a part of the license, read it next time, just like how you’re supposed to. ;)

    • anon

      i strongly doubt you even use opensuse. But hey, enjoy your lawsuit, it will cost you a forutune to find out that you take full responsibility any damages that occur to you beta testing.

  6. Brandon Johnson

    This isn’t just exclusive to SUSE, any Linux distro that has the kernel in SUSE Linux 11.1 may have this issue. I have read that Fedora users have had similar issues so this isn’t just a openSUSE or SLE issue.

  7. Brandon Johnson is right. I’ve seen mandriva users having this issue as well

  8. Steve Wilson

    Does this affect OpenSUSE 11.0? We converted our ‘LTSP Server’ from 10.3 (which was very stable) to 11.0 and we now find LDAP/LTSP clients terminals are VERY, VERY slow, as are OpenSUSE 11.0 workstations. The Server has e1000e and others have e1000.

  9. Christopher Estep

    This bug does not affect VirtualBox (either OSE or non-OSE) or openSuSE 11.0 (which uses an earlier kernel). The issue applies to any distribution with kernels 2.6.27-3 and 2.6.27.4 (and variations thereof), and is not unique to SuSE (Fedora 10 alpha and Ubuntu 8.10 alpha 6 are both known to be affected also). Also, Intel CSA gigabit Ethernet (copper only) built into several enthusiast and workstation motherboards with Intel 845PE, 865PE, and 875P AGPsets (especially the 875P AGPset) are not affected (despite using the 82557EI copper gigabit chipset, the CSA uses the original e1000 driver, not e1000e.

  10. It’s a BETA. You are taking full responsibility by using it.

  11. theo

    so … what’s the prognosis … i was considering testing around a little in 11.1beta1 ….but not if it fries my hardware … did opensuse release any plan of action? … theo

  12. I just know that not every IT guys know the meaning of “BETA” version. But I hope SUSE reduce critical bug in their s/w, specially any bugs that can fire their beta tester users. If no, then no one won’t to be beta tester!