On 2024/10/05 09:45, Pierre Peyronnel wrote:
> Happened to me too.
>
> Will I need to manually boot the next snapshot bsd kernel to fix ?
I don't know whether it was a kernel diff or a userland diff that was
the problem. But manually upgrading the machine (kernel+userland) to
the next snapshot (o
Happened to me too.
Will I need to manually boot the next snapshot bsd kernel to fix ?
In the meantime it still routes and serve wg VPN
On Fri, Oct 4, 2024, 11:31 Stuart Henderson
wrote:
> On 2024-10-03, Michael Joy wrote:
> > Hey all, just did a sysupgrade -s on current. It all appeared to b
That's what I did and it worked out fine
Sent from Proton Mail Android
Original Message
On 05/10/2024 08:45, Pierre Peyronnel wrote:
Happened to me too.
Will I need to manually boot the next snapshot bsd kernel to fix ?
In the meantime it still routes and serve wg VPN
On Fri, O
Leaving a headstone for the next person who goes looking:
It was the transceivers. Some intel-coded transceivers from FS worked
straight away.
Thanks all who provided helpful suggestions and pointers, I appreciate
it.
weaver
On Fri, Oct 4, 2024, at 06:54, Wouter Prins wrote:
> hi Matthew,
>
>
Yes, the firmware was ancient! You'll notice the later boots
included in my dmesg show the interfaces with the latest firmware:
ixl0 at pci1 dev 0 function 0 "Intel X710 SFP+" rev 0x02: port 0, FW
9.152.77998 API 1.15, msix, 8 queues, address 40:a6:b7:b3:4b:28
ixl1 at pci1 dev 0 function 1 "Intel
5 matches
Mail list logo
