Yup, I was compiling from source.  I'll take your advice and try a vanilla
config and see if I can get it going.  When I looked again, smp was enabled
but IO-APIC wasn't.  Not quite sure what that means.  Anyway, I'm
recompiling with SMP disabled and if that doesn't do the trick, I'll try
your suggestion.  As far as the compiler goes, I'm just using the default
that comes with Redhat 7.2 (I'm not sure which one it's using without
checking) and the source is from the RH 7.2 CD (downloaded from iso).

Thanks for your help with this... it's been driving me nuts.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Benjamin Scott
Sent: Monday, January 07, 2002 9:35 PM
To: Greater NH Linux Users' Group
Subject: RE: 2.4.17 eepro module problem


On Mon, 7 Jan 2002, Rob Round wrote:
> When I checked before, the IO-APIC options was not turned on so based on
> your email smp should also be disabled already, but I'll take a look
> anyway.

  Are you compiling your own kernel from source?

  If so, what compiler are you using?  Red Hat's "GCC 2.96" is notorious for
causing all sorts of weird problems.  Also, try reducing the kernel to a
"vanilla" configuration -- no SMP, no APIC, no APM, i386 target, and so on.

  If not, try compiling from source.  Pristine source, if at all possible.

--
Ben Scott <[EMAIL PROTECTED]>
| The opinions expressed in this message are those of the author and do not
|
| necessarily represent the views or policy of any other person, entity or
|
| organization.  All information is provided without warranty of any kind.
|


*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************


*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************

Reply via email to