[tulip-bug] ether= option on the kernel command line

Florian Wunderlich fwunderlich@devbrain.de
Fri, 03 Aug 2001 12:19:26 +0200


Thanks for your quick reply.

I assumed that the driver in the 2.4 kernels is the same as your tulip
driver, because you are saying on
http://www.scyld.com/network/tulip.html that "It has been integrated
with the kernel source tree since 1.1.90". Obviously the tulip driver in
2.4.7 (what I am using) at least is not yours. You might want to change
your page.


Donald Becker wrote:
> 
> On Fri, 3 Aug 2001, Florian Wunderlich wrote:
> 
> > Because of the media type autoselect bug (see below), I want to force
> > the compiled-in tulip driver to use a specific media type; according to
> > http://www.scyld.com/network/tulip.html, I have to pass
> > ether=0,0,media-type,eth0, which does not seem to work.
> 
> ...or you can use 'mii-diag -F <type>' with a current driver.
> 
> > I tried ether=0,0,5,eth0 on an append line in /etc/lilo.conf and on the
> > lilo boot prompt, and /proc/cmdline shows that it was correctly parsed,
> > but the tulip driver seems to ignore it. When built as a module it works
> > fine when using options=5.
> 
> What driver are you using?
> 
> > What I assume is an autoselect bug has already been reported by a number
> > of people:
> > http://sourceforge.net/tracker/index.php?func=detail&aid=432622&group_id=13004&atid=113004
> > http://www.geocrawler.com/archives/3/6977/2001/6/0/5904481/
> > http://sourceforge.net/tracker/index.php?func=detail&aid=430617&group_id=13004&atid=113004
> > http://sourceforge.net/tracker/index.php?func=detail&aid=425571&group_id=13004&atid=113004
> 
> These are all different problems.
> 
> Donald Becker                           becker@scyld.com
> Scyld Computing Corporation             http://www.scyld.com
> 410 Severn Ave. Suite 210               Second Generation Beowulf Clusters
> Annapolis MD 21403                      410-990-9993