| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Wed, 29 Jan 2003, Lars Damerow wrote: > >From Kevin McConnell <kevymac@yahoo.com>, Wed, Jan 29, 2003 at 11:32:44AM -0800: > > > > --- Lars Damerow <lars-rhdevel@pixar.com> wrote: > > > >From Kevin McConnell <kevymac@yahoo.com>, Wed, Jan > > > 29, 2003 at 11:13:23AM -0800: > > > > > > > > This is just something to get your mind working. I > > > > know there is a way to pass options to modules as > > > > they're loaded. Using the IRQ and base address, > > > > couldn't one conceivably assign eth0 to be one and > > > > > > That might be possible--I'll check it out. > > > > Check the notes for the drivers for details on how to > > do this. I know for the 3com cards it's possible and > > that's what I use. I once had a similar problem with > > some other brand of cards, and that's how I solved the > > problem. By saying that such and such card residing at > > this base address is eth0, etc.. > > What type of network card(s) are they? > > Documentation/networking/3c509.txt points out the following option: > > ether=10,0x310,3,0x3c509,eth0 > > Is that what you meant? It looks like it. > > In our workstations, the cards are 3c59x on-board ethernet and either an Intel > e1000 or Alteon AceNIC PCI card. Our servers have two on-board e1000 cards. Removing the modules for the NICs you don't want to use will force the issue;-) -- Please, reply only to the list. _______________________________________________ Redhat-devel-list mailing list Redhat-devel-list@redhat.com https://listman.redhat.com/mailman/listinfo/redhat-devel-list