I have both drivers compiled into the kernel at the moment and 
I wish I knew why eth1 is not "available". Anyway, I will
try your suggestion. 

Does anyone know a good source on linux ethernet networking?

Thanks,

--
Valmor de Almeida



> On Wednesday 04 February 2004 22:08, Valmor de Almeida wrote:
> > The result from lspci on my laptop shows two
> > ethernet interfaces. One is on the port replicator,
> > and the other (functional) is on the laptop chassi.
> >
> > 02:08.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev
> > 78) 08:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100]
> > (rev 08)
> >
> > I've been trying to configure the interface on the port replicator
> > but no luck. I do have eth0 to configure but eth1 does not exist.
> > How are those created anyway?  Anybody with past experience on that?
> 
> I wish I *knew* how the interfaces are numbered, but if you keep the drivers 
> as modules (or 1 of), you can force the order.
> i.e. compile the 3x59x into the kernel, and the eepro100 as a module. The 
> kernel will have support for the 3com during boot assigning it eth0, loading 
> eepro100 later will give it eth1.
> 
> Alternatively, leave both drivers as modules, and in /etc/modules.d/aliases 
> add:
> alias eth0 3c59x
> alias eth1 eepro100
> 
> Once you've 'update-modules''d, don't try to automatically load the modules, 
> as when something tries to access either eth0 or eth1 the module will 
> automatically be loaded.
> 
> - -- 
> Mike Williams
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> 
> iD8DBQFAIXYnInuLMrk7bIwRAngPAKCQqVUzTRvR3MdZ9/wHxdnmLOgm2ACfenJ1
> r/oQCSP+yTEmyg5NPq6TADM=
> =93eb
> -----END PGP SIGNATURE-----
> 
> --
> [EMAIL PROTECTED] mailing list
> 
> 

--
[EMAIL PROTECTED] mailing list

Reply via email to