All,
I am having some issues getting the PCMIA serivce to start. I am new with all Linux systems so please forgive me if I don't provide some needed info.
During the install Fedora found the PCMIA NIC so I assume that something went right; however each boot (when looking at the detailed logging screen) shows that the NIC Card is not found and initalization fails. So once in the GUI I look at the services and everything looks good but PCMIA which shows the service is stopped. I request a service start Fedora the OS reports the service has started correctly, but when I stat the service it still hasn't started, thus the NIC card cannot be found.
System: IBM Thinkpad A20m Intel PIII TI PCMIA Cardbus 3c589 PCMIA NIC
Thanks!
Chris Canavan
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
On Fri, 16 Jul 2004, Chris Canavan wrote:
All,
I am having some issues getting the PCMIA serivce to start. I am new with all Linux systems so please forgive me if I don't provide some needed info.
During the install Fedora found the PCMIA NIC so I assume that something went right; however each boot (when looking at the detailed logging screen) shows that the NIC Card is not found and initalization fails. So once in the GUI I look at the services and everything looks good but PCMIA which shows the service is stopped. I request a service start Fedora the OS reports the service has started correctly, but when I stat the service it still hasn't started, thus the NIC card cannot be found.
if this is the same problem others have been having, try the following after you boot:
# modprobe yenta_socket # service pcmcia start
what happens?
rday
That did the trick. Is there a way to implement this fix permanently through the startup routine.
Thanks for all your assistance
Regards, Chris Canavan
--- "Robert P. J. Day" rpjday@mindspring.com wrote:
On Fri, 16 Jul 2004, Chris Canavan wrote:
All,
I am having some issues getting the PCMIA serivce
to start. I am
new with all Linux systems so please forgive me if
I don't provide
some needed info.
During the install Fedora found the PCMIA NIC so I
assume that
something went right; however each boot (when
looking at the
detailed logging screen) shows that the NIC Card
is not found and
initalization fails. So once in the GUI I look at
the services and
everything looks good but PCMIA which shows the
service is stopped.
I request a service start Fedora the OS reports
the service has
started correctly, but when I stat the service it
still hasn't
started, thus the NIC card cannot be found.
if this is the same problem others have been having, try the following after you boot:
# modprobe yenta_socket # service pcmcia start
what happens?
rday
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
Chris Canavan wrote:
That did the trick. Is there a way to implement this fix permanently through the startup routine.
This has been a thorn in the side for a long time--especially with pcmcia-based network cards. The problem is that the network is started long before pcmcia is (the /etc/rc.d/rcx.d sequence number for network is S10, that for PCMCIA is S24).
The easiest fix is to:
cd /etc/rc.d/rc(your-run-level).d mv S24pcmcia S09pcmcia
so pcmcia starts before the network. The network scripts are supposed to work around this issue, but they don't reliably.
Thanks for all your assistance
Regards, Chris Canavan
--- "Robert P. J. Day" rpjday@mindspring.com wrote:
On Fri, 16 Jul 2004, Chris Canavan wrote:
All,
I am having some issues getting the PCMIA serivce
to start. I am
new with all Linux systems so please forgive me if
I don't provide
some needed info.
During the install Fedora found the PCMIA NIC so I
assume that
something went right; however each boot (when
looking at the
detailed logging screen) shows that the NIC Card
is not found and
initalization fails. So once in the GUI I look at
the services and
everything looks good but PCMIA which shows the
service is stopped.
I request a service start Fedora the OS reports
the service has
started correctly, but when I stat the service it
still hasn't
started, thus the NIC card cannot be found.
if this is the same problem others have been having, try the following after you boot:
# modprobe yenta_socket # service pcmcia start
what happens?
rday
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
On Fri, Jul 16, 2004 at 04:20:57PM -0700, Rick Stevens wrote:
Chris Canavan wrote:
That did the trick. Is there a way to implement this fix permanently through the startup routine.
This has been a thorn in the side for a long time--especially with pcmcia-based network cards. The problem is that the network is started long before pcmcia is (the /etc/rc.d/rcx.d sequence number for network is S10, that for PCMCIA is S24).
The easiest fix is to:
cd /etc/rc.d/rc(your-run-level).d mv S24pcmcia S09pcmcia
so pcmcia starts before the network. The network scripts are supposed to work around this issue, but they don't reliably.
Even easier, and more correct IMHO, is to NOT set "start on boot" option of the PCMCIA network card interface setup.
The network interface will start when PCMCIA starts or when you plug-in your PCMCIA network card.
Norman Gaywood wrote:
On Fri, Jul 16, 2004 at 04:20:57PM -0700, Rick Stevens wrote:
Chris Canavan wrote:
That did the trick. Is there a way to implement this fix permanently through the startup routine.
This has been a thorn in the side for a long time--especially with pcmcia-based network cards. The problem is that the network is started long before pcmcia is (the /etc/rc.d/rcx.d sequence number for network is S10, that for PCMCIA is S24).
The easiest fix is to:
cd /etc/rc.d/rc(your-run-level).d mv S24pcmcia S09pcmcia
so pcmcia starts before the network. The network scripts are supposed to work around this issue, but they don't reliably.
Even easier, and more correct IMHO, is to NOT set "start on boot" option of the PCMCIA network card interface setup.
You then have to start the network manually every time--either via an "ifup eth0" or a "service network start". That's a pain if this is your primary machine and that's your sole NIC.
The network interface will start when PCMCIA starts or when you plug-in your PCMCIA network card.
The NIC doesn't always start when pcmcia starts or I wouldn't have made my suggestion about changing the start sequence. It's SUPPOSED to, but in many instances it doesn't. This may be a glitch in the pcmcia handling code or the /etc/pcmcia.d setup stuff, but it's not always reliable. My "cheap and dirty fix" works every time.
"If it's stupid and it works...it ain't stupid." -- Regimental Sergeant Major Henry G. Kester, "Warbots" ---------------------------------------------------------------------- - Rick Stevens, Senior Systems Engineer rstevens@vitalstream.com - - VitalStream, Inc. http://www.vitalstream.com - - - - Consciousness: that annoying time between naps. - ----------------------------------------------------------------------
On Fri, 2004-07-16 at 19:33, Norman Gaywood wrote:
The easiest fix is to:
cd /etc/rc.d/rc(your-run-level).d mv S24pcmcia S09pcmcia
so pcmcia starts before the network. The network scripts are supposed to work around this issue, but they don't reliably.
Even easier, and more correct IMHO, is to NOT set "start on boot" option of the PCMCIA network card interface setup.
The network interface will start when PCMCIA starts or when you plug-in your PCMCIA network card.
While this works it always seemed to me that this was still a poor work around for this problem. It does not make a lot of sense that when you set "do not start on boot" in the network dialog that the card will subsequently startup. And if you do set start on boot it will NOT start up.
What if you really don't want that card to start up? Or on the off chance that you have two pcmcia cards (probably nobody has that) and you want just one or the other to start up? With the current solution this would be impossible.
I need to check bugzilla to see if this is still an open issue or if there is even a request for change to this.