[GRLUG] Hardware changes

Bob Kline bob.kline at gmail.com
Fri Jul 14 21:12:50 EDT 2006


First thing I tried.  Didn't help.

Is it the case that almost every
distribution does these  things
differently?

   -Bob


On 7/14/06, Michael Mol <mikemol at gmail.com> wrote:
> Try dropping the 3c59x module into that list.  A couple Google
> searches suggest that might help.
>
> On 7/14/06, Bob Kline <bob.kline at gmail.com> wrote:
> > A kernel presentation would be useful.
> > I've only configured the kernel once,  and
> > that was back when Caldera had a decent
> > Linux distribution - some 10 years ago.
> >
> > I'd also put in a plug for a wireless setup
> > presentation.
> >
> > Re /etc/modules,  no.  The only device
> > entry is "nvidia".  That's both before and
> > after I run the setup script Mandriva provides
> >
> >
> >   -Bob
> >
> >
> > On 7/14/06, Michael Mol <mikemol at gmail.com> wrote:
> > > I'll put together a presentation on it.  It's not difficult, just time
> > > consuming if one doesn't know which kernel options to choose.
> > >
> > > Question...is your 3c59x driver listed in /etc/modules?
> > >
> > > On 7/14/06, Bob Kline <bob.kline at gmail.com> wrote:
> > > > Not an option in that I know how to do
> > > > it off hand.  For us lower level users,  this
> > > > might be another useful topic to confront
> > > > if/when the group every has another install
> > > > getogether.
> > > >
> > > >    -Bob
> > > >
> > > >
> > > > On 7/14/06, Michael Mol <mikemol at gmail.com> wrote:
> > > > > (Sorry about not responding sooner)
> > > > >
> > > > > If the 3c59x driver isn't loaded until after you run the configuration
> > > > > software, then it's not getting loaded on bootup.  I would bet that's
> > > > > why the script can't find the hardware.
> > > > >
> > > > > For Mandriva, I'm not sure how to force the module to load during
> > > > > bootup, outside of compiling it into the kernel.  Is that an option?
> > > > >
> > > > > On 7/13/06, Bob Kline <bob.kline at gmail.com> wrote:
> > > > > > During boot I see something called "forcedeth,"
> > > > > > and then the statement that the hardware does
> > > > > > not seem to be present.
> > > > > >
> > > > > > Something's not meshing.  Whatever detects
> > > > > > the hardware does not seem to execute during
> > > > > > boot,  but must run during install,  and also
> > > > > > using the manual effort later on.
> > > > > >
> > > > > >    -Bob
> > > > > >
> > > > > >
> > > > > > On 7/13/06, Michael Mol <mikemol at gmail.com> wrote:
> > > > > > > Are you running HAL or udev?  Both can run scripts when they detect hardware.
> > > > > > >
> > > > > > > On 7/13/06, Bob Kline <bob.kline at gmail.com> wrote:
> > > > > > > > The scenario is that I set up Linux
> > > > > > > > on one machine,  and later move the hard
> > > > > > > > drive to another,  with a different set
> > > > > > > > of hardware.  Mostly this worked just
> > > > > > > > fine.  A tweak here and there.
> > > > > > > >
> > > > > > > > The one snag has been the Ethernet
> > > > > > > > ports.  Each time I boot up I have to
> > > > > > > > go through the same routine of running
> > > > > > > > a config script to set one of them up
> > > > > > > > again.
> > > > > > > >
> > > > > > > > How do I get the appropriate files updated
> > > > > > > > now,  as they would be during a first install,
> > > > > > > > so the configuration is there again the
> > > > > > > > next time I boot,  and the Ethernet ports
> > > > > > > > function?
> > > > > > > >
> > > > > > > >   -Bob
> > > > > > > > _______________________________________________
> > > > > > > > grlug mailing list
> > > > > > > > grlug at grlug.org
> > > > > > > > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > :wq
> > > > > > > _______________________________________________
> > > > > > > grlug mailing list
> > > > > > > grlug at grlug.org
> > > > > > > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> > > > > > >
> > > > > > _______________________________________________
> > > > > > grlug mailing list
> > > > > > grlug at grlug.org
> > > > > > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > :wq
> > > > > _______________________________________________
> > > > > grlug mailing list
> > > > > grlug at grlug.org
> > > > > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> > > > >
> > > > _______________________________________________
> > > > grlug mailing list
> > > > grlug at grlug.org
> > > > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> > > >
> > >
> > >
> > > --
> > > :wq
> > > _______________________________________________
> > > grlug mailing list
> > > grlug at grlug.org
> > > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> > >
> > _______________________________________________
> > grlug mailing list
> > grlug at grlug.org
> > http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
> >
>
>
> --
> :wq
> _______________________________________________
> grlug mailing list
> grlug at grlug.org
> http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug
>


More information about the grlug mailing list