[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<AM0PR03MB59381C3714D1B54C867CB65CB9B8A@AM0PR03MB5938.eurprd03.prod.outlook.com>
Date: Fri, 24 Nov 2023 07:38:14 +0000
From: Ivar Simensen <is@...arespons.no>
To: Michal Kubecek <mkubecek@...e.cz>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: ethtool module info only reports hex info
Hi Michal
I'm not sure of this. I did not build the ethtool my selves, but used the version that comes with Jammy. When testing different versions of ethtool, I used the deb packages found at
http://archive.ubuntu.com/ubuntu/pool/main/e/ethtool/ and installed with dpkg.
I assumed however that pretty dump was enabled.
-----Original Message-----
From: Michal Kubecek <mkubecek@...e.cz>
Sent: torsdag 23. november 2023 16:20
To: Ivar Simensen <is@...arespons.no>
Cc: netdev@...r.kernel.org
Subject: Re: ethtool module info only reports hex info
On Thu, Nov 23, 2023 at 07:42:07AM +0000, Ivar Simensen wrote:
> Hi
> I'm not sure if this is a conscious decision or a bug, but I
> discovered a change of behavior between version 5.4 an 5.16 according
> to get module info from a SFP Fiber connector: "ethtool -m ens5".
>
> After upgrading a target from Ubuntu 18.04 to 22.04, I discovered that
> the ethtool just report a hex dump when I tried to verify my fiber SFP
> connectors. In 18.04 I got a report with ethtool. I have tried to
> upgrade from version 5.16 to 6.1 and 6.5, but it did not fix the
> issue. I then downgraded to version 5.4 and now it works again.
Are you sure your ethtool was built with pretty dumps enabled?
Michal
Powered by blists - more mailing lists