Intel PRO/1000 Gigabit Ethernet Adapters working !

[Brecht Vermeulen]

oh yes, shame on me !

indeed, if I install another click configuration which doesn't refer to
the e1000 driver, the unloading is perfect.
(well, I had to ifconfig down to make the e1000 module be unused, then
in fact, click should put 'module in use' references on the e1000
driver, don't know if this is difficult to do).

I must have known this, sorry for bothering you.

Though, a notice about the -DHAVE_INTEL_CPU in the Makefile could be
useful.

(I believe I had trouble also with installing the click e1000 driver
after the official Intel driver when click then, of course, didn't made
use of these interfaces, however as Intel e1000 3.0.10 doesn't work with
me, I can't test this for now).

regards,
Brecht


Robert Morris wrote:
> 
> Are you unloading e1000 while click is loaded into the kernel?  If so,
> does the Click configuration refer (w/ To, From, or PollDevice) to the
> e1000 device?
> 
> > Date: Thu, 07 Jun 2001 18:06:46 +0200
> > From: Brecht Vermeulen <brecht.vermeulen at rug.ac.be>
> > To: click at amsterdam.lcs.mit.edu
> > Cc: Benjie Chen <benjie at amsterdam.lcs.mit.edu>
> > Subject: Intel PRO/1000 Gigabit Ethernet Adapters working !
> > References: <20010602105802.B9296 at amsterdam.lcs.mit.edu> <3B1A4E63.675D19B5 at rug.ac.be> <20010605084429.A2106 at amsterdam.lcs.mit.edu> <3B1E26AB.CFC2542E at rug.ac.be> <20010606100805.A17246 at amsterdam.lcs.mit.edu> <3B1E39E3.6422A869 at rug.ac.be> <20010606101354.A25422 at amsterdam.lcs.mit.edu> <3B1E3FB5.4B9D2ED6 at rug.ac.be> <20010606104932.A22054 at amsterdam.lcs.mit.edu> <3B1F50FB.9387FB2D at rug.ac.be> <20010607081607.A32672 at amsterdam.lcs.mit.edu>
> >
> >
> > Hi guys,
> >
> > our Intel PRO/1000 Gigabit Ethernet Adapters are finally working with
> > Click !
> >
> > There is a very strict initialisation series needed :
> >
> > -boot
> > -install the e1000.o module out of the click source code
> > -ifconfig up the interfaces
> > -install click configuration
> >
> > seems logical, but the following problems can occur :
> >
> > 1) if you unload the e1000 module, there is a kernel oops, after which
> > you have to reboot the machine or otherwise it will not work (this
> > happens both with the click e1000.o and the Intel e1000.o, the latter I
> > can't check anymore as the version 3.0.10 causes a kernel panic after
> > the first ping).
> > --> so if you test and load and unload the module, it will not work...
> > Do you see these same kernel oopses ?
> >
> > 2) we have no Intel CPU, so in the Makefile, we had to remove
> > -DHAVE_INTEL_CPU for the e1000 driver, otherwise, yes, a kernel oops.
> >
> > 3) Our machine was booted every time by a working e1000.o driver from
> > Intel (a previous version) which I unloaded to load the click one, and
> > of course each time a kernel oops...
> >
> > sorry for all the noise (especially to Benjie),
> > maybe this info can be added in a README file in the e1000 dir ? (or of
> > course, fix the unloading :-) if you can reproduce it).
> >
> > best regards,
> > Brecht