[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

PCMCIA problems upgrading slink -> potato

The following happened to both me and a friend.  I don't know if it
still occurs, but it can be very nasty.

When doing an apt-get update; apt-get dist-upgrade from a slink laptop
to potato, where the slink machine was running a 2.0.36 kernel, apt
decided that the potato modutils (?) conflicted with the slink
pcmcia-modules-2.0.36 (although it may have been something else; I'm
not quite sure).  Whichever, I accidentally went ahead with the
upgrade, and sure enough, I lost contact with all of my PCMCIA devices
and hence with the outside world.  No problem, though, as I'll just
recompile my kernel and reinstall the modules, forcing things if
necessary.  But -- horror! -- the 2.0.36 kernel wouldn't compile with
the potato gcc (too new, needed some sort of patch).  And I was
stuck.  Thankfully, I had a 2.2.1 kernel source package on my slink
CD, so I was able to bootstrap my machine back until I could download
a more stable 2.2.x kernel.

But I think that apt offering to remove a pcmcia-modules-* package in
favour of something else is potentially quite nasty.

I'm not sure what to suggest to do about it, though.



  Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
        Debian GNU/Linux Developer,  see http://www.debian.org/~jdg
  Donate free food to the world's hungry: see http://www.thehungersite.com/

To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: