[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PCMCIA NIC & internal NIC



    "Chris" == Chris Horn <chorn@rand.org> writes:

    Chris> Thanks a lot for this info.  I'm glad it's not something
    Chris> I/we did!  So, to check, how will the eth1 interface be
    Chris> brought up?  Do I have to do it manually with 'ifup eth1'
    Chris> or another command, or is there some way to have this down
    Chris> a) whenever the machine boots b) whenever the card is
    Chris> inserted into its slot?

Hi Chris,

eth1 will be bought up when the PCMCIA subsystem starts. Basically,
when the networking script is run from /etc/rcN.d/ it will do an 'ifup
-a' which will bring up any network devices marked 'auto'. A little
later the pcmcia subsystem will start, and if you have a ethernet card
in the PCMCIA slot, cardmgr and friends *should* (in a normal
installation)  detect it, beep, look in /etc/network/interfaces, and
bring it up for you. If you don't have the card in there, it will come
up on insertion. 

If you consider this ordering you should immediately realize why
adding 'auto' to eth1 screws things up. The networking script can't
bring it up because it is PCMCIA, the pcmcia script can't bring it up
because the 'ifup -a' from the network script marked the device as
failed (in /etc/network/ifstate). The user then needs to go in and do
a 'ifdown eth1' followed by a 'ifup eth1' or something at that point
to bring sanity to the interfaces.

This approach works just fine for me on two different laptops. I
do believe it is the "right thing" for Debian.....but you don't have
to take my word for it ;-)

Cheers!
Shyamal


    Chris> take care.  chris.

    Chris> At 07:19 PM Tuesday 1/7/2003, Shyamal Prasad wrote:
    >> "chris" == chris horn <chorn@rand.org> writes:
    >> 
    chris> hello.  there's a colleague at work here with a sony vaio
    chris> and two network interfaces.  one is the built in nic that
    chris> requires a dongle to use, and the other is a pcmcia network
    chris> card.  the problem is that apparently the network is being
    chris> initialized before the pcmcia devices are.  judging by the
    chris> scripts in /etc/init.d/, everything is in order - but in
    chris> practice eth1 (the pcmcia card) is not initialized before
    chris> it tries to get set up with the config in
    chris> /etc/network/interfaces.  what's the matter here?  is this
    chris> a configuration error on my part, or debian's?
    >>  nope, nothing wrong unless you a have done something really
    >> non standard. pcmcia cards are bought up by the pcmcia
    >> subsystems, the other network cards are bought up by the
    >> network scripts (which run earlier). so, if you are setting up
    >> the pcmcia card via /etc/network/interfaces do not use the
    >> 'auto' keyword for eth1. that should take care of it unless you
    >> did something else to the standard installation.
    >> 
    >> cheers!  shyamal
    >> 
    >> 
    >> -- to unsubscribe, email to
    >> debian-laptop-request@lists.debian.org with a subject of
    >> "unsubscribe". trouble? contact listmaster@lists.debian.org


    Chris> ----- chorn@rand.org 703.413.1100 x5100


    Chris> -- To UNSUBSCRIBE, email to
    Chris> debian-laptop-request@lists.debian.org with a subject of
    Chris> "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: