init.d/pcmcia blocks on Dell Precision 340

Bug #7340 reported by Matt Zimmerman
16
Affects Status Importance Assigned to Milestone
pcmcia-cs (Ubuntu)
Fix Released
Low
Colin Watson

Bug Description

One of my sounders ran into an issue where the first reboot blocked while the
pcmcia init script was running:

(15:17:23) Joe: Starting PCMCIA Services: Linux Kernel Card Services
(15:17:35) Joe: options [pci] [cardbus] [pm]
(15:17:41) mdz: and then what? it crashed?
(15:17:47) Joe: just hangs

After rebooting into single-user mode and disabling that init script, the system
came up OK.

Revision history for this message
Matt Zimmerman (mdz) wrote :

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

Revision history for this message
Matt Zimmerman (mdz) wrote :

Colin, if you want to argue for dynamically removing pcmcia-cs after install if
it's not needed, this is the place to do it. :-)

Revision history for this message
Colin Watson (cjwatson) wrote :

Hoorah. There's no need to dynamically remove it after install, though; all we
need to do is move it from BaseSeed to ShipSeed, and ddetect will dynamically
install it if it's needed. The code's all there; Debian does it this way.

I feel that an exception from the general policy of "install all hardware
support so that users have it if they upgrade" is justified here, since
upgrading a computer to have PCMCIA support when it previously didn't is
extremely rare.

Revision history for this message
Colin Watson (cjwatson) wrote :

I've done installs on both a desktop and a laptop with pcmcia-cs removed from
/usr/lib/debootstrap/scripts/warty. The desktop correctly didn't install
pcmcia-cs, while the laptop correctly did install it.

Is this enough to push pcmcia-cs out to ShipSeed?

Revision history for this message
Matt Zimmerman (mdz) wrote :

The machine in question is now running Debian unstable, and I am unable to
reproduce the problem with the Debian 2.4.16-1-686 kernel and pcmcia-cs 3.2.5-8.
It fails in a perfectly normal way with those versions.

liquorice:~# /etc/init.d/pcmcia start
Starting PCMCIA services:
/lib/modules/2.4.26-1-686/kernel/drivers/pcmcia/i82365.o: init_module: No such
device
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.26-1-686/kernel/drivers/pcmcia/i82365.o: insmod
/lib/modules/2.4.26-1-686/kernel/drivers/pcmcia/i82365.o failed
/lib/modules/2.4.26-1-686/kernel/drivers/pcmcia/i82365.o: insmod i82365 failed
Error: Failed to load i82365

Revision history for this message
Matt Zimmerman (mdz) wrote :

As discussed, I think we should test out moving pcmcia-cs to ShipSeed, and if
there are no issues, we'll do that and downgrade this bug

Revision history for this message
Matt Zimmerman (mdz) wrote :

pcmcia-cs moved to ShipSeed; downgrading

Revision history for this message
Matt Zimmerman (mdz) wrote :

This bug should be addressed by LaMont's changes to prevent pcmcia-cs from
starting up if no PCMCIA controller is detected

pcmcia-cs (3.2.5-8ubuntu4) hoary; urgency=low

  * Only start/stop if PCMCIA is present on the machine.

 -- LaMont Jones <email address hidden> Fri, 28 Jan 2005 07:32:56 -0700

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.