From: Andrew Morton <akpm@osdl.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: nico-kernel@schottelius.org, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org
Subject: Re: 3c59x problem with 2.4.6-test[34]
Date: Fri, 24 Oct 2003 13:24:03 -0700 [thread overview]
Message-ID: <20031024132403.2d574e3f.akpm@osdl.org> (raw)
In-Reply-To: <20031024195243.GB985@ip68-0-152-218.tc.ph.cox.net>
Tom Rini <trini@kernel.crashing.org> wrote:
>
> On Fri, Oct 24, 2003 at 12:43:56PM -0700, Andrew Morton wrote:
> > Tom Rini <trini@kernel.crashing.org> wrote:
> > >
> > > Okay. First an odd part. When the card does not work, I didn't get
> > > anything in the syslog with debug=7, but I did get plenty when it works.
> >
> > Well that's a big hint. If no debug output comes out then the driver
> > simply isn't being executed. You'll need to investigate and report on this
> > further. Make sure that you've set `dmesg -n 7' of course...
>
> >From the original message, something is happening:
> Sep 6 18:13:57 opus kernel: 0000:00:0e.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xe480. Vers LK1.1.19
> Sep 6 18:13:57 opus vmunix: ***WARNING*** No MII transceivers found!
>
Oh, OK, I didn't look at your initial message closely enough.
Every register is coming up with 0xff, so the NIC isn't powered up. There
have been a couple of reports of this.
I don't know why this has changed from 2.4. Suggest you try disabling (or
enabling) ACPI, and see if there are any BIOS settings which might affect
this.
next prev parent reply other threads:[~2003-10-24 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-07 21:23 3c59x problem with 2.4.6-test[34] Tom Rini
2003-09-29 15:18 ` Tom Rini
2003-10-15 18:35 ` Tom Rini
2003-10-17 23:53 ` Tom Rini
2003-10-18 12:27 ` Nico Schottelius
2003-10-18 11:14 ` Andrew Morton
2003-10-24 19:34 ` Tom Rini
2003-10-24 19:43 ` Andrew Morton
2003-10-24 19:52 ` Tom Rini
2003-10-24 20:24 ` Andrew Morton [this message]
2003-10-24 22:01 ` Tom Rini
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=20031024132403.2d574e3f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=nico-kernel@schottelius.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.