I was just playing around with it tonight and I added a realtek card and disabled the intels just to see what the result would be and sure enough it has the exact same problem. So now I guessing that rather than an intel problem, it's more of a kernel problem. I know other people on the net have had similar issues but I haven't found anyone that found a solution. I actually tried recompiling the kernel with that -ac patch... talk about errors. There were hundreds, so I'm thinking that's a no-go.
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. I do have an identical spare processor lying around I can put in to test but it comes out of a machine I had planned for something else. Might be worth a shot I guess. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Benjamin Scott Sent: Monday, January 07, 2002 8:39 PM To: Greater NH Linux Users' Group Subject: Re: 2.4.17 eepro module problem On Sun, 6 Jan 2002, Rob Round wrote: > The NIC's recognize ok and the eepro100 module is loaded however, I > can't get any traffic though the card ... You might try Intel's site. Intel actually does provide some native Linux drivers, complete with source, that work better (or worse, YMMV) than the ones in the mainstream kernel. Also try <http://www.scyld.com>. Scyld employs Donald Becker, who is *the* Linux network adapter driver guy. There is often good information and/or driver updates to be found there. Be aware that just about every NIC Intel makes is called an "EtherPro 100". One often has to read part numbers off chips to accomplish positive identification. > The only thing I could find was a document that said to recompile the > kernel without the IO-APIC option but my kernel didn't have that module > loaded. Not every kernel compile option is a module. In particular, IO-APIC support is not. APIC = Advanced Programmable Interrupt Controller, and it is very low-level, so it affects the entire kernel. Support for IO-APIC is required for SMP, but you can have IO-APIC without SMP. Try booting a uni-processor kernel to see if that makes the problems go away. Since you only have one processor anyway, the SMP support is not gaining you anything, and in fact adds overhead which might slow things down. FWIW, I have seen various weird problems for SMP boards with only a single processor. In at least one case, the system locked *hard* (power-cycle required) if the network interface was brought down. Hope this helps, -- 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. *****************************************************************
