Bug 985 – pcmcia-cs-3.1.31-r3.ebuild breaks a working pcmcia-cs environment

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Avi Schwartz 2002-03-06 11:59:03 UTC]

I have the following problems with the new pcmcia-cs package:

1) Default settings that used to be in /etc/init.d/pcmcia (PCIC) are no longer
set in /etc/pcmcia.conf.

2) /etc/init.d/pcmcia used to insmod the required modules (pcmcia_core, ds). 
This does not happen anymore causing the following error to be displayed:

 * You need to load the pcmcia modules () and ds)
 * in order for cardmgr to start.

[Comment 1 Daniel Robbins (RETIRED) 2002-03-06 12:12:23 UTC]

I didn't touch these things in -r3.  I'm guessing they were changed in -r2 or
earlier?  It's really hard for me to work with this package as I don't have a
laptop.

[Comment 2 Avi Schwartz 2002-03-06 12:28:44 UTC]

Something very strange is going on here.  When I look at the original 
/etc/init.d/pcmcia file on my system, I can see it is not a standard gentoo 
script but rather the original file that ships with the PCMCIA-CS 
distribution.  Is it possible that the gentoo script went in by mistake?

Here are the first few lines of the pcmcia script that works properly.  You 
can see it is not a gentoo startup script:

#!/bin/sh

# rc.pcmcia 1.39 2001/10/04 12:30:05 (David Hinds)
#
# This is designed to work in BSD as well as SysV init setups.  See
# the HOWTO for customization instructions.

# Tags for Red Hat init configuration tools
#
# chkconfig: 2345 45 96
# processname: cardmgr
# pidfile: /var/run/cardmgr.pid
# config: /etc/pcmcia/config
# config: /etc/pcmcia/config.opts
# description: PCMCIA support is usually to support things like ethernet \
#              and modems in laptops.  It won't get started unless \
#              configured so it is safe to have it installed on machines \
#              that don't need it.

[Comment 3 Karl Trygve Kalleberg (RETIRED) 2002-03-08 18:07:48 UTC]

chadh submitted a new gentoo-specific script, but it breaks a bit. I'll get to
the bottom of this during the weekend. 

[Comment 4 Chad Huneycutt (RETIRED) 2002-03-09 13:28:26 UTC]

Yep.  I am the culprit.  After speaking with drobbins, we decided to remove the
module loading from the init script.  I also moved the environment variables to
/etc/conf.d/pcmcia, which is more appropriate, IMO.

A definite bug is that I didn't know how to determine if pcmcia_core,
yenta_socket/i82365, and ds were compiled into the kernel.  I can tell if the
modules are loaded, but not if they are compiled in.

[Comment 5 Chad Huneycutt (RETIRED) 2002-03-15 17:26:33 UTC]

pcmcia-cs-3.1.31-r4 is now available and should address all these issues.

[Comment 6 Chad Huneycutt (RETIRED) 2002-03-15 17:28:32 UTC]

*** Bug 1076 has been marked as a duplicate of this bug. ***