On Wed, 1 May 2002, Jay Nugent wrote: > Greetings, > > On Wed, 1 May 2002, Net Llama! wrote: > > > I've got a Redhat based laptop that doesn't want to have its PCMCIA NIC > > come up at eth0 at bootup. Its a static IP on an internal network. I can > > always bring it up with "ipfup eth0" manually, but it won't come up on its > > own. I've got "ONBOOT=YES" in /etc/sysconfig/network-scripts/ifcfg-eth0 > > and the network service is started upon bootup for runlevels 3 and 5 (it > > boots into 5 by default). So, i'm utterly stumped at why it won't > > cooperate. I've also got eth0 aliased to the tulip module (the correct > > module for the NIC) in /etc/modules.conf. Anyone have suggestions or > > ideas? > > I believe you must start all the PCMCIA crap/drivers first before you > will be able to start eth0. See what your startup order in in rc3.d or > rc4.d (whichever applies to your runlevel) and see that PCMCIA is started > *before* Network.
Thanks, i'll check on that and get back to you. This laptop is at home at the moment. > > It's amazing they just don't build laptops with 10/100BaseT ethernet > interfaces built-in. Ten bucks worth of parts. PCMCIA sucks soooo > badly... I dunno, i don't mind PCMCIA stuff. Its always worked just fine for me on x86 architecture. Now on Macs, it was a completely different story. The thing is, any time something gets built in on a laptop, it ends up being some crappy hack that requires a windoze-only driver. the winmodems are a prime example. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman [EMAIL PROTECTED] Linux Step-by-step & TyGeMo http://netllama.ipfox.com _______________________________________________ Linux-users mailing list - http://linux-sxs.org/mailman/listinfo/linux-users Subscribe/Unsubscribe info, Archives,and Digests are located at the above URL.
