Re: PCMCIA modules - custom kernel - unresolved symbols

To: debian-laptop@lists.debian.org
Subject: Re: PCMCIA modules - custom kernel - unresolved symbols
From: David Reviejo <dreviejo@terra.es>
Date: Mon, 18 Sep 2000 21:29:34 +0200
Message-id: <[🔎] 20000918212934.A24694@pandora>
Mail-followup-to: debian-laptop@lists.debian.org
In-reply-to: <[🔎] Pine.GS4.4.21.0009181421580.18438-100000@jeeves.stud.ntnu.no>; from osstein@stud.ntnu.no on lun, sep 18, 2000 at 02:35:49 +0200
References: <[🔎] Pine.GS4.4.21.0009181421580.18438-100000@jeeves.stud.ntnu.no>

* Ole Sebastian Stein <osstein@stud.ntnu.no> [000918 19:48]:
> I get unresolved symbols in these modules:
> 
> epic_cb.o and parport_cs.o
> 
> in /lib/modules/2.2.17/pcmcia/

If you are using the original potato pcmcia packages (3.1.8?), this a
known problem.

AFAIK, you have no problem if you don't need the epic or parport
modules. Anyway, you may want to upgrade to the 3.1.20 packages
(pcmcia-cs and pcmcia-source) in /dists/proposed-updates at your
favorite debian mirror.

HTH,
-- 
David

Reply to:

References:
- PCMCIA modules - custom kernel - unresolved symbols
  - From: Ole Sebastian Stein <osstein@stud.ntnu.no>

Prev by Date: Re: Good window manager for laptop
Next by Date: pcmcia-card with 2 interfaces
Previous by thread: PCMCIA modules - custom kernel - unresolved symbols
Next by thread: Re: PCMCIA modules - custom kernel - unresolved symbols
Index(es):
- Date
- Thread