Daniel Nilsson wrote on Nov, 1:
> On Mon, Oct 31, 2005 at 08:56:46PM -0500, Patrick Wiseman wrote:
> > This is on a laptop, so the card is a pcmcia card; it always used to get
> > connected after being recognised. Now it gets recognised quickly but doesn't
> > get connected until I manually 'ifup eth0'. Anyone know why this broke? Do I
> > need to change the order in which things start up?
>
> I've seen a similar issue, I belive what changed was the hotplugging so
> that you now need a line that says:
>
> allow-hotplug eth0
>
> in /etc/network/interfaces
This won't solve the problem if you don't have hotplug installed (I don't).
pcmcia-cs docs say that, in /etc/default/pcmcia, REFRAIN_FROM_IFUP can't be
"yes". I commented it out, but cardmgr still didn't ifup eth0.
I browsed /etc/pcmcia/network and found out these suspicious lines in
/etc/pcmcia/network.opts:
start_fn () { return; }
stop_fn () { return; }
changed them to:
start_fn () { ifup $1; }
stop_fn () { ifdown $1; }
and now cardmgr behaves as it used to do (not sure when it changed).
It might be a bug in the documentation: it doesn't say that cardmgr won't be
starting the interface anymore. Or it might be a bug in this script. Whichever
way, I think it's a bug, since the documentation doesn't match the behaviour.
Paulo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
