PXE bootup issues on Multi-Ethernet CPU
Posted: 01 May 2017, 16:19
So,
I have been experimenting with the Porteus PXE boot option (3.1 I believe) , which is really great.
My issue is that the CPU has multiple Ethernet ports. If I boot Porteus from the "primary" Ethernet port on the booting CPU (the lowest one in PCI space), everything works fine and great.
If I choose another Ethernet port on the bootin CPU, the Porteus Boot menu shows up but when it attempts to load in the startup script but after the
searching for porteus-v3.1-x86_64.sgn file
udhcpc (v1.21.1) started
I just get a bunch of
Sending discover...
Sending discover...
So it mostly comes up but when it attempts to get the rest of the system, I believe it goes for the first found Ethernet port and fails to continue. I can prove this by moving the Connection to the first port of the booting CPU and everything continues on fine.
Basically, it boots the startup menu and script from a secondary Ethernet , but then finishes the download from the primary Ethernet.
I hope this makes sense.
I am looking at the initrd package and attempting to modify linuxrc but I don't see where the control section to select the ethernet really comes into play, and I don't have the experience to figure it out.
Anyone know of an easy hack?
I have been experimenting with the Porteus PXE boot option (3.1 I believe) , which is really great.
My issue is that the CPU has multiple Ethernet ports. If I boot Porteus from the "primary" Ethernet port on the booting CPU (the lowest one in PCI space), everything works fine and great.
If I choose another Ethernet port on the bootin CPU, the Porteus Boot menu shows up but when it attempts to load in the startup script but after the
searching for porteus-v3.1-x86_64.sgn file
udhcpc (v1.21.1) started
I just get a bunch of
Sending discover...
Sending discover...
So it mostly comes up but when it attempts to get the rest of the system, I believe it goes for the first found Ethernet port and fails to continue. I can prove this by moving the Connection to the first port of the booting CPU and everything continues on fine.
Basically, it boots the startup menu and script from a secondary Ethernet , but then finishes the download from the primary Ethernet.
I hope this makes sense.
I am looking at the initrd package and attempting to modify linuxrc but I don't see where the control section to select the ethernet really comes into play, and I don't have the experience to figure it out.
Anyone know of an easy hack?