On Sat, 2002-03-23 at 07:33, Matthew Saltzman wrote: > > I'm curious if your experience matches mine: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=60205
No, but your problem is what I described in an email I sent to the redhat-list last night titled "initscripts improvement". > Mine is a Latitude C610 with built-in ethernet and an internal Orinoco > wireless card. The ethernet card is not on the PCMCIA bus, and this seems > to confuse the startup scripts for network and wireless. The ethernet > interface won't start if pcmcia is running and the wireless card won't > start unless pcmcia is started with eth0 initialized (even if it isn't > actually up). I suppose that problem arises from the fact that you have both of them set to "ONBOOT=no". I believe that in that case, your built-in ethernet card is not initialized at boot or resume (the module isn't loaded in either case), but the PCMCIA card is, even though it isn't configured. In both cases, your PCMCIA card is eth0, because it was the first to have its module loaded. You won't be able to 'ifup eth0', because the configuration for your built-in card is attached to the PCMCIA card by name, and you can't bring up eth1 for the reverse reason. Stopping the PCMCIA service to bring up eth0 solves your problem by removing the module for the PCMCIA card, so that the built-in card can be 'eth0' when its module is loaded. Then, regardless of whether or not it gets configured by DHCP, the PCMCIA card will be eth1 when it's loaded. The solution to your problem should be to set up your built-in ethernet card with "ONBOOT=yes". Additionally, set "DHCPCDARGS=-t 15" in the config file so that it won't take forever to time out when the system boots and is not connected to ethernet. This should ensure that the built-in card is always eth0, and the PCMCIA card is always eth1. > Don't know about the Inspiron, but the Latitude a nice machine. This is > the only real quirk I've found. Windows 2000 handles the network > interfaces just fine, but the way redhat handles wireless is screwed up > (https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=58469, for example) Red Hat's system is much easier for them to maintain correctly with GUI setup tools. Rewriting network.opts would suck. I'm all in favor of keeping all of the information for a network card in one file, as Red Hat does, but attaching the config to the logical link name, which may vary, seems problematic for laptops especially.
signature.asc
Description: This is a digitally signed message part
