disabling nics in efi.
I have a bunch of HP rx2600 that have two internal nics (10/100Mbit and 1Gbit) and one external nic (1Gbit). Is it possible to disable the two internal ones in efi so linux won't see them? I tried to use the disconnect command in the efi shell, but they still keep showing up when I boot up linux. I used
disconnect 4C
disconnect 49
and they report successful operation. Am I missing the point completely?
I also tried the reserve= boot option to avoid linux to probe them, but that didn't work either. I probably computed the iobase and extents wrong. Do anyone know how to determine the correct parameters?
The reason for wanting to disable the internal nics is that the redhat installer insists on fetching the kickstart file over eth0 when doing installations over the network and the external nic that I want to use becomes eth2.
Any hints is greatly appreciated.
Best regards,
Roy.
Signature · 4 lines
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: [email protected]Have you tried just using the 'ksdevice=eth2' option to tell anaconda to use eth2 for the kickstart install?
Quoted 35 lines
I have a bunch of HP rx2600 that have two internal nics (10/100Mbit and 1Gbit) and one external nic (1Gbit). Is it possible to disable the two internal ones in efi so linux won't see them? I tried to use the disconnect command in the efi shell, but they still keep showing up when I boot up linux. I used
disconnect 4C
disconnect 49
and they report successful operation. Am I missing the point completely?I also tried the reserve= boot option to avoid linux to probe them, but that didn't work either. I probably computed the iobase and extents wrong. Do anyone know how to determine the correct parameters?
The reason for wanting to disable the internal nics is that the redhat installer insists on fetching the kickstart file over eth0 when doing installations over the network and the external nic that I want to use becomes eth2.
Any hints is greatly appreciated.
Best regards,
Roy.Signature · 10 lines
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway. phone:+47 77 64 41 07, fax:+47 77 64 41 00 Roy Dragseth, High Performance Computing System Administrator Direct call: +47 77 64 62 56. email: [email protected] _______________________________________________ Linux-IA64 mailing list [email protected] http://lists.linuxia64.org/lists/listinfo/linux-ia64
The EFI driver has nothing to do with whether the NIC shows up
to the OS. It only makes it unavailble from EFI, the hardware is still there. I don't know of any way to make the NICs not show up other than not loading the module.
Alex
Quoted 26 lines · Roy Dragseth
I have a bunch of HP rx2600 that have two internal nics (10/100Mbit and 1Gbit) and one external nic (1Gbit). Is it possible to disable the two internal ones in efi so linux won't see them? I tried to use the disconnect command in the efi shell, but they still keep showing up when I boot up linux. I used
disconnect 4C
disconnect 49
and they report successful operation. Am I missing the point completely?I also tried the reserve= boot option to avoid linux to probe them, but that didn't work either. I probably computed the iobase and extents wrong. Do anyone know how to determine the correct parameters?
The reason for wanting to disable the internal nics is that the redhat installer insists on fetching the kickstart file over eth0 when doing installations over the network and the external nic that I want to use becomes eth2.
Any hints is greatly appreciated.
Best regards,
Roy.
--The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
Quoted 8 lines
phone:+47 77 64 41 07, fax:+47 77 64 41 00 Roy Dragseth, High Performance Computing System Administrator Direct call: +47 77 64 62 56. email: [email protected]_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Alex Williamson Linux Development Lab
[email protected] Hewlett Packard
970-898-9173 Fort Collins, CO
Quoted 2 lines · Joseph V Moss
Have you tried just using the 'ksdevice=eth2' option to tell anaconda to use eth2 for the kickstart install?
yes, it still insists on getting it through eth0. At least that what I think it is trying to do because it works ok when I connect a cable to that interface.
r.
Signature · 4 lines
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: [email protected]Quoted 4 lines · Alex Williamson
The EFI driver has nothing to do with whether the NIC shows up
to the OS. It only makes it unavailble from EFI, the hardware is still there. I don't know of any way to make the NICs not show up other than not loading the module.
So, I was indeed missing the point.
The only viable path seems to be preventing the kernel to probe the interfaces using the reserve boot option. If I only could figure out how to compute the right addresses...
r.
Signature · 4 lines
The Computer Center, University of Tromsø, N-9037 TROMSØ, Norway.
phone:+47 77 64 41 07, fax:+47 77 64 41 00
Roy Dragseth, High Performance Computing System Administrator
Direct call: +47 77 64 62 56. email: [email protected]