Carsten Aulbert wrote:
> I'm currently looking through the device IDs which module to use for these.
OK, found the igb kernel driver for that one. I'll try what will happen
if this is included.
Thanks for listening and suggestions!
Carsten
--
Carsten Aulbert wrote:
ions during installation, but that's really hacky.
>
> If you know of a tool to activate PXE on the add-on NICs please let me
> know. I'll try to find out the IDs now.
>
OK, I suspect the NICs are just too new for the 2.6.23 kernel (and also
for the 2.6.27?)
The addon NICs
Carsten,
I don't know if this is what you want to know.
But, you can change the name of the net_device using /sbin/ip
command like the following:
$ ip link set ethX name whatever_name
ethX has to be DOWN beforehand.
Maybe you could add commands to reorder in early part of rc scripts?
Best,
Tomo
Hi Roman,
Roman Chertov wrote:
> I frequently use this on CentOS as I have some machines with 10 NICs.
> You can try to see how CentOS/RH do it so that you can use it on your
> own distribution. In /etc/sysconfig/network-scripts there are files
> like ifcfg-ethX. There you can specify the MAC an
Hi all,
Brandeburg, Jesse wrote:
>
> if your add-in nics are e1000 server adapters they can be configured to PXE
> boot too. You have to enable option rom support in the BISO and the option
> rom itself.
I don't see these cards in the BIOS right now only the onboard ones.
I've enabled everyth
Carsten,
I frequently use this on CentOS as I have some machines with 10 NICs.
You can try to see how CentOS/RH do it so that you can use it on your
own distribution. In /etc/sysconfig/network-scripts there are files
like ifcfg-ethX. There you can specify the MAC and the dev name like
eth2.
Carsten Aulbert wrote:
> sorry to bother you such a thing, but I'm not getting anywhere right
> now. I've a server with four NICs which are all powered by the e1000
> driver. Two are on the Supermicro main board and two are added via an
> add-on card. It seems that I can only PXE boot from the two
Bummer.
I guess I was too focused to get the 'ordering' right, i.e. to have eth0
and eth1 on the motherboard and then eth2 and eth3 on the PCIe card,
that I totally oversaw this part of my 'kernel line':
ip=:eth0:dhcp
Probably i just need to put eth2 here.
If that's the cure, sorry for the
Carsten Aulbert wrote:
> Hi Auke,
>
> Kok, Auke wrote:
>> if you have udev installed and running you can just edit:
>>
>> /etc/udev/rules.d/70-persistent-net.rules
>>
>> to rename the devices persistently. No ugly firmware hacks needed.
>
> That's too far down the road as the kernel needs to make
Hi Auke,
Kok, Auke wrote:
>
> if you have udev installed and running you can just edit:
>
> /etc/udev/rules.d/70-persistent-net.rules
>
> to rename the devices persistently. No ugly firmware hacks needed.
That's too far down the road as the kernel needs to make the inquieries
already and udev
if you have udev installed and running you can just edit:
/etc/udev/rules.d/70-persistent-net.rules
to rename the devices persistently. No ugly firmware hacks needed.
Auke
Carsten Aulbert wrote:
> Hi all,
>
> sorry to bother you such a thing, but I'm not getting anywhere right
> now. I've
Hi all,
sorry to bother you such a thing, but I'm not getting anywhere right
now. I've a server with four NICs which are all powered by the e1000
driver. Two are on the Supermicro main board and two are added via an
add-on card. It seems that I can only PXE boot from the two on-board
NICs while th
12 matches
Mail list logo
