Mailinglist Archive: opensuse (4053 mails)

[<dog@xxxxxxxxx>]

i have run into this before.  it happens because the network services are
started before the pcmcia services are started.  just go into
/etc/init.d/rc#.d and change the order of your network and pcmcia scripts
by renumbering them (change S05network to something like S75network)
of course if you are running services like apache or named or something
that might cause a problem.  or you could just do

echo "dhcpcd eth1" /etc/init.d/pcmcia-start
chmod 755 /etc/init.d/pcmcia-start
ln -s /etc/init.d/pcmcia-start /etc/init.d/rc3.d/S90pcmcia-start

On Mon, 27 Aug 2001, Anthony Moulen wrote:

>Hello,
>
>I have a PCMCIA Wireless Card that works just fine under SuSE 7.2 and runs
>on my home wireless hub.  However, the problem comes in that there are two
>network devices in my laptop.  A built in eth0 intel card, and the PCMCIA
>wavelan compatible (PrismII) card.  I have tried to get SuSE to
>automatically configure the PCMCIA card on boot but it doesn't work.
>Right now what I do is after I log in, I 'su' to and type dhcpcd eth1.
>This is getting old really fast.  I didn't have this problem with Mandrake
>8.0 (but I had a host of other problems so that isn't an option).  When I
>try to configure the card through the SuSE tools, the card keeps losing
>its information.  It seems the tools have an issue with PCMCIA network
>cards.
>
>Anyone have any ideas before I start manually tearing apart script to
>shoehorn this puppy into a working state?
>
>Thanks,
>Anthony.
>
>
>--
>To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
>For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
>Also check the FAQ at http://www.suse.com/support/faq and the
>archives at http://lists.suse.com
>

Chad Whitten
Network/Systems Administrator
Nexband Communications
chadwick@xxxxxxxxxxx