Peter T. Breuer wrote: > It doesn't seem to stop the kernel threads. Right.
> Of course this is far too dangerous to actually DO worldwide. But you > may want to at least try and get the kernel threads stopped somehow on > demand by registering a bug against something. Why don't you file it yourself? > The problem is that without udev, apparently the whole pcmcia system > needs to be loaded "for a first time" in order to detect the pcmcia cards > and get to the point where an ident shows something. Otherwise one > just can go blue in the face with eject and insert with nothing ever > showing up, and no reason for it not showing up ever appearing. There is a program, /lib/udev/pcmcia-socket-startup, which needs to be run for certain PCMCIA sockets (in case of 16-bit cards). Also, it could be a bug in your kernel. You should try a later kernel version, at least 2.6.18. Anything below is simply not supported by Debian (2.6.18 is the kernel in stable). > And if anyone could explain to me how pcmcia is supposed to work > nowadays, that would be great! I found a PCMCIA HOWTO for 2.6 kernels > on the net, and it is a start in the right direction. Certainly it > gives me a few ideas. It's mostly documented here: http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html Maybe that's where you found the HOWTO. PCMCIA on 2.6 kernels is mostly supposed to work through udev. First, the bridge module is loaded (probably by udev). Then, udev gets events from the kernel for card insertions, and loads the correct modules by comparing the card ID with pcmcia:* aliases exported by the modules. It also runs pcmcia-socket-startup and pcmcia-check-broken-cis (and some other things), as you can see from looking at /etc/udev/pcmcia.rules. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
