Problem: FC2, Dell Latitude CSx, Linksys PCM100 EtherFast 10/100 Integrated PC Card

[Scot L. Harris]

On Sat, 2004-11-27 at 22:36, Mike Detwiler wrote:
> Hello,
> 
> I just upgraded my notebook from RH 7.2 to FC2 (kernel 
> 2.6.5-1.358). My Linksys PCM100 card worked fine with RH 
> 7.2, but when I boot to FC2 I get the following message:
> 
> pcnet_cs device eth0 does not seem to be present, delaying 
> initialization
> 
> I searched the list archives and found that others had 
> similar problems, but none of the posted solutions seemed 
> to apply to my situation. I'm not sure if all of the 
> information listed below is relevant, but I'll list it in 
> case it helps. Thanks in advance to anyone who takes the 
> time to help me out.
> 
> - The FC2 installation process appeared to recognize the 
> card in that I was prompted for setup information and eth0 
> was configured. system-config-network shows the following 
> information on the hardware tab:
> 
> Description: pcnet_cs
> Type: Ethernet
> Device: eth0
> Status: configured
> 
> - system-config-services shows a check next to pcmcia, but 
> the status reads "cardmgr is stopped."
> 
> - entering "cardmgr -v" at the command line returns:
> 
> carmgr[4762]: no sockets found!
> 
> - hwbrowser shows the following information for 
> PCMCIA/PC-Card devices:
> 
> Selected Device: PCI1225
> Manufacturer: Texas Instruments
> Driver: yenta_socket
> 
> (note: the PCI1225 entry appears twice in the Selected 
> Device box; both entries have the Device Information 
> listed above.)
> 
> - the following entry exists in /etc/pcmcia/config:
> 
> card "Linksys Etherfast 10/100 Fast Ethernet"
>    version "Linksys", "Etherfast 10/100 Integrated PC Card 
> (PCM100)"
>    #manfid 0x0149, 0xc1ab
>    bind "pcnet_cs"

I've been running FC2 on a Dell Latitude CPx laptop for some time now.
I don't have the linksys card, I use a xircom and a D-Link DWL-G650
card.

Can you get the interface started by using the command:

ifup eth0

If that works then the problem most likely is that you told the system
to start the interface at boot time.  Turn that off.  This problem is
known and needs to be fixed.  What happens is the network service starts
before the pcmcia service.  Since the card is a pcmcia device it can not
start when the network service starts.  However, if you tell it NOT to
start at boot network services starts and then when pcmcia services
start the network card will magically start up.  

The other possibility is that there were some people that had a problem
with the yenta_socket stuff.  I don't remember the solution but there
was a fix.  Check the archives for the specifics on that problem.


-- 
Scot L. Harris
webid at cfl.rr.com

Schshschshchsch.
		-- The Gorn, "Arena", stardate 3046.2