[GLLUG] Debian 2.4 Bootup Issues

[Brian Hoort]

Ah! Is *that* what all those silly numbers are in front of those things. I 
really need to read a description of the rc folders if I can find one. 
Seems kind of a silly way to do it... do I risk blowing up my system doing 
a move like that? There must be some reason that the distribution 
maintainers chose to order them as they are... or it doesn't work for 
anyone out there with a PCMCIA network card... that's hard to believe they 
would make that choice without good reason.

Thanks!

At 01:58 PM 10/28/2002, you wrote:
>I had the same issue with mandrake 9.0 on my Gateway
>laptop.  Network would load before the pcmcia card did.
>I fixed it by changing the load order of the pcmcia to
>before the network.  I am at work and not in front of my
>linux box at the moment so I can't tell you the exact
>folders but I think they are /etc/rc.d, /etc/rc1.d and
>the like.  I went through each directory and renamed the
>pcmcia driver that was something like S90pcmcia and did
>a mv S90pcmcia to S87pcmcia (whatever number is just
>before your network).  For instance if your network is
>S89network and pcmcia is S90pcmcia you would do a mv
>S90pcmcia S88pcmcia.  This worked for me, although
>someone else might have a better solution.
> > When booting my laptop into a 2.2.18 kernel, I have to:
> > # /etc/init.d/networking stop && /etc/init.d/networking start
> > because, presumably, the networking tries to initialize before PCMCIA does.
> > Over the weekend I downloaded a 2.4.19 kernel-image and it's
> > kernel-pcmcia-modules. After hours of playing, I have figured out that I
> > have to:
> > # modprobe i823xxx (to load the pcmcia driver)
> > # /etc/init.d/pcmcia stop && /etc/init.d/pcmcia start
> > # /etc/init.d/networking stop && /etc/init.d/networking start
> >
> > So I have a few questions for you Debian wizards:
> > 1. Why isn't the i823xxx.o module for the pcmcia loading at boot?
> > 2. Why is the networking being initialized before pcmcia?
> > 3. How do I fix this, the right way?
> >
> > Extra Question 4:
> > On a completely different note, I did a lot of reading up on modules over
> > the weekend in trying to fix this problem and learned that Debian is
> > configured to depmod -a on every boot. While booting I can see this occur,
> > and it takes a long time. Isn't this overkill? You should only have to do
> > that after loading new modules, which presumably, most people don't do 
> very
> > often after getting their PCs setup right. Shoot, if I get this working 
> I'm
> > not liable to do that for a LONG time. :) Couldn't we all save a lot of
> > time booting by turning this off?
> >
> > Thanks
> >
> >
> >
> > --
> > Brian Hoort
> >
> > _______________________________________________
> > linux-user mailing list
> > linux-user@egr.msu.edu
> > http://www.egr.msu.edu/mailman/listinfo/linux-user
>_______________________________________________
>linux-user mailing list
>linux-user@egr.msu.edu
>http://www.egr.msu.edu/mailman/listinfo/linux-user