[wplug] Modify SuSE modules

[Robert Coutch]

Just to see what happens..........

If the system runs a desktop, fire up Yast2 and see what it shows
for network cards installed and configured.

Add your card in if it's not there and see if that helps/hurts the situation.

Yast2 will handle ALL the config files but I don't know what will happen
if you compiled a device into the kernel that it normally loads a module for.

I thought only old-timers and people woking under size constraints made 
kernels with drivers compiled in. ( hehe)


-Bob


On Wednesday 07 January 2004 10:00 am, Wise, Jeremey wrote:
> The issue was that I tried to compile a custom kernel and did the 'make
> install' which removed the e100 module reference in /etc/modules.conf
> because I compiled it into the kernel. The kernel had too much stripped out
> so I canned it. Problem was when I rebooted to the old one no network. If I
> did a 'modprobe e100' then ran /etc/rc.d/network start' the network came up
> fine. I added 'eth0 e100' back into modules.conf thinking this would allow
> all to work again but network still fails at boot. I am still getting use
> to the "SuSE way of doing things" and so figured their was another approach
> to getting startup dependencies fixed.
>
> Thx.
>
> Jeremey Wise (440)-519-6006
> Systems Consultant(CNE,MCSE,CSE)
> Agilysys, Inc.
> Jeremey.Wise at Agilysys.com
>
> IBM ED PACK -Part # SB033 $4,500 ... SP Discount 11%
> IBM ED CARD - Part # SB218 $8,995 ... SP Discount 8.5%
>
> -----Original Message-----
> From: wplug-admin at wplug.org [mailto:wplug-admin at wplug.org] On Behalf Of
> Robert Coutch
> Sent: Tuesday, January 06, 2004 10:22 PM
> To: wplug at wplug.org
> Subject: Re: [wplug] Modify SuSE modules
>
> The SuSE way is just like the RedHat way but maybe we could get a better
> idea
> of what you mean, describe the situation.
>
> What module are you loading for what reason?
>
> SuSE used to use the rc.local method similar to BSD but has since changed
> to the System V type /etc/rc.d/ type init scripts.
>
> Yast2 will add/modify entries in modules.conf for you so you will see
> warning
> statements in the file where you should not make changes.
>
> Let us know what you are trying to do.
>
>
> Thanks,
>
> Bob
>
> On Tuesday 06 January 2004 05:17 pm, Brian Sammon wrote:
> > > Without going into great detail I need to understand 'the SuSE way' of
> > > re-enabling a module. In my past RedHat days I would simply vi
> > > /etc/modules.conf and all was well. That does not appear to be the way
>
> to
>
> > > get the module to initialize at boot now. What am I missing.
> >
> > Do you want the module to load at boot or do you want it to load only
> > when needed.  I don't know "the SuSE way", but based on my experience
> > with
>
> other
>
> > distributions, I'm pretty sure that /etc/modules.conf is only for
>
> on-demand
>
> > module loading by kerneld or kmod.  /etc/modules.conf generally works
> > that way regardless of the distribution.
> > If you want a module to always load on boot, regardless of whether it is
> > needed, then most of the distributions have a way of doing that.  It's
> > usually a file like /etc/<something>/init.d/module<something>
> >
> >
> > _______________________________________________
> > wplug mailing list
> > wplug at wplug.org
> > http://www.wplug.org/mailman/listinfo/wplug
>
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug
>
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug