<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=2170&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / ethtool --identify fails for ixgbe X553 NICs]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=2170</link>
		<description><![CDATA[The most recent posts in ethtool --identify fails for ixgbe X553 NICs.]]></description>
		<lastBuildDate>Thu, 21 Jun 2018 09:18:36 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: ethtool --identify fails for ixgbe X553 NICs]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=10285#p10285</link>
			<description><![CDATA[<p>Disclaimer: I have no foreknowledge of ethtool.</p><p>However, from a quick glance at <a href="https://linux.die.net/man/8/ethtool" rel="nofollow">ethtool(8)</a>, there appear to be a number of options to query the driver to see what functionality is supported.&#160; So perhaps not a matter of unsupported hardware, but an unsupported feature?</p>]]></description>
			<author><![CDATA[dummy@example.com (cynwulf)]]></author>
			<pubDate>Thu, 21 Jun 2018 09:18:36 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=10285#p10285</guid>
		</item>
		<item>
			<title><![CDATA[ethtool --identify fails for ixgbe X553 NICs]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=10259#p10259</link>
			<description><![CDATA[<p>Hi,</p><p>we&#039;re currently setting up new hardware with Linux (Devuan Ascii / Debian 9) on Atom Denverton SoC systems utilizing the X553 NICs.</p><p>While general networking seems to work just fine, our go-to method to identify the NICs by LEDs blinking (ethtool -p / --identify ethX) doesn&#039;t seem to do anything. The command is being accepted (on unsupported hardware we&#039;d get a &quot;Operation not supported&quot;), but there&#039;s simply no blinking happening :-(</p><p>Various other Intel NICs in use (older chipsets using the e1000 or igb drivers, for example 82574L or I350) display the expected behavior. We&#039;ve tried the newest drivers 5.3.7. as well as the ones shipped with our kernel of choice (4.16. from backports) - neither seem to work.</p><p>Are we doing it wrong? Any hints appreciated :-)</p>]]></description>
			<author><![CDATA[dummy@example.com (andrew)]]></author>
			<pubDate>Wed, 20 Jun 2018 12:39:11 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=10259#p10259</guid>
		</item>
	</channel>
</rss>
