<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hello Gavin,<br>
    <br>
    thanks for the hint, I'll have a look for Florians patch and your
    post. I applied Florians "Link detection" patch for e1000e driver
    3.4 to the 3.2er driver (see attatchment), it solves the link
    detection issue here.<br>
    <br>
    Regards,<br>
    Jürgen Kunz<br>
    <br>
    <div class="moz-cite-prefix">Am 05.02.2013 06:26, schrieb Gavin
      Lambert:<br>
    </div>
    <blockquote cite="mid:072a01ce0361$628f1ba0$27ad52e0$@com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0cm;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New","serif";
        color:black;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle19
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
            Jürgen & Daniel,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
            have a fix for the first issue in my local copy of the
            driver (see my post to the dev list on 25 October for
            specific details).  I have seen the second issue but not
            chased down a fix for it yet.<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Also
            I just noticed that Florian updated the drivers on 4 January
            (posted in response to my message; I haven’t checked whether
            it includes the same fix or not).  I haven’t had a chance to
            test the new version myself yet but maybe it will help in
            your case too?<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Regards,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Gavin
            Lambert<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"
                    lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"
                  lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:etherlab-users-bounces@etherlab.org">etherlab-users-bounces@etherlab.org</a>
                  [<a class="moz-txt-link-freetext" href="mailto:etherlab-users-bounces@etherlab.org">mailto:etherlab-users-bounces@etherlab.org</a>] <b>On
                    Behalf Of </b>Jürgen Kunz<br>
                  <b>Sent:</b> Tuesday, 5 February 2013 18:16<br>
                  <b>To:</b> Daniel Helmick<br>
                  <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:etherlab-users@etherlab.org">etherlab-users@etherlab.org</a><br>
                  <b>Subject:</b> Re: [etherlab-users] e1000e driver
                  still not working with 3.2 kernel with latest
                  stable-1.5 branch?<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><o:p> </o:p></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt">Hello
            Daniel,<br>
            <br>
            I am using this combination for a while now, with 32- and
            64-bit versions of the 3.2er Debian RT-Kernel. If there is a
            EtherCAT device connected to the computer, the driver works
            fine.<br>
            There are two issues in this driver version, if there are no
            EtherCAT devices connected. The first, the one you mentioned
            here, is when the EtherCAT Master starts up with no device
            connected, then the network-adapter is continously reseted
            until a device is connected. It may hang the computer if no
            device is connected for a while.<br>
            The second issue is that when the link is plugged off, the
            link state is not updated. Unfortunately, I did not have
            time yet to correct these issues.<br>
            <br>
            Greetings,<br>
            Jürgen Kunz<o:p></o:p></p>
          <div>
            <p class="MsoNormal">Am 05.02.2013 01:59, schrieb Daniel
              Helmick:<o:p></o:p></p>
          </div>
          <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
            <p class="MsoNormal">Has anyone else gotten this combination
              of driver and kernel to work?<br>
              <br>
              Here's the /var/log/messages output when I start the
              ethercat master:<br>
              <br>
              [  869.854110] EtherCAT: Master driver 1.5.1 9cdd7669dc0b<br>
              [  869.854252] EtherCAT: 1 master waiting for devices.<br>
              [  869.944866] e1000e 0000:04:00.0: PCI INT A disabled<br>
              [  869.948134] ec_e1000e: EtherCAT-capable Intel(R)
              PRO/1000 Network Driver - 1.5.1-k-EtherCAT<br>
              [  869.948138] ec_e1000e: Copyright(c) 1999 - 2011 Intel
              Corporation.<br>
              [  869.948202] ec_e1000e 0000:04:00.0: Disabling ASPM L0s
              <br>
              [  869.948261] ec_e1000e 0000:04:00.0: PCI INT A -> GSI
              17 (level, low) -> IRQ 17<br>
              [  869.948530] ec_e1000e 0000:04:00.0: setting latency
              timer to 64<br>
              [  869.951386] ec_e1000e 0000:04:00.0: irq 65 for
              MSI/MSI-X<br>
              [  869.951393] ec_e1000e 0000:04:00.0: irq 66 for
              MSI/MSI-X<br>
              [  869.951397] ec_e1000e 0000:04:00.0: irq 67 for
              MSI/MSI-X<br>
              [  870.120739] EtherCAT: Accepting 68:05:CA:10:C0:82 as
              main device for master 0.<br>
              [  870.197588] EtherCAT 0: Starting EtherCAT-IDLE thread.<br>
              [  870.197651] ec_e1000e 0000:04:00.0: (unregistered
              net_device): (PCI Express:2.5GT/s:Width x1)
              68:05:ca:10:c0:82<br>
              [  870.197656] ec_e1000e 0000:04:00.0: (unregistered
              net_device): Intel(R) PRO/1000 Network Connection<br>
              [  870.197687] ec_e1000e 0000:04:00.0: (unregistered
              net_device): MAC: 3, PHY: 8, PBA No: E46981-008<br>
              [  870.197825] ec_e1000e 0000:04:00.0: (unregistered
              net_device): Reset adapter<br>
              [  872.196168] ec_e1000e 0000:04:00.0: (unregistered
              net_device): Reset adapter<br>
              [  874.196169] ec_e1000e 0000:04:00.0: (unregistered
              net_device): Reset adapter<br>
              [  876.196159] ec_e1000e 0000:04:00.0: (unregistered
              net_device): Reset adapter<br>
              [  878.196162] ec_e1000e 0000:04:00.0: (unregistered
              net_device): Reset adapter<br>
              <br>
              <br>
              And the reset adapter message occurs every 2 seconds until
              I stop the ethercat master.<br>
              <br>
              Thanks,<br>
              Dan<br>
              <br>
              <br>
              <br>
              <o:p></o:p></p>
            <pre>_______________________________________________<o:p></o:p></pre>
            <pre>etherlab-users mailing list<o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="mailto:etherlab-users@etherlab.org">etherlab-users@etherlab.org</a><o:p></o:p></pre>
            <pre><a moz-do-not-send="true" href="http://lists.etherlab.org/mailman/listinfo/etherlab-users">http://lists.etherlab.org/mailman/listinfo/etherlab-users</a><o:p></o:p></pre>
          </blockquote>
          <p class="MsoNormal"><o:p> </o:p></p>
          <div>
            <p class="MsoNormal">-- <br>
              Dipl.-Inform. Jürgen Kunz<br>
              <br>
              <a moz-do-not-send="true"
                href="http://www.tu-darmstadt.de">Technische Universität
                Darmstadt</a><br>
              <a moz-do-not-send="true"
                href="http://www.sim.tu-darmstadt.de">FG Simulation,
                Systemoptimierung und Robotik</a><br>
              Hochschulstr. 10<br>
              64289 Darmstadt<br>
              <br>
              Tel.: ++49 (0) 6151-16-70383<br>
              Fax: ++49 (0) 6151-16-6648<br>
              E-Mail: kunz(at)sim.tu-darmstadt.de<br>
              Homepage: <a moz-do-not-send="true"
                href="http://www.sim.tu-darmstadt.de">http://www.sim.tu-darmstadt.de</a><o:p></o:p></p>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      Dipl.-Inform. Jürgen Kunz<br>
      <br>
      <a href="http://www.tu-darmstadt.de">Technische Universität
        Darmstadt</a><br>
      <a href="http://www.sim.tu-darmstadt.de">FG Simulation,
        Systemoptimierung und Robotik</a><br>
      Hochschulstr. 10<br>
      64289 Darmstadt<br>
      <br>
      Tel.: ++49 (0) 6151-16-70383<br>
      Fax: ++49 (0) 6151-16-6648<br>
      E-Mail: kunz(at)sim.tu-darmstadt.de<br>
      Homepage: <a href="http://www.sim.tu-darmstadt.de">http://www.sim.tu-darmstadt.de</a></div>
  </body>
</html>