Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

X553 NICs don't link up through Marvell 88E6190 switch #232

Open
2 tasks done
jayPare opened this issue Jan 15, 2025 · 1 comment
Open
2 tasks done

X553 NICs don't link up through Marvell 88E6190 switch #232

jayPare opened this issue Jan 15, 2025 · 1 comment
Labels
upstream Third party issue

Comments

@jayPare
Copy link

jayPare commented Jan 15, 2025

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Describe the bug

Ports through MV88E6190 switch with Intel X553 NICs are not linking up despite Commit 9aba063.

To Reproduce

Configuring login behaviour...done. 

Default interfaces not found Running interface assignment option.

Press any key to start the manual interface assignment: <press any key>

Do you want to configure LAGGs now? [y/N]: <press n>
Do you want to configure VLANs now? [y/N]: <press n>

Valid interfaces are: 
ix0 Intel(R) X553 (KR Backplane) 
ix1 Intel(R) X553 (KR Backplane) 

If you do not know the names of your interfaces, you may choose to use auto-detection. In that case, disconnect all interfaces now before hitting 'a' to initiate auto detection.

Enter the WAN interface name or 'a' for auto-detection: <press a>

Connect the WAN interface now and make sure that the link is up. Then press ENTER to continue. 

No link-up detected.

Enter the WAN interface name or 'a' for auto-detection:

Expected behavior

X553 should be able to link up through Marvell 88E6190.

Additional context

Problem is documented in several places:

Disclamer

I didn't test it myself, since I don't have this hardware. I'm looking at buying an Watchguard M270 and should have it in hands to test next week.

@jayPare
Copy link
Author

jayPare commented Jan 15, 2025

@fichtner fichtner added the upstream Third party issue label Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Third party issue
Development

No branches or pull requests

2 participants