8:34 p.m.
I almost said "cart before the horse"
I remember some discussion about this, but it's been eons and I don't
recall the solution, if there was one.
In the process of booting, Fedora tries to connect to the network before
initializing pcmcia. Since I have a pc card NIC, this doesn't work very
well. The NIC does ultimately get an IP and I'm on the network without
any intervention on my part, it's just the long pause and the error as
it times out during the boot sequence.
Is there any way I can rearrange thing where pcmcia starts first, then
the network, or can I hard code something that will at least shorten the
timeout and / or eliminate the error message ??
Any tips or pointers to docs would be much helpful.
Thanks
Joebewan
8:58 p.m.
On Thu, 2004-08-05 at 02:34, Price Technology wrote:
I almost said "cart before the horse"
I remember some discussion about this, but it's been eons and I don't
recall the solution, if there was one.
In the process of booting, Fedora tries to connect to the network before
initializing pcmcia. Since I have a pc card NIC, this doesn't work very
well. The NIC does ultimately get an IP and I'm on the network without
any intervention on my part, it's just the long pause and the error as
it times out during the boot sequence.
Is there any way I can rearrange thing where pcmcia starts first, then
the network, or can I hard code something that will at least shorten the
timeout and / or eliminate the error message ??
I'm using a fresh install of FC2 with all updates installed, so if
you're not YMMV, but the solution when I first came across this problem
was in the Network settings tool to set all PCMCIA NICs including
Wireless ones to *not* start on boot (because the PCMCIA scripts
automatically start any NICs which are PCMCIA cards anyway). I have no
long pauses, and no error messages on boot. That way, I believe, the
part in the boot sequence when it says "bringing up network interfaces"
just brings up the loopback interface.
As I understood the discussion when I first asked about this on this
list, there is no obvious "fix" for this (I use scare quotes because it
is debatable whether there is any problem needing a fix). If you try to
start PCMCIA before the network services, the PCMCIA service will try to
start you NIC card, but the network stuff hasn't been started and so
that fails. If you tell the network services to start your NIC that
fails because the PCMCIA service hasn't been started yet. It makes sense
I think, although I have never understood how come it worked in RHL9
when I had it set for the network service to start my PCMCIA Wi-Fi card
on boot -- if the card was present the network service would wait
silently in the background without error until the PCMCIA service
started. (I can't remember now what it used to do if the card wasn't
present, but it certainly wasn't anything that annoyed me like causing a
massive pause or generating scary sounding warnings.)
Best, Darren
--
=====================================================================
D. D. Brierton darren(a)dzr-web.com www.dzr-web.com
Trying is the first step towards failure (Homer Simpson)
=====================================================================
8:59 p.m.
On Wed, 2004-08-04 at 21:34, Price Technology wrote:
I almost said "cart before the horse"
I remember some discussion about this, but it's been eons and I don't
recall the solution, if there was one.
In the process of booting, Fedora tries to connect to the network before
initializing pcmcia. Since I have a pc card NIC, this doesn't work very
well. The NIC does ultimately get an IP and I'm on the network without
any intervention on my part, it's just the long pause and the error as
it times out during the boot sequence.
Is there any way I can rearrange thing where pcmcia starts first, then
the network, or can I hard code something that will at least shorten the
timeout and / or eliminate the error message ??
Any tips or pointers to docs would be much helpful.
Thanks
Joebewan
In the network config set it to NOT start the card on boot. When pcmcia
is started the card will magically (and unexpectedly) get started
anyway.
:)
--
Scot L. Harris <webid(a)cfl.rr.com>
9:12 p.m.
On Wed, 2004-08-04 at 20:59, Scot L. Harris wrote:
On Wed, 2004-08-04 at 21:34, Price Technology wrote:
> I almost said "cart before the horse"
>
> I remember some discussion about this, but it's been eons and I don't
> recall the solution, if there was one.
>
> In the process of booting, Fedora tries to connect to the network before
> initializing pcmcia. Since I have a pc card NIC, this doesn't work very
> well. The NIC does ultimately get an IP and I'm on the network without
> any intervention on my part, it's just the long pause and the error as
> it times out during the boot sequence.
>
> Is there any way I can rearrange thing where pcmcia starts first, then
> the network, or can I hard code something that will at least shorten the
> timeout and / or eliminate the error message ??
>
> Any tips or pointers to docs would be much helpful.
>
> Thanks
>
> Joebewan
In the network config set it to NOT start the card on boot. When pcmcia
is started the card will magically (and unexpectedly) get started
anyway.
I like magic. I'll give that a try. Thanks
Joebewan
9:34 p.m.
On Thu, 2004-08-05 at 10:12, Price Technology wrote:
On Wed, 2004-08-04 at 20:59, Scot L. Harris wrote:
> On Wed, 2004-08-04 at 21:34, Price Technology wrote:
> > Is there any way I can rearrange thing where pcmcia starts first, then
> > the network, or can I hard code something that will at least shorten the
> > timeout and / or eliminate the error message ??
Set the /etc/init.d/rc.X/Sxxpcmcia to start before the network.
--
Ow Mun Heng
Fedora GNU/Linux Core 2 on D600 1.4Ghz CPU kernel
2.6.7-2.jul1-interactive
Neuromancer 07:51:51 up 1:58, 5 users, load average: 3.20, 3.03, 2.46
7:08 a.m.
Ow Mun Heng wrote:
On Thu, 2004-08-05 at 10:12, Price Technology wrote:
>On Wed, 2004-08-04 at 20:59, Scot L. Harris wrote:
>
>
>>On Wed, 2004-08-04 at 21:34, Price Technology wrote:
>>
>>
>
>
>
>>>Is there any way I can rearrange thing where pcmcia starts first, then
>>>the network, or can I hard code something that will at least shorten the
>>>timeout and / or eliminate the error message ??
>>>
>>>
Set the /etc/init.d/rc.X/Sxxpcmcia to start before the network.
Better yet, just configure the interface to not start at boot.
Detection of the card when pcmcia is started will cause the interface to
be brought up.
--
-----------------------------------------------------------
"Spend less! Do more! Go Open Source..." -- Dirigo.net
Chris Johnson, RHCE #807000448202021
7:38 a.m.
hi
You can go to /etc/rc*.d and change the number in the filname (*= the number
of the runlevel you use )
eg S10network make (rename) S30network the number must be higer as
SXXpcmcia and you should use a free number
armand
----- Original Message -----
From: "Christopher K. Johnson" <ckjohnson(a)gwi.net>
To: "For users of Fedora Core releases" <fedora-list(a)redhat.com>
Sent: Sunday, August 15, 2004 2:08 PM
Subject: Re: eth0 before pcmcia
Ow Mun Heng wrote:
>On Thu, 2004-08-05 at 10:12, Price Technology wrote:
>
>
>>On Wed, 2004-08-04 at 20:59, Scot L. Harris wrote:
>>
>>
>>>On Wed, 2004-08-04 at 21:34, Price Technology wrote:
>>>
>>>
>>
>>
>>
>>>>Is there any way I can rearrange thing where pcmcia starts first, then
>>>>the network, or can I hard code something that will at least shorten
the
>>>>timeout and / or eliminate the error message ??
>>>>
>>>>
>
>Set the /etc/init.d/rc.X/Sxxpcmcia to start before the network.
>
>
>
Better yet, just configure the interface to not start at boot.
Detection of the card when pcmcia is started will cause the interface to
be brought up.
--
-----------------------------------------------------------
"Spend less! Do more! Go Open Source..." -- Dirigo.net
Chris Johnson, RHCE #807000448202021
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
9:33 p.m.
On Wed, 2004-08-04 at 20:59, Scot L. Harris wrote:
In the network config set it to NOT start the card on boot. When
pcmcia
is started the card will magically (and unexpectedly) get started
anyway.
I just tried it, and the magic works like ... well, magic.
Thanks; I'll put that in my list of "tips from the mailing list"
Joebewan
7:33 a.m.
On Thu, 2004-08-05 at 07:36, Shu Hung (Koala) wrote:
I know this is a stupid question... How to do so?
If you're in GNOME:
Applicatons (Main Menu) -> System Settings -> Network
(or in a terminal run system-config-network). Select the device you wish
to configue, click the edit button on the toolbar, and in the General
tab of the dialog that pops up unselect "Activate device when computer
starts".
Best, Darren
--
=====================================================================
D. D. Brierton darren(a)dzr-web.com www.dzr-web.com
Trying is the first step towards failure (Homer Simpson)
=====================================================================
7:50 a.m.
On Thu, 2004-08-05 at 02:36, Shu Hung (Koala) wrote:
I know this is a stupid question... How to do so?
Scot L. Harris wrote:
>In the network config set it to NOT start the card on boot. When pcmcia
>is started the card will magically (and unexpectedly) get started
>anyway.
>
>:)
Not a stupid questions. It is a stupid problem! :)
Go to the main menu and select: System Settings --> Network, then edit
your interface. There will be a check box that says something like
Activate device when computer starts.
Make sure that box is NOT checked for pcmcia network cards.
<rant>
The network startup code needs to be modified to look for pcmcia cards
and set a flag if they are marked to be activated when the computer
starts. Then when the pcmcia services start and it sees a network card
it needs to check that flag and start the card if it is checked. This
would resolve this problem once and for all.
If this is not done this will continue to be a problem.
</rant>
Had to get that off my chest, again!
--
Scot L. Harris <webid(a)cfl.rr.com>
5:11 p.m.
On Thu, 2004-08-05 at 01:36, Shu Hung (Koala) wrote:
I know this is a stupid question... How to do so?
Under Gnome:
Main Menu --> System Settings --> Network.
You'll be prompted for the root password.
Under the Devices tab, select the device in question and click Edit.
Uncheck "Activate Device When Computer Starts"
Click OK
Click File --> Save then close the Network Configuration window.
Joebewan
7234
days inactive
7244
days old
11 comments
7 participants
participants (7)
-
armand -
Christopher K. Johnson -
D. D. Brierton -
Ow Mun Heng -
Price Technology -
Scot L. Harris -
Shu Hung (Koala)