From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Andrew Morton <akpm@digeo.com>
Cc: jamagallon@able.es, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3c59x gives HWaddr FF:FF:...
Date: 29 Mar 2003 02:23:17 +0100 [thread overview]
Message-ID: <1048900997.597.19.camel@teapot> (raw)
In-Reply-To: <20030328164419.0fe82430.akpm@digeo.com>
On Sat, 2003-03-29 at 01:44, Andrew Morton wrote:
> > I had exactly the same issue as you, but this time it was on my laptop
> > when using a 3CCFE575CT CardBus 10/100 NIC.
>
> Don't think so. You were getting 0xff when reading all PCI registers. In
> this case it is only the MAC address (which comes from an external eeprom)
> which is coming up as 0xff.
Nah! The problem I described in this mail happened a long, long time ago
(in a galaxy far, far away) and was exactly a "no command response"
(IIRC) error logged continuously to the console. Now, the problem I'm
experiencing is the slowdown-when-sending you may have read about which,
unfortunately, doesn't throw any kind of errors to the console ;-)
Thanks for your support, Andrew.
________________________________________________________________________
Felipe Alfaro Solana
Linux Registered User #287198
http://counter.li.org
next prev parent reply other threads:[~2003-03-29 1:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 14:51 3c59x gives HWaddr FF:FF: J.A. Magallon
2003-03-28 15:57 ` Eric Weigle
2003-03-28 20:48 ` Andrew Morton
2003-03-28 23:05 ` J.A. Magallon
2003-03-28 23:16 ` Andrew Morton
2003-03-29 0:46 ` J.A. Magallon
2003-03-29 17:12 ` Thomas Backlund
2003-03-29 19:45 ` Felipe Alfaro Solana
2003-03-30 2:21 ` Juan Quintela
2003-03-30 10:19 ` Felipe Alfaro Solana
2003-03-30 10:53 ` Thomas Backlund
2003-03-30 11:16 ` Felipe Alfaro Solana
2003-03-31 19:09 ` Bas Vermeulen
2003-03-29 0:29 ` Felipe Alfaro Solana
2003-03-29 0:44 ` Andrew Morton
2003-03-29 1:23 ` Felipe Alfaro Solana [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-28 16:13 Alex Davis
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=1048900997.597.19.camel@teapot \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@digeo.com \
--cc=jamagallon@able.es \
--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 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.