From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] New 100G Broadcom NIC Ubuntu
Date: Tue, 28 Jul 2020 10:22:35 -0700 [thread overview]
Message-ID: <CACZ4nhuVV6CWmkrKT7kBoAh4KNKjqk13h_NdjOZPyroPBtwKrQ@mail.gmail.com> (raw)
In-Reply-To: <CAOeXdvZoeycKfZyZ59y5HfePpUox90YAbAERCk00mB0ExD0Upg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1848 bytes --]
Brandon,
I have sent them a reminder. I will keep you posted.
But I tried to login into the system to peek around and the VPN seems to
continuously negotiate/authenticate. For some reason the connection
is getting reset.
Any idea on what might be causing this?
Thanks
Ajit
On Tue, Jul 28, 2020 at 9:48 AM Brandon Lo <blo@iol.unh.edu> wrote:
> Hi Ajit,
>
> Have you gotten a response yet?
> I've tried the firmware from the official website but it's supported on
> Fedora/Redhat instead of Ubuntu.
>
> Thanks,
> Brandon
>
> On Tue, Jul 21, 2020 at 5:28 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
> wrote:
>
>> Hi Brandon,
>> Maybe I might have to update it to a newer firmware.
>> Let me check internally and get back.
>>
>> Thanks
>> Ajit
>>
>>
>> On Tue, Jul 21, 2020 at 1:23 PM Brandon Lo <blo@iol.unh.edu> wrote:
>>
>>> Hi Ajit,
>>>
>>> We've received the Broadcom 100G NIC and installed it onto the machine.
>>> However, the drivers don't seem to support Ubuntu, information from
>>> https://www.broadcom.com/products/ethernet-connectivity/network-adapters/100gb-nic-ocp/p2100g
>>> .
>>>
>>> I've also updated the kernel to the latest version. The card appears
>>> with the correct name in lspci and lshw, but it has no available MAC
>>> address, so I can't use it in setting up the nic single core performance
>>> testing.
>>>
>>> Do you know what could be causing this issue?
>>>
>>> Thanks,
>>> Brandon
>>>
>>>
>>> --
>>>
>>> Brandon Lo
>>>
>>> UNH InterOperability Laboratory
>>>
>>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>> <https://www.google.com/maps/search/21+Madbury+Rd,+Suite+100,+Durham,+NH+03824?entry=gmail&source=g>
>>>
>>> blo@iol.unh.edu
>>>
>>> www.iol.unh.edu
>>>
>>
>
> --
>
> Brandon Lo
>
> UNH InterOperability Laboratory
>
> 21 Madbury Rd, Suite 100, Durham, NH 03824
>
> blo@iol.unh.edu
>
> www.iol.unh.edu
>
[-- Attachment #2: Type: text/html, Size: 6797 bytes --]
next prev parent reply other threads:[~2020-07-28 17:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 20:22 Brandon Lo
2020-07-21 21:27 ` Ajit Khaparde
2020-07-28 16:47 ` Brandon Lo
2020-07-28 17:22 ` Ajit Khaparde [this message]
2020-07-28 17:32 ` Brandon Lo
2020-07-28 19:19 ` Ajit Khaparde
2020-07-28 19:41 ` Brandon Lo
2020-08-04 16:16 ` Brandon Lo
2020-08-04 16:37 ` Ajit Khaparde
2020-08-04 17:42 ` Brandon Lo
2020-08-11 17:45 ` Brandon Lo
2020-08-11 17:47 ` Ajit Khaparde
2020-08-20 4:29 ` Ajit Khaparde
2020-08-20 15:39 ` Brandon Lo
2020-08-20 21:07 ` Ajit Khaparde
2020-08-25 20:13 ` Brandon Lo
2020-08-26 19:57 ` Ajit Khaparde
2020-09-01 18:09 ` Brandon Lo
2020-09-01 18:11 ` Ajit Khaparde
2020-10-22 19:03 ` Brandon Lo
2020-10-22 19:27 ` Ajit Khaparde
2020-12-03 16:48 ` [dpdk-ci] [dpdklab] " Brandon Lo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACZ4nhuVV6CWmkrKT7kBoAh4KNKjqk13h_NdjOZPyroPBtwKrQ@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).