From: Andrew Morton <andrewm@uow.edu.au>
To: Christian Loth <chris@gidayu.max.uni-duisburg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: DHCP Problems with 3com 3c905C Tornado
Date: Thu, 04 Jan 2001 23:59:11 +1100 [thread overview]
Message-ID: <3A54739F.FB8D6F3D@uow.edu.au> (raw)
In-Reply-To: <20010104123139.A15097@gidayu.max.uni-duisburg.de> <3A546F8E.ABF952F@uow.edu.au>, <3A546F8E.ABF952F@uow.edu.au>; from andrewm@uow.edu.au on Thu, Jan 04, 2001 at 11:41:50PM +1100 <20010104134315.C15097@gidayu.max.uni-duisburg.de>
Christian Loth wrote:
>
> >
> > Did _both_ 3c90x and 3c59x fail, or only 3c59x?
> >
>
> Both did not work. And 3c59x from 2.2.18 didn't work
> as well, and as far as I could judge 3c90x is not included
> in the kernel proper, right?
Now that is wierd. They're radically different drivers,
and the 3com one doesn't seem to undergo many changes at
all.
I wonder if the PCI scan order may have changed. What
other PCI devices did you have in that machine? Any other
NICs?
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-04 12:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 11:31 Christian Loth
2001-01-04 12:41 ` Andrew Morton
2001-01-04 12:43 ` Christian Loth
2001-01-04 12:59 ` Andrew Morton [this message]
2001-01-04 13:19 ` Christian Loth
2001-01-04 16:01 ` Arjan van de Ven
2001-01-04 17:25 ` Christian Loth
2001-01-04 19:07 ` idalton
2001-01-07 13:42 ` Andrew Morton
2001-01-08 7:02 ` Tim Wright
2001-01-08 9:12 ` Andrew Morton
2001-01-08 9:13 ` David Ford
2001-01-08 11:56 ` Alan Cox
2001-01-08 12:53 ` Andrew Morton
2001-01-08 13:10 ` Christian Loth
2001-01-04 13:11 Ingo T. Storm
2001-01-04 13:23 ` Christian Loth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A54739F.FB8D6F3D@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=chris@gidayu.max.uni-duisburg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®