9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Mr Neuralwright <neuralwright@tutamail.com>
To: 9front <9front@9front.org>
Subject: Re: [9front] 10Gbit PCIE Intel 85299-1SFP Troubleshooting
Date: Thu, 4 Apr 2024 23:32:16 +0200 (CEST)	[thread overview]
Message-ID: <Nuf0hbt--3-9@tutamail.com> (raw)
In-Reply-To: <1B93E530C6703688BD56070231A8492B@eigenstate.org>

[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]

%pci -v
<snip>
1.0.0: net 02.00.00 8086/10fb 255 0:4f880004 524288 2:00004001 32 4:4f900004 16384
Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection

In my SFP port is an SFP to RJ45 copper module, it is a unbranded generic 10/100/1000Base-T, confirmed to work on Ubuntu. 
4 Apr 2024, 22:05 by ori@eigenstate.org:

> % pci -v
> <snip>
> 1.0.0:	net  02.00.00 8086/1557  11 0:e030000c 524288 2:0000f001 32 4:e038000c 16384
>  Intel Corporation 82599 10 Gigabit Network Connection
>
> This card works for me out of the box, with a 10g sfp.
> What specific PCI id do you have? what SFP?
>
> This is going to take some debugging.
>
> Quoth Mr Neuralwright <neuralwright@tutamail.com>:
>
>> Hi All,
>> I have recently acquired a 10Gbit PCIE Intel 85299-1SFP network card since this chipset is supported in 9front, although now I suspect the driver may have only RJ45 port variants of 85299 supported, and not SFP - hopefully I'm wrong and I'm just missing something.
>>
>> #ip/ipconfig
>> "no success with DHCP*
>>
>> #ip/ipconfig -g 192.168.1.1 ether /net/ether0 192.168.1.200 255.255.255.0
>> #ip/ping 192.168.1.1
>> Pings fail
>> #cat /net/ether0/adder
>> successfully returns a MAC address
>>
>> (Yes, ether0 is the PCIE card and not the integrated NIC)
>> Notably the Rx/Tx lights on the SFP port do not light up at all. Networking and the activity lights work perfectly fine on Ubuntu out-the-box, so the hardware is fine.
>>
>> 9front does at least recognise the device exists, which is a start. Any suggestions on how to resolve this?
>>


[-- Attachment #2: Type: text/html, Size: 2699 bytes --]

  reply	other threads:[~2024-04-04 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 19:10 Mr Neuralwright
2024-04-04 21:03 ` ori
2024-04-04 21:32   ` Mr Neuralwright [this message]
2024-04-06  7:57     ` Anthony Martin
     [not found]   ` <Nuf0hbt--3-9@tutamail.com-Nuf1NHk--7-9>
2024-04-06  0:28     ` Mr Neuralwright

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=Nuf0hbt--3-9@tutamail.com \
    --to=neuralwright@tutamail.com \
    --cc=9front@9front.org \
    /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).