Bug 36991 - can't start PCMCIA service -- invalid parameter param_do_scan
can't start PCMCIA service -- invalid parameter param_do_scan
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-04-21 12:05 EDT by Need Real Name
Modified: 2008-08-01 12:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-02 10:55:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/etc/sysconfig/pcmcia file (112 bytes, text/plain)
2001-05-01 08:35 EDT, Need Real Name
no flags Details
/etc/sysconfig/pcmcia.rpmnew file (63 bytes, text/plain)
2001-05-01 08:37 EDT, Need Real Name
no flags Details
/etc/sysconfig/hwconf file (2.27 KB, text/plain)
2001-05-16 14:56 EDT, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2001-04-21 12:05:50 EDT
After an upgrade from RH7 to RH7.1 (on a Dell Inspiron 3200), I was unable
to start the pcmcia service.  This is the error message I got:
"starting PCMCIA services:  modules
/lib/modules/2.4.2-4/pcmcia/yenta_socket.o: invalid parameter parm_do_scan
/lib/modules/2.4.2-2/pcmcia/ds.o: init_module: Operation not permitted
Hint : insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters"

I can fixed this by commenting out or removing this line from

I did not add this line to the /etc/sysconfig/pcmcia file:  either it was
left over from the previous RH7 install or it was added during the upgrade
to 7.1.
Comment 1 Brent Fox 2001-04-27 17:29:21 EDT
Well, it's important for us to know whether the file was already like that or if
the 7.1 installer did that.  But that's kind of hard to reproduce now...
Do you see a file called /etc/syconfig/pcmcia.rpmsave?
Comment 2 Need Real Name 2001-04-28 10:27:14 EDT
No, I do not have a pcmcia.rpmsave file in /etc/sysconfig/.

I do have a /etc/sysconfig/pcmcia.rpmnew file, but the modification time (Mar
11,pre-7.1) indicates that it's left over from a previous update.
Comment 3 Brent Fox 2001-04-30 12:23:14 EDT
When you say "pre-7.1"...do you mean one of the beta releases for 7.1?  I hope
you weren't trying to upgrade from a beta to the final release...   :)
Comment 4 Need Real Name 2001-04-30 13:40:58 EDT
No.  I upgraded from the regular RH7 release.  I have never installed a RH beta
on this machine.  

I suppose it's possible that an update/errata package for RH7 might have witten
this file, but looking over the list of updates/errata for RH7
(http://www.redhat.com/support/errata/rh7-errata.html), I don't see any likely
Comment 5 Brent Fox 2001-04-30 17:35:30 EDT
Ok...can you attach the pcmcia.rpmnew and pcmcia files?  Just curious.
Comment 6 Need Real Name 2001-05-01 08:35:30 EDT
Created attachment 16967 [details]
/etc/sysconfig/pcmcia file
Comment 7 Need Real Name 2001-05-01 08:37:00 EDT
Created attachment 16968 [details]
/etc/sysconfig/pcmcia.rpmnew file
Comment 8 Brent Fox 2001-05-01 12:15:37 EDT
Brock, do we have any of these machines in house?
Comment 9 Brent Fox 2001-05-15 14:36:08 EDT
We don't have a machine like this in our test lab.  Can you attach your
/etc/sysconfig/hwconf file?
Comment 10 Need Real Name 2001-05-16 14:56:38 EDT
Created attachment 18650 [details]
/etc/sysconfig/hwconf file
Comment 11 Matt Wilson 2001-07-02 10:58:09 EDT
This option must have been added by hand.  Since this option was added by hand
it's up to the user to make adjustments in this config file as options to kernel
pcmcia modules change.

Note You need to log in before you can comment on or make changes to this bug.