> I am curious too. If you get any idea, please post. I will :)
> PCMCIA is hardware initialization. So it fits nicely to rcS.d. Yes, but as I said, I can't reload the PCMCIA subsystem - I have to reboot system. > Script in PCMCIA package uses runlevel to switch behavor. So it should > be run by rcn.d (n=1..6). > > ???? > > My system boots OK. > > I had to disable ipmasq and dhclient in rcn.d and run from inside > PCMCIA. I will check that. > I give long wait after PCMCIA to run bind and others to run after > complete PCMCIA initialization. > > PCMCIA initialization un in back ground so some other initialization > started after PCMCIA can run in race condition, I think. > > I had that problem with other notebook. That could be - I will give it a try. It takes some time, until PCMCIA-loading is finished on my Xircom combo-card (10MBit LAN+33.6 kBit Modem) Thank you very much, Mike > On Wed, Dec 12, 2001 at 12:31:20PM +0100, Michael Forstner wrote: > > I've installed Woody (binary-CDs 25-NOV-2001) base system. > > Every time, when the system boots, PCMCIA crashes with a kernel > panic (and > > much output). > > > > I booted the system with parameter init="/bin/sh" and changed > the symbolic > > link in /etc/rc2.d: > > > > rm /etc/rc2.d/S13pcmcia > > cd /etc/rcS.d > > ln -s ../init.d/pcmcia ./S15pcmcia > > > > Now the pcmcia package starts after filesystem check and works > fine - why? > > > > It's annoying, because if I switch to runlevel 1 (and shut down > pcmcia) and > > back to 2 (and restart pcmcia) the system will crash again. > > > > Thank you for any ansers. > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > > > > >
