bxe0: ERROR: Invalid SHMEM Validity signature: 0x0000008bxe0: ERROR: Invalid phy config in NVRAM (PHY1=0x0000008 PHY2=0x0000008)bxe0: Uknown mediabxe0: IFMEDIA flags: 20bxe0: using defaults for TSO: 65518/35/2048bxeo: ERROR FW failed to respond!bxe0: ERROR MCP response failure, abortingbxe0: ERROR Failed to unload previous driver! time_counter 10 rc -1
if I were you, I'd verify that firmware on the card is as it should be by booting it onto a vanilla freebsd of the same OPN version and on a linux one.Cases like these can be down to corrupted or wrong firmware like a bad crssflash. Booting to other OS can help verify in a non-destructive way.
Quote from: cookiemonster on December 27, 2023, 02:08:48 pmif I were you, I'd verify that firmware on the card is as it should be by booting it onto a vanilla freebsd of the same OPN version and on a linux one.Cases like these can be down to corrupted or wrong firmware like a bad crssflash. Booting to other OS can help verify in a non-destructive way.Thats actually helpful, im going to try this this weekend, thnx
Quote from: thecrankygamer on January 05, 2024, 06:32:39 pmQuote from: cookiemonster on December 27, 2023, 02:08:48 pmif I were you, I'd verify that firmware on the card is as it should be by booting it onto a vanilla freebsd of the same OPN version and on a linux one.Cases like these can be down to corrupted or wrong firmware like a bad crssflash. Booting to other OS can help verify in a non-destructive way.Thats actually helpful, im going to try this this weekend, thnxHi, did you find a solution? I have the same exact output from dmesg on opnsense.
I cant even get it to work when using vmxnet, so i think the 10gb card has a bad firmware, or, is just broken