From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 10 Jun 2003 - 00:30:36 BST
Hi Mike!
On Mon, Jun 09, 2003 at 02:30:07PM -0400, Mike Savage wrote:
> > both drivers are usually available, one from intel
> > called e100, and the other from D.Becker called eepro100 ...
>
> > I would prefer the intel driver, because it is actively maintained ...
>
> Both drivers are available under the RedHat kernel, this is true. I too
> agree that the Intel version, e100.o, should be the preferred version.
> Seems that RedHat is in agreement as well, as that is what they aliased to
> eth0 in his modules.conf at install time.
>
> However, the Intel e100.o driver is not present in the kernel-2.4.20ctx-17
> kernel supplied at ftp://ftp.solucorp.qc.ca/pub/vserver/ , which is what Mr.
> Chung indicated that he had installed.
that might easily be ... (read: I didn't check it)
> I wonder if we could have a copy of the .config file used for compiling the
> official vserver kernel included in the version released in the future, ie.
> Copy .config to the /boot directory as config-2.4.20ctx-17 for example,
> before packaging the tarball or RPM? This would make things ideal for those
> of us who wish to have as close to the official release configuration as
> possible, while still allowing us to quickly enable one or two extra modules
> before we recompile. Any thoughts? I know I would appreciate it.
hmm, last time I checked, Jacques server was up *G*
and the config files present ...
ftp://ftp.solucorp.qc.ca/pub/vserver
> >> Dual booting between the stock RedHat kernel and the vserver kernel
> >> would require some additional finesse in order to get your NIC to work
> >> without intervention at boot time.
>
> > hmm, not if you compile the eepro100 into the kernel
>
> ...which I would define as additional finesse, because it involves more than
> a simple one line config file edit.
depends, usually changing the 'm' to an 'y' suffices ...
CONFIG_EEPRO100=m
CONFIG_EEPRO100=y
best,
Herbert
> Regards,
> Mike
>
> -----Original Message-----
> From: Herbert Poetzl [mailto:herbert_at_13thfloor.at]
> Sent: Monday, June 09, 2003 11:37 AM
> To: vserver_at_solucorp.qc.ca
> Subject: Re: Re[2]: [vserver] eth0 fail to start
>
>
> On Mon, Jun 09, 2003 at 09:33:04AM -0400, Mike Savage wrote:
> > The RedHat-supplied kernel employs the Intel version of the driver,
> > e100.0, for your NIC. The vanilla kernel, which the vserver is most
> > like as no modules/drivers patches are applied against it AFAIK,
> > supplies the original open source driver, eepro100.o, by Donald
> > Becker.
>
> both drivers are usually available, one from intel
> called e100, and the other from D.Becker called eepro100 ...
>
> I would prefer the intel driver, because it is actively maintained ...
>
> > So, change this line...
> >
> > alias eth0 e100
> >
> > To this...
> >
> > alias eth0 eepro100
> >
> > ...in /etc/modules.conf if you are always going to boot into your
> > vserver kernel.
> >
> > Dual booting between the stock RedHat kernel and the vserver kernel
> > would require some additional finesse in order to get your NIC to work
> > without intervention at boot time.
>
> hmm, not if you compile the eepro100 into the kernel
> (which means not as module)
>
> best,
> Herbert
>
> > Hope that helps,
> > Mike
> >
> > -----Original Message-----
> > From: Joseph S Chung [mailto:jschung_at_itsd.gov.hk]
> > Sent: Friday, June 06, 2003 10:21 PM
> > To: vserver_at_solucorp.qc.ca
> > Subject: RE: Re[2]: [vserver] eth0 fail to start
> >
> >
> >
> > Please find /etc/modules.conf below...
> > ==============================================
> > alias eth0 e100
> > alias usb-controller usb-uhci
> > alias sound-slot-0 es1370
> > post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L
> > >/dev/null 2>&1 || :
> > pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S
> >/dev/null
> > 2>&1 || :
> > ==============================================
> >
> > Thanks,
> > Joseph
> >
> >
> >
> >
> >
> > From: Mike Savage <Mike.Savage_at_datastream.net> on 06/06/2003 21:40
> > Please respond to vserver_at_solucorp.qc.ca
> > To: "'vserver_at_solucorp.qc.ca'" <vserver_at_solucorp.qc.ca>
> > cc:
> > Subject: RE: Re[2]: [vserver] eth0 fail to start
> >
> >
> >
> >
> > What does the contents of your /etc/modules.conf file look like?
> >
> > -----Original Message-----
> > From: Joseph S Chung [mailto:jschung_at_itsd.gov.hk]
> > Sent: Thursday, June 05, 2003 11:03 PM
> > To: vserver_at_solucorp.qc.ca
> > Subject: Re[2]: [vserver] eth0 fail to start
> >
> >
> >
> > I do not see eth0 with ifconfig command. It is not working.
> > I did not complie the kernel after downloading from web. How can I get
> > the .config file. I do not have one in /usr/src/linux-2.4. By the way,
> > I am using RedHat 9.0. Thanks. Joseph
> >
> >
> >
> >
> >
> > From: Guillaume Plessis <gui_at_moolfreet.com> on 05/06/2003 18:07 Please
> > respond to vserver_at_solucorp.qc.ca
> > To: vserver_at_solucorp.qc.ca
> > cc:
> > Subject: Re: [vserver] eth0 fail to start
> >
> >
> >
> >
> > Joseph S Chung wrote:
> > > I am not sure. It is Intel 82557/8/9 Ethernet Pro 100. How can I
> > > check? Thanks, Joseph
> >
> > There are many way do to this :
> >
> > 1/ Check that the following options are marked "=y" or "=m" in the
> > .config file used during your kernel compilation: CONFIG_NET_PCI
> > CONFIG_EEPRO100 in case of "=m", you ahve to check that the modules is
> > loaded during the system boot
> >
> > 2/ check that you get eth0 when you lauch "ifconfig -a"
> >
> > 3/ ...
> >
> > Best regards
> >
> > Gui
> >
> >
> >
> >
> >
> >