I recall hearing something about that. I don't think this is the problem,
though, because I've used this exact same .config file to compile a kernel on
2.4.20 and later kernels and they worked great. Now, with Debian woody, I'm
trying to run 2.4.18, so the same driver I selected before should still work.
One question: are the old/arcane kernel options that dhcpclient requires in
the 2.4.18 kernel or have they been pulled out? Maybe, instead of switching
to pump from dhcpclient, I could use them if available.
On Friday 03 October 2003 10:50 am, you wrote:
> On Thursday 02 October 2003 09:56 pm, Eric Jahn wrote:
> > computer for many kernels. lsmod says both kernels have the same
> > eepro100 module loaded when they are running, and DHCP loads on boot for
> > both. When I boot from the one installed by Debian, I can ping out.
> > However when I boot from the one I compiled, I can't ping out.
>
> This could be a case of there being two separate drivers for the
> EtherExpressPro/100 cards in the newer kernels -
> the original Becker driver and the (newer) Alternate Intel Driver.
> I have found on a few systems and when using a newer kernel (2.4 vs. the
> stock 2.2), I had to use the Alternate Intel Driver to get the NIC
> recognized and working properly.
> Try loading ee100 instead of eepro100
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:50:06 EDT